While many web technologies are getting much cheaper (if not completely free) some services are becoming much more expensive and time consuming. Sending emails is a perfect example.
About 10 months into existence we experienced our first misclassification as a spammer, eaming all our sent mail goes straight to bulk or trash folders. Since then it’s been a day-by-day battle to remain white-listed by all large ISPs (e.g. Hotmail, Gmail, Bellsouth, Comcast, AOL, MSN, Yahoo, etc.) We understand their services have been crushed by spam for years and they’ve have to over-aggressively filter, bounce, or silently delete incoming mail, making big headaches for innocent small and medium businesses
When we first had problems in late 2004 we were sending out 50,000 member-requested emails a week. Since mail functions are so deeply wired into core server technologies the average web engineer has no ideas how many emails are going out. I sure didn’t. But now I do. We’re sending about 400,000 member-requested emails a week. We’ve had to dedicate significant amounts of time (and thus money) to become sendmail geeks, mastering the myriad error codes, loopback systems and contact policies of the large mail providers and scripting many back-end and website functions to stay in compliance as best we can. We’ve even had to retain a mail delivery analysis partner, and still debate if we’ll have to pay a third party to send all out emails. If one of us was already a master of sendmail, and had connections at big mail providers this would be easy, but how many people fit that descirption in the average 10 person start-up?
Here are all the steps we’ve had to take to be able to send our own emails - some are much harder and more expensive than others.
Perfect and frequently review our outgoing mail headers so they always conform to the ISPs preferred settings.
Collect, filter and database every single bounce-back email. Depending on the response error we than must wait 30 days or never send an email to that addresses again. (ISPs keep track of each bounceback they send out. If they send a bounceback twice they consider you at-risk even though the member has asked us to send them an email at that address.)
We have a double opt-in system for all members that want to get emails form us. Since day one there has been an option to ‘never get email’
We have a two-click unsubscribe feature at the footer of each newsletter. Member password is not required.
All member-request emails, such as friend-invites and virtual gift notifications offer direct links to modify their account to not get such email notifications.
We have set-up loopback emails accounts for all the major ISPs. Emails are sent to these accounts each time a person marks mail from us as spam. Marking email as spam is a huge problem because the member innocently believes they are harmlessly keeping their inbox free of email they are no longer interested in, but they are also telling their mail provider we are a probably a spammer. The ISP tehn forwards a copy of the email the person marked as spam and for now we manually open each one of those figure out who it was sent to and manually unset that user’s preference to stop receiving such emails. (Yes, we’d love to script this but their are so many variants we still do by hand.)
We have added code to our website that alerts members if an email we sent them was bounced backed and how they can fix it. Once we get a bounce-back we can’t email them for at least 30 days even if it was a 5 minute problem because someone sent them a 50Mb attachment. (Asking members for an alternate email from the get-go now sounds much more appealing).
We have retained a professional mail delivery monitoring service (ReturnPath) which has hundreds of test accounts over all the big ISPs and we can determine which ISPs are routing our mail to bulk folders or worse. It’s important to realize that of the many spam checks an ISP deploys is messages-sent-per-hour. Thus, we can be a member in good standing, then a spammer, then a member in good standing all in the course of a three hour period.
We have notification code in a couple places on the site that alert members who are using an ISP that misdeliverying our mail to bulk or spam folders that they should either whitelist us by adding our email address to their mail client’s address book, or switch to using a email address with a more trusting mail server.
While I used to be disgusted at AOL’s and Yahoo’s plan to start charging email senders to deliver their messages, considering the money we have to spend to stay in their good graces, we would now prefer to simply pay in advance for our emails to be delivered and know that they will.
Also want to say we’re not proud or bragging about any of our solutions. If anyone knows how to do these things better, more effieciently or has better connections in the mail departments of any major ISPs we’d really appreciate sharing any ideas in the comments.
UPDATE 12/19/06: AOL just whitelisted our entire domains. Praise Dog! This has been a very long time coming. It’s hardly as simple as asking. ALL email-sending IPs have to be considered spam-free for decent length of time. To stay whitelisted we’ll have to keep their complaint rates under 0.1%, bounce rates under 10% and bounce acceptance rates above 90%. Fortunately we can now dip under these rates and get a postmaster email instead of an immediate spammer classification. As long as the problem is rectified quickly we should remain whitelisted.
Digg It or Del.icio.us It