Controlling delivery

How much control over delivery do senders have? I have repeatedly said that senders control their delivery. This is mostly true. Senders control their side of the delivery chain, but there is a point where the recipient takes over and controls things.
As a recipient I can

  • report your email as spam
  • forward your email to another account on another mail system
  • file your email in a mailbox I never read
  • block all your images
  • delete your email before it ever hits my mailbox
  • forward your email to public or private blocklists
  • fold, spindle or mutilate your email
  • forward your email to friends
  • blog about your email
  • purchase something from that email
  • visit your website and purchase something else
  • reply to you

Some of these things are going to hurt your reputation as a sender. And there’s nothing you can do about it. You can’t make a recipient accept your email. You can’t make a recipient ISP accept your email.
What you, as a sender, can do is send mail that your recipients want to read. Send mail that they expect, even anticipate. For instance, it’s now noon on Tuesday, I know I’m going to get Ken Magill’s newsletter in the next 2 hours. Then I will read it, chat about it with some other delivery folks and possibly comment on his blog. I may even get inspired and blog about something he wrote.
Influence and inspire your recipients. Send them mail they want, don’t just send mail they tolerate. Because they don’t have to just tolerate your email. They can react in many ways, some of them positive, some of them negative.
Senders need to remember they only control one end of delivery, but they can influence the whole stream.

Related Posts

AOL changes bounce behaviour

A couple other bloggers have commented on the recent AOL blog post talking about changes to the MAILER-DAEMON string on bounce messages.

Read More

Problems at Cox: Resolved

People mailing to Cox in the wee hours of this morning may have received a rejection message citing the Invaluement DNSBL.
554 IMP a.b.c.d blocked.  IPBL100 – Refer to Error Codes section at http://postmaster.cox.net for more information.
I spoke with one of the folks at Cox and they said there was an error in the implementation causing non-listed IPs to be rejected erroneously between about 4am to 8am (Eastern) this morning.  The problem has been resolved as of 8am, and all traffic is flowing  normally.  The also stated that attempts to resend any blocked messages will succeed. They do apologize for any problems this may have caused.
For those of you with aggressive bounce handling, removing addresses after a single 550 bounce, you will also want to re-enable any cox.net subscribers that bounced off during this configuration problem.

Read More

The secret to dealing with ISPs

What is the secret to dealing with ISPs?
The short answer is: Don’t do it if at all possible. Talking to ISP reps generally isn’t going to magically improve your reptuation.  There is no place in the reputation systems where delivery can be modified because the delivery specialist knows or is liked by the postmaster at an ISP.
With my clients, I work through delivery issues and can solve 80 – 90% of the issues without ever having to contact anyone at the ISPs. 90% of the remaining issues can be handled using the publicly available contacts and websites provided by the ISPs.
In the remaining cases, the “secret” to getting useful and prompt replies is to:

Read More