Re: [Fetchmail-users] sometime in the night, fetchmail 6.5.0beta6 heard a bump

[Matthias A. <mat...@gm...>]

Am 05.11.21 um 17:52 schrieb Gene Heskett:
> Greetings Mathias;
>
> The bump was a msg that landed in the inbox at imap.shentel.net. no
> subject, no body, no from address, from the debian listmail server.
> at about 6:53 EDT.
>
> That convinced fetchmail it had an error 7, and exited that invocation
> without fetching any more msgs.  Wash, rinse and repeat at 2 minute
> intervals till shentel and I figured it out a few seconds after the
> log entry below.
>
> log looked like this:
>
> ov 05 11:42:32 fetchmail: 54 messages for ghe...@sh... at imap.shentel.net.
> Nov 05 11:42:33 fetchmail: reading message ghe...@sh...@imap.shentel.mail2world.com:1 of 54 (2182 header octets) (log message
> incomplete)
> Nov 05 11:42:33 fetchmail: client/server synchronization error while fetching from ghe...@sh...@imap.shentel.net
> Nov 05 11:42:33 fetchmail: Query status=7 (ERROR)
>
> I finally logged into the webmail, saw that funky msg and deleted it,
> which unplugged the drain  and it fetched the other 53 msgs ok.
>
> Unforch the log is all I could salvage. Is this helpfull?

Hi Gene,

thanks for the report. Unfortunately, this log does not suffice to check
where fetchmail failed - I would need to see a verbose log with at least
one -v (or possibly -vv if you can spare the disk logging space).

I know fetchmail lacks some parser support for edge cases like yours.

Cheers,
Matthias