You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Chris Harvey <sa...@e-harvey.com> on 2005/04/08 17:16:58 UTC
report_safe doesn't seem to work since FC3 upgrade
I upgraded to FC3 this last weekend and I just noticed today that the mail
in my junk folder are not encapsulated/wrapped like they were before.
I checked my config file and have:
required_hits 4.5
rewrite_header Subject **SPAM(_SCORE_)**
report_safe 1
use_bayes 1
So it seems ok, but it's definitely seeing spam, milter-tagging it and then
filing it without wrapping it anymore.
Anyone having the same issue?
RE: report_safe doesn't seem to work since FC3 upgrade
Posted by Chris Harvey <sa...@e-harvey.com>.
> For those of us who use mail clients that understand what headers like
> Thread-Index: AcVAiG7iyfb2TrlzT+CYcsBsxEhNiAAYn8GA
> In-Reply-To: <42...@dostech.ca>
> mean, replying to a message in a thread to ask a different question means
> that
> we may or may not see your question (as it may be nested way down in an
> existing thread).
>
> Hence, you hijacked a thread to ask a new question. As the other poster
> said,
> message -> new to ask new questions that are unrelated.
Thanks, a way more polite response as I'd expect from a fellow Englishman.
:-)
Good to know that there are thread indexes in the headers, I hadn't noticed
it. In future I'll start clean new messages.
Re: report_safe doesn't seem to work since FC3 upgrade
Posted by Duncan Hill <sa...@nacnud.force9.co.uk>.
On Thursday 14 April 2005 13:12, Chris Harvey typed:
> > guess the people reading that thread don't know about your problem. I'd
> > suggest next time you send a new message (thus starting a new thread)
> > rather than hijacking an existing thread.
>
> Not sure where you are getting that from. I did reply to a message just to
> grab the list name as I don't use it very often but for all intents and
> purposes the message was new not a reply to a thread so no I wasn't
> hijacking anything.
For those of us who use mail clients that understand what headers like
Thread-Index: AcVAiG7iyfb2TrlzT+CYcsBsxEhNiAAYn8GA
In-Reply-To: <42...@dostech.ca>
mean, replying to a message in a thread to ask a different question means that
we may or may not see your question (as it may be nested way down in an
existing thread).
Hence, you hijacked a thread to ask a new question. As the other poster said,
message -> new to ask new questions that are unrelated.
Re: report_safe doesn't seem to work since FC3 upgrade
Posted by "Daryl C. W. O'Shea" <sp...@dostech.ca>.
Chris Harvey wrote:
>>The problem with your setup is with spamass-milter, not SpamAssassin.
>
>
> And people exclusively ask questions about SA on here? Never ever one on the
> milter?
Perhaps I should have been a little more verbose -- I wasn't saying not
to ask your question here. It's not a SpamAssassin config issue it's
likely a config issue with the spamass-milter.
Your maillog paste doesn't show the Subject: header being modified, it
only shows the X-Spam headers being added. This may be a symptom of the
'-m' option being present in the call to whatever the spamass-milter
executable is.
As for the lack of encapsulation, in the 60 seconds or so of looking
through the spamass-milter documentation to find the -m option info, I
didn't see any mention of encapsulation -- I don't think it's possible
with this milter.
Daryl
RE: report_safe doesn't seem to work since FC3 upgrade
Posted by Chris Harvey <sa...@e-harvey.com>.
> The problem with your setup is with spamass-milter, not SpamAssassin.
And people exclusively ask questions about SA on here? Never ever one on the
milter?
> The problem with your lack of responses is that you started your thread
> by replying to a message in the thread titled "--username flag". I
> don't know what your problem has to do with the --username option, but I
> guess the people reading that thread don't know about your problem. I'd
> suggest next time you send a new message (thus starting a new thread)
> rather than hijacking an existing thread.
Not sure where you are getting that from. I did reply to a message just to
grab the list name as I don't use it very often but for all intents and
purposes the message was new not a reply to a thread so no I wasn't
hijacking anything.
Re: report_safe doesn't seem to work since FC3 upgrade
Posted by "Daryl C. W. O'Shea" <sp...@dostech.ca>.
The problem with your setup is with spamass-milter, not SpamAssassin.
The problem with your lack of responses is that you started your thread
by replying to a message in the thread titled "--username flag". I
don't know what your problem has to do with the --username option, but I
guess the people reading that thread don't know about your problem. I'd
suggest next time you send a new message (thus starting a new thread)
rather than hijacking an existing thread.
Daryl
RE: report_safe doesn't seem to work since FC3 upgrade
Posted by Chris Harvey <sa...@e-harvey.com>.
OK.. last request. I think I've sent this in three times now and not even
seen one response which is quite amazing for this list.
I'm having a hard time believing I'm the only one running this combination
of software.
I've stopped 1,128 spam and fraud messages. You can too!
One month FREE spam and fraud protection at
http://www.cloudmark.com/safetybarsig/?
> -----Original Message-----
> From: Chris Harvey [mailto:sa@e-harvey.com]
> Sent: Monday, April 11, 2005 9:21 PM
> To: 'SpamAssassin list'
> Subject: RE: report_safe doesn't seem to work since FC3 upgrade
>
> Anyone else seeing similar behavior!? I cannot find out what is wrong.
>
> If I edit my sensitivity (require_hits) it's reflected in my logs, yet
> none
> of these settings appear to be working:
>
> report_safe 1
> rewrite_header Subject **NEW_SPAM(_SCORE_)**
>
> If I put the old settings back of:
>
> rewrite_subject 1
> subject_tag [SPAM]
>
> I see it complain in the maillog file when I start up spamassassin.
>
> Removing the report_safe option entirely also doesn't seem to make it work
> even though it's the default.
>
> Versions I'm using are:
>
> Kernel 2.6.10-1.770_FC3
> sendmail-8.13.1-2.i386.rpm
> sendmail-cf-8.13.1-2.i386.rpm
> spamassassin-3.0.2-0.fc3.i386.rpm
> spamassassin-tools-2.60-1.i386.rpm
> spamass-milter-0.3.0-1.1.fc3.rf.i386.rpm
>
> Is really no-one else seeing this? I can't believe I'm the only person
> seeing this?
>
> Headers are being stuck into the messages just fine by the milter as is
> show
> in the log below, but subject isn't being written and neither are the
> messages being encapsulated.
>
> HELP!!?!!!
>
>
> > > I upgraded to FC3 this last weekend and I just noticed today that the
> > mail
> > > in my junk folder are not encapsulated/wrapped like they were before.
> > >
> > > I checked my config file and have:
> > >
> > > required_hits 4.5
> > > rewrite_header Subject **SPAM(_SCORE_)**
> > > report_safe 1
> > > use_bayes 1
> > >
> > > So it seems ok, but it's definitely seeing spam, milter-tagging it and
> > > then
> > > filing it without wrapping it anymore.
> > >
> > > Anyone having the same issue?
> >
> > Actually I just noticed something else. Even though the messages are
> being
> > put in my junkmail folder and maillogs show that the messages are being
> > identified and tagged as spam, none of the messages from the upgrade
> have
> > either the changed subject line or are encapsulated.
> >
> > I've run --lint and can't see any obvious errors. Here's a quick slice
> of
> > the maillog showing it should be tagging the messages:
> >
> > Apr 9 04:05:27 xxxx sendmail[23122]: j3985KIc023122: Milter add:
header:
> > X-Spam-Flag: YES
> > Apr 9 04:05:27 xxxx sendmail[23122]: j3985KIc023122: Milter add:
header:
> > X-Spam-Status: Yes, score=9.9 required=4.5
> >
> tests=BAYES_99,HTML_90_100,\n\tHTML_MESSAGE,MIME_HTML_ONLY,MIME_HTML_ONLY_
> > MU
> > LTI,MPART_ALT_DIFF,\n\tURIBL_SBL,URIBL_SC_SURBL autolearn=no
> version=3.0.2
> > Apr 9 04:05:27 xxxx sendmail[23122]: j3985KIc023122: Milter add:
header:
> > X-Spam-Level: *********
> > Apr 9 04:05:27 xxxx sendmail[23122]: j3985KIc023122: Milter add:
header:
> > X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on xxxx
> >
> > Interestingly I noticed that as part of the Fedora Core 3 (FC3) upgrade
> I
> > got a new milter. I'm wondering if that's causing the issue.
RE: report_safe doesn't seem to work since FC3 upgrade
Posted by Chris Harvey <sa...@e-harvey.com>.
Anyone else seeing similar behavior!? I cannot find out what is wrong.
If I edit my sensitivity (require_hits) it's reflected in my logs, yet none
of these settings appear to be working:
report_safe 1
rewrite_header Subject **NEW_SPAM(_SCORE_)**
If I put the old settings back of:
rewrite_subject 1
subject_tag [SPAM]
I see it complain in the maillog file when I start up spamassassin.
Removing the report_safe option entirely also doesn't seem to make it work
even though it's the default.
Versions I'm using are:
Kernel 2.6.10-1.770_FC3
sendmail-8.13.1-2.i386.rpm
sendmail-cf-8.13.1-2.i386.rpm
spamassassin-3.0.2-0.fc3.i386.rpm
spamassassin-tools-2.60-1.i386.rpm
spamass-milter-0.3.0-1.1.fc3.rf.i386.rpm
Is really no-one else seeing this? I can't believe I'm the only person
seeing this?
Headers are being stuck into the messages just fine by the milter as is show
in the log below, but subject isn't being written and neither are the
messages being encapsulated.
HELP!!?!!!
> > I upgraded to FC3 this last weekend and I just noticed today that the
> mail
> > in my junk folder are not encapsulated/wrapped like they were before.
> >
> > I checked my config file and have:
> >
> > required_hits 4.5
> > rewrite_header Subject **SPAM(_SCORE_)**
> > report_safe 1
> > use_bayes 1
> >
> > So it seems ok, but it's definitely seeing spam, milter-tagging it and
> > then
> > filing it without wrapping it anymore.
> >
> > Anyone having the same issue?
>
> Actually I just noticed something else. Even though the messages are being
> put in my junkmail folder and maillogs show that the messages are being
> identified and tagged as spam, none of the messages from the upgrade have
> either the changed subject line or are encapsulated.
>
> I've run --lint and can't see any obvious errors. Here's a quick slice of
> the maillog showing it should be tagging the messages:
>
> Apr 9 04:05:27 xxxx sendmail[23122]: j3985KIc023122: Milter add: header:
> X-Spam-Flag: YES
> Apr 9 04:05:27 xxxx sendmail[23122]: j3985KIc023122: Milter add: header:
> X-Spam-Status: Yes, score=9.9 required=4.5
> tests=BAYES_99,HTML_90_100,\n\tHTML_MESSAGE,MIME_HTML_ONLY,MIME_HTML_ONLY_
> MU
> LTI,MPART_ALT_DIFF,\n\tURIBL_SBL,URIBL_SC_SURBL autolearn=no version=3.0.2
> Apr 9 04:05:27 xxxx sendmail[23122]: j3985KIc023122: Milter add: header:
> X-Spam-Level: *********
> Apr 9 04:05:27 xxxx sendmail[23122]: j3985KIc023122: Milter add: header:
> X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on xxxx
>
> Interestingly I noticed that as part of the Fedora Core 3 (FC3) upgrade I
> got a new milter. I'm wondering if that's causing the issue.
RE: report_safe doesn't seem to work since FC3 upgrade
Posted by Chris Harvey <sa...@e-harvey.com>.
> I upgraded to FC3 this last weekend and I just noticed today that the mail
> in my junk folder are not encapsulated/wrapped like they were before.
>
> I checked my config file and have:
>
> required_hits 4.5
> rewrite_header Subject **SPAM(_SCORE_)**
> report_safe 1
> use_bayes 1
>
> So it seems ok, but it's definitely seeing spam, milter-tagging it and
> then
> filing it without wrapping it anymore.
>
> Anyone having the same issue?
Actually I just noticed something else. Even though the messages are being
put in my junkmail folder and maillogs show that the messages are being
identified and tagged as spam, none of the messages from the upgrade have
either the changed subject line or are encapsulated.
I've run --lint and can't see any obvious errors. Here's a quick slice of
the maillog showing it should be tagging the messages:
Apr 9 04:05:27 xxxx sendmail[23122]: j3985KIc023122: Milter add: header:
X-Spam-Flag: YES
Apr 9 04:05:27 xxxx sendmail[23122]: j3985KIc023122: Milter add: header:
X-Spam-Status: Yes, score=9.9 required=4.5
tests=BAYES_99,HTML_90_100,\n\tHTML_MESSAGE,MIME_HTML_ONLY,MIME_HTML_ONLY_MU
LTI,MPART_ALT_DIFF,\n\tURIBL_SBL,URIBL_SC_SURBL autolearn=no version=3.0.2
Apr 9 04:05:27 xxxx sendmail[23122]: j3985KIc023122: Milter add: header:
X-Spam-Level: *********
Apr 9 04:05:27 xxxx sendmail[23122]: j3985KIc023122: Milter add: header:
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on xxxx
Interestingly I noticed that as part of the Fedora Core 3 (FC3) upgrade I
got a new milter. I'm wondering if that's causing the issue.