Re: mail expunge mismatch (0 actual != 1 expected)

On Tuesday 25 June 2019 06:54:06 Jerry wrote:

> fetchmail release 6.3.26+RPA+SDPS+SSL-SSLv2-SSLv3+OPIE+NLS
> FreeBSD 12.0-RELEASE-p6 GENERIC  amd64
>
> The following entries have started appearing in my fetchmail log file:
>
> fetchmail: 1 message for [email protected] at imap.aim.com.
> fetchmail: reading message
> [email protected]@internal-aol.imap.mail.g03.yahoodns.net:1 of 1 (4137
> header octets) (54943 body octets) flushed fetchmail: mail expunge
> mismatch (0 actual != 1 expected)
> fetchmail: client/server synchronization error while fetching from
> [email protected]@imap.aim.com fetchmail: Query status=7 (ERROR)
>
> This appears every time fetchmail runs. It had worked correctly
> previously and there have been no changes to the system that I am
> aware of. I visited the site and deleted any files that were present.
> At that time, there were none.
>
> Can any one tell me what is causing this problem? It appears to be
> localized to AOL.
>
> Thanks!

Some ISP's are serving their imap using customers from the same 
filesystem that also serves up pop3 to fetchmail, and because the 
customer may switch depending on the machine, they have disabled the 
fetchmail issued DELE.  So I log in with a browser and use it to clean 
house at the ISP.  Sounds like AOL has figured out yet another way to 
annoy their pop3 customers with phony error msgs.

I use fetchmail with kmail here, and kmail will occasionally get its 
indices out of synch, so I had to use t-bird in imap mode for about a 
day, and boy did I get an education on how NOT to do email. I suppose 
one could learn to live with it, but imap=spit to me.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>