Axios, the Washington Post, and others are reporting that the Gmail political email pilot program is coming to an end.Axios buries the lede on this one — putting the important bit (to me) at the very end: “Google’s pilot email program, which saw more than 100 political committees participate, will end January 31, and the company is evaluating next steps.”More from the Washington Post: “The company will let the program sunset at the end of January instead of prolonging it, Google’s lawyers said in a filing on Monday.” The filing is an attempt to get the RNC “unfair spam filtering” lawsuit against Google dismissed. How the shutdown of the pilot program ties to that effort, I am not equipped enough to say at the moment, but I’ll be curious to learn more.
The other day, I ran across a complaint on Linkedin. “Just saw another email go to the Promotions Folder with DKIM, SPF, and DMARC set up perfectly. Stop telling people this will fix their e-mail problems!” It’s not the first time I’ve heard this, and I can understand why the author is frustrated. But, it’s important not to miss the true point — email authentication will help to improve inbox delivery. Because it does! But there’s a nuanced explanation to go along with that. The devil truly is in the details.Email authentication is fantastic. SPF and DKIM both allow you to set yourself up as YOU in the eyes of mailbox providers — as opposed to just being one of the many clients of ESP or CRM platform X, based on a shared IP address or shared DKIM domain. This is a good thing, but it’s just the start.Setting yourself
Mike Scarcella, reporting for Reuters: Google has hired law firm Perkins Coie to help defend it against the RNC’s spam filtering lawsuit. “While Perkins long has provided legal services to the Democratic National Committee in matters of political law, and to political candidates, most of the lawyers fielded to defend against the RNC’s claims focus on privacy, security and business litigation.” Read it all here.
Google and various news outlets are reporting that Gmail had a significant outage today (Saturday, December 10th). Google reports that as of 4:16 PM UTC (10:16 AM US central time) things are on the mend, but that there’s a backlog of messages to be delivered.I can’t tell if senders found inbound delivery attempts delayed with 4xx errors, or if Google servers accepted messages then sat on them. Message delivery to the inbox, however, was definitely delayed for folks (observed by myself, too), regardless of what the backend systems were doing.
To ensure your Google Calendar invites make it to the intended destination, configure DKIM signing using these steps. The post How to get Google Calendar Invites to Pass DMARC appeared first on dmarcian.
A few months ago, Google made a splash in the political press and the email marketing space when they asked the FEC the following question: May Google launch a free and non-partisan pilot program to test Gmail design features, which will be open to authorized candidate committees, political party committees, and leadership political action committees, where spam detection as applied to messages from a pilot participant on direct feedback from the recipient rather than standard spam detection, and each pilot participant will receive information regarding the rate of emails delivered into Gmail users’ inboxes, as long as the pilot will rely predominantly participant is in compliance with the program’s requirements?Google’s letter to the FEC (.pdf link) The letter is actually worth a read as many of the general press reports about the request focused on Google asking the FEC to allow politicians to spam freely. I mostly avoided discussions about
Here is the scenario. Maybe you’ve just gotten a bounce message that looks like this:Aug 25 11:20:24 s1 postfix/smtp[26906]: 98299221BB: to=, relay=gmail-smtp-in.l.google.com[142.250.141.27]:25, delay=1.2, delays=0.04/0.77/0.2/0.21, dsn=5.7.1, status=bounced (host gmail-smtp-in.l.google.com[142.250.141.27] said: 550-5.7.1 [206.125.175.2] Our system has detected that this message is not RFC 550-5.7.1 5322 compliant: duplicate headers. To reduce the amount of spam sent 550-5.7.1 to Gmail, this message has been blocked. Please review 550 5.7.1 RFC 5322 specifications for more information. j6-20020a637a46000000b0042b3a763e76si3563504pgn.127 – gsmtp (in reply to end of DATA command))Or perhaps it looks like this:Aug 25 12:48:59 s1 postfix/smtp[14180]: C90492056B: to=, relay=aspmx.l.google.com[142.250.141.27]:25, delay=0.69, delays=0.08/0/0.39/0.22, dsn=5.7.1, status=bounced (host aspmx.l.google.com[142.250.141.27] said: 550-5.7.1 [206.125.175.2] Our system has detected that this message is not RFC 550-5.7.1 5322 compliant: 550-5.7.1 Multiple ‘From’ headers found. 550-5.7.1 To reduce the amount of spam sent to Gmail, this message has been 550-5.7.1 blocked. Please visit 550-5.7.1 https://support.google.com/mail/?p=RfcMessageNonCompliant 550 5.7.1 and review RFC 5322 specifications for more information.
Are you getting inundated with calendar spam? Are you annoyed that events from spammers show up on your calendar automatically, even if you didn’t accept the invite and RSVP to attend? Google now has a setting that will configure it to auto-add events to your calendar only if the invitation comes from someone you know. CNBC’s Ashley Capoot explains how to turn this on.
Today’s guest post comes from my colleague Jennifer Nespola Lantz, VP of Industry Relations and Deliverability at Kickbox, keeping us updated on a potentially upcoming Gmail spam filtering process change that is likely to have a great impact upon all of us. Take it away, Jen!On June 28th, I saw a news article by Axios reporting that “Google moves to keep campaign messages out of spam.” At first glance I was very surprised about the statement knowing all Gmail does to protect users and how hands off they tend to be (outside of the machines doing their magic.) What I originally defined as campaign messages was coming from a too in-the-weeds mental dictionary about email production. I always coined campaigns as a singular email marketing effort. And then I read it…”Google has asked the Federal Election Commission to green light a program that could keep campaign emails from ending up
Here’s what is sure to be your favorite fun factoid forever from today: At Gmail — for the domains gmail.com and googlemail.com — whether or not the username portion has dots in it is irrelevant. If you send mail to al.iverson.mailbox@gmail.com and aliversonmailbox@gmail.com, you’re sending mail to the same person, the same account, twice. Don’t take my word for it — here’s the Google help page with details.As Google indicates, this does not apply to Google for Business, aka G-Suite addresses. So if you send mail to al.iverson.mailbox@wombatmail.com and aliversonmailbox@wombatmail.com, those are indeed two separate addresses.The Gmail “dot thing” is sometimes a huge pain in the rear for senders. If you can work it into your registration forms, you could try normalizing Gmail addresses by removing the dots, to prevent duplicate submissions. Or disallowing dots in the username, if the domain is gmail.com or googlemail.com. However, even this is a bit…
