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

Jerry <[email protected]>
Newsgroups gmane.mail.fetchmail.user
Organization seibercom.net
Message-ID <[email protected]>
On Sat, 6 Jul 2019 17:43:25 +0200, Matthias Andree stated:
>Am 28.06.19 um 00:07 schrieb Matthias Andree:
>> Am 25.06.19 um 12:54 schrieb Jerry:  
>>> 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!
>>>  
>> Jerry,
>>
>> as Ralph Corderoy asked, we need to see detailed logs, and for
>> instructions, please see
>> <http://www.fetchmail.info/fetchmail-FAQ.html#G3> to evaluate the
>> situation. Please provide them.
>>
>> Best regards,
>> Matthias  
>
>Jerry, any news?

Sorry, but I have been on vacation fr a week, I just checked the logs,
and that message sequence is still evident; however, no mail is being
lost, so I think it is just some sort of harmless error or warning
message.

If I get a chance in the next week or so, I will put fetchmail into
debug mode and see if I can isolate the problem.

I could probably set up another "dummy" account and see if it exhibits
the same problem. If it does, I could just give you access to it so you
could diagnose the problem yourself. That would probably be quicker.

-- 
Jerry
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.