|
|
|
Click the comments link on any story to see comments or add your own. Subscribe to this blog |
07 Sep 2019
The DNS has always had a few names for use as examples in documentation, domains example.com, example.net, example.org, and example.edu. In 1999 RFC 2606 formally reserved the first three. There's nothing technically special about these names, which have normal WHOIS and DNS entries, managed by IANA. Until recently, that meant that even though none of them handle any e-mail, mail sent to them by mistake worked badly.
28 May 2019
03 May 2018
Recently I've been working on EAI mail, looking at what software is available (Gmail and Outlook/Hotmail both handle it now) and what work remains to be done. A surprisingly tricky part is assigning EAI addresses to users. In traditional ASCII mail, the local part of the address, what goes before the @ sign, can be any printable ASCII characters. Although an address like %i()/;~f@examp1e.com is valid, and mail systems will handle it, users don't want addresses like that. A good address is one that is easy to remember, easy to tell someone over the phone, and easy to type. Mail systems all give senders some help when interpreting addresses. If an address is Bob@example, they'll accept bob@ or BOB@. If the address is joe.smith@, they'll accept Joe.Smith@ and often variations in punctuation like joesmith@ without the dots. The flip side of this is that you don't assign different addresses that are too similar. While it is techincally possible that BOB@ and bob@ could deliver to different mailboxes, nobody does that. Similarly, nobody makes joesmith@ and joe.smith@ different. (They may not both work, but if they do, they're the same mailbox.) The domain (the part of the address after the @ sign) has to follow the DNS rules, which don't allow any fuzzy matching other than ASCII upper and lower case. How does all this extend into EAI mail?
21 Apr 2017
Classified ad site craigslist is famously protective of its contents. While they are happy for search engines like Google to index the listings, they really, really do not like third parties to scrape and republish their content in other forms. In 2013 craigslist sued a company called 3taps which had created an API for craigslist data. They also sued real estate site Padmapper, which showed craigslist and other apartment listings on a map, something craigslist didn't do at the time. After extensive legal wrangling, 3taps eventually gave up and in 2015 paid craigslist $1 million and shut down. Craigslist donated the money to the EFF which was a little odd since the EFF had generally supported 3taps. One of 3taps' other customers was another real estate site Radpad, which kept showing craigslist listings after 3taps shut down.
26 Jan 2017
In September I wrote about a proposal to allow one-click unsubscriptions from mailing lists without user interaction. After taking a rather tortuous path through the IETF, it's now been issued as RFC 8058. The changes since September are quite minor, mostly tightening up some details to prevent various attacks from fake unsub requests. Now that it's official, I expect email service providers will start implementing it, and we'll have an arguably better alternative to mail feedback loops to tell mailers when their mail is unwanted.
|
TopicsMy other sitesOther blogsCAUCE A keen grasp of the obvious Related sitesCoalition Against Unsolicited Commercial E-mail |
|||||||||||||||||||||||||||||||||||||||
© 2005-2018 John R. Levine.
CAN SPAM address harvesting notice: the operator of this website will
not give, sell, or otherwise transfer addresses maintained by this
website to any other party for the purposes of initiating, or enabling
others to initiate, electronic mail messages.
