Quarantined message * as it caused MailScanner to crash several times - fixed?

[Richard Mealing]

Hi,

Mailscanner -lint didn't show any problems with my configuration. I found the error when turning on Debug = yes for mailscanner. SA was fine but mailscanner produced the error -

Can't call method "CombineReports" on unblessed reference at /usr/local/lib/MailScanner/MailScanner/MessageBatch.pm line 736.
When looking at the logs I see no sendmail processing emails but just mailscanner going around in a loop quarantining all the emails.

I've tightened the timeouts on my sendmail mta as I think this was the problem. I've also changed the permissions on the incoming and outgoing queue folders. I can't reproduce the problem but I don't believe this is a mailscanner issue.
If it happens again I might change over to postfix or I might try Exim (as a test).

Thanks.
Rich

From: mailscanner-bounces at lists.mailscanner.info [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf Of Stephen Cox
Sent: 19 July 2013 07:24
To: MailScanner discussion
Subject: Re: Quarantined message * as it caused MailScanner to crash several times - fixed?

On Thu, Jul 18, 2013 at 1:20 PM, Richard Mealing <richard at fastnet.co.uk<mailto:richard at fastnet.co.uk>> wrote:
I'm fairly sure this has nothing to do with mailscanner itself, but my MTA. When it happens my MTA doesn't seem to be running properly (or can't handle the emails).

I've changed some permissions on the incoming and outgoing (and slow) queue's now, according to the mailscanner sendmail configuration page. I'll report back if it happens again.



What the output of MailScanner --lint?


Thanks,

From: mailscanner-bounces at lists.mailscanner.info<mailto:mailscanner-bounces at lists.mailscanner.info> [mailto:mailscanner-bounces at lists.mailscanner.info<mailto:mailscanner-bounces at lists.mailscanner.info>] On Behalf Of Richard Mealing
Sent: 18 July 2013 10:30
To: 'MailScanner discussion (mailscanner at lists.mailscanner.info<mailto:mailscanner at lists.mailscanner.info>)'
Subject: Quarantined message * as it caused MailScanner to crash several times

Hi,

I have searched for a while and I cannot find a solution to my problem. The only reference to this problem was when I reported it back in 2011.

I've been struggling along updating to the latest mailscanner and FreeBSD versions but this problem keeps hitting all of my servers once and a while.



Basically I get a log entry similar to this  -

Jul 17 22:44:40 mailfilter6 sm-mta-in[8204]: r6HLicbY008204: to=<info at somedomain.com<mailto:info at somedomain.com>>, delay=00:00:01, mailer=esmtp, pri=63196, stat=queued
Jul 17 22:49:53 mailfilter6 MailScanner[10329]: Making attempt 2 at processing message r6HLicbY008204
Jul 17 22:52:39 mailfilter6 MailScanner[11223]: Making attempt 3 at processing message r6HLicbY008204
Jul 17 22:55:07 mailfilter6 MailScanner[12183]: Making attempt 4 at processing message r6HLicbY008204
Jul 17 22:57:58 mailfilter6 MailScanner[13318]: Making attempt 5 at processing message r6HLicbY008204
Jul 17 23:00:48 mailfilter6 MailScanner[14702]: Making attempt 6 at processing message r6HLicbY008204
Jul 17 23:00:53 mailfilter6 MailScanner[14733]: Warning: skipping message r6HLicbY008204 as it has been attempted too many times
Jul 17 23:00:53 mailfilter6 MailScanner[14733]: Quarantined message r6HLicbY008204 as it caused MailScanner to crash several times
Jul 17 23:00:53 mailfilter6 MailScanner[14733]: Saved entire message to /var/spool/MailScanner/quarantine/20130717/r6HLicbY008204

It then fails on every subsequent message. To resolve I have to turn off the server and remove all the emails in the queue. If I pass the emails over to another server, say around 6000 emails, that server then has the exact same problem.

I've debugged mailscanner and spamassassin, I don't see any problems with SA, but mailscanner I get the following, still -

Can't call method "CombineReports" on unblessed reference at /usr/local/lib/MailScanner/MailScanner/MessageBatch.pm line 736.



Can anyone help me with this problem? I am using the -U flag, but this doesn't make any odds to the problem.

#!/usr/bin/perl -U -I/usr/local/lib/MailScanner


When I debug mailscanner I move the first problematic message to it's incoming queue and run the debug (I stop mailscanner before this so it's not running as a daemon) and I get no problems with the debug, but when I run it with over 6000 emails in the queue it comes up with the above debug message. I imagine this is a problem with timeout or such, but I'm not sure why it stops processing messages in the first place.

Does anyone have any ideas what I can do to fix this problem?

Thanks,
Rich

--
MailScanner mailing list
mailscanner at lists.mailscanner.info<mailto: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!

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.mailscanner.info/pipermail/mailscanner/attachments/20130719/a665a20e/attachment.html