Segfault

[Yann Bachy]

In fact this has worked fine for at least over a 100 days (uptime)...  
but server has been installed about 1 or 2 years ago ... never had  
this problem before

We finally found the problem.... there was a mal-formatted mail in the  
queue... I put it aside and gonna check it out on monday morning when  
I get back to it.

I'll let you guys know if I find something, thanks anyway... I'll do  
some updates ;)

bye!




--
Yann Bachy

CAPENSIS
30 rue du Triez
59290 Wasquehal
----------------------
Tel     03 59 39 13 40
Fax     03 59 39 13 49


Quoting Martin Hepworth <maxsec at gmail.com>:

> Yann
> that's a really old version of mailscanner - there's an update debian port
> somewhere or move to the generic installer.
>
> normally this is something like a bad spool file, or the fact you;ve
> upgraded postfix and the version of MS you've got doesn't understand the new
> spool  file format.
>
> Has this ever worked or is this a new install??
>
>
> --
> Martin Hepworth
> Oxford, UK
>
> 2009/8/14 Yann Bachy <yann.b at capensis.fr>
>
>> Hello everyone!
>>
>> I've got the following problem with my mailscanner:
>>
>> every time Mailscanner loads a batch of mails to scan it quits and starts
>> all over again :
>>
>> Aug 14 18:13:59 localhost MailScanner[6844]: MailScanner E-Mail Virus
>> Scanner version 4.55.10 starting...
>> Aug 14 18:13:59 localhost MailScanner[6844]: Read 748 hostnames from the
>> phishing whitelist
>> Aug 14 18:13:59 localhost MailScanner[6844]: Config: calling custom init
>> function SQLBlacklist
>> Aug 14 18:13:59 localhost MailScanner[6844]: Starting up SQL Blacklist
>> Aug 14 18:13:59 localhost MailScanner[6844]: Read 0 blacklist entries
>> Aug 14 18:13:59 localhost MailScanner[6844]: Config: calling custom init
>> function MailWatchLogging
>> Aug 14 18:13:59 localhost MailScanner[6844]: Started SQL Logging child
>> Aug 14 18:13:59 localhost MailScanner[6844]: Config: calling custom init
>> function SQLWhitelist
>> Aug 14 18:13:59 localhost MailScanner[6844]: Starting up SQL Whitelist
>> Aug 14 18:13:59 localhost MailScanner[6844]: Read 2 whitelist entries
>> Aug 14 18:13:59 localhost MailScanner[6844]: Using SpamAssassin results
>> cache
>> Aug 14 18:13:59 localhost MailScanner[6844]: Connected to SpamAssassin
>> cache database
>> Aug 14 18:13:59 localhost MailScanner[6844]: Enabling SpamAssassin
>> auto-whitelist functionality...
>> Aug 14 18:14:00 localhost MailScanner[6844]: Using locktype = flock
>> Aug 14 18:14:00 localhost MailScanner[6844]: New Batch: Found 15 messages
>> waiting
>> Aug 14 18:14:00 localhost MailScanner[6844]: New Batch: Scanning 5
>> messages, 922438 bytes
>> Aug 14 18:14:00 localhost MailScanner[6844]: SpamAssassin cache hit for
>> message 8248C328003.1CFD1
>> Aug 14 18:14:00 localhost MailScanner[6844]: SpamAssassin cache hit for
>> message 132F5328005.8800B
>> Aug 14 18:14:00 localhost MailScanner[6844]: SpamAssassin cache hit for
>> message 96FA0328004.08A04
>> Aug 14 18:14:00 localhost MailScanner[6844]: SpamAssassin cache hit for
>> message 212D9328007.B19A9
>> Aug 14 18:14:01 localhost MailScanner[6844]: SpamAssassin cache hit for
>> message 9735C328006.BEBA0
>> Aug 14 18:14:01 localhost MailScanner[6844]: Virus and Content Scanning:
>> Starting
>> Aug 14 18:14:10 localhost MailScanner: Process did not exit cleanly,
>> returned 0 with signal 11
>>
>>
>>
>> and it does this over and over again
>>
>> I ran an strace on the process and get a segfault when it calls a brk()
>>
>> Mailscanner is running with postfix on a Debian 4.0 2.6.17-2-686
>> Mailscanner : 4.55.10-3
>>
>> thanks for any info
>>
>>
>>
>>
>> --
>> Yann Bachy
>>
>> CAPENSIS
>> 30 rue du Triez
>> 59290 Wasquehal
>> ----------------------
>> Tel     03 59 39 13 40
>> Fax     03 59 39 13 49
>>
>>
>>
>> --
>> MailScanner mailing list
>> mailscanner at lists.mailscanner.info
>> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>>
>> Before posting, read http://wiki.mailscanner.info/posting
>>
>> Support MailScanner development - buy the book off the website!
>>
>