![]() |
![]() |
|
Click the comments link on any story to see comments or add your own. Subscribe to this blog |
14 Oct 2020
I get a lot of mail from political campaigns. I expect a lot of us do. In my case, each campaign gets a separate e-mail address so I can track how much they pass the addresses around. (Nothing surprising, local passes them to national for the same party, stuff like that.) While I was supposed to be doing something else, I wrote some scripts to track the mail, per campaign. You can see the results, updated daily, at https://www.taugh.com/polispam.php. If it looks like one day the Republican presidential campaign sent me 15 separate messages, yup, they did. It's not entirely clear what their strategy is because they keep telling me that I am one of their TOP 100 SUPPORTERS even though I've never sent them a dime.
11 Mar 2020
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?
|
TopicsMy other sitesOther blogsCAUCE A keen grasp of the obvious Related sitesCoalition Against Unsolicited Commercial E-mail |
© 2005-2020 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.