Problem messages when spam checks enabled
nwilson123 at gmail.com
Mon Nov 5 12:01:50 GMT 2012
On Mon, Nov 5, 2012 at 1:21 PM, Stephen Cox <stephencoxmail at gmail.com> wrote:
> On Mon, Nov 5, 2012 at 12:30 PM, Neil <nwilson123 at gmail.com> wrote:
>> Should I paste the output of my spamassassin --lint -D into a pastebin
>> link, or send it here? Also I'm not sure how to go about doing a
>> "debug run on one of the problem emails?"
> Pastebin please
Okay, paste bin as requested.
>> MailScanner -v
>> Running on
>> Linux mail.mydomain.co.za 2.6.32-279.5.2.el6.x86_64 #1 SMP Fri Aug 24
>> 01:07:11 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
>> This is CentOS release 6.3 (Final)
>> This is Perl version 5.010001 (5.10.1)
>> This is MailScanner version 4.84.5
>> Module versions are:
>> 1.00 AnyDBM_File
>> 1.30 Archive::Zip
> It can be an insecure dependency, stop MailScanner and process a single
> email using MailScanner --debug. The email must be one of the messages that
> crashed MailScanner.
I ran the --debug and saw the following in the logs....
Building a message batch to scan...
Nov 5 13:54:04 mail MailScanner: New Batch: Scanning 1
messages, 766 bytes
Have a batch of 1 message.
Nov 5 13:54:04 mail MailScanner: Virus and Content Scanning: Starting
Insecure dependency in open while running with -T switch at
/usr/lib64/perl5/IO/File.pm line 185.
Nov 5 13:54:11 mail MailScanner: Spam Checks: Found 1 spam messages
It's very easy to get it to replicate the issue, just by sending a
test email with lots of common spam key words in the subject line.
Do you need more than the above, or is this enough? I don't want to
leave it running for too long in case it starts blocking legitimate
Thank you very much.
More information about the MailScanner