How about:
body CORRECT_FOR_EXCHANGE /This message is in MIME format/
score CORRECT_FOR_EXCHANGE -2.6
describe CORRECT_FOR_EXCHANGE Correct for MIME 'null block'
C
On Sun, 2002-02-03 at 19:59, Jason Haar wrote:
Email from our Exchange server is tallying up the score points in S
No, it really is looking for actual control characters. The regular
expression in question will match if it sees a string which starts with
'http://' then features a control character (ascii <= 0x1f except CR and
LF) before it sees another '/'. Now on the line in question, it will in
fact match
On Sun, Feb 03, 2002 at 11:56:58PM -0800, Craig Hughes wrote:
>
> Hmm, it seems that it's trying to match an actual perl regexp, so
> you'll want
>
> .*@PASSPORT.COM
>
> or such, despite the docs which say it wants a glob-style pattern.
Oops.
> The docs are right that this is probably a securi
On Sun, Feb 03, 2002 at 11:43:48PM -0800, Craig Hughes wrote:
>
> No, not really any way to avoid this... it's a fairly important part
> of NoMailAudit.pm
>
> I've looked again and again at the relevant lines and can't make out
> what could possibly be going wrong. It seems these header line
> a
Greg,
does this work with Mail::SpamAssassin::NoMailAudit instead? MailAudit
is renowned on this list for not playing nice... Probably requires the
line where the $mail object is created to be updated as well. Let me
know and I'll update in CVS.
C
On Sun, 2002-02-03 at 14:25, Greg Blakely wr
Hmm, it seems that it's trying to match an actual perl regexp, so you'll want
.*@PASSPORT.COM
or such, despite the docs which say it wants a glob-style pattern. The docs are right that this is probably a security flaw. Any perl guru have a handy snippet for converting a glob-style patte
No, not really any way to avoid this... it's a fairly important part of
NoMailAudit.pm
I've looked again and again at the relevant lines and can't make out
what could possibly be going wrong. It seems these header line aren't
matching the regex which jm built for matching email header lines, but
Email from our Exchange server is tallying up the score points in SA faster
than it should.
All the MIME messages contain the phrase:
---
MIME-Version: 1.0
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible
This is a trimmed forward from a user. If there were really control
characters in one of these urls, I'd sorta expect them to show up as I
am composing this message in vim. Hmm, perhaps it is geeing overly
greedy about what constitutesa url, and thinks it's all one big url with
the whitespace bein
Hi, folks. I've made a lot of noise here, and received a lot of useful
information from many of you. So, I thought that it would be a good
time to give a little bit back.
I finally got the "spamproxyd" smtp filter going with Postfix, and it
was all just one little thing that was missing.
In /
> It needs to treat the part after the *final* '@' symbol as case
> insensitive, but the part before it, possibly including more '@'
> characters, as case sensitive.
Unfortunately, I have both *@passport.com and *@PASSPORT.COM in my SQL table
for "whitelist_from". The From line is block caps so
On 03 Feb 2002, Craig Hughes wrote:
> Yeah, I'd seen this claim of non-compliant headers in a few places
> that seemed OK to me too -- The regex it's checking is pretty nasty
> though. I'll see if I can figure out what jm was trying to do there
> and fix it.
Cool. Hrm...
...is there any easy way
On 03 Feb 2002, Craig Hughes wrote:
> It is the right place to bring this up, and I think someone else
> mentioned something similar a while back. Don't remember what the
> resolution was.
IIRC, the conclusion was that SpamAssassin does not do correct RFC822
matching on the address part.
It nee
Yeah, I'd seen this claim of non-compliant headers in a few places that seemed OK to me too -- The regex it's checking is pretty nasty though. I'll see if I can figure out what jm was trying to do there and fix it.
C
On Sun, 2002-02-03 at 13:23, Daniel Pittman wrote:
Most messages t
Most messages that I get, these days, matches the "missing date" test,
and ends up with something like:
X-Mail-Format-Warning: Bad RFC822 header formatting in Date: Sun, 3 Feb 2002 14:31:08
+ (GMT)
Of course, that's /not/ an invalid RFC822 date, it's SpamAssassin[1]
deciding that it's not r
On Sun, 3 Feb 2002, Andrew Kohlsmith wrote:
>> I would be extremely happy to see SpamAssassin extended to recognize
>> the routine, vaguely irritating spam that is attached to "free" email
>> messages and the like.
>
> I think I will give my regexp skills a shot at this, as it is probably
> the b
It is the right place to bring this up, and I think someone else mentioned something similar a while back. Don't remember what the resolution was. I'll take a look at it. And I won't forget to take a look at it if you file a bugzilla bug :)
C
On Sun, 2002-02-03 at 06:07, Andrew Kohlsmi
Thanks, committed to CVS after some testing here.
C
On Sat, 2002-02-02 at 23:53, Michael Moncur wrote:
In 20_body_tests.cf, there's a rule for the phrase "work at home":
body WORK_AT_HOME /(?:WORK (?:AT|FROM) HOME|HOME.?WORKER)/
describe WORK_AT_HOME Informat
FreeBSD defaults to /var/mail, and apparantly $MAIL doesn't get set in
.forward, so spamassassin fails in delivery mode from there.
Oh, and can you please watch your whitespace usage. If you must use
spaces (evil), please stick to them. I see stuff like:
if (defined $prevhdr) {
»···$
Is there any reason I can't add *@PASSPORT.COM to the global whitelist (in
SQL)? I keep getting "confirm your email address" messages from various
@PASSPORT.COM (block caps) addresses and despite my having it in the
whitelist, it keeps getting detected as spam.
Regards,
Andrew
Also, is this
> Yes, if you check the archives I think I mentioned it a couple weeks ago,
> then someone else brought it up again just a couple days ago. Either study
> the headers and figure out why it is flawed, or just comment the rule out
> and go on.
For now I just 0'd the score for this test but I'll se
> I would be extremely happy to see SpamAssassin extended to recognize the
> routine, vaguely irritating spam that is attached to "free" email
> messages and the like.
I think I will give my regexp skills a shot at this, as it is probably the
biggest single factor which causes hotmail/msn email
22 matches
Mail list logo
