Help debugging false positives with SURBL

[Steve Freegard]

Hi Ian,

Ian wrote:
> I posted to this list because it only happens when the mail is passed through MailScanner, so 
> I actually need help on debugging on what happens to the message when it is passed to 
> spamassassin from MailScanner.  I actually need to know what MailScanner/SpamAssassin 
> thinks is the bad url.
> 
> Is it the domain name of the server?  The name of the perl script? Something else I'm not 
> seeing?
> 
> What does the MailScanner option:
> 
> 	Debug SpamAssassin = yes
> 
> actually do?  Where do I read the debug output?
> 
> Any help would be appreciated.

Try this:

Place the attached file into your CustomFunctions directory
(/usr/lib/MailScanner/MailScanner/CustomFunctions on RedHat and clones),
then in MailScanner.conf set:

Always Looked Up Last = &SALongReport

Then do a full restart of MailScanner and run the message in question
through MailScanner again.  You will now see the full SpamAssassin
report in the mail log which should contain all the information that you
need.

Hope this helps.  Please report back your findings to the list if it does.

Kind regards,
Steve.

--
Steve Freegard
Development Director
Fort Systems Ltd.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SALongReport.pm
Type: application/x-perl
Size: 1604 bytes
Desc: not available
Url : http://lists.mailscanner.info/pipermail/mailscanner/attachments/20070213/ce3bd22c/SALongReport.bin