Fotis,
There are many possible situations where an inbound MX would not necessarily
be authorized to send mail for a domain. In today's environment of hosted
email, hosted spam filtering, etc., the published MX may have no
relationship to the actual sending machine. This is where spf_guess can be
used, but it should be left out of the SPF specification.
Marc Alaia
-----Original Message-----
From: Fotis Georgatos [mailto:gef(_at_)eexi(_dot_)gr]
Sent: Thursday, March 04, 2004 7:02 AM
To: spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
Subject: [spf-discuss] A note on the semantic of MX records
Dear All,
the very original meaning of an "MX record" in DNS, is Mail Exchanger.
As such, in *absence* of SPF information in TXT of a given domain,
any single host defined as MX in a zonefile should be treated,
by default, as a valid sender AND receiver of email.
Such a filtering decision, would be beneficial to thousands
if not millions of domain owners by not blocking the hosts
that are obviously authoritative for sending emails.
On the contrary, by not doing so we will severely damage a great
number of small Internet users that don't have sysadmins or the
technical means to easily implement SPF (think of appliances).
PS.
In the future, we might end up with MS and MR records in DNS,
standing for Mail Senders and Mail Receivers respectively.
Until that day, we should consider MX as representing both,
rather cutting with a knife non SPF-adopters. If not, why?
all yours,
Fotis Georgatos
Network Engineer,
Secretary General of Hellenic Association of Internet Users
-------
Sender Policy Framework: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
Latest draft at http://spf.pobox.com/spf-draft-20040209.txt
Wiki: http://spfwiki.infinitepenguins.net/pmwiki.php/SenderPermittedFrom/
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname(_at_)©#«Mo\―HέάξU;±?Φ?Ν΅ψ?ʽ