We recently had one of our email accreditation customers ask us whether we would contact all of the blacklists listed at on a particular site on their behalf, because the site listed their IP address' reputation with these blacklists as "neutral".
Often the way that you find out that a user's email address is no longer valid is that you get a bounce back ("user not found"). But sometimes a user will switch email addresses, and they will actually try to notify you. What do you do then?
Do not use a noreply email address in the email you send out; just don't do it. Don't send out email with a noreply email address as the 'from' email address, don't send out email from an address that can't accept replies, just don't go near any type of noreply email address at all. Besides being the opposite of best practices, think about what happens if you reply to a noreply email. When someone to whom you send email doesn't notice the noreply email address from which you sent the email, they will reply and either get a bounce (frustrating) or get no response (also frustrating). And if they do notice the noreply email address, that on its own will frustrate them. Why would you want to frustrate your customers, leads, or others to whom you are sending email? But beyond that, there are important technical reasons to not use noreply email addresses. Here they are.
What if I told you that there is a way that you can get your email into the inbox 100% of the time? And what if I told you that it was guaranteed?
Have you ever wondered what the majority of your users are using to read their email? The answer may surprise you - even stun you!
We have officially rolled out our Feedback Loop Reports service today, with its own spiffy section on our website, and we couldn't be prouder.
Every so often we run into a sender who has a sense of entitlement - or even righteous indignation - about how an ISP should, must - even has to - accept their email. Whether because it's "requested" or opt-in or because it "complies with CAN-SPAM", the sender gets all in our face about how a given ISP has a responsiblity and duty to accept their email. Sometimes they even rant that it's required by {CAN-SPAM| tort law | the 1st Amendment | insert your favourite rant here}. Except, that's completely wrong.
You'd think that by now people would understand that spam complaints impact your deliverability, both to the inbox and, ultimately, even to the inbox provider themselves. Yet we regularly get questions and comments, both in the course of our business day, and in casual conversation, which make clear that there is something that people just aren't grokking, so here it is, put as plainly and clearly as we can put it: If you get too many spam complaints YOUR EMAIL IS GOING TO START GOING TO THE JUNK FOLDER and may eventually be blocked. Period.
Disclaimers. Whether in email, print marketing, or contracts, who reads them? We'll tell you who reads email disclaimer language: spam filters. Email senders often put disclaimer language at the bottom of an email saying something like "You are receiving this email because you opted in and requested to receive it." Of course how often do you think a user sees a message that starts with "You have received this message because" and thinks "Oh! That's right, I did ask for this, so I won't mark it as spam!"? Less often than you might hope.
