More than a decade ago I was included in one of these. It wasn’t work related per se, but the address list included a lot of experienced, BTDT, names-on-RFCs technology folks.
Yeah, even they got stuck in the mess of replying all, unsubscribing, lecturing people about not replying to all. It was a mess, but funny given the names involved. #neverdothis #noreplytoall
When you spend most of your day working on email and spam issues, it starts to cross into all aspects of your life. In October, I was amused by authors who find names in spam, SMTP-related t-shirts on camping trips, and spam that makes you laugh. Maybe I need a vacation?
We were quite busy with conference presentations and client work this month, but took time to note the things that captured our attention, as always. We highlighted a few things we enjoyed reading around the web: Brian Krebs’ Reddit AMA, the results of Jan Schaumann’s survey on ethics in internet operations, and a great post on Usenet from Joe St. Sauver.
In industry news, we covered a few glitches that are worth noting, in case you missed them: Yahoo FBL confirmation emails, Google postmaster tools, Network Solutions email, and weird Lashback listings. Even though these have mostly been resolved, it’s useful to keep track of the types and frequency of these sorts of issues, as they can significantly impact your deliverability and may be useful as your clients or business stakeholders raise questions about campaign performance.
Steve contributed a few key technical posts this month, including a short post on IPv6 authentication issues, following up on the issues he outlined back in July. He also noted Gmail’s upcoming move to DMARC p=reject, which is notable for the ways they are are looking to mitigate risks with their ARC proposal. Finally, he wrote that it’s worth looking at false positives every now and then, as it can reveal interesting patterns in the ESP landscape.
Finally, a good suggestion from the best practices file: engagement through confirming user names, and a not-so-good plan for an app that’s sure to invite abuse and harassment.
Al over at SpamResource reports that the next generation of Apple’s iOS has support for the list unsubscribe header.
To the best of my knowledge, this is the first time an independent email client has built in support for the List-Unsubscribe header. Microsoft and Google support it, but only in their webmail system. Hopefully other mail clients will follow suit.
I 
received a message on our 800 number. “This is Mark from a-website.example. Your customers are complaining to me that they are not getting my mail. And you’re blocking mail from me. Explain this to me!”
I called him back and left a message: “I think you’re confused and I probably can’t help you.”
A few minutes later, Mark returns my call.
L: Hi, this is laura.
M: Who are you? You called me, you must be from Clearwire!
L: No, I’m not with Clearwire, I’m with WttW.
M: Then why is your phone number on the Clearwire website?
L: I don’t know, but this isn’t Clearwire. The Clearwire website is redirecting to Sprint. They got bought out a while ago.
M: Redirecting to Sprint? What does that mean? Your phone number is on Clearwire’s website. You must be with Clearwire.
L: No, really, I’m not.
M: Why is your phone number on their website?
L: I don’t know. But this is not Clearwire. (I start searching the blog because I remember some post somewhere about Clearwire.)
M: Well, who are you?
L: I run a delivery consulting firm. Is it possible you found my website and the blog post that says all clearwire.net addresses are being discontinued April 15, 2015?
M: They’re gone?
L: Yes, for more than a year now.
M: Oh.
scene
That blog post is the #1 google hit if you search for clearwire.net.