"MA" == Matthias Andree
<ma(_at_)dt(_dot_)e-technik(_dot_)uni-dortmund(_dot_)de> writes:
> Joseph Barillari <joseph+fetchmail(_at_)barillari(_dot_)org> writes:
>> I think I've found a bug in fetchmail: while retrieving
>> messages with certain headers, it hangs. Unusually enough, it
>> only does so when SSL is enabled. Disabling SSL or changing the
>> headers (by editing the message on the IMAP server with
>> Mutt)[0] eliminates the lockup.
> Even though you don't reproduce the problem with mutt, so it may
> indeed be a fetchmail issue:
> Can you check (with netstat or lsof) if the actual connection to
> the server is still in "ESTABLISHED" state? I fixed SSL related
> bugs (infinite loop stuff) some patchlevels ago, and the fixes
> cured MY problem.
It appears to be established:
tcp 0 0 washer.barillari.o:3364 mmp.Princeton.EDU:imaps ESTABLISHED
...this is with all of the other IMAP clients closed and
fetchmail hanging.
> The other interesting thing might be what commands mutt or
> fetchmail use to pull the mail from the server. Only if they
> send the same command sequence, we can be confident it's not a
> server bug for now.
Is there an easy way to record that sequence without resorting to
tcpdump? It's an imap-ssl link so using a network-level tool like
tcpdump would be non-trivial. I assume I could use a null cipher, but
that might change the dynamics of the problem.
Thanks,
--Joe