Its the same sort of answer with 3rd-level domains. www.example.com is for the web, ftp.example.com is for FTP, why not mail.example.com?
In order to maintain control over the authentication records, everything must be under a single TLD. While individual entities could agree to set up a common third-level domain to indicate responsible email, there would be nothing preventing an irresponsible sender from setting up the same domain and sending large amounts of spam. When it comes to spam, a deficiency of the Sender Authentication Technologies (SAT) is that they do nothing to prevent a spammer from registering a large number of “throw-away” domains, setting up SAT records on them, spamming from them until they are blocked, and then moving on to the next domain. The .mail sTLD Sponsor Organization-monitored zone is really the key that makes this system function spam-free. If you spam, you lose the use of the domain.
Related Questions
- I want to run a web and/or ftp server on one of my internal system, how can I let users on the internet to access my server behind Comtun firewall?
- Its the same sort of answer with 3rd-level domains. www.example.com is for the web, ftp.example.com is for FTP, why not mail.example.com?
- Keeping a Travel Journal - Are Temporary Web Logs the Answer?
