It is a good idea, however...
Here are a few things to know about what you would like to do:
1) You could create your own Received: headers before passing the email =
on
to SA. No problems. Then I would suggest you strip them back off after =
you
get the results back from SA...
2) I suspect XMail's author doesn't write the Received: header at the
post-data stage because of a couple reasons...
a) Here you can get the untouched original email.
b) What would you put in the "for" section if there were multiple
recipients? (More than one RCPT TO)?
3) If you reject a SPAM after it has been sent to you, you didn't gain
anything... the time and bandwidth has already been wasted.
4) Rejecting spam often means the sending server will attempt endlessly
again and again even if you pass a 554 or other similar fatal error....
meaning that the one 40KB spam now can take up 400KB or more bandwidth =
as
the spammer keeps trying to resend.
Personal experience tells me that you need to just accept it, score it,
label it as "[SPAM]", and if you wish, delete it, or move it to another
folder if it scores high enough (I use XMail-WAI web interface... so =
spams
show up in a spam box folder).
When I did what you propose, my bandwidth use shot up over 10x!
Now, an idea I have would be to combine the SA scoring with perhaps a
greylisting? That's what I am looking at writing up right now...
1) PRE-DATA: check triplets database, temp error if in list and not =
enough
time has past.
2) POST-DATA: check SA score for email, if above a 5, then temp error it =
and
add to greylist.
I like this modified form of greylisting because it allows low scored =
emails
to be delivered immediately (which I often want when buying things =
online,
retrieving lost password for websites, etc). Only high-scoring emails =
get
delayed.
Any comments on my idea?
------------------------------------------------------------
Jason J Ellingson
Sr. Web Software Developer
615.301.1682 : nashville
612.605.1132 : minneapolis
www.ellingson.com
[EMAIL PROTECTED]
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] =
On
Behalf Of S=F6nke Ruempler
Sent: Tuesday, January 11, 2005 2:04 AM
To: [email protected]
Cc: Henrik Steffen; Alexander Hagenah
Subject: [xmail] Spamassassin and SMTP Filter
Hi,
I thought about integrating SA into a XMail SMTP Filter, so that it =3D
would be
possible to reject SPAM directly. At the SMTP Stage, XMail hasn't put =
=3D
it's
headers into the spoolfile - IMHO SA *needs* this headers for looking up
HELO/IP/etc. Now Davide could change the code that the headers are there =
=3D
in
the spoolfile at this stage, but I guess he doesn't want to and he has =
=3D
good
reasons for this. I think it's possible to build the "Received" header =
=3D
from
scratch from the INFO-DATA by my own, prepend it to the spoolfile and =
=3D
pass
the whole thing (without the XMail Headers) to spamc.
Any thoughts?
-
To unsubscribe from this list: send the line "unsubscribe xmail" in
the body of a message to [EMAIL PROTECTED]
For general help: send the line "help" in the body of a message to
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe xmail" in
the body of a message to [EMAIL PROTECTED]
For general help: send the line "help" in the body of a message to
[EMAIL PROTECTED]
