Semantics. I understand your point completely, however, you might have
missed my point.
WCSMTP is a single exe system with a multi-threaded Receiver, Router, and
Sendmail system system. The same is true for MS exchange.
The receiver "personality" is
MTA - if the mail is non-local
MDA - if the mail is local
I believe this is the common "semantics" used in the SMTP world.
The received mail is queued for the router who makes the final decision to:
For Remote Domains - Queue it for the send mail worker thread
For Local Domains - Queued for our independent GATEWAY processor
Our GATEWAY (wcMAIL) imports/exports the mail into/from the user's bin.
My point?
Why would you go into such details simply to catalog what "SMTP
servers/products" support SPF?
If we are going to say "MTA" for some, then you need to do it for ALL. MS
Exchange is a MTA just like the rest.
Anyway, thanks. I really don't care. But it doesn't make sense to make such
a distinction unless Meng et al are doing so for "marketing promotion"
reasons. Like I said, if you going to break down the protocols, how they
work, what part of the 3 basic parts of an complete SMTP server it works,
then that's another story. :-)
Sincerely,
Hector Santos, CTO
Santronics Software, Inc.
http://www.santronics.com
305-431-2846 Cell
305-248-3204 Office
----- Original Message -----
From: "Theo Schlossnagle" <jesus(_at_)omniti(_dot_)com>
To: <spf-discuss(_at_)v2(_dot_)listbox(_dot_)com>
Cc: "Theo Schlossnagle" <jesus(_at_)omniti(_dot_)com>
Sent: Thursday, December 16, 2004 11:47 PM
Subject: Re: [spf-discuss] Wildcat! SPF Support
On Dec 16, 2004, at 11:30 PM, Hector Santos wrote:
I mean, what is a MTA?
MTAs are used for transit, both the sending and receiving side are MTAs.
In fact, you are technically incorrect by saying MTA because that
means the
"sender component" of a SMTP server is SPF compliant. No. If you
want to
be specific, it is a list of MDAs (the receiver) that is important in
this
case.
No. I disagree completely with this. An MDA is for delivery into
mailboxes. Cyrus is a perfect example of an MDA and it doesn't even
speak SMTP. Many MTAs also incorporate MDA featuresets as well (like
Exim, Postfix, Sendmail, etc. as they support writing
maildir/mailspool/etc.).
In order to enforce SPF on the inbound side you need to be an MTA. And
more so, delivery into a user's mailbox is not required. So, an MTA on
the edge of ones network can implement SPF checking and enforcement on
inbound messages and just store and forward legitimate mail to the
inside.
But why confuse people? I would suggest to Just note down the
supportive
SMTP servers/product names. Simple.
I would say that the list should be Mail Transport Agents (MTAs) that
support SPF validation and enforcement for inbound SMTP transactions.
Specifically stay away from language like: SPF compliant MTAs as
outbound only MTAs can be SPF compliant by simply saying they are.
// Theo Schlossnagle
// Principal Engineer -- http://www.omniti.com/~jesus/
// OmniTI Computer Consulting, Inc. -- http://www.omniti.com/
// Ecelerity: fastest MTA on Earth
-------
Sender Policy Framework: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
Read the whitepaper! http://spf.pobox.com/whitepaper.pdf
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com