Re: [fetchmail-devel] timeout not working for TLS

[Thomas J. <tho...@in...>]

On Thursday, 28. April 2011 13:18:59 Matthias Andree wrote:
> Looks like GMX.

Yes, 1&1 ;)

> what OS and version (distribution) does this happen on?  Do the
> -debuginfo packages match the actual RPMs?  Could you try building
> 6.3.19 from source and use that to somehow reproduce the hang?

It's our custom distribution which is based on Fedora.

I recovered the correct -debuginfo packages from the time I built the binary 
RPMs. If the debuginfo packages don't fit (f.e. glibc header changed),
gdb will skip those debug symbols with an CRC mismatch error.

> I wonder if the SSL stuff somehow masks the timeout alarm we're using,
> that could possibly explain things, but I don't have an idea how to
> figure that out yet.

It just came to my mind: We can simulate the situation with socat.
And I was able to trigger the problem. Try this:

- Start a "fake POP3 server" with socat: socat - tcp4-listen:110

- fetchmail connects to this server

- Paste the welcome greeting:
+OK POP fake server ready H mimap4

- fetchmail will reply with: "CAPA"

- Paste this:
+OK Capability list follows
TOP
USER
UIDL
STLS
SASL PLAIN
IMPLEMENTATION trinity
.

- fetchmail will reply: "STLS"

- Paste this:
+OK Begin TLS negotiation


Then do nothing in socat until the timeout should be triggered.

Hope that helps,
Thomas