Mike,
One of SpamAssassins weaknesses is that it only has access to the
message body of the email. It can't create rules to detect certain
behaviours of the connecting host during delivery.
[...]
I was thinking along the lines of an interface where the mta connects to
SpamAssassin when a
On Sat, May 16, 2009 at 01:36, Mark ad...@asarian-host.net wrote:
-Original Message-
From: Mike Cardwell [mailto:spamassassin-us...@lists.grepular.com]
Sent: vrijdag 15 mei 2009 11:44
To: Spamassassin Mailing List
Subject: An SMTP transaction, SpamAssassin interface
I know
-Original Message-
From: jma...@gmail.com [mailto:jma...@gmail.com] On Behalf Of Justin Mason
Sent: zaterdag 16 mei 2009 10:21
To: Mark
Cc: Spamassassin Mailing List
Subject: Re: An SMTP transaction, SpamAssassin interface
On Sat, May 16, 2009 at 01:36, Mark ad...@asarian-host.net wrote
On Sat, 16 May 2009, Mark wrote:
From: jma...@gmail.com
there's a much simpler way -- just record the info in synthetic headers,
...as I initially suggested. :)
But that approached WOULD require a change to the MTA
No, it wouldn't. Milters can inject headers.
One of SpamAssassins weaknesses is that it only has access to the
message body of the email. It can't create rules to detect certain
behaviours of the connecting host during delivery.
For example, during SMTP. If the connecting client sends:
MAIL FROM: u...@example.com
Instead of:
MAIL
hi -- this stuff is generally recorded in the Received header, and SA
will act on it if it's there. that's the place to do it...
--j.
On Fri, May 15, 2009 at 09:42, Mike Cardwell
spamassassin-us...@lists.grepular.com wrote:
One of SpamAssassins weaknesses is that it only has access to the
Justin Mason wrote:
hi -- this stuff is generally recorded in the Received header, and SA
will act on it if it's there. that's the place to do it...
The STARTTLS example is recorded in the received headers, yes. None of
the other 3 examples are recorded in the received headers though...
Mike Cardwell wrote:
Justin Mason wrote:
hi -- this stuff is generally recorded in the Received header, and SA
will act on it if it's there. that's the place to do it...
The STARTTLS example is recorded in the received headers, yes. None of
the other 3 examples are recorded in the
Mike Cardwell wrote:
One of SpamAssassins weaknesses is that it only has access to the
message body of the email. It can't create rules to detect certain
behaviours of the connecting host during delivery.
MAIL FROM:u...@example.com SIZE=12345
am i mistaken, or is SIZE only offered if the
Mike Cardwell wrote:
One of SpamAssassins weaknesses is that it only has access to the
message body of the email. It can't create rules to detect certain
behaviours of the connecting host during delivery.
MAIL FROM:u...@example.com SIZE=12345
On 15.05.09 07:28, Michael Scheidell
Michael Scheidell wrote:
One of SpamAssassins weaknesses is that it only has access to the
message body of the email. It can't create rules to detect certain
behaviours of the connecting host during delivery.
MAIL FROM:u...@example.com SIZE=12345
am i mistaken, or is SIZE only offered if
Mike Cardwell wrote:
Mike Cardwell wrote:
Justin Mason wrote:
hi -- this stuff is generally recorded in the Received header, and SA
will act on it if it's there. that's the place to do it...
The STARTTLS example is recorded in the received headers, yes. None
of the other 3 examples are
that would trash everyone running cisco firewalls with smtp fixup (or as
we call it here, smtp screwup)
hm?
http://www.google.com/search?q=cisco+smtp+fixup
http://www.issociate.de/board/post/195084/SMTP_Fixup_--_On_or_Off???.html
Telnet (someone who does NOT use smtp screwup on cisco pix:
On Fri, 15 May 2009, Mike Cardwell wrote:
I was thinking along the lines of an interface where the mta connects to
SpamAssassin when a connection comes in, and it then sends the full smtp
transaction to SpamAssassin as it happens.
Ugh. Why alter SA that much? It would be better if the MTA
On Fri, 15 May 2009, Mike Cardwell wrote:
For example, during SMTP. If the connecting client sends:
MAIL FROM: u...@example.com ...
That is a *high* indicator that the email is going to be spam. I haven't
found a real mail server that adds that whitespace it's self...
I have. I get
-Original Message-
From: Mike Cardwell [mailto:spamassassin-us...@lists.grepular.com]
Sent: vrijdag 15 mei 2009 11:44
To: Spamassassin Mailing List
Subject: An SMTP transaction, SpamAssassin interface
I know this would be a massive job, would be resource hungry, and
would also require
16 matches
Mail list logo
