Ian Callahan <icalla(_at_)bigpond(_dot_)net(_dot_)au>:
This has been previously reported by, at least, Mark Bergman
<bergman(_at_)panix(_dot_)com> (07feb2001) and Chip Salzenberg
<chip(_at_)valinux(_dot_)com>,
but since there doesn't appear to have been any resolution posted, I
thought I would try again. I can add a little more information to the
previous postings.
I previously had fetchmail 4.5.8 running without trouble on a 486
running RedHat Linux 5.2, and fetching from 2 ISP's POP3 servers. The
486 karked it, so I tried to move the mail onto the firewall, a 486
running RedHat 6.2, fetchmail 5.3.1.
I found exactly the same symptoms as reported by Mark, except that I
have not yet tried removing the first message from the server. To
reiterate those symptoms:
restarting fetchmail doesn't help
changing timeout doesn't help
it appears that headers are sent, then fetchmail times out waiting for
body
Netscape & kmail can read all messages just fine
The network and firewall configurations are unchanged from when
fetchmail was running on the RH 5.2 machine.
Downgrading fetchmail from 5.3.1 to 4.5.8 (the previously working
version) didn't help, but fetchmail reported a stupid number in its
timeout message, and took a lot longer to time out. (5.3.1 reports 0
seconds, but appears to actually wait for the correct timeout period).
Upgrading to fetchmail 5.7.0 is not practical at this time, but will
eventually happen in conjunction with a Linux upgrade.
Any ideas?
Is this bug deterministic, that is does it repeat every time with a
particular message? And if so, can you send me a copy of the message?
(It looks like it might be related to the message having oversized
headers.)
--
<a href="http://www.tuxedo.org/~esr/";>Eric S. Raymond</a>
The IRS has become morally corrupted by the enormous power which we in
Congress have unwisely entrusted to it. Too often it acts like a
Gestapo preying upon defenseless citizens.
-- Senator Edward V. Long