Hector Santos wrote:
If both the primary and secondary MX servers are administered by the
same organization or by closely-cooperating organizations, this works
well. However, there are ISPs that offer "secondary MX service" to
their customers, and they are unlikely (or sometimes unable) to make
special arrangments to synchronize user lists.
We offer a special utility to our customers who subscribe to these
secondary MX services which allows them to export their user email
addresses, translations, aliases, etc, which is then sent to the
service.
That's a neat feature, but an ISP that needs to support dozens of
different SMTP servers and many different ways of maintaining
user lists is still not going to be happy. A standard way to do
this sort of thing would be welcome.
Perhaps an RFC for querying whether or not an e-mail address is
valid using DNS? :-)
host -t txt some.email.AT.example.com.email-verification-zone.example.com
After all, there are already well-established and widely-used mechanisms
for synchronizing DNS data. (I skip tedious details like restrictions
on local-part of e-mail addresses, etc.)
Regards,
David.