# 🔷 Security issue | Emails to Gmail not deliverable - Adjust SPF-Record

**URL:** <https://community.sitejet.io/t/security-issue-emails-to-gmail-not-deliverable-adjust-spf-record/2498>\
**Category:** Sitejet News\
**Created:** [June 29, 2023, 10:20am UTC](https://community.sitejet.io/t/security-issue-emails-to-gmail-not-deliverable-adjust-spf-record/2498 "2023-06-29T10:20:33Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andre](https://dub1.discourse-cdn.com/flex017/user_avatar/community.sitejet.io/andre/32/3459_2.png) [@Andre](https://community.sitejet.io/u/Andre)\
**Post date:** [June 29, 2023, 10:20am UTC](https://community.sitejet.io/t/security-issue-emails-to-gmail-not-deliverable-adjust-spf-record/2498/1 "2023-06-29T10:20:33Z")

</div>

🔷 Hello dear Sitejetters,

I would like to point out recent issues with Gmail. Lately, we have been getting more and more information that your mails sent to Gmail addresses come back with an error message from Gmail.

Google has tightened up its email security settings in an effort to combat the flood of spam and abuse. This new requirement means that some mails no longer arrive at Gmail addresses if they are not authenticated via DMARC or an SPF record. This is very commendable, but it does mean that you should make an adjustment.

Usually, you receive this type of error message:

> [xxx@gmail.com](mailto:xxx@gmail.com): host
> 
> [gmail-smtp-in.l.google.com](http://gmail-smtp-in.l.google.com)[108.177.126.26] said: 550-5.7.26 This mail is unauthenticated, which poses a security risk to the 550-5.7.26 sender and Gmail users, and has been blocked. The sender must 550-5.7.26 authenticate with at least one of SPF or DKIM. For this message, 550-5.7.26 DKIM checks did not pass and SPF check for [[xxx.com](http://xxx.com) 550-5.7.26 1 did not pass with ip: [138.201.56.180]. The sender should visit 550-5.7.26
> 
> [Email sender guidelines - Gmail Help](https://support.google.com/mail/answer/81126#authentication) for 550 5.7.26 instructions on setting up authentication.
> 
> g27-20020a170906395b0000983591d105s5579867eje. 405 - gstp (in reply to end of DATA command)
> 
> Reporting-MTA: dns; [mxi.sitehub.io](http://mxi.sitehub.io)
> 
> X-Postfix-Queue-ID: 5D194427673
> 
> X-Postfix-Sender: rfc822; [xxx@xxx.com](mailto:xxx@xxx.com)
> 
> Arrival-Date: Thu, 29 Jun 2023 10:25:59 +0200 (CEST)

Since we do not grant access to DMARC, we recommend adjusting the SPF records. Currently, the following SPF record is set up _by default_ if you obtain your domains through us:

**v=spf1 mx -all**

This is very general. We recommend the following entry:

**v=spf1 a:mx1.sitehub.io a:mx2.sitehub.io mx -all**

This ensures that the mails are considered authentic. If you are still facing issues, please consider this article here first and then write us a support mail: [Common questions about emails - Sitejet Help](https://help.sitejet.io/article/1091-faq-email)

All the Best!

_Further information:_

> **[Email sender guidelines - Gmail Help](https://support.google.com/mail/answer/81126#authentication)**
>
> Important: Starting February 2024, Gmail will require the following for senders who send 5,000 or more messages a day to Gmail accounts: Authenticate outgoing email, avoid sending unwanted or unsol

> **[DNS settings with Sitejet - Sitejet Help](https://help.sitejet.io/article/876-dns-settings#sfp-txt-records)**
>
>  In this article, you will learn everything about Sitejet's DNS settings. Table of content What are DNS settings? DNS settings at a glance How to manage DNS set

* * *

🇩🇪 🔷 Hallo liebe Sitejetters,

ich möchte euch gerne auf ein “Issue” mit E-Mails und Gmail hinweisen. In letzter Zeit bekommen wir vermehrt Hinweise darauf, dass eure Mails, die ihr an Gmail-Adressen versendet, mit einer Fehlermeldung von Gmail wieder zurückkommen.

Google hat seine Sicherheitseinstellungen für E-Mails verschärft, um so der Flut an Spam und Missbrauch entgegenzuwirken. Diese neue Anforderung führt dazu, dass einige Mails nicht mehr bei Gmail-Adressen ankommen, wenn diese nicht authentifiziert sind via DMARC oder einem SPF-Record. Das ist sehr löblich, führt aber dazu, dass ihr eine Anpassung vornehmen solltet.

Ihr bekommt dann in den meisten Fällen diese Art der Fehlermeldung.

> [xxx@gmail.com](mailto:xxx@gmail.com): host
> 
> [gmail-smtp-in.l.google.com](http://gmail-smtp-in.l.google.com)[108.177.126.26] said: 550-5.7.26 This mail is unauthenticated, which poses a security risk to the 550-5.7.26 sender and Gmail users, and has been blocked. The sender must 550-5.7.26 authenticate with at least one of SPF or DKIM. For this message, 550-5.7.26 DKIM checks did not pass and SPF check for [[xxx.com](http://xxx.com) 550-5.7.26 1 did not pass with ip: [138.201.56.180]. The sender should visit 550-5.7.26
> 
> [Email sender guidelines - Gmail Help](https://support.google.com/mail/answer/81126#authentication) for 550 5.7.26 instructions on setting up authentication.
> 
> g27-20020a170906395b0000983591d105s5579867eje. 405 - gstp (in reply to end of DATA command)
> 
> Reporting-MTA: dns; [mxi.sitehub.io](http://mxi.sitehub.io)
> 
> X-Postfix-Queue-ID: 5D194427673
> 
> X-Postfix-Sender: rfc822; [xxx@xxx.com](mailto:xxx@xxx.com)
> 
> Arrival-Date: Thu, 29 Jun 2023 10:25:59 +0200 (CEST)

Da wir keinen Zugriff auf DMARC gewähren, empfehlen wir die Anpassung der SPF-Records. Aktuell ist standardmäßig folgender SPF-Record eingerichtet, wenn ihr eure Domains über uns bezieht:

**v=spf1 mx -all**

Dieser ist sehr allgemein gehalten. Wir empfehlen folgenden Eintrag:

**v=spf1 a:mx1.sitehub.io a:mx2.sitehub.io mx -all**

Dadurch wird gewährleistet, dass die Mails als authentisch angesehen werden. Solltet ihr weiterhin Probleme haben, schaut euch gerne einmal diesen Artikel an und wenn ihr weitere Hilfe benötigt, schreibt uns bitte eine Support-Mail: [Häufig gestellte Fragen zu Mails - Sitejet Hilfe](https://hilfe.sitejet.io/article/1108-faq-mails)

Liebe Grüße!

Weitere Informationen:

> **[Email sender guidelines - Gmail Help](https://support.google.com/mail/answer/81126#authentication)**
>
> Important: Starting February 2024, Gmail will require the following for senders who send 5,000 or more messages a day to Gmail accounts: Authenticate outgoing email, avoid sending unwanted or unsol

> **[DNS-Einstellungen in Sitejet - Sitejet Hilfe](https://hilfe.sitejet.io/article/1081-dns-einstellungen#spf-txt)**
>
> In diesem Artikel erklären wir dir die Grundlagen der DNS-Einstellungen und geben dir einen Überblick. Inhaltsangabe Was sind DNS-Einstellungen? Wichtige Begrif

---

<div class="post-metadata">

**Author:** ![realKC](https://dub1.discourse-cdn.com/flex017/user_avatar/community.sitejet.io/realkc/32/990_2.png) [@realKC](https://community.sitejet.io/u/realKC)\
**Post date:** [June 29, 2023, 1:26pm UTC](https://community.sitejet.io/t/security-issue-emails-to-gmail-not-deliverable-adjust-spf-record/2498/2 "2023-06-29T13:26:16Z")

</div>

Hi Andre,

so all we have to do is copy&paste it?  
**v=spf1 a:mx1.sitehub.io a:mx2.sitehub.io mx -all**

TTL 900 and Prio 0 doesn’t need to be changed?

 ![Screen Shot 2023-06-29 at 8.23.28 AM](https://europe1.discourse-cdn.com/flex017/uploads/sitejet/original/2X/b/bd79ccc991a934cb1d0983636588ed8f43b85cf3.png)

Thanks

---

<div class="post-metadata">

**Author:** ![Andre](https://dub1.discourse-cdn.com/flex017/user_avatar/community.sitejet.io/andre/32/3459_2.png) [@Andre](https://community.sitejet.io/u/Andre)\
**Post date:** [June 30, 2023, 9:24am UTC](https://community.sitejet.io/t/security-issue-emails-to-gmail-not-deliverable-adjust-spf-record/2498/3 "2023-06-30T09:24:09Z")

</div>

Hey @realKC I do recommend taking a look and make an adjustment, yes. The SPF-Record is also in the help articles from us. Just in case.

We have changed the default DNS for all new domains but can not do this for older domains, as this would overwrite individual DNS settings 🙃

---

<div class="post-metadata">

**Author:** ![Armin\_Hang](https://avatars.discourse-cdn.com/v4/letter/a/b4bc9f/32.png) [@Armin\_Hang](https://community.sitejet.io/u/Armin_Hang)\
**Post date:** [July 4, 2023, 12:44pm UTC](https://community.sitejet.io/t/security-issue-emails-to-gmail-not-deliverable-adjust-spf-record/2498/4 "2023-07-04T12:44:49Z")

</div>

Hallo… nacdem ich letzte Woche zwangsweise und mit GROSSEM EINSATZ DES HERVORRAGENDEN SITEJET SUPPORTES (das musste mal öffentlich gesagt sein) viel zum Thema DNS Einträge gelernt habe wie man mehrere SPF Einträge zusammenfasst wollte ich mich demnächst dem Thema DMARC widmen 😉 Warum bietet Ihr darauf keinen Zugriff? das wäre doch eine starke Steigerung der Vertrauenswürdigkeit.

---

<div class="post-metadata">

**Author:** ![Andre](https://dub1.discourse-cdn.com/flex017/user_avatar/community.sitejet.io/andre/32/3459_2.png) [@Andre](https://community.sitejet.io/u/Andre)\
**Post date:** [July 5, 2023, 8:33am UTC](https://community.sitejet.io/t/security-issue-emails-to-gmail-not-deliverable-adjust-spf-record/2498/5 "2023-07-05T08:33:52Z")

</div>

There is actually a feature request for DMARC 🙂

> [@I'd like to setup DKIM](https://community.sitejet.io/t/id-like-to-setup-dkim/731):
>
> Hey there, I’d love to setup DKIM, DMARC etc. DKIM is not present as an option at the moment?

---

<div class="post-metadata">

**Author:** ![Andre](https://dub1.discourse-cdn.com/flex017/user_avatar/community.sitejet.io/andre/32/3459_2.png) [@Andre](https://community.sitejet.io/u/Andre)\
**Post date:** [March 4, 2024, 11:01am UTC](https://community.sitejet.io/t/security-issue-emails-to-gmail-not-deliverable-adjust-spf-record/2498/6 "2024-03-04T11:01:13Z")

</div>