Menu
▾
▴
[fetchmail-devel] [Bug #9449] Malformed headers causes segfault
|
From: <ad...@be...> - 2006-11-14 08:14:40
|
Bug #9449, was updated on 2006-Nov-13 22:10 Here is a current snapshot of the bug. Project: Community Fetchmail Category: None Status: Open Resolution: None Bug Group: None Priority: 5 Submitted by: dgersic Assigned to : none Summary: Malformed headers causes segfault Details: This is probably the same as the other two, but maybe it'll help you find the problem. Your operating system: Linux (SuSE 9.2 Pro) dgersic@linux:~> uname -a Linux linux 2.6.8-24.25-smp #1 SMP Thu Aug 24 09:57:32 UTC 2006 i686 i686 i386 GNU/Linux Your compiler version, if you built from source; otherwise, the name and origin of the RPM or other binary package you installed. fetchmail-6.5.3-1.i486.rpm downloaded from http://fetchmail.berlios.de on 11 November 2006. It was installed via SuSE's YaST installer for RPMs. Also installed were fetchmailconf-6.3.5-1.i486.rpm, rsaref-2.0-507.i586.rpm (for fetchmail), and python-tk-2.3.4-3.1.i586.rpm and blt-2.4z-204.1.i586.rpm (for fetchmailconf). A copy of your POP or IMAP server's greeting line. fetchmail: POP3< +OK myrealbox.com NetMail POP3 Agent $Revision: 1.6 $ The name and version of the SMTP listener or MDA you are forwarding to. I've configured Fetchmail to call Procmail directly, but I don't think that applies here. Procmail is procmail-3.22-40.4 Any command-line options you used. fetchmail --nodetach --verbose The output of fetchmail -V called with whatever other command-line options you used. Following the FAQ, I ran fetchmail --nodetach -vvv and got the output from it. Looks like it's having trouble with a header on a message (probably mangled spam). The end result is a segfault. /*----------------------------------------Begin-----------------------------------------------*/ dgersic@linux:~> fetchmail --nodetach -vvv fetchmail: removing stale lockfile fetchmail: starting fetchmail 6.3.5 daemon fetchmail: 6.3.5 querying mail.zaccaria-pinball.com (protocol POP3) at Mon 13 Nov 2006 11:53:31 PM CST: poll started fetchmail: Trying to connect to 64.202.165.92/110...connected. fetchmail: POP3< +OK <183...@po...> fetchmail: POP3> CAPA fetchmail: POP3< -ERR authorization first fetchmail: authorization first fetchmail: Repoll immediately on cp...@za...@pop.secureserver.net fetchmail: Trying to connect to 64.202.165.92/110...connected. fetchmail: POP3< +OK <140...@po...> fetchmail: POP3> USER cp...@za... fetchmail: POP3< +OK fetchmail: POP3> PASS * fetchmail: POP3< +OK fetchmail: selecting or re-polling default folder fetchmail: POP3> STAT fetchmail: POP3< +OK 0 0 fetchmail: No mail for cp...@za... at mail.zaccaria-pinball.com fetchmail: POP3> QUIT fetchmail: POP3< +OK fetchmail: 6.3.5 querying mail.zaccaria-pinball.com (protocol POP3) at Mon 13 Nov 2006 11:53:33 PM CST: poll completed fetchmail: not swapping UID lists, no UIDs seen this query fetchmail: Query status=1 (NOMAIL) fetchmail: 6.3.5 querying pop3.myrealbox.com (protocol POP3) at Mon 13 Nov 2006 11:53:33PM CST: poll started fetchmail: Trying to connect to 151.155.5.201/110...connected. fetchmail: POP3< +OK myrealbox.com NetMail POP3 Agent $Revision: 1.6 $ fetchmail: POP3> CAPA fetchmail: POP3< +OK fetchmail: POP3< TOP fetchmail: POP3< USER fetchmail: POP3< SASL LOGIN fetchmail: POP3< RESP-CODES fetchmail: POP3< PIPELINING fetchmail: POP3< EXPIRE NEVER fetchmail: POP3< UIDL fetchmail: POP3< STLS fetchmail: POP3< . fetchmail: POP3> STLS fetchmail: POP3< +OK Begin TLS negotiations fetchmail: Server certificate verification error: unable to get local issuer certificate fetchmail: Server certificate verification error: certificate not trusted fetchmail: Issuer Organization: Comodo Limited fetchmail: Issuer CommonName: Comodo Class 3 Security Services CA fetchmail: Server CommonName: *.myrealbox.com fetchmail: pop3.myrealbox.com key fingerprint: 20:B6:63:2B:E5:5D:46:10:B6:21:A6:05:7D:69:AE:4D fetchmail: pop3.myrealbox.com: opportunistic upgrade to TLS. fetchmail: POP3> CAPA fetchmail: POP3< +OK fetchmail: POP3< TOP fetchmail: POP3< USER fetchmail: POP3< SASL LOGIN fetchmail: POP3< RESP-CODES fetchmail: POP3< PIPELINING fetchmail: POP3< EXPIRE NEVER fetchmail: POP3< UIDL fetchmail: POP3< STLS fetchmail: POP3< . fetchmail: POP3> USER dgersic fetchmail: POP3< +OK Password required fetchmail: POP3> PASS * fetchmail: POP3< +OK fetchmail: selecting or re-polling default folder fetchmail: POP3> STAT fetchmail: POP3< +OK 3 21601 fetchmail: POP3> LAST fetchmail: POP3< +OK 0 fetchmail: 3 messages for dgersic at pop3.myrealbox.com (21601 octets). fetchmail: POP3> LIST 1 fetchmail: POP3< +OK 1 2821 fetchmail: POP3> TOP 1 99999999 fetchmail: POP3< +OK fetchmail: reading message dg...@po...:1 of 3 (2821 octets) fetchmail: About to rewrite Return-Path: <jqb...@pl...> Rewritten version is Return-Path: <jqb...@pl...> fetchmail: About to rewrite To: <dg...@my...> Rewritten version is To: <dg...@my...> fetchmail: About to rewrite From: "MalenaLanoraFatimaNeryMarceleneExieNaomaMahalia sqppffk" <jqb...@pl...> Rewritten version is From: "MalenaLanoraFatimaNeryMarceleneExieNaomaMahalia sqppffk" <jqb...@pl...> fetchmail: incorrect header line found while scanning headers fetchmail: line: boundary="------------Next_Part_37605954" ..Segmentation fault /*-----------------------------------------End--------------------------------------------------*/ I don't have ftp access to the remote machine, or any other way to get at the actual mail spool on it, so I downloaded the offending message via KMail's POP3 support, and here it is in all its spammy glory: /*----------------------------------------Begin-----------------------------------------------*/ |
