Re: [fetchmail-users] IMAP problem (fetchmail 6.3.1-pre1)

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

Jason White <jas...@in...> writes:

> Dec 16 18:40:03 jdc fetchmail[13415]: IMAP> A0006 FETCH 1 RFC822.HEADER 
> Dec 16 18:40:03 jdc fetchmail[13415]: IMAP< * 1 FETCH (UID 16
> RFC822.HEADER {1360} 

Well, this tells fetchmail that 1360 bytes (octets) will
follow. Since this works for me with a Dovecot upstream server, I wonder
if it's really fetchmail's fault or perhaps SurgeMail's.

Could I possibly get a test mail account on that server to find out
which software is wrong?  If so, please send the IMAP server, mail
address (where I would send test messages), account and password or
other credentials off-list. The X-PGP-Key header mentions my GnuPG key
so encrypted communication is possible (and should be used).

If that is not possible, can you change your password, run ethereal,
tethereal or tcpdump -s5000 to capture to a file (the tcpdump filter
rule would be "host mail.internode.on.net and port 143"), run fetchmail
once, then change your password again and mail me the resulting tcpdump
or tethereal capture file? It contains the password, hence the hassle
with changing it. Looking at the tcpdump/tethereal dump should also give
us an idea which of the two sides miscounted the message size.

> Dec 16 18:40:33 jdc fetchmail[13415]: timeout after 30 seconds waiting for server mail.internode.on.net. 
> Dec 16 18:40:33 jdc fetchmail[13415]: socket error while fetching from jas...@ma... 

Thank you for retrying with 6.3.1-pre1 and reporting your problem.

-- 
Matthias Andree