Justin MasonDec 29
Oh crap. Gmail is deprecating support for picking up mail from a remote server using POP3 polling in January 😭 Given that I switched to this mode due to reliability problems with direct delivery via mail forwarding, this really sucks...
Show threadNelson MinarDec 29
@jmason Good god why would they turn that off.
Show threadJustin MasonDec 29
@nelson I know! It had a very elderly no-js-just-html UI flow; I wouldn't be surprised if some kind of UI related dependency deprecation drove this
Show threadNelson Minar
@jmason do they also support pulling mail via IMAP?
Dec 29 at 3:26pmWeb
Show threadJustin MasonDec 29
@nelson no, I don't think so. There seems to be IMAP support in the mobile Gmail client? But it doesn't sound like it pulls to the real Gmail store
Show threadErwan 🚄Dec 29
@jmason @nelson I read email in Thunderbird through imap. Some strange things with folders (which are in reality tags thus mails are in several folders, and if you delete a mail in another folter than "all mail" it is not deleted...
Show threadTodd KnarrDec 29
@nelson @jmason They support IMAP. "Pulling" is just fetch and then delete from server. Most interactive clients don't do it, but things like fetchmail support it nicely.
Show threadTodd KnarrDec 29
@nelson @jmason Oh, having Gmail do the pulling. No, they don't support that on their side, but you can use fetchmail to pull from a remote and store in Gmail just as easily as the other way around.
Show threadNelson MinarDec 29
@tknarr @jmason one thing I appreciate using the Shortwave email client is Gmail has a robust third party API. But does fetchmail have a "store in Gmail" system using some Google-proprietary API? Or do you have to forward it with a mail agent via SMTP and hope Google accepts it?
Show threadScott EllisDec 30

@nelson @tknarr @jmason

I wrote https://github.com/ScottESanDiego/gmail-api-client to work around this, using exim and fetchmail to get things into #gmail . It's working REALLY WELL so far, with all the usual filters and stuff, just as when using #gmailify .

Problem is that it uses "restricted" API calls which means annual code security reviews which I'm not going to do ($$) OR renew the auth every seven days. My app is "in production" so the token isn't expiring, not sure what happens when I fail to do a code review.

GitHub - ScottESanDiego/gmail-api-client

Contribute to ScottESanDiego/gmail-api-client development by creating an account on GitHub.

GitHub
Show threadTodd KnarrDec 30
@ScottE @nelson @jmason Hmm. 'deliver' can take email on stdin and send it to an IMAP server. That would avoid having to use any Gmail APIs at all. Using it with the --mda option to fetchmail looks promising.
Show threadScott EllisDec 30
@tknarr @nelson @jmason Yeah, the benefit of IMAP is no restricted API calls, but the downside is no filtering on Google's side. You'd have to implement spam and other filters upstream with Sieve or something.
Show threadTodd KnarrDec 30
@ScottE @nelson @jmason This sounds like just going the Workspace route and having GMail be the mailserver for the domain would be simpler. I'm pretty sure Google's going to phase out access to GMail via any routes other than the Web interface and their APIs, simply to get advertising, analytics and AI integrated without giving people an out. They'd probably drop accepting inbound mail via SMTP if they could get away with it.
Show threadJonDec 29

@nelson @jmason after the nightmare that was fetchmail vs. Gmail OAUTH 2.0, I gave up and just forward gmail to my ISP account. But thankfully gmail was never anything other than a place to trap notifications from FB and that sort of crap I don't care about, anyway.

https://billauer.co.il/blog/2022/06/fetchmail-gmail-lsa-oauth2/

Fetchmail and Google’s OAuth 2.0 enforcement