RE: spam filter working, but not well

roprc below the sorting rules (the folder sorting rules are things like: if (/^X-Spam-Flag: .*YES/) {exception {to "$HOME/Maildir/.spam/"} } Now I have a bayes item in the header of each spam and ham message. This is great! Thank you, Brian On Tue, November 7, 2006 11:22, Bowie Bailey

Re: spam filter working, but not well

MAIL PROTECTED] Subject: rejected Uganda rebel Thanks, -Brian On Tue, November 7, 2006 10:42, Jim Maul wrote: > Brian S. Meehan wrote: >> Spamassassin is invoked from Courier-MTA. (OS is SUSE Pro 9.3) >> The /usr/lib/courier/etc/courierd file has the following line: >> DEFAULTDEL

Re: spam filter working, but not well

tc/sysconfig/spamd file and the only uncommented line is: SPAMD_ARGS="-d -c" -Brian On Mon, November 6, 2006 05:20, Peter Teunissen wrote: > > On 6-nov-2006, at 1:54, John Andersen wrote: > >> On Sunday 05 November 2006 15:48, Brian S. Meehan wrote: >>> Hi all, >>

spam filter working, but not well

Hi all, Spam filtering is working, but I'm getting about half the spam in my mailbox. Anyone have tips on adjustments I could make? Here's what I have in the local.cf file: rewrite_header SUBJECT **SPAM** dns_available yes required_score 4.0 bayes_path /etc/mail/spamassassin/bayesfiles/bayes use_

Spam isn't getting caught, can anyone help please?

I know y'all are smart, just looking for a little help on this one. In addition to the below info, spamassassin -lint works fine and quietly. Thanks, Brian Original Message Subject: upgraded, now no spam is caught From:&qu

Re: upgraded, now no spam is caught

spamassassin --lint is quiet. no output. Thank you for replying and assisting; I look forward to other suggestions also. Regards, Brian On Wed, October 25, 2006 22:07, Matt Kettler wrote: > Brian S. Meehan wrote: >> I upgraded spamassassin from 3.0.4 to 3.1.7 and now no spam is getting

upgraded, now no spam is caught

I upgraded spamassassin from 3.0.4 to 3.1.7 and now no spam is getting caught. My mail server (courier-MTA) is still sending mail through spamc before it hits maildrop, so I know it's being processed. I found one header in a single message out of about fifty: X-Spam: Not detected I'm still running

Re: errors after upgrade to 3.1.7, now it doesn't work

When you say blow them away, are there folders besides the below ones that should be removed? /etc/mail/spamassassin /usr/share/spamassassin Thank you, Brian On Fri, October 20, 2006 14:35, Theo Van Dinter wrote: > On Fri, Oct 20, 2006 at 02:30:14PM -0400, Brian S. Meehan wrote: >>

errors after upgrade to 3.1.7, now it doesn't work

I had a working setup of Courier-MTA, spamassassin 3.0.4, and maildrop, but I upgraded spamassassin to 3.1.7 and now I have errors and mail doesn't get delivered unless I remove the tie-in to spamassassin in the courierd file. Here are some of the errors: Oct 20 14:10:20 mail spamd[5776]: configur

Any suggestions for 'postmaster' spams?

It appears that my email address is now being used as a from address in many spam emails to many addresses. Over the past week, I have gotten 150+ "postmaster: mail delivery failure" -each day-. Does anyone have suggestions on how to handle this? They're all semi-standard 'delivery failure' or 'co

Rewriting header fields help please. anyone??

So, no one is going to tackle this one? Must be too easy for y'all to answer. ;-) (a little friday humor) Brian Original Message Subject: Rewriting header fields help please From:"Brian S. Meehan" <[EMAIL PROTEC

Rewriting header fields help please

Hi, There's the option "rewrite_header Subject" in the local.cf file, however, I've been observing when looking through the spam folder that sorting by subject is more helpful when looking for incorrectly caught emails since many emails often have the same subject and different from fields, includi

Re: spam still isn't being caught much.

So far, here's an update. The OS is Suse Pro 9.3 I haven't seen any spam messages with ALL_TRUSTED in the headers. I have seen empty emails with a spam score of zero though and spamd tries to autolearn those as ham and shows "failed". The bayes_file_mode is now set to 0777 I'm still getting abou

Re: Re[2]: spam still isn't being caught much.

Hi Bob, spamassassin --lint returns no errors. I've been checking it after I add rules. You can view my entire local.cf at http://www.meehanontheweb.com/local.cf.txt I haven't seen "ALL_TRUSTED" in any of the x-spam-status headers in any message. So far, what I've been doing is logging in as roo

Re: spam still isn't being caught much.

>> required_score 4.0 >> bayes_path /etc/mail/spamassassin/bayes >> use_bayes 1 >> bayes_auto_learn 1 >> bayes_file_mode 0777 >> report_safe 0 >> bayes_ignore_header X-purgate >> bayes_ignore_header X-purgate-ID >> bayes_ignore_header X-purgate-Ad >>

Re: spam still isn't being caught much.

7 report_safe 0 bayes_ignore_header X-purgate bayes_ignore_header X-purgate-ID bayes_ignore_header X-purgate-Ad bayes_ignore_header X-GMX-Antispam bayes_ignore_header X-Antispam bayes_ignore_header X-Spamcount bayes_ignore_header X-Spamsensitivity On Sat, February 4, 2006 23:50, Matt Kettler wrote: > B

spam still isn't being caught much.

I'm using spamassassin with bayes filtering, nightly I use sa-learn to go though the folders I have, learning spam and learning ham. This has gone on for about 6 weeks now with me moving the uncaught spam messages that are in my inbox into the spam folder. I know it has well over 200 messages as th

a rule for just re:

Somewhere I got a rule for emails with only "Re:" in the subject line. However, I received a valid email and it had a valid subject line with stuff in it but it got marked as meeting the below rule. header SPAM_RE_SUBJECT_RULE Subject =~ /Re:/i score SPAM_RE_SUBJECT_RULE 2.1 describe SPAM_RE_SUBJE