[fetchmail-devel] [PATCH] Re: fetchmail segfault on 'empty' mail

[Sunil S. <sh...@bo...>]

Hi,

Quoting from Daniel Drake's mail on Wed, Dec 07, 2005:
> I don't have any more of these mails right now, so this is fairly 
> fabricated, but more or less accurate.
> 
> Before:
> 
> fetchmail: 6.2.5.2 querying aap.businessserve.co.uk (protocol POP3) at Wed, 
> 07 Dec 2005 13:20:02 +0000 (GMT): poll started
> fetchmail: POP3< +OK <..>
> fetchmail: POP3> CAPA
> fetchmail: POP3< -ERR authorization first
> fetchmail: authorization first
> fetchmail: Repoll immediately on xxx
> fetchmail: POP3< +OK <..>
> fetchmail: POP3> USER xxx
> fetchmail: POP3< +OK
> fetchmail: POP3> PASS *
> fetchmail: POP3< +OK
> fetchmail: POP3> STAT
> fetchmail: POP3< +OK 26 82969
> fetchmail: POP3> LIST 1
> fetchmail: POP3< +OK 1 1329
> fetchmail: POP3> RETR 1
> fetchmail: POP3< +OK 1329 octets follow.
> reading message xyz:1 of 26 (1329 octets)
> Segmentation fault

The problem is specific to multidrop mailbox only where the
duplicate-message killer cannot handle a headerless mail. The attached
patch should fix this issue. 

The patch also cleans up the code by calling free() at one point
only for static variables.

-- 
Sunil Shetye.