Recent Posts

Testing your opt-out process

When was the last time you tested your opt-out process? Did you just click the unsubscribe link to see if the page loaded? How did you confirm the email address was unsubscribed?
If you have a Gmail account, Gmail allows you to use unlimited aliases. For example, if your Gmail email address is josh@gmail.com, you can add the + symbol to your email address to create an alias. An example of an alias would be josh+test1@gmail.com. Sending an email to josh+test1@gmail.com gets delivered to the mailbox for josh@gmail.com.
On your next mailing add a Gmail alias email address like josh+unsubtest06192015@gmail.com to be included with the mailing. After sending the mailing, find the email sent to the alias address and go through the unsubscribe process. After unsubscribing, log into your ESP or mailing software to confirm that the alias email address was successfully unsubscribed. Testing the unsubscribe process ensures that the landing page for the unsubscribe is working and that your ESP is registering the unsubscribe request.
A few reminders about your unsubscribe page:

On Father's Day

always be batman
I’m on quite a few mailing lists for companies whose main product is sending gifts: food hampers, jewelry, flowers, overpriced desk toys and so on. They tend to ramp up their volume before appropriate holidays such as Christmas, Mother’s Day, Thanksgiving, Valentine’s Day or Father’s Day and target their promotions to those particular holidays.
One recipient may have a toxic relationship with their Mother and not want to be reminded of Mother’s Day, another may have recently lost their Father and not want to revisit that distress every time they open their mail client in June, yet another may be recently divorced and really not want to see diamonds and roses in their inbox right now.
You should try and avoid sending mail that will distress your recipients. You should do that because you’re a compassionate human and you want to treat your recipients as humans. But if you need an ROI argument to justify the effort needed to do so… those recipients will associate your brand with that distress and then they’ll buy less or they’ll unsubscribe and you’ll lose their business entirely – even if they are interested in and responsive to your offers for the rest of the year.
How do you identify those recipients? Maybe just ask them. Or add an “Unsubscribe from Father’s Day promotions” link next to the “Unsubscribe” link – it’s not hard to do. Help your customers segment your list for you.

Google Apps for ISPs is gone

Google Apps for ISPs is being shut down. While this was a scheduled end of life, apparently some users weren’t notified (always keep the contact email address up to date at your vendor!) and other users were told that it would be discontinued in July and were surprised when their service was turned off a month earlier than they expected.
I’ve not seen any reports of mail bouncing due to this yet, but it’s likely that some consumer ISPs will be scrambling to migrate to new email providers and their inbound mail may be a mess for a while. If you see domain-wide problems at consumer domains, check to see if their MXes point at the google aspmx cluster.
It seems to be a rolling shutdown, and some ISPs have apparently had their service extended by a few days or weeks, so issues may start with some domains throughout the month.

Yahoo Feedback Loop

If you are utilizing the Yahoo Complaint Feedback Loop, you should have received an email today about an upcoming change to the CFL.
The message received was:
“On June 29, 2015, we will transition Yahoo Complaint Feedback Loop (CFL) administration from Return Path to Yahoo Customer Care.
We will continue sending spam reports during this transition. However, you will need to save existing CFL information as it will not be available after the transition.
To save the existing CFL information:

ROKSO lawsuit settled

Earlier this year Ken Magill reported that a judge in the UK was allowing a libel case against Spamhaus to go forward. I thought for sure I’d blogged about the case at the time, but apparently I didn’t.
The short version is that today Spamhaus announced the lawsuit was settled and the complainants paid for Spamhaus’ legal fees.
As with most legal cases the details are complex and convoluted. Let me try to sum up.

Image Blocking

I received this email earlier this week, an email that I wanted but this is how it arrived.
email example 1
The email contained a single image link, a text line of who the message was sent to, the senders name, address, and finally an unsubscribe link.
Good news, the email is CAN-SPAM compliant! Bad news, I have no idea what the content of the message is and it looks somewhat spammy. The email was sent to my Junk Folder and all images were blocked. As a good netcitizen, we’re trained not to click links if we’re not sure what they are.
Here is another message I received around that same time and also had the images blocked. I immediately recognize the domain name, bowling.com and there is text that mentions bowling shoes, balls, and bags. Being an avid bowler, I wanted this message and I will be adding them to my safe senders list in Outlook.
email example 2
The good news for marketers who rely on image based emails is Gmail and many mobile mail clients will auto-load images but there are still many clients that will only display images if the user sets the sender as a trusted sender. If you are sending a Welcome Message, it’s best to include text along with your images so the recipient can recognize your email and will then add you as a trusted sender. You can also segment your list by users who are opening the images. The recipients who have not loaded the images would get a different version of the message that includes more text.

Another M3AAWG on the books

Another M³AAWG is over. It was great to see old friends, some of whom I’ve known for more than a decade. It was even better to meet new people who I’m sure will become old friends. The conference has grown so much bigger than my first MAAWG back in San Diego (MAAWG 3 in 2005). That was maybe a hundred people. Today M³AAWG has more members companies than were at the original conference.
I’m still processing all the information from the conference. I learned a lot of new things. I had some of my knowledge confirmed. I’ve had some of my beliefs challenged.
It’s always great to see everyone. And thank you for everyone who went out of your way to tell me you read the blog. It’s great to know that I’ve made some of you think and helped you learn and given you backup when you need to talk to bosses or customers.
Regular blogging resumes tomorrow.
Sláinte

Whirlwind that is M3AAWG

It’s been a great conference, and it’s only about half done. As is common at these conferences, I write down lots of things we should do and need to publish. The difference is now that we are growing I may have the time to put the polish on them and get them published.
Today’s keynote discussed the economics of botnet mitigation. Michel van Eeten from Delft University of Technology presented information compiled from some different datasets about botnets.
Good news
Botnet infection rates are relatively stable. They’ve not spiraled out of control like some people were predicting.
Interesting news
More than 50% of bot infections are contained on 50 ISPs in the entire world.
Bad news
Centers set up specifically to fix botnet infections don’t really have a big impact on infection cure rate.
Good news
ISP actions and walled gardens do have an impact on infection cure rates.
The biggest take away from the session is that ISPs are critical in both protecting from infection and helping users cure infection once it happens.

2016 Mary Litynski Award

The Mary Litynski Award is presented by M³AAWG to people who have done extensive work outside the public eye over a significant period of time. At the Dublin conference the award was presented to Rodney Joffe. A lot of other people will talk about Rodney’s accomplishments, including his role in the founding of Genuity, his work with the DMA in the early days of spam, his efforts against SMS spam and his efforts to secure the Internet infrastructure. But I have a much more personal perspective.
Rodney was seminal in changing my life and career path. Back in 1999, Rodney asked Steve to look into some DNS creativity he was testing. A few months later, Rodney invited Steve to join a new company he was founding based on that DNS creativity. We moved out the the Bay area and Steve started working for UltraDNS in early 2000.
Moving out to the Bay Area triggered my career shift into anti-spam and anti-abuse. I started working at MAPS (now Trend Micro) in their experimental consulting service division. We were the “carrot” end of the equation, where our job was to help companies minimize the abuse coming out of their networks.
After MAPS went through a round of layoffs in 2001, Rodney started recommending me as an email consultant to some of his connections in the marketing world. This work was a success and directly led to the founding of Word to the Wise and everything that flows from that.
M³AAWG has published a video where Rodney discusses his role in the history of spam and some of the other things he’s done to fight junk advertising (both fax and SMS spam). He sued junk faxers in small claims court. He was instrumental in getting SMS spam covered under the TCPA. He wrote the first global opt-out list supported by both the DMA and the ISPs and proved that global opt-out would never work. He literally pulled the plug on spamming customers.
Rodney says he’s “Not smart, just the guy who carries the bags of money and helps the smart people get things done.” I certainly don’t believe that is true. He has done things on the global scale to make the Internet a safer place for end users. But my appreciation is much more personal. I will forever be grateful to him for starting us on this path and the help and advice he gave us so many years ago.

May 2015: The Month in Email

Greetings from Dublin, where we’re gearing up for M3AAWG adventures.
In the blog this month, we did a post on purchased lists that got a lot of attention. If you’ve been reading the blog for any length of time, you know how I feel about purchased lists — they perform poorly and cause delivery problems, and we always advise clients to steer clear. With your help, we’ve now compiled a list of the ESPs that have a clearly stated policy that they will not tolerate purchased lists. This should be valuable ammunition both for ESPs and for email program managers when they asked to use purchased lists. Let us know if we’re missing any ESPs by commenting directly on that post. We also shared an example of what we saw when we worked with a client using a list that had been collected by a third party.
In other best practices around addresses, we discussed all the problems that arise when people use what they think are fake addresses to fill out web forms, and gave a nod to a marketer trying an alternate contact method to let customers know their email is bouncing.
We also shared some of the things we advise our clients to do when they are setting up a mailing or optimizing an existing program. You might consider trying them before your own next send. In the “what not to do” category, we highlighted four things that spammers do that set them apart from legitimate senders.
In industry news, we talked about mergers, acquisitions and the resulting business changes: Verizon is buying AOL, Aurea is buying Lyris, Microsoft will converge Office365/EOP and Outlook.com/Hotmail, and Sprint will no longer support clear.net and clearwire.net addresses.
Josh posted about Yahoo’s updated deliverability FAQ, which is interesting reading if you’re keeping up on deliverability and ESP best practices. He also wrote about a new development in the land of DMARC: BestGuessPass. Josh also wrote a really useful post about the differences between the Mail From and the Display From addresses, which is a handy reference if you ever need to explain it to someone.
And finally, I contributed a few “meta” posts this month that you might enjoy: