Answers.Body: <p>I'm getting a number of other flags from other systems that gmail's deliverability rules have changed. Although DKIM still isn't required, it appears that there's been an update to google's algorithm that decides whether email is spam or not, and it's harder to cross than it used to be.</p>
  <p>Bottom line: for civimail deliverability, you probably need at least SPF, the messageId, and a &quot;cleanish&quot; ip reputation, and I suspect that DKIM on the from address will help.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-07-26T21:22:01.123Z
Answers.Text: Also don't send spam (grin).
Answers.UserDisplayName: Demerit
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-08-10T13:33:21.490Z
Answers.Text: Well, in fact, you might think so, but I'm not convinced. It depends on your definition of spam, and ultimately, the only one that matters for the purpose of deliverability is that of the mail provider, and with the proliferation of "AI", that definition is harder to figure out, and subject to all kinds of weird manipulation by bad actors.
Answers.UserDisplayName: Alan Dixon
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-08-10T13:34:09.440Z
Answers.Text: Also, there are multiple gates for deliverability - and not all of them result in a bounce. So it's really a dark art.
Answers.UserDisplayName: Alan Dixon
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-07-26T21:14:07.460Z
Answers.LastActivityDate: 2022-07-26T21:14:07.460Z
Answers.UserDisplayName: Alan Dixon
Body: <p>As of July 11, I'm getting this from civimail messages, mostly to @gmail.com addresses. The same install has been successfully sending out to the same address list for a long time.</p>
  <p>550-5.7.1 [209.15.213.100] Messages missing a valid messageId header are not 550 5.7.1 accepted.</p>
  <p>I've turned on the checkbox that generates it, so perhaps problem solved, but is this a policy change from gmail?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-07-12T18:00:41.520Z
Comments.Text: Perhaps most smtp services are already adding this? This one is going out directly from the server via postfix, so maybe there's a setting in there? I'm surprised this hasn't been flagged as a bigger deal.
Comments.UserDisplayName: Alan Dixon
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-07-18T16:17:58.207Z
Comments.Text: Here's an indication that something might have changed at google mail servers: https://blog.mxtoolbox.com/2022/06/09/googles-recent-smtp-relay-exploit-and-dmarc-policies/
Comments.UserDisplayName: Alan Dixon
Tags: <civimail>
Title: Does gmail/google now demand a messageId?
ThreadText: # Does gmail/google now demand a messageId?
  
  (Asked by: username_0 on 2022-07-12)
  
  As of July 11, I'm getting this from civimail messages, mostly to @gmail.com addresses. The same install has been successfully sending out to the same address list for a long time.
  
  550-5.7.1 [209.15.213.100] Messages missing a valid messageId header are not 550 5.7.1 accepted.
  
  I've turned on the checkbox that generates it, so perhaps problem solved, but is this a policy change from gmail?
  
  **Tags:** civimail
  
  > **Comments:**
  > **username_0**: Perhaps most smtp services are already adding this? This one is going out directly from the server via postfix, so maybe there's a setting in there? I'm surprised this hasn't been flagged as a bigger deal.  
  > **username_0**: Here's an indication that something might have changed at google mail servers: https://blog.mxtoolbox.com/2022/06/09/googles-recent-smtp-relay-exploit-and-dmarc-policies/  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2022-07-26. Score: 1 | Accepted answer
  
  I'm getting a number of other flags from other systems that gmail's deliverability rules have changed. Although DKIM still isn't required, it appears that there's been an update to google's algorithm that decides whether email is spam or not, and it's harder to cross than it used to be.
  
  Bottom line: for civimail deliverability, you probably need at least SPF, the messageId, and a "cleanish" ip reputation, and I suspect that DKIM on the from address will help.
  
  > **Comments:**
  > **username_1**: Also don't send spam (grin).  
  > **username_0**: Well, in fact, you might think so, but I'm not convinced. It depends on your definition of spam, and ultimately, the only one that matters for the purpose of deliverability is that of the mail provider, and with the proliferation of "AI", that definition is harder to figure out, and subject to all kinds of weird manipulation by bad actors.  
  > **username_0**: Also, there are multiple gates for deliverability - and not all of them result in a bounce. So it's really a dark art.  
  
  ---
  
  