Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 37732 - fetchmail segmentation fault
fetchmail segmentation fault
Product: Red Hat Linux
Classification: Retired
Component: fetchmail (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2001-04-26 02:39 EDT by Michael Schwendt
Modified: 2007-04-18 12:32 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-08-22 18:11:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michael Schwendt 2001-04-26 02:39:44 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.2-2 i686; en-US; rv:0.8.1+)

$ fetchmail -a pop.mail.yahoo.com
reading message 5 of 6 (3240 octets) ...fetchmail: message delimiter
found while scanning headers
Segmentation fault

$ telnet pop.mail.yahoo.com 110
+OK maildrop ready, 6 messages (22942 octets) (488754 6291456)
+OK 6 messages (22942 octets)
1 3001
2 5599
3 3502
4 4441
5 3240
6 3159
+OK 3240 octets
X-Apparently-To: mschwendt@yahoo.com via web6202.mail.yahoo.com
Return-Path: <

I've been able to reproduce this several times. After I had downloaded,
compiled, and installed fetchmail 5.8.0, I could not reproduce above
segfault. However, if Yahoo's POP3 server was in a bad condition only
temporarily, it could still be that 5.8.0 also causes a segfault the next
time a bad message is found. Maybe you find a related bug in the code.

Reproducible: Always
Steps to Reproduce:
Only while running version fetchmail 5.7.4 -- and as long as the damaged
message was on the server -- I was able to reproduce the bug always. Yes, I
know I should have kept the bad message on the server to be able to test
this further. :-(

Expected Results:  Fetchmail should not cause a segmentation fault, but
should skip the bad message and try downloading any subsequent messages.
Comment 1 Michael Schwendt 2001-04-26 02:42:45 EDT
This is a copy of the bug-report to Eric S. Raymond (fetchmail author).

Meanwhile, fetchmail 5.8.0 has dealt with a similar situation properly. It said
"message delimiter found while scanning headers" but didn't throw a segfault.

Comment 2 Michael Schwendt 2001-05-21 14:19:05 EDT
ESR's fetchmail 5.8.0-1 release throws a SegFault, too. It just needs an
incomplete message which is cut somewhere in the headers. Seems to happen now
and then with Yahoo Mail's POP3 server. ;-)

reading message 3 of 4 (2829 octets) ..fetchmail: message delimiter
found while scanning headers
Segmentation fault
Comment 3 Michael Schwendt 2001-07-26 07:07:32 EDT
Happily running 5.8.14 for quite some time by now without similar symptoms. Have
encountered a very few truncated/damaged mails only, though. I post this because
it happens usually that the bug occurs shortly after. :)

Seriously, this bug _could_ be related to the buffer overflow in the header
parser of all versions prior to 5.8.6 (bugtraq id 2877). But I'm not uptodate on
that one and what has been fixed.
Comment 4 Michael Schwendt 2001-08-22 18:10:56 EDT
Running without problems with 5.9.0 for some time (which is in Roswell 7.1.94
now, too).
Comment 5 Michael Schwendt 2001-09-10 23:07:28 EDT
As long as I don't get this failure again with the newer releases of fetchmail,
I consider this resolved.

Note You need to log in before you can comment on or make changes to this bug.