Tribes

Earlier Laura talked about a communication gap between ESPs and ISPs.
My take on it is that it’s something more than just a difficulty in communicating, rather it’s a division due to differences in personality and approach of those individuals whose primary interest is themselves and those whose primary interest is the health of the overall email ecosystem.
The former group (who I mentally refer to using the shorthand “frat boys“) want to make everything all about them, and their companies revenue, and their visibility in the industry, and their ego resume. Broad generalizations with little need for understanding are adequate to raise their visibility and keep them employed. Details aren’t that important to them. Dominating the conversation is. (Lest that sound negative, these are exactly the individuals who can thrive in sales, customer relations, bizdev and marketing environments.)
The latter (shorthand “utilitarians“) instinctively want to make email work well and to be useful for everyone. They want email to be a healthy, useful system and tend to believe that that means optimizing for the greatest good for the greatest number. (If you’ve any philosophy background, think “felicific calculus as applied to email”). They tend to understand the system in much more detail than the frat boys, though maybe less than the mechanics. And they tend to be better at working together – as they’re more interested in hearing other peoples data in order to get better at what they do, rather than being there to convince others of their pre-decided agenda.
(There’s a third group I think of as “mechanics” who take more joy in the details of keeping the system running smoothly on a small scale, without much interest in the broader system, whether that be in a technical or business role. They tend not to be very interactive in public, though, so don’t have much impact at the level of conversations I’m thinking about).
While I hate the broad terms “senders” and “receivers” used to (falsely) divide the industry into two disjoint halves, I’m painting with a fairly broad brush here, so I’m going to stick with them.
There are quite a few of all three types of people at both senders and receivers – but their power and visibility varies.
At senders there’s a mix of frat boys and utilitarians in operational and policy making positions, but the frat boys tend to have a lot more public visibility – they’re the ones who are trying to be visible, to dominate the conversation, and they’re the people you tend to see doing all the talking and less of the listening, whether it be on industry mailing lists or at the microphone at a conference. Because of their greater visibility, they’re who you think of when you think of senders, and typically they’ll be the ones you end up interacting with most in any random mix of individuals from senders.
At receivers the  operational (as opposed to policy) level is where the real decision making power is as far as email is concerned, and it’s heavily dominated by the utilitarians. (In fact, the more visible frat boys I can think of who were in influential positions at receivers are mostly now working on behalf of senders).
Frat boys are very, very bad at communicating with utilitarians. And utilitarians find it very hard to discuss issues they consider serious with frat boys at anything deeper than a superficial level.
Mechanics aren’t great at communicating with strangers in anything other than a fairly friendly environment, but manage best with other mechanics or with utilitarians.
If you’re a C level manager at a sender, and you’re deciding which of your staff are well suited to collaborate with typical receiver staff that’s something important to consider. The public face of the recievers are probably utilitarians. Frat boys are the worst representatives to send out to talk to them.

Related Posts

Senders need to take responsibility

Having just returned home from another conference, my head is full of new ideas, new thoughts and new projects. I enjoy seeing old friends, making new contacts and sharing ideas. One thing I don’t enjoy, though, is listening to senders and marketers complaining about how hard it is to be a sender because the ISPs will not tell them what standards they need to meet.
If the ISPs would just tell us what they want us to do, we’ll do it.

The ISPs have told senders what they want them to do. They want senders to stop sending mail that their users don’t want. It is a very simple statement.
Stop sending spam.

For many senders, however, it’s not enough. “Tell us exactly what we need to do to stop sending spam. What complaint rates must we be under? What bounce rates do we have to be under? How do you want us to do this?” By this point in the conversation the ISP person is mentally rolling their eyes and looking for a way to escape the conversation.
The ISPs don’t want to tell senders how to behave, they want senders to start behaving. Stop sending spam should be all they need to tell senders.
Senders who ask for ISPs to tell them how to stop sending mail recipients think is spam are looking for specific thresholds they can stay under. They’re not really interested in actually sending wanted mail, they’re interested in sending good-enough mail, where good-enough mail is simply mail that gets to the inbox.
Want to know why ISPs don’t think much of many senders? Because the senders are not visibly taking any stand against abuse. I know there are a lot of senders out there who stop a lot of spam from ever leaving their systems, but there’s also a lot of unwanted mail that goes out, too. Some of that mail is even spam by any definition of the word. All the ISPs can see is the spam that gets through, and then they hear just tell us what to do and we’ll do it. From an ISP perspective, this means the senders only care about the thresholds and getting in under the ISPs’ radars.
Senders need to take more responsibility for the mail that goes out over their networks.
What do I mean by this? I mean senders need to stop waiting for the ISPs to define good practices. Senders need to implement standards and good practices just because they’re good practices, not because the ISPs are dictating the practices. Senders need to stop customers from doing bad things, and dump them if they won’t stop. Senders need to stop relying on ISPs for specific answers to why mail is being blocked. Senders need to take responsibility for the mail going across their networks.
It’s time for senders to grow up and stop relying on others for guidance. They shouldn’t implement good practices just because the ISPs tell them to, but instead should implement good practices because they are good practices.

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

Rescuing reputation

One of the more challenging things I do is work with companies who have poor reputations that they’re trying to repair. These companies have been getting by with poor practices for a while, but finally the daily delivery falls below their pain threshold and they decide they need to fix things.
That’s when they call me in, usually asking me if I can go to the ISPs and tell the ISPs that they’re not spammers, they’re doing everything right and will the ISP please stop unfairly blocking them. Usually I will agree to talk to the ISPs, if fixing the underlying problems doesn’t improve their delivery on its own. But before we can talk to the ISPs, we have to try to fix things and at least have some visible changes in behavior to take to them. Once they have externally visible changes, then we can ask the ISPs for a little slack.
With these clients there isn’t just one thing they’ve done to create their bad reputation. Often nothing they’re doing is really evil, it’s just a combination of sorta-bad practices that makes their overall reputation really bad. The struggle is fixing the reputation requires more than one change and no single change is going to necessarily make an immediate improvement on their reputation.
This is a struggle for the customer, because they have to start thinking about email differently. Things have to be done differently from how they’ve always been done. This is a struggle for me because I can’t guarantee if they do this one thing that it will have improved delivery. I can’t guarantee that any one thing will fix their delivery, because ISPs measure and weight dozens of things as part of their delivery making decisions. But what I can guarantee is that if they make the small improvements I recommend then their overall reputation and delivery will improve.
What small improvement have you made today?

Read More