Re: designate an email address for testing at any provider

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I'm puzzled. If you said the logistics are too time-consuming to carry out because providers are unlikely to agree on a guaranteed-to-bounce address, that would make sense and I'd probably drop it.

But you mention routing, mapping of domains to providers, and many ways of handling mail. How email is routed from anyone to a provider has nothing to do with what the address says to the left of the "@" sign. How many domains a provider has is relevant only insofar as each domain represents an email service provider. The policies of ICANN, IANA, a TLD registry operator, or a registrar or reseller hardly matter. If they don't use a domain at all but only an IP address, either IPv4 or IPv6, that doesn't matter either. If what's on the right of the "@" sign gets to an email service provider, what's on the left should guarantee a bounce. There should be one bouncing address at each domain or IP. Who handles it once an email arrives at a domain or an IP address does not matter. What method they apply to handling it doesn't matter. All they have to do is bounce it. How a provider does the bouncing is up to the provider. Probably if I email
 billgates@xxxxxxxxxxxxx it'll bounce (Bill probably has some other address, although I haven't tried). They already know how to bounce. That step doesn't have to change.

The only difficulty is picking the one address no one has given to a customer. That's probably not impossible.

-- 
Nick


      
_______________________________________________

Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]