Cannot test spamassassin, what is going on here?

[Martin Hepworth]

Laszio

make sure you're running the same configs by running as the same user that
Mailscanners is (the RunAs parameter in mailscanner.conf) and using the
same config so it's picking up the mailscanner.cf

spamassassin -t test.email -C /directory/where/mailscanner.cf/is

-- 
Martin Hepworth, CISSP
Oxford, UK

On 10 September 2015 at 13:50, Les <nagylzs at gmail.com> wrote:

> 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 "shopzeus.com",
> 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:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148581
>    [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 http://www.dnswl.org/,
> high
>                             trust
>                             [8.8.178.116 listed in list.dnswl.org]
>
>
> 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 freebsd.org
> 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?
>
> Mailscanner version: MailScanner-4.84.6
> Spamassassin version: 3.4.1
>
> Thanks
>
>    Laszlo
>
>
>
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/listinfo/mailscanner
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mailscanner.info/pipermail/mailscanner/attachments/20150910/ea0d5676/attachment.html>