Is Gmail About to Wreck your Email Marketing?

What you need to know

Google has announced that, starting next month, they will reject email that purports to come from Gmail, but isn’t sent by a Gmail server.

How this might affect you

If you use a third party email service, like FeedBlitz, to send your email updates, AND your from address is a Gmail domain (e.g. mysuperduperblog@gmail.com), then your emails will probably not get through, unless either your email service or you change something.

What you need to do this month

If you’re with FeedBlitz, nothing! We will take care of this for you, and your email will get through, just as we did when Yahoo and AOL implemented the same policies in 2014.

If you are not with FeedBlitz, and you send emails using a Gmail address, you need to change your sending address. Ideally to one that better reflects your brand (such as me@mysuperduperblog.com). If you have a hosted web site, most site hosting packages come with at least one email address. Use that!

If you are with FeedBlitz, we recommend you do this anyway, not because your mail won’t go through (remember, we’re taking care of this for you), but because it’s better branding.

Do I have to give up using Gmail for my business?

Absolutely not. You can set up Gmail to pull from other email accounts (it’s in Gmail’s Settings, on the Accounts & Import tab).

What’s going on?

Google is helping curb spam by changing their DMARC policy. AOL and Yahoo did this in 2014. Basically, they’re saying to inbox providers, if you can’t prove that the email really came from Gmail, don’t accept it. Why? Because spammers use fake Gmail addresses, but they don’t run through Google’s servers. Spam sent this way fails DMARC authentication, and because Google’s policy will change to “reject” next month, most modern ISPs will not deliver it. Result: Much less spam for you. Hurrah!

This is a Good Thing.

BUT… legitimate email, such as your newsletters and blog updates, sent by email services like FeedBlitz that have been using your Gmail address will now get blocked, because that email won’t authenticate as coming from Gmail (which is true; it’s coming from us). FeedBlitz will automatically change the sending address where necessary to ensure your emails do in fact get through (and your replies will reach your Gmail account, so that’s OK too), so no FeedBlitz publishers or subscribers will be affected.

But if you’re not with us (you should fix that ;) ), you need to check with your email service provider (ESP) – and probably change your sending address.

Let’s Talk Branding for a Moment

Many (far too many) bloggers use <theirsite>@gmail.com as their email address when their domains are at <theirsite>.com. You’ve ponied up for the web site, have your branding just so, and then … oof. Let the ball drop at the email address. It’s not a huge branding fail, but ceding control of your business’ email address to Gmail could just get very sticky, starting next month.

So, go on. Finish the play on your branding with your email address. Update your mailing list’s settings.

Incidentally, if you’d like to find out about how you can extend your own domain’s email authentication to your FeedBlitz mailings, you can, using SPF and / or DKIM. It’s easy to set up, provided you have access to your DNS (domain name) settings.

AOL Follows Yahoo with DMARC Changes

Earlier this month, Yahoo changed what’s called a DMARC record in an attempt to limit spoofing of Yahoo email addresses.

The bottom line was that small businesses and bloggers who used their own yahoo email addresses saw undeliverable rates skyrocket.

We at FeedBlitz quickly built a workaround to enable our publisher’s email to be delivered successfully again.

AOL has followed suit, it seems, on the DMARC policy front. If you now send an email using your AOL account via a third party service, that email will be bounced by AOL, Yahoo, Gmail and other major ISPs until you change the email address used to send your newsletters and other bulk emails. [Read more...]

Authenticating your Emails with SPF

Following up on last week’s post about Yahoo’s DMARC policy change, here’s how to authenticate mailings that (a) you send, and (b) we send on your behalf. Before going into this, I want to make this point abundantly clear:

FeedBlitz automatically authenticates email we send; you don’t HAVE to do anything.

And for the vast majority of our clients, that’s perfect! That said, let’s say you want to authenticate email you send for your site’s domain anyway, and email we send for you as well. OK, sure, can do. In order to make that happen, you must have the ability to add a TXT record to your DNS settings, because that’s how SPF (the authentication protocol we’re going to set up) works.

Got that ability? Ok, good. Here’s what you have to do. [Read more...]

DMARC’s (Un)intended Consequences: Why Yahoo is Bouncing Your Emails

Let’s get straight to the point. Over the weekend, possibly last Friday night, Yahoo changed a key DNS (domain name system) entry. The effect was brutal: It started bouncing out every email that said it was from a yahoo address, but had not been sent by a yahoo server.

So, if your email said it was from blogger@yahoo.com but was in reality sent by a third party, such as FeedBlitz (bear in mind this is not targeting FeedBlitz specifically, and is not a blacklisting; this applies to any third party service and I’m using us as an example), then if you sent your email over the weekend, it was bounced by Yahoo.

That’s bad, and it gets worse. It was also bounced by Gmail, because they are paying attention to the DNS record Yahoo changed, called a DMARC record. Bottom line: Your emails didn’t get through, if you specified your “from” address to be a Yahoo email.

They didn’t get routed to junk or the spam folder. They were bounced out and never accepted for delivery, if (to repeat ad nauseam) you specified your “from” address to be a Yahoo email account. [Read more...]