Re: Gmail pop3 failing since yesterday
[email protected] (Tory S. Anderson)
| Newsgroups | gmane.mail.getmail.user |
|---|---|
| Message-ID | <[email protected]> |
In my case, still using pop3, it turns out it was some invalid message (I still don't know what makes a message invalid). I fixed it by having getmail skip the breaking messages, which I found one-at-a-time. There were apparently 3 of them amid my 400-message backlog. Details blogged here: https://tech.toryanderson.com/2020/04/19/gmail-pop3-suddenly-broken-for-getmail/ Volker Wysk <[email protected]> writes: > Am Montag, den 20.04.2020, 13:00 -0600 schrieb Charles Cazabon: >> Tory S. Anderson <[email protected]> wrote: >> > Has anyone else experienced issues with gmail pop3 recently? I have >> > one of >> > my gmail addresses failing since yesterday, receiving the error >> > from >> > getgmail: >> [...] >> > > Retrieval error: server for >> > > SimplePOP3SSLRetriever:recent:<<myaddress>@[ >> > > [email protected]]:995 >> > > is broken; offered message GmailId1718e4039279f0fe but failed to >> > > provide >> > > it. Please notify the administrator of the server. Skipping >> > > message... >> >> This is a nonfatal error. getmail is warning you that the server - >> it can >> happen with POP3 or IMAP - included a message in the mailbox contents >> listing, >> but when getmail tried to actually retrieve that message, the server >> responded >> with "no such message with that ID". >> >> The server is broken. getmail will happily let you continue using >> it. If you >> can somehow convince the server to stop including the phantom message >> in its >> list of the messages in the mailbox, the error message will go >> away. Please >> contact your email provider for further help with this. > > The server isn't necessarily broken. I've had this problem with a > server (Dovecot) and TWO clients which both accessed the same mailbox. > Both tried to download messages with IMAP IDLE, but it should be the > same with POP3. It could happen that one downloaded and erased a > message while the other wasn't done with the same message. It's a race > condition. > > The problem went away when I deactivated one of the two listeners. > > The actual issue here is, that the IMAP protocol doesn't discriminate > non-existent message-IDs from expired message-IDs. > > Happy hacking, > Volker > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected]