There are filters available to do filtering with XMail based on SPF =
data.
However, there are two other important issues to fully supporting SPF.  =
One
is SASL SMTP (allowing customers to send email on port 587, but only =
with
SMTP AUTH).  You can easily bind XMail's SMTP service to both ports 25 &
587, but XMail does not yet have any way of setting up port 587 to be =
SMTP
AUTH only.  The other issue is SRS (Sender Rewriting Scheme).  With SRS =
and
SASL SMTP support, it is not practical to enable SPF within our own DNS
records.  It is unfortunate, because I would love to be able to fully =
deploy
SPF to protect all of the domains I host against forgery.  At this =
point,
all I can do with XMail and the existing SPF filters is filter incoming
email to prevent forged emails from arriving.  It's a start, but more =
work
still needs to be done.  I'm really excited for the day when XMail =
supports
SASL SMTP and SRS.

Some people will argue that SASL SMTP and SRS could be implemented using
perl or bash filters.  I think that is the wrong move, since these are =
core
functions that need to be as fast as possible to scale properly.  =
Spawning
separate processes instead of handling the task in process is slower,
especially on Windows platforms.

For more info on SRS:
http://spf.pobox.com/srspng.html
http://spf.pobox.com/emailfwdpng.html

For more info on SASL SMTP:
http://www.faqs.org/rfcs/rfc2222.html


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] =
On
Behalf Of Tom Banting
Sent: Tuesday, October 12, 2004 11:13 AM
To: [EMAIL PROTECTED]
Subject: [xmail] SPF

Has anyone added SPF functionality to xmail?

-
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]

Reply via email to