James Lay wrote:
-----Original Message-----
From: Wolfgang Zeikat [mailto:[EMAIL PROTECTED]
Sent: Friday, October 13, 2006 9:49 AM
To: users@spamassassin.apache.org
Subject: Re: Is there any way to score this?
On 10/13/06 17:34, Wolfgang Zeikat wrote:
Received =~ /from \S{1,30} \(unknown
\[\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}\]\)\s+by\s+your\.smtp\.server\.de
sy/
Replace "your.smtp.server" by your server's name ...
Oops, and leave out "\.desy" of course ;) And - just to make sure - that's a
header rule.
Cheers,
wolfgang
So does:
header UNKNOWN Received =~ /from \S{1,30}
\(unknown\[\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}\]\)\s+by\s+mail\.slave-tothe-b
ox\.net/
score UNKNOWN 3
describe UNKNOWN Unknown hosts
Look about right?
James
Hi all,
excuse me for my ignorance, but is this really the correct approach
right now,
since it is quite a lot of badly configured DNS servers out there.
Should this not be handled by the SMTP server as is instead!
And return an error code of 421 or something like this.
Like AOL has implemented at their servers, you will be informed as
sender about the problem,
with an URL link to http://postmaster.info.aol.com/errors/421dnsnr.html
Or if one should have this above Rule, me my self would not for the time
being, have that high of a score,
check out your legitimate and non SPAM incoming mails, you will find
tons of e-mail server IP's that is not registered with a good PTR.
And even further, if this test is done at SMTP server level, there will
not be that much of CPU consuming processing to check if the sender is
an "unknown" sender IP.
/Micke
