Simon
Justin MasonOh 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...
update on the POP3pocalypse. it appears that the most likely thing to work in the future will be to use SMTP forwarding to gmail with ARC headers added to the mails, going by comments on @jwz 's post at: https://www.jwz.org/blog/2025/12/today-in-google-broke-email-2/#comment-265285 , and it looks like there is a rather complex Postfix/OpenARC setup that may do the job. really looking forward to having to do this soon
Today in "Google broke email"
I have just learned that, beginning in 3 days, my employees will no longer be able to receive their work email. Apparently Google is dropping support for Gmail accounts being able to fetch mail from outside accounts. At all. And they announced this change less than 60 days ago. (The announcement was in the basement, stairs, leopard, etc.) What I want to accomplish is simple: When email ...
Waider
gwire
Nelson Minar@jmason Good god why would they turn that off.
@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
@jmason do they also support pulling mail via IMAP?
@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
Erwan 🚄
Todd Knarr
Scott EllisI 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.
@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.
Jon@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/
Dan Sugalski@nelson @jmason Because the code is getting old, it's a massive pain in the ass to keep running, and more and more remote servers have... questionable POP services.
Basically it's a lot of neverending support work on the back end with (frankly because of C-suite level bad decisions on staffing) fewer resources available to continue producing a neverending stream of band-aids.
@wordshaper @jmason bitrot I guess, ugh. Between this kind of integration failure and the difficulty of getting email delivered at all through spam filters, SMTP has long since stopped being a proper peer to peer system of equals and has been dominated by a hegemony. I recently switched to Google Apps for Your Domain just to get my email delivered.
@nelson @jmason Yep, absolutely bitrot. We have this habit of building systems, making them really solid, then de-staffing the project. A few years later things break, people notice, and we have to decide whether it's worth re-staffing the project or just killing it.
Also spammers. One of the other ginormous reason we can't have Nice Things is spammers. (I think, though have no direct knowledge, that this is also one of the reasons for us sunsetting third-party POP polling)
jwz@wordshaper @nelson @jmason "Because some people might be using this feature insecurely, we are removing the feature entirely without providing any alternative, secure or otherwise" is, while not a *surprising* move by Google, still a *deeply infuriating* one. https://mastodon.social/@jwz/115804789003343393
TiTiNoNero 
@jwz @nelson @jmason oh, I 100% won’t defend the timing, the time horizon, or the messaging. We’re handling this in our normal way, which is to say badly.
Given all the hassles and technical nightmares I’m not surprised we decided to kill this off, but we could and should have managed this very differently.
@wordshaper Do you know if they are actually turning off POP3 fetch on Jan 1, or if they're just removing the UI checkbox or something? Do I really only have 48 hours to solve this problem?
@jwz I honestly don't know what they're doing, and everyone I know to ask isn't around because of the holidays. Prod freeze ends midnight Jan 1 (so when Jan 1 rolls over to Jan 2) so that's the earliest it's likely to happen, but extremely cold comfort there.
I went looking for whoever wrote that *extremely* time-vague announcement for details (*when* in january? It's a whole month) but also no luck, given everyone's out for the holidays.
So... yeah. Check the origin POP accounts to be safe.
@wordshaper @jwz The really annoying thing about this is that I (and others) would pay actual $$/year for the POP3 fetch service to continue just as it is.
@jmason you still have imap ?
ghosttie
Bitslingers-R-Us@jmason IMAP is still an option, as is moving away from Google ;)