Spamming for deliverability

This morning I woke up to a job offer. I hear a number of other email deliverability folks received the same job offer.

I am writing to you from [Company].  We are one of the oldest and best reputed partners for Salesforce.  We have succeeded because we only hire the best, most experienced developers.  We have a need for an excellent expert in deliverability.  We have been watching you for years via social media and we feel that you are proven and match this profile. If you are satisfied where you are, then we apologize for bothering you, however if you welcome the challenge of being stretched by working with the best and brightest in the world, we want to talk to you.

Most of our developers work remotely from their home.  We have complete centralized support for you, you will be expected to concentrate on helping customers solve their deliverability problems and you will be working with the largest corporations and with growing small and medium size businesses. This is a fulltime position with full benefits. 

We are interested in you, and we would like to discuss the position with you so that we may proceed.  Please just reply to this email and let me know your preferred method of communication.  We have multiple open positions, so please share this invite with others you feel are qualified.

I know a lot more about this particular position than is conveyed in the email. See, last week I spoke to Company. They were looking for some help with deliverability. Not, of course, the kind of deliverability I do they have all the expertise they need in high level strategy. Instead, they wanted someone to run Salesforce reports and … something? It was never that clear what they were expecting to do with the Salesforce reports as they didn’t need advice or assistance.

The email itself links to a website and a blog site. If I click on the blog site gives me a default CPanel “this website is horribly misconfigured” error page. If I go to their website and click “blog” it shows me a blog that’s not been updated since Dreamforce 2017.

A screenshot of the 404 page linked to in the spam I received.

I share this so that my deliverability colleagues are aware that this company is scraping and sending out mail without even checking basics like “did we contact this person already?”

I’m also a little concerned about the offer of full time remote work. Given how this position was pitched to me last week and how it’s being pitched in the email, I’m really unsure this is a legitimate offer. It also looks like it is, potentially, a bad cut and paste of a job offering a different position. Of all the things I’ve heard deliverability folks called “developer” is not on the list.

Just be careful out there.

Related Posts

McCain Campaign Spamming

As I mentioned in my post on spam from the Obama campaign, there have been reports of spam coming from the McCain campaign. However, the McCain campaign does not seem to be sending the volume of mail that the Obama campaign is, and so they are not as visible.
A recent post over at Denialism Blog shows that the McCain campaign has some of the same problems as the Obama campaign. Chris talks about the unsubscribe options he is presented when trying to stop the spam he is receiving. He suggests the campaign adds another option:

Read More

What about the spamtraps?

I’ve been slammed the last few days and blogging is that thing that is falling by the wayside most. I don’t expect this to change much in the very short term. But, I do have over 1200 blog posts, some of which are still relevant. So I’ll be pulling some older posts out and sharing them here while I’m slammed and don’t have a lot of time left over to generate new content.
Today’s repost is a 2015 post about spamtraps.
Spamtraps are …
… addresses that did not or could not sign up to receive mail from a sender.
… often mistakenly entered into signup forms (typos or people who don’t know their email addresses).
… often found on older lists.
… sometimes scraped off websites and sold by list brokers.
… sometimes caused by terrible bounce management.
… only a symptom …

Read More

August 2016: The Month in Email

August was a busy month for both Word to the Wise and the larger world of email infrastructure.
IMG_0026
A significant subscription attack targeted .gov addresses, ESPs and over a hundred other industry targets. I wrote about it as it began, and Spamhaus chief executive Steve Linford weighed in in our comments thread. As it continued, we worked with M3AAWG and other industry leaders to share data and coordinate efforts to help senders recover from the attack.
In the aftermath, we wrote several posts about abuse, blocklists, how the industry handles these attacks currently, and how we might address these issues going forward. And obviously this has been on my mind before this attack — I posted about ongoing problems with internet security, how open subscription forms contribute to the problem, and other ways that companies inadvertently support phishing operations.
I posted about the history of email, and recounted some of my earliest experiences, when I had a .bitnet and a .gov address. Did you use email before SMTP? Before email clients? I’d be curious to hear your stories.
Speaking of email clients, I did two posts about how mail gets displayed to the end user: Gmail is displaying authentication results, which should provide end users with a bit more transparency about how authentication is used to deliver or block messages, and Microsoft is partnering with Litmus to improve some of the display issues people face using Outlook. These are both notable — if this is not your first time reading this blog, you know about my constant refrain that delivery is a function of sending people mail they want to engage with. If the mail is properly formatted and displayed, and people have a high degree of confidence that it’s been sent from someone they want to get mail from, that goes a long way towards improving engagement in the channel.
On that note, I spoke at length with Derek Harding about how marketers might change their thinking on deliverability, and he wrote that up for ClickZ. I also participated in the creation of Adobe’s excellent Teaching the Email Marketer How to Fish document (no, not phish…).
Steve was very busy behind the scenes this month thinking about abuse-related topics in light of the SBL issues, but he wrote up a quick post about the Traffic Light Protocol, which is used to denote sensitive information as it is shared.
Finally, for my Ask Laura column this month, I answered questions about delivery and engagement metrics and about permissions with purchased lists. As always, if you have a general question about email delivery, send it along and I’ll consider it for the column.

Read More