You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by tom wright <to...@maladmin.com> on 2005/12/29 11:30:52 UTC
Confusing X-Spam-Status header
Hi folks,
First time posting here so thanks in advance for any assistance. Looking
at my email headers it appears spamassassin is doing an excellent job of
classifying my email but in the X-Spam-Status header, even when a mail
is classified as ham I still get a summary message. I'm guessing this is
incorrect configuration somewhere but since I'm running with pretty much
default configuration I'm not sure where to start looking.
I'm running SA 3.1.0 on Perl 5.8.7
> X-Spam-Status: No (score -2.6): Spam detection software, running on
> the system "portal.maladmin.com", has identified this incoming email
> as possible spam. The original message has been attached to this so
> you can view it (if it isn't spam) or label similar future email. If
> you have any questions, see postmaster@maladmin.com for details.
> Content preview: [...] Content analysis details: (-2.6 points, 5.0
> required) pts rule name description ----
> ----------------------
> -------------------------------------------------- 0.2 NO_REAL_NAME
> From: does not include a real name -2.8 ALL_TRUSTED Did not
> pass through any untrusted hosts
Re: Confusing X-Spam-Status header
Posted by Patrick von der Hagen <pa...@wudika.de>.
tom wright wrote:
>> This dosnt seem to have solved the issue. I'm using the
>> exiscan-acl-4.42-27.patch (http://duncanthrax.net/exiscan-acl/) so exim
>> send mails direct to spamassassin at smtp time. I'm no expert here but
>> looking at the code it seems that this passes the message direct to
>> spamd.
You probably did something like this:
# Always put X-Spam-Report header in the message.
# This is a multiline header that informs the user
# which tests a message has "hit", and how much a
# test has contributed to the score.
warn message = X-Spam-Report: $spam_report
condition = ${if <{$message_size}{80k}{1}{0}}
spam = nobody:true
You will always get a X-Spam-Report-Header in your emails to prove that
the email has been scaned and (in the case of a false-negative) to
explain why it was not considered to be spam.
If you need more support, please provide your exim-ACL which refer to
spamassassin.
--
CU,
Patrick.
Re: Confusing X-Spam-Status header
Posted by tom wright <to...@maladmin.com>.
That loks like it, is there anyway of having a different report if the
mail is identified as spam cf identified as ham?
On Thu, 2005-29-12 at 20:16 +0100, Patrick von der Hagen wrote:
> tom wright wrote:
> > This dosnt seem to have solved the issue. I'm using the
> > exiscan-acl-4.42-27.patch (http://duncanthrax.net/exiscan-acl/) so exim
> > send mails direct to spamassassin at smtp time. I'm no expert here but
> > looking at the code it seems that this passes the message direct to
> > spamd.
>
> You probably did something like this:
>
> # Always put X-Spam-Report header in the message.
> # This is a multiline header that informs the user
> # which tests a message has "hit", and how much a
> # test has contributed to the score.
> warn message = X-Spam-Report: $spam_report
> condition = ${if <{$message_size}{80k}{1}{0}}
> spam = nobody:true
>
> You will always get a X-Spam-Report-Header in your emails to prove that
> the email has been scaned and (in the case of a false-negative) to
> explain why it was not considered to be spam.
>
> If you need more support, please provide your exim-ACL which refer to
> spamassassin.
Re: Confusing X-Spam-Status header
Posted by tom wright <to...@maladmin.com>.
This dosnt seem to have solved the issue. I'm using the
exiscan-acl-4.42-27.patch (http://duncanthrax.net/exiscan-acl/) so exim
send mails direct to spamassassin at smtp time. I'm no expert here but
looking at the code it seems that this passes the message direct to
spamd.
On Thu, 2005-29-12 at 08:28 -0500, tom wright wrote:
> Interesting, it looks like I could be calling spamassassin twice (both
> through spamc). Once through exim and once with maildrop. I've turned
> off the maildrop call and am waiting to see what happens.
>
> On Thu, 2005-29-12 at 11:46 -0500, Matt Kettler wrote:
> > tom wright wrote:
> > > Hi folks,
> > > First time posting here so thanks in advance for any assistance. Looking
> > > at my email headers it appears spamassassin is doing an excellent job of
> > > classifying my email but in the X-Spam-Status header, even when a mail
> > > is classified as ham I still get a summary message. I'm guessing this is
> > > incorrect configuration somewhere but since I'm running with pretty much
> > > default configuration I'm not sure where to start looking.
> > > I'm running SA 3.1.0 on Perl 5.8.7
> >
> > How are you calling SpamAssassin? You're not using the -t command-line
> > parameter, are you?
> >
> >
>
>
Re: Confusing X-Spam-Status header
Posted by tom wright <to...@maladmin.com>.
Interesting, it looks like I could be calling spamassassin twice (both
through spamc). Once through exim and once with maildrop. I've turned
off the maildrop call and am waiting to see what happens.
On Thu, 2005-29-12 at 11:46 -0500, Matt Kettler wrote:
> tom wright wrote:
> > Hi folks,
> > First time posting here so thanks in advance for any assistance. Looking
> > at my email headers it appears spamassassin is doing an excellent job of
> > classifying my email but in the X-Spam-Status header, even when a mail
> > is classified as ham I still get a summary message. I'm guessing this is
> > incorrect configuration somewhere but since I'm running with pretty much
> > default configuration I'm not sure where to start looking.
> > I'm running SA 3.1.0 on Perl 5.8.7
>
> How are you calling SpamAssassin? You're not using the -t command-line
> parameter, are you?
>
>
Re: Confusing X-Spam-Status header
Posted by Matt Kettler <mk...@evi-inc.com>.
tom wright wrote:
> Hi folks,
> First time posting here so thanks in advance for any assistance. Looking
> at my email headers it appears spamassassin is doing an excellent job of
> classifying my email but in the X-Spam-Status header, even when a mail
> is classified as ham I still get a summary message. I'm guessing this is
> incorrect configuration somewhere but since I'm running with pretty much
> default configuration I'm not sure where to start looking.
> I'm running SA 3.1.0 on Perl 5.8.7
How are you calling SpamAssassin? You're not using the -t command-line
parameter, are you?