Cannot test spamassassin, what is going on here?

Nagy László Zsolt gandalf at
Wed Sep 9 12:09:11 UTC 2015

Given a test file "test.eml" I can run this test:

spamassassin -t test.eml

and I get this:

> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> Spam detection software, running on the system "",
> has NOT identified this incoming email as spam.  The original
> message has been attached to this so you can view it or label
> similar future email.  If you have any questions, see
> The administrator of that system for details.
> Content preview:  We've run into ths bug: 
>    [libc] fopen(3) fails with EMFILE if there are more than SHORT_MAX 
> fds open
>    [...]
> Content analysis details:   (-5.0 points, 5.0 required)
>  pts rule name              description
> ---- ---------------------- 
> --------------------------------------------------
> -5.0 RCVD_IN_DNSWL_HI       RBL: Sender listed at 
>, high
>                             trust
>                             [ listed in]

However, the very same email went through postfix/Mailscanner and 
resulted in these headers:

> X-shopzeus-MailScanner-Information: Please contact the ISP for more information
> X-shopzeus-MailScanner-ID: 4FFF48895E15.AB608
> X-shopzeus-MailScanner: Found to be clean
> X-shopzeus-MailScanner-SpamCheck: spam, JUNKEMAIL
> X-shopzeus-MailScanner-From: owner-freebsd-questions at
> X-Spam-Status: Yes

So the "spamassassin -t" command gives -5.0 score identifying as ham, 
but when the email actually comes in then it is identified as spam.

Looks like spamassassin is using different rules/settings when it is ran 
from the mailscanner daemon. The configuration should be the same ( 
/usr/local/etc/mail/spamassassin is a symbolic link to 
/usr/local/etc/MailScanner/spam.assassin.prefs.conf )

I cannot test spamassassin with the same user, because it is postfix 
which is disabled:

> # su postfix " spamassassin -t test.eml "
> This account is currently not available.

How to overcome this problem? What is going on here?



More information about the freebsd-questions mailing list