Re: Parsing Received Headers

2007-09-01 Thread John Rudd
Bret Miller wrote: Received: from [206.74.184.2] (HELO [206.74.184.2]) by mail.wcg.org (CommuniGate Pro SMTP 5.1.11) ... Meaning that there was no RDNS for 206.74.184.2 Actually, CommuniGate sometimes does that even when RDNS _is_ available. For example: Received: from [128.114.12

Re: header /^\Q...\E$/m

2007-09-01 Thread Kai Schaetzl
File this at Bugzilla. This may look like an unnecessary extra step for you, but it really isn't. Mailings flow by and are easily forgotten, tracker items are not. It's so much easier for developers to handle them, even a year later. I see this in the projects I'm involved myself. Something tha

Re: header /^\Q...\E$/m

2007-09-01 Thread Kai Schaetzl
wrote on Sat, 01 Sep 2007 20:52:41 +0800: > I was just struggling for an hour with the meaning of > > It might help to quote what you want to match. Sorry, I didn't mean to be cryptic. I just wanted to point out it might help if we can see the original header you want to match, you posted only

Re: Parsing Received Headers

2007-09-01 Thread Bob Proulx
Bret Miller wrote: > Received: from [206.74.184.2] (HELO [206.74.184.2]) >by mail.wcg.org (CommuniGate Pro SMTP 5.1.11) > ... > Meaning that there was no RDNS for 206.74.184.2 and when it said helo, it > said "HELO [206.74.184.2]". However, SA is not parsing it that way. So, can > anyone te

Re: header /^\Q...\E$/m

2007-09-01 Thread jidanni
MP> "Patches Welcome" All you have to do is (using your much greater knowledge of the program) is to add a paragraph to complement The 'raw body' of a message is the raw data inside all textual parts. The text will be decoded from base64 or quoted-printable encod

Re: header /^\Q...\E$/m

2007-09-01 Thread Michael Parker
[EMAIL PROTECTED] wrote: > < so whenever one uses a ^ or $ in a pattern, one is almost obliged to > < append a /m flag, otherwise one risks being at a mercy of malicious > < senders... Depending on a situation, this can be a security risk. > > Sure wish Mail::SpamAssassin::Conf would mention all t

Re: header /^\Q...\E$/m

2007-09-01 Thread jidanni
I was just struggling for an hour with the meaning of > It might help to quote what you want to match. when the following arrived, thank goodness: < SpamAssassin joins all mail header fields with the same header name < into one multine string of header field bodies, Ah, no wonder $ matched but ^ d

Re: header /^\Q...\E$/m

2007-09-01 Thread Mark Martinec
On Saturday September 1 2007 05:06:24 [EMAIL PROTECTED] wrote: > If > header J Delivered-To =~ /.mailing list [EMAIL PROTECTED]/ > doesn't match this mail, but > header J Delivered-To =~ /mailing list [EMAIL PROTECTED]/ > does, why doesn't > header J Delivered-To =~ /^mailing list [EMAIL PROTECTED]

Re: nodigest [EMAIL PROTECTED]

2007-09-01 Thread Matus UHLAR - fantomas
On 01.09.07 09:59, sinkomai wrote: > From: sinkomai <[EMAIL PROTECTED]> > Date: Sat, 1 Sep 2007 09:59:03 +0100 > Subject: nodigest [EMAIL PROTECTED] > To: users@spamassassin.apache.org > > > > ... are you aware that mail sent to list will end up in the list and thus resent to its recipients? Co

nodigest [EMAIL PROTECTED]

2007-09-01 Thread sinkomai
...

Re: header /^\Q...\E$/m

2007-09-01 Thread Kai Schaetzl
It might help to quote what you want to match. Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com