Re: [Fetchmail-users] mail expunge mismatch (0 actual != 1 expected)

[Jerry <je...@se...>]

On Tue, 25 Jun 2019 09:39:49 -0400, Gene Heskett stated:
>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 XX...@ai... at imap.aim.com.
>> fetchmail: reading message
>> XX...@ai...@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
>> XX...@ai...@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


I have logged in with a browser and cleaned out every thing I could
find. Actually, there were no emails or Spam shown in any folders. I
did the run twice to insure it was completely sanitized. Unfortunately,
the problem still exists. My next move is to try and contact technical
support at AOL and see what they have to say. I know it is a waste of
time because either,

1) I will never get to actually speak to a rep
2) They will inevitably blame it on me.

-- 
Jerry