MAAWG: Sender Best Practices

The MAAWG Sender Subcommittee has published a Sender Best Current Practices document.
This document details what the current best practices in the sending industry are. Summarized the document says:

  • Senders must get clear and conspicuous consent from recipients. In other words, recipients should know what they are signing up for and what kind of mail they should expect.
  • Senders must provide unsubscription options that make it easy for recipients to get off mailing lists.
  • Senders should adhere to recipient ISP policies
  • Senders should authenticate email
  • Senders must be accountable for the email they send
  • Senders must handle bounces and stop sending email to accounts that no longer exist

Related Posts

Mailing to corporate domains

One of the struggles of delivery consulting is doing ISP relations and problem resolution for clients attempting to mail to corporate domains. The rules for getting mail into ISPs are generally pretty clear, and if they’re not I can typically find someone there who will give me the time of day. At corporate domains, though, all bets are off.
While ISPs strive to deliver wanted mail to their customers while protecting them from spam, businesses have different goals for email. For most businesses email is a tool. Mail boxes belong to the business, not the employee. In many cases, businesses do allow personal use of email so some marketing mail to employees is acceptable. However, if a corporation blocks personal marketing email, they are less likely than commercial ISPs to let even legitimate email through.
Large corporations typically run their own mail systems. Once a sender is blocked, however, the corporation will not unblock their email unless the sender can demonstrate that the mail is business related.
Smaller businesses typically use commercial appliances or filtering services. In these cases there is less need to justify the business related nature of email. Unfortunately, some commercial filters do not listen to senders or provide block resolution. At least one filter claims that the only way you can deliver mail to their users is for the users themselves to whitelist the sender.
Businesses of all types are much more security conscious than home users. Some “spam” blocking may be more related to security than actual spam. Finally, there are workplace and environment issues. Companies may be liable under the hostile workplace laws if they allow porn or other offensive emails into their employee mailboxes. One company I know of blocks any email with the word “viagra” in it. The email administrator of said company says that in the years this block has been in place there has only been one false positive… and that employee was told his wife should not use that word when emailing him shopping lists in the future.
All of these issues make it difficult to troubleshoot delivery problems at corporations.

Read More

Busy Busy.

Getting ready to head to MAAWG next week. We leave for the plane in a couple hours. I expect there will be some interesting information coming out of the talks and sessions and will be sharing some of the more interesting bits throughout the week.
Also, Steve has written a new tool to visualize blacklists. He’s put up a beta version. It still has a few bugs and missing features, but there are already some interesting patterns in XBL data with it.
The demo installation only displays XBL data (rather than letting you overlay multiple datasets) and is missing search and bookmarking, amongst other things. Enough disclaimers yet?

Read More

It really can be your email

Yesterday I wrote about activist groups getting blocked at major ISPs and how the ISPs don’t block mail because they don’t like the political viewpoints in email. This morning Mark Brownlow has a post up about delivery in general and the cause of many delivery problems.

Read More