Spam Resource
Zeta Global is searching for an Email Deliverability Specialist. Could that be you?”As an Email Deliverability Specialist, you will be part of our customer-facing deliverability team. You’ll work directly with our customers to provide reporting, best practices, and recommendations to improve their email programs and get the most out of Zeta Global. Teams at Zeta work collaboratively to deliver great customer experiences. You’ll be a close partner with our Client Services, Technical Support, Sales, and Growth Teams to develop and iterate on strategies that improve both our customers and our teams.”Click here to learn more or to apply.
I’m busy as a bee this week, with so much going on with work (and outside of work), that I’ve not been able to update the blog as much as I would like to. But, I can spare a few minutes to talk about helping a client out yesterday, connecting with them just after he running their first inbox tests and sharing understanding on how to interpret the deliverability results. We walked through this snapshot data showing what it can show, with an eye to identifying difficulties. This time around, like is so often the case, Microsoft was the main problem/focus area found. No mail delivered means they’re probably blocked at Outlook.com/Hotmail.com (but not Office 365). Even before the client checks for the text of bounce messages in their sending platform, we know that they’re going to look like this: 550 5.7.1 Unfortunately, messages from [x.x.x.x] weren’t sent. Please contact
Hey, fellow email nerds! It’s webinar time again. What do you know about Spamhaus? If not everything, I hope you’ll join Matthew Stith and myself on March 21st at 9:00 am central time, where we’ll talk about Spamhaus, what it is, how (and why) blocklists work, how it intersects with domain reputation (and why domain reputation is such a big thing right now) and a whole bunch of at least slightly interesting info nuggets. We’ll try very hard to have time for your questions as well. Want in? Register here. Thanks and hope to see you there!
A friend recently shared a link to a spammer’s blog post bragging about how what they’re doing isn’t illegal. Weird flex, but OK. Going on your blog and defend your business model that way? “We’re not actually breaking the law! We promise! Cold lead emails are totally legal!” You do what you gotta do, I guess. But remember, farts are not illegal either, and they’re just about as broadly unloved as cold lead email campaigns.So, yeah, duh. Spam is not illegal. I’ve been pointing that out for years – here’s me mentioning back in 2010 that CAN-SPAM does not actually prohibit spam. It’s legal, flat out. But, as an argument to defend bad practices, “this is legal” is a red herring. What you should be asking is: how does CAN-SPAM regulate spam and what does it say about mail filtering and blocking? As I wrote about just a couple of
Looks like GPT is down again — it’s not just you. The user interface for Google Postmaster Tools is showing a spinning wheel and nothing else, as of 9:00 am US central time on Friday, March 3rd. When this happened last time, the API remained up (so if you pull GPT data into a third party tool you are possibly unaffected) and when GPT returned, no data seemed to be lost. Hang in there — I’m sure folks at Google are aware and working on the issue.
From Bleeping Computer: A woman in Australia was arrested for sending over 32,000 emails to a Federal Member of Parliament, impacting systems enough that people weren’t able to do their normal jobs as a result. She faces charges that could result in a prison term of up to ten years. Read more.Is 32,000 a lot of emails? I guess so, for a regular mailbox. Here I am today, deleting 12,000 messages out of this mailbox, 6,000 out of that mailbox, times about a hundred, for the various deliverability tracking stuff at work, so it doesn’t seem that overwhelming to me. Back at my last job, I had Gmail test mailboxes that would occasionally fill up and I’d be deleting upwards of 150,000 messages at a time. But still, I probably wouldn’t want to be on the receiving end of that have to work around it to get to the emails
Founded in 2006, the Messaging, Malware and Mobile Anti-Abuse Working Group (M3AAWG) consists of messaging industry companies — sending and receiving platforms, security services and platforms and more come together to collaboratively address spam and internet security issues. If you read my recent DELIVTERMS post, you know that best practices for email senders and receivers are one of the many areas they focus on.M3AAWG recently released a new and useful white paper entitled “Help! I Hit a Spam Trap!” that is primarily oriented toward email service providers (ESPs) and how they can help monitor and guide their clients when learning that mail is being sent to spamtrap addresses. If you’re looking for a very solid form of documentation when referencing spamtraps, what they are and what senders need to do about them, this wouldn’t be a bad thing to reference. Check it out here.
We’ve all been tempted; you’re probably surprised I haven’t already attempted to write blog posts here on Spam Resource using ChatGPT. I still like to generate by content the old fashioned way (poorly) so not only will I avoid using AI to write blog content, but I’ll be sure to avoid using it to generate email content, too. Turns out, somebody at Vanderbilt University thought it would be a good idea to use ChatGPT to write an email in response to the recent Michigan State University Shootings, and now they’re getting nothing but negative feedback about it. Read it yourself here, courtesy of Buzzfeed’s Pocharapon Neammanee.
Customer.io “is an automated messaging platform for tech-savvy marketers who want more control and flexibility to craft and send data-driven emails, push notifications, in-app messages, and SMS.” And they’re hiring! Could you be the Deliverability Specialist they’re looking for?In that Deliverability Specialist role, you will “assist our customers with deliverability support requests and act as a point of escalation for Technical Support and Customer Success teams. In addition to working with customers to resolve their deliverability issues, you will also perform outreach to inform customers about any breaches of Customer.io’s strict Anti-Spam Policy.”To learn more or to apply, click here.
Today: Let’s talk about domain warming.You might have heard about IP warming. I’ve talked about it before (and my Kickbox colleague Jennifer Nespola Lantz has covered the topic in great detail). TL;DR? IP warming is, when you’re newly sending from a particular dedicated IP address, you build up your sending reputation, to maximize your chances of solid inbox placement, by slowly building up your email send volume over the first thirty days or so of email sending. In other words, you don’t just show up and start blasting millions of emails a day. You limit your volume until internet service providers (ISPs) and mailbox providers (MBPs) know who you are.Domain warming is a very similar concept. When you introduce a new domain name, either because you’re launching anew, or because you’re rebranding, domain warming means starting out with low volume sends referencing that domain, and building up volume over the