Re: fetchmail expunge error
Hans Carlson <[email protected]>
| Newsgroups | gmane.mail.fetchmail.user |
|---|---|
| Message-ID | <alpine.LFD.2.02.2104251324590.8311@xippy> |
On Sun, 25 Apr 2021, Gerard E. Seibert wrote: > On Sun, 25 Apr 2021 12:24:06 -0500, Leslie Rhorer stated: > >> In any case, I can now login using the IMAP protocol, but fetchmail >> can only download a single message at a time, producing a mail expunge >> mismatch error (0 actual != 1 expected) and exiting after each message. >> Eventually, it does manage to get all the messages, but typically only >> after a very long time, whenever several messages come in over a short >> time frame. While not quite critical, this is definitely not good. >> >> Is anyone else having this issue with AT&T? How can I fix it? > > Both YAHOO and AOL exhibit the same problem. Most MUAs simply ignore the > problem. Fetchmail has taken a more stringent approach. Yup... same problem here with YAHOO. I asked the same question about a year ago and Matthias said this is due to a broken server. See thread here: https://sourceforge.net/p/fetchmail/mailman/fetchmail-users/thread/alpine.LFD.2.02.2005041620590.1519%40xippy/#msg37003167 Unfortunately, getting someone like YAHOO to fix their server is next to impossible. Calling "support" results in clueless (fictionalized) exchanges like the following: Me: <DIAL>...<LONG WAIT ON HOLD> Support: YAHOO tech support. How can I help? Me: It looks like the YAHOO mail server isn't behaving correctly to the IMAP STORE command. Support: <PAUSE> Have you tried to reboot Windows? Me: I'm not using Windows, I'm using Linux. Support: Linux? I don't know what that is. We only support Windows. Me: It shouldn't matter, the problem is with the mail server. Support: <LONG PAUSE> Have you tried to reboot Windows? Me: <SIGH> Never Mind. Support: Is there anything else I can help you with? Me: Nope. Thanks. <CLICK> To be clear... I don't recall if I actually called YAHOO support last year or not. I may have. But based on previous calls to support, I suspect this was the type of exchange I would have had. It might be possible to eventually get to someone with enough knowledge to at least understand the problem, but getting them to fix it would probably be a different story. Actually, I wonder if it might be the case that YAHOO (et al) is unwilling to fix their servers because so many (major) MUAs depend on the current broken behavior. I have no idea if that's the true or not, just speculating.