Mandrill changes

Last week Mandrill announced that they were discontinuing their free services and all customers would be required to have a corresponding paid Mailchimp account.

Going forward, all Mandrill users will be required to have a paid monthly MailChimp account and verify ownership of all sending domains. Important changes to Mandrill

mc-logo-2380f23aOn March 16th all new Mandrill users will be required to create a Mailchimp account and existing Mandrill users will be able to merge their Mandrill and Mailchimp accounts. All users will have to merge accounts by April 27th.

When I saw the announcement I didn’t think it was that big a deal. Mandrill, for better or worse, has been a source of spam for a while and I knew that Mailchimp would be taking some action to clean it up. To me, this change seems really all about being able to hold customers accountable. Mandrill users will need to have real contact information, be able to verify their domains and have a valid credit card. This is a step that was, at least to me, obvious.
sparkpostWhat I wasn’t expecting was the number of companies who think this is a dumb idea and that Mandrill is giving up valuable customers. I have no doubt that Mailchimp knows exactly which customers are going to walk and has a good handle on how much revenue this will cost them. Personally, I don’t think it’s actually that much revenue. To me, the majority of companies who will be walking away are those who can’t or won’t pay $10 a month for a Mailchimp account.
I suppose there are going to be customers who are already paying and who are going to walk just because they don’t want to be restricted to having to have a real account. Or customers who don’t want to (or can’t) pass Mailchimp’s anti-fraud protections. Or customers who’ve been terminated from MC but snuck back as a Mandrill customer. These customers, to me, feel like way more trouble than they’re worth.
My viewpoints aren’t shared by a lot of other companies in the industry. The good folks over at Sparkpost, have jumped at the opportunity to provide services for companies leaving Mandrill. They’re even offering to honor Mandrill’s pricing for companies migrating. I know Sparkpost has a great team of compliance and abuse desk folks, and I hope they have thought ahead to how they’re going to deal with problems that come with freemium services. Only time will really tell if it’s enough, though.
 
 
 
 
 

Ask Laura: Will our ESP kick us off for mailing purchasers?
Laura's Speaking Events early 2016

Related Posts

Mary Litynski Award winner Jayne Hitchcock

This morning the Messaging, Mobile and Malware Anti-Abuse Working Group announced the winner of the Mary Litynski Award.
Congratulations to Jayne Hitchcock of WHO@ for her work over the last 2 decades fighting online abuse and cyberstalking.
I’ve never actually met Jayne, but I do remember following her story in the late 90s. She started off trying to protect people from being scammed by Woodside Literary Agency. In return for her work to inform and protect people the principals of Woodside set out on a multi-year harassment campaign against her.
This was in the late 90s and the Internet was very new. There weren’t any laws. There weren’t really abuse desks. We had to protect each other. Law enforcement didn’t know what to do with problems. There weren’t any laws against harassment online. The word “cyberstalking” was created by a reporter when describing what was happening to Jayne.
Jayne has been a force for good online and she and her volunteers help people who are victims of abuse online and cyberstalking. She’s been instrumental in getting anti-cyberstalking laws passed and helping law enforcement understand why online abuse is an issue and that it should be addressed.

Read More

January 2016: The Month in Email

Jan2016_blogHappy 2016! We started off the year with a few different “predictions” posts. As always, I don’t expect to be right about everything, but it’s a useful exercise for us to look forward and think about where things are headed.
I joined nine other email experts for a Sparkpost webinar on 2016 predictions, which was a lot of fun (see my wrap up post here), and then I wrote a long post about security and authentication, which I think will be THE major topic in email this year both in policy and in practice (see my post about an exploit involving Trend Micro and another about hijacked Verizon addresses). Expect to hear more about this 2016 continues.
My other exciting January project was the launch of my “Ask Laura” column, which I hope will prove a great resource for people with questions about email. Please let me know if you have any questions you’d like to see me answer for your company or your clients — I’ll obscure any identifying information and generalize the answers to be most widely applicable for our readers.
In other industry news, it’s worth noting that Germany has ruled it illegal to harvest users’ address books (as Facebook and other services do). Why does that make sense? Because we’re seeing more and more phishing and scams that rely on social engineering.
In best practices, I wrote about triggered and transactional emails, how they differ, and what to consider when implementing them as part of your email program. Steve describes an easy-to-implement best practice that marketers often ignore: craft your mails so the most important information is shown as text.
I re-published an older post about SMTP rules that has a configuration checklist you might find useful as you troubleshoot any issues. And a newer issue you might be seeing is port25 blocking, which is important if you are hosting your own email senders or using SMTP to send to your ESP.
Finally, I put together some thoughts about reporting abuse. We work closely with high-volume abuse desks who use our Abacus software, and we know that it’s often not worth the time for an individual to report an incident – but I still think it’s worthwhile to have the infrastructure in place, and I wrote about why that is.

Read More

Do you have an abuse@ address?

I’ve mentioned multiple times before that I really don’t like using personal contacts until and unless the published or official channels fail. I don’t hold this opinion just about resolving delivery issues, but also use official channels when reporting spam to one of my addresses or spam traps.
My usual complaints contain a plain text copy of the mail, including full headers and a short summary of the email address it was sent to. “This is an address that was part of a leak from…” or “This is an address scraped off my website. It’s been removed from the website since 2004” or “This address isn’t used to sign up for any mail.”
Sadly, there are a number of “legitimate” ESPs that don’t have or don’t monitor their abuse address. In some cases it’s an oversight or a break down of internal mail handling. But in most cases, it’s a sign that the ESP doesn’t actually handle abuse.
It’s frustrating to watch an ESP post long blog posts about “best practices” and “effective delivery” and “not spamming” and yet not be able to actually stop their own customers from spamming. It’s not even that I necessarily want them to disconnect their spamming customers (although that would be nice) but suppressing the address that I’ve told them was a spamtrap seems trivial. And yet, a month after my first complaint and weeks after escalating to a personal contact, I’m still getting spam.
The 5 things every ESP should do to handle spam complaints.

Read More