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?
We've talked previously about why all the email addresses you send from (i.e. your email's "return address") should really exist. It's because if they don't, you're email is going to get junk foldered, both due to spam complaints, and because ISPs actually test whether your from address exists. But there are some email addresses - used as "From:" addresses - that even if you create them on your system - even if they really do exist - you should just never use.
We recently had a customer contact us to ask us whether a particular vendor's Permission Pass system was legitimate, because to them it seemed to cross the line. Smart customer! Because, in fact, this particular vendor (no, I'm not going to name them) is not only conducting Permission Pass in the completely wrong way - but in a way that would be sure to have gotten our customer in hot water with the ISPs and spam filters!
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?
Get to the Inbox by SuretyMail Email Deliverability Company Inbox Logo
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.
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 getting - 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 be junkfoldered.
Disclaimers. Whether in email, print marketing, or contracts, who reads them? I'll tell you who reads them: spam filters. How often do you think a user reads a message that starts with "You have received this message because you have opted in" or "You received this message due to your subscription" and thinks "Oh! That's right, I did ask for this, so I won't mark it as spam?" Now, how often do you think that a spam filter (or, indeed, a user) sees that and thinks "This must be spam"?
Search
Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
Search in posts
Search in pages
Filter by Categories
Content Issues
Deliverability
Email Authentication
Email List Building
Feedback Loops
Mailing List Hygiene
Monitoring and Tracking
Opt-in Practices
Our News
Privacy & Email Laws
Sending Practices
Spam Complaints
Technical Stuff
The Industry

Join our email community and get
How to Stay Out of the Spam Folder 
& How to Grow Your Email List free!


 Get to the Inbox by SuretyMail
The Original Email Deliverability Company

Free stuff!
Close
Skip to content