Stuart D. Gathman wrote:
To be clear, the Custom DNS is *not* a requirement. Setting
up the simple UDP SES validation server is very easy. The
only reason for the Custom DNS is the chicken and egg problem
of nobody actually checks SES validation servers, and lots of
people check SPF.
Point. So "pure SES" doesn't need SPF with SES name server.
For the chicken with too many eggs (MTAMARK, CSV, SPF, SES)
maybe SIQ could act as a uniform lookup interface. If SES
offers no results that could be cached the mere fact "FQDN
doesn't support pure SES" could be still managed by SIQ, to
avoid pointless queries about some missing eggs.
Tnx for info, Frank
-------
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
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