Re: SUBJ_ILLEGAL_CHARS

2006-03-14 Thread Philip Prindeville
Милен Панков wrote: > Matt Kettler написа: >>Realistically, you have two options: >> >> 1) tell the sender their client isn't properly QP encoding Bulgarian >> text in >>the subject headers. >> 2) accept that many email clients don't properly handle Bulgarian text, >> and >>disable this

headers creeping into message body after upgrade to 3.1.1

2006-03-14 Thread Carl Brewer
Hello, I just upgraded to 3.1.1 on a NetBSD box via pkgsrc, and am using sendmail 8.13.5 with spamass-milter 0.3.0, and sendmail is configured to use cyrus imapd as its local delivery agent. Since I upgraded, I'm seeing bits of the X-Spam-Header message in my mail bodies, like this : To: Carl

Re: SUBJ_ILLEGAL_CHARS

2006-03-14 Thread Милен Панков
Matt Kettler написа: Милен Панков wrote: Hi to all, I'm using spamassassin for years without any serious problems. First: In my answer's I'm assuming you are running 3.1.0 or higher. If you aren't please specify your version. Yes, it's 3.1.0, sorry Except for one. My users write messag

Re: Is this header stuff right? Ver 3.1.1

2006-03-14 Thread [EMAIL PROTECTED]
Thank you Theo! I will put it online and sleep somewhat better tonight. :) Theo Van Dinter wrote: On Tue, Mar 14, 2006 at 08:01:53PM -0700, [EMAIL PROTECTED] wrote: I have noticed that the headers in the non-spam messages seem different from what I remember. In short, it seem

Re: Is this header stuff right? Ver 3.1.1

2006-03-14 Thread Theo Van Dinter
On Tue, Mar 14, 2006 at 08:01:53PM -0700, [EMAIL PROTECTED] wrote: > I have noticed that the headers in the non-spam messages seem different > from what I remember. In short, it seems that the spam stuff inserted > from SA are at the top of the header in non-spam messages, but where I > remembe

Is this header stuff right? Ver 3.1.1

2006-03-14 Thread [EMAIL PROTECTED]
Hi All, I just upgraded to ver 3.1.1 and after the CRLF problems I had with 3.1.0 I am somewhat paranoid. I have noticed that the headers in the non-spam messages seem different from what I remember. In short, it seems that the spam stuff inserted from SA are at the top of the header in no

Re: Tasks run as root in SpamAssassin 3.1.0

2006-03-14 Thread Theo Van Dinter
On Tue, Mar 14, 2006 at 05:45:44PM -0500, Brett Smith wrote: > I found the rationale for this at > , and it makes > plenty of sense. I was wondering if it'd be possible to get a rough > outline of what tasks spamd runs as root, however, s

Re: Tasks run as root in SpamAssassin 3.1.0

2006-03-14 Thread Matt Kettler
Brett Smith wrote: > Hello, > > I run a SpamAssassin installation where we run spamd system-wide under a > dedicated account, and users filter their mail with spamc. When we > upgraded to 3.1.0, we noticed that a spamd process always runs as root > now. The should only be root when idle. They sh

Tasks run as root in SpamAssassin 3.1.0

2006-03-14 Thread Brett Smith
Hello, I run a SpamAssassin installation where we run spamd system-wide under a dedicated account, and users filter their mail with spamc. When we upgraded to 3.1.0, we noticed that a spamd process always runs as root now. I found the rationale for this at

RE: Received-SPF header.

2006-03-14 Thread Matthew.van.Eerde
Xavier Sudre wrote: > I read that an SPF aware smtp server should introduce the Received-SPF > header in the email headers. There are patches for Postfix to support SPF... for example: http://www.ipnet6.org/postfix/spf/ -- Matthew.van.Eerde (at) hbinc.com 805.964.4554 x902 Hispanic

RE: Received-SPF header.

2006-03-14 Thread Matthew.van.Eerde
Xavier Sudre wrote: > Is there a way to get spamassassin record a Recevied-SPF header in the > email headers? Only MTAs can add headers.

Received-SPF header.

2006-03-14 Thread Xavier Sudre
Hi there! I have spamassassin running on a server and I added SPF at that level. I read that an SPF aware smtp server should introduce the Received-SPF header in the email headers. As I said I have implemented SPF at spamassassin level only, not at the MTA level and this mainly for the simple

Any windows users try the new Active Perl with SA?

2006-03-14 Thread [EMAIL PROTECTED]
Hi, I am wondering if anyone running Windows and SA has tried the new ActivePerl with 3.1.1?

Re: SUBJ_ILLEGAL_CHARS

2006-03-14 Thread Matt Kettler
Милен Панков wrote: > Hi to all, > > I'm using spamassassin for years without any serious problems. First: In my answer's I'm assuming you are running 3.1.0 or higher. If you aren't please specify your version. > Except for one. My users write messages mostly in bulgarian and the > 'SUBJ_ILLEGAL

Re: Can SA tag addresses seen for the first time?

2006-03-14 Thread Theo Van Dinter
On Tue, Mar 14, 2006 at 11:22:55AM -0500, [EMAIL PROTECTED] wrote: > based on MySQL-stored preferences. For each email coming in, I would like > SpamAssassin to check the database for $WHITELISTED or $BLACKLISTED email > addresses and tag the email as ${UNSEEN} if it is a newly seen address. > >

Can SA tag addresses seen for the first time?

2006-03-14 Thread spamassassin
Hello list: This is the challenge I face. I would like to be able to filter emails based on MySQL-stored preferences. For each email coming in, I would like SpamAssassin to check the database for $WHITELISTED or $BLACKLISTED email addresses and tag the email as ${UNSEEN} if it is a newly seen ad

Re: CheapTickets newsletter triggering SARE_BAYES plus others

2006-03-14 Thread David Landgren
Chris Purves wrote: Loren Wilton wrote: The other rule is looking for a really standard spammer trick: . Interesting. How is this helpful to spammers? Indeed. This used to crop up regularly in MS-Frontpage circa 1998 when people added and then removed markup. Dunno if that is still the ca

RE: Drug email keeps getting thru

2006-03-14 Thread Tracey Gates
I have URIBL lookups enabled. I have also increased my score in mangled.cf. I have posted the email that I'm receiving at www.yoursummit.com/pharmNews.html if you'd like to view the actual email content. Below is the header of the latest email that I've gotten. The names of the drugs are in blu

Re: error after upgraded to 3.11

2006-03-14 Thread Mike Jackson
> You have an older version of the stock rules. Doc fixed this > one a week or two ago, since we knew it was going to come up. Weird. rules_du_jour did not grab the newer version. I had the same issue. I deleted the stock ruleset, ran rules_du_jour again, and everything was fine. Obvious t

Re: X-Spam-Status settings

2006-03-14 Thread Shane Mullins
Yes, That is what I was looking for. Thanks Shane - Original Message - From: "Bowie Bailey" <[EMAIL PROTECTED]> To: Sent: Monday, March 13, 2006 3:44 PM Subject: RE: X-Spam-Status settings Steven Manross wrote: _TESTSSCORES(,)_ From: Shane Mullins [mailto:[EMAIL PROTECTED

SUBJ_ILLEGAL_CHARS

2006-03-14 Thread Милен Панков
Hi to all, I'm using spamassassin for years without any serious problems. Except for one. My users write messages mostly in bulgarian and the 'SUBJ_ILLEGAL_CHARS' rule very often stops good mail. I have put in my local.cf the line 'ok_languages bg en', but it doesn't fix the problem. For now I

Re: more pharmacy woes

2006-03-14 Thread Payal Rathod
On Sat, Mar 11, 2006 at 06:40:35PM +0530, Dhawal Doshy wrote: > For URIBL, see http://www.uribl.com/usage.shtml OR add this to your > local.cf I am getting an error which say, 2006-03-14_10:47:27.97266 2006-03-14 10:47:27 [17977] i: server killed by SIGTERM, shutting down 2006-03-14_10:47:35.617

Re: FP with MSGID_DOLLARS_RANDOM

2006-03-14 Thread Dhawal Doshy
Dhawal Doshy wrote: Hello, The following Message ID causes a '+3.78' (bayes+network) score for hitting a meta rule MSGID_DOLLARS_RANDOM, SA Version 3.1.x Message-ID: <[EMAIL PROTECTED]> X-Mailer: Intrapop 1.4 SMTP Component 1.0 It is a regular mail and the sender appears to be using a mail

Re: error after upgraded to 3.11

2006-03-14 Thread Dennis Davis
On Tue, 14 Mar 2006, Spamassassin List wrote: > From: Spamassassin List <[EMAIL PROTECTED]> > To: Loren Wilton <[EMAIL PROTECTED]>, users@spamassassin.apache.org > Date: Tue, 14 Mar 2006 14:21:12 +0800 > Subject: Re: error after upgraded to 3.11 > > > You have an older version of the stock rules.