Gmail blocking incoming mail.

[ajlelectronics]

I am getting very frustrated lately with Google randomly blocking important emails to gmail.com addresses. I get this incomprehensible bounce message...

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of
its recipients. This is a permanent error.

The following address failed:

xxx@gmail.com:
SMTP error from remote server for TEXT command, host: gmail-smtp-in.l.google.com (173.194.76.26) reason: 550-5.7.26 This mail is unauthenticated, which poses a security risk to th
e
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 [ajlelectronics.co.u
k]
550-5.7.26 did not pass with ip: [212.227.126.187]. The sender should visi
t
550-5.7.26 https://support.google.com/mail/answer/81126#authenticationfo
r
550 5.7.26 instructions on setting up authentication. u15-20020a5d434f0000
00b002d8d5fa91a7si6099999wrr.1005 - gsmtp


--- The header of the original message is following. ---

Received: from [192.168.2.209] ([31.94.16.137]) by mrelayeu.kundenserver.de
(mreue012 [212.227.15.163]) with ESMTPSA (Nemesis) id
1MVJZv-1pv4D72ZrL-00SKMv for <xxx@gmail.com>; Sun, 09 Apr 2023
17:59:31 +0200
Content-Type: multipart/mixed; boundary="------------n2LurArpTr02e2KI0k1vN5nt"
Message-ID: <53b4dcb3-bf8a-1564-c9ce-8ca973a39fd4@ajlelectronics.co.uk>
Date: Sun, 9 Apr 2023 16:59:29 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
Thunderbird/102.9.1
Reply-To: xx@ ajlelectronics.co.uk
Subject: Re:
To: xx xx <xxx@gmail.com>
References: <CAFwPFQZjwVkD5di6U0s0Q0=G0KOO6dB-2MDXsjZNyhwPsqYNPQ@mail.gmail.com>
<0ea75f10-351a-fd1b-109b-0a8392d8a155@ajlelectronics.co.uk>
<CAFwPFQYXa_=Wi68fTyn_mdUA46ePGYA64ZuuB=O4HEta6pfMmw@mail.gmail.com>
<cd692271-b889-6b72-e318-08df0f068518@ajlelectronics.co.uk>
<CAFwPFQbDPHGAQxVUbJm7zzcXuah4GCG98GqNhQOwa1NC6VuQmw@mail.gmail.com>
Content-Language: en-GB
From: "AJL Electronics (G6FGO) Ltd" <xx@ ajlelectronics.co.uk>
Organization: AJL Electronics G6FGO
In-Reply-To: <CAFwPFQbDPHGAQxVUbJm7zzcXuah4GCG98GqNhQOwa1NC6VuQmw@mail.gmail.com>
X-Provags-ID: V03:K1:HhgTRtulRIBRehpjt0XL1dcTeSfa2j1TyUVmFpyqtlFsUDY3Kul
KB4tVCBdty+UgffXcofRGPd2iIovx9uNHXk+nXVdWMdwXKwM6wAhDen5BUoRTHriFhLvRp0
sHS7CGGkp3OQdCViVeINIcvI22kqnE2+iCn1CM71K1aZ1kjAm1ypRhuSKsd/YJmJ4zoKkcN
YaVJ5KLFn5nWwP1FR8hPg==
X-Spam-Flag: NO
UI-OutboundReport: notjunk:1;M01:P0:i02pDiUqD10=;73kVCGptVv2v3a7QCTg+rezhxyO
KoY+a73zNekqMgUw1yTLCC1yFhiMDvKkQS7L63JOOeY1V182XMW13iRo6dJUtTyJ3SiLSnnpf
YUvEjDO2Q7FFXjt/bQRt8S7t/I4YhWlZVpjdRNbhu89un0Zogn0RqpZ56+mUnqfDFGVhN8qnQ
Colu/HNGhAd9KhppSDZ9f388QV+4W0YqvXPlvb0eTXV2m5mI2RemlpPUkg8wCf0TPPT9m9lxL
U8rgnfkuJq/KVC3vxeW5J7XwdABM5zFZQPIsUHtxxLSS/TbrNToYJGz8bQgHmoXWBwmm5jAfw
fHUa4FfDnFy6ihGleg/bZ2f+TYKIOlNjQlE8MepbyR1nAzh7PBa04jtUb8+/inMoabXv6axcO
qKGkooCkYhVzC1etuaAlyLHKcHntC7o6oxqhfFZ9ymYibYPUJhymkAKBhyAOKr48ShuNXjH+A
9HYjKZIPLH0tJideTG4O/R/9Jtqz6XW2s6va4St1LTk84P+TbD5EG25iZbZPoBhsUFCuk2w3u
ZAOWH3dQkRLu9E2+yhE1InwxhZEIOE9IhuLQLJ5IQHk1prN6X5RkeVsmfJRaMcz581/RH3OjF
NKD3tg5iRBDU89ux2qDNfPwKgeKl5edmkKOBmwTOJtcw10AImZ/2ehrKg2Y1VWDuvZVABwVan
5dj23OzK1Lcyo0DiBhCWLlB0mh/iqBzuxZCYWunK/w==

 

[jonclancy]

Same here. It’s a pain. I followed the link to look at setting up authentication on my outgoing mail server (Ionos), but haven’t got round to sorting it yet. I started, but glazed over with the SPF/DKIM stuff. Anyone with a plain English solution, please?

 

[qwakers]

the bounce message is clearly telling you to go here https://support.google.com/mail/answer/81126#authentication and going there tells you to setup skf and or dkim with your mail server

 

[Agrismith]

It's not just Gmail. My yahoo account gets rejected by the company account. I have a Gmail and yahoo so sometimes just can't receive anything from work.

 

[ajlelectronics]

the bounce message is clearly telling you to go here https://support.google.com/mail/answer/81126#authentication and going there tells you to setup skf and or dkim with your mail server

I went there and read what it said. It might as well have been written in Swahili. I logged into my IONOS email domain settings and I have virtually no settings that I can make. Hence the request for an English translation. I really wish that people wouldn't prostitute themselves to Google, but my opinion isn't going to make users change.

 

[roofman]

My ntl or now virgin mail bangs legitimate looking email straight into my spam for no reason...there filters seem to be set to "just in case" mode

 

[500e]

Swahili more like Arawakan
Same as you AJ settings minimal
Strange all the S**t gets through though

 

[voipio]

For the ajelectronics return email address, there's a space after the "@", but not after the gmail return address. Not saying this is the cause of the present issue, but could it cause problems with reply emails?

 

[ajlelectronics]

For the ajelectronics return email address, there's a space after the "@", but not after the gmail return address. Not saying this is the cause of the present issue, but could it cause problems with reply emails?

No, that was an edit to prevent scraping.

 

[Misterg]

Pain in the ****.

Aparently google / gmail are interpreting the header information incorrectly. This causes problems where mail relay servers are used:

Working around SPF problems delivering to Gmail | End Point Dev

www.endpointdev.com

I don't think it has happened since I added my own domain to the SPF record (which I shouldn't need to do), or it might mean that google/gmail just haven't checked the last messages.

(Edit to add: I had DKIM & SPF properly set up before the gmail issue started and still had problems because of the issue highlighted in the article above.)

 

[Craig-SM]

I had this issue and needed to add the SPF Record

v=spf1 mx a include:spf.123-reg.co.uk -all

obviously this is for an email account hosted by 123.reg.co.uk so you will need the correct one for you email provider. Took about a day for it to work but no issues with gmail emails since.

 

[ajlelectronics]

I had this issue and needed to add the SPF Record

v=spf1 mx a include:spf.123-reg.co.uk -all

obviously this is for an email account hosted by 123.reg.co.uk so you will need the correct one for you email provider. Took about a day for it to work but no issues with gmail emails since.

There appears to be no way to do that on my IONOS control panel.

 

[MetalMonkey]

Simply put it is an anti spam system that has been in place now for many years. Not just by Google.

If you check your domain with something like mxtoolbox you will see your domain fails on this check. Once you have sorted your SPF record and the changes have propagated it should pass the test, which should solve the issue.

https://mxtoolbox.com/problem/mx/dm...onics.co.uk&showlogin=1&hidepitch=0&hidetoc=1

 

[MetalMonkey]

There appears to be no way to do that on my IONOS control panel.

I've never used their hosting but there are some help articles available on their website. Might be worth a look through.

https://www.ionos.co.uk/help/domain...ds/using-ionos-spf-to-improve-email-delivery/

 

[ajlelectronics]

I've never used their hosting but there are some help articles available on their website. Might be worth a look through.

https://www.ionos.co.uk/help/domain...ds/using-ionos-spf-to-improve-email-delivery/

Useful link, thank you kindly. However it seems not possible to get that far with my domains as there are no settings available apart from redirect or delete. I will continue to look.

 

[ajlelectronics]

I have had another look and I was trying to adjust email settings rather than domain. I have now tweaked it according to the instruction and we will see what happens now. I really am very grateful for your patient help with this problem.

 

[jonclancy]

Thank you @MetalMonkey ! I have made the same changes - hopefully sorted now.

 

[skotl]

This was the same issue that we had with this forum's emails not getting to gmail accounts. Google made a change in November 2022 to mandate a valid SPF record for all inbound emails.
This forum's DNS entries didn't have one, which is why Google was bouncing emails to gmail addresses.

If you have a gmail address and are finding that lots of other emails are failing to get to you then the sender needs to update their DNS entries to include a valid SPF record. If you have a mail domain that is sending to google (actually to any!) accounts then you also need to set up this SPF record.

More info from Google / Gmail: https://support.google.com/a/answer/33786?hl=en

...and a sample SPF record (where myemail.com is the domain you're sending email from, which could also be multiple IP addresses).

v=spf1 a mx include:myemail.com -all

If you're using a mail relay service like authsmtp.com then you need to state that DNS name as the email sender. For example:

v=spf1 a mx include:authsmtp.com -all

 

[skotl]

By the way, all of that ^^^ is the relatively easy bit. You may be asking yourself "so.... where do I put this 'SPF record', then?"

It's a DNS entry so you need to go to whatever portal you use to maintain either your web presence, email hosting or DNS. As there's a million of these I can't suggest specific instructions for each one however you're looking for a menu option that allows you to set / configure something like: DNS records, MX records, CNAMES, virtual web host names, etc. You'll then add a "text record" and put in one of the lines I mentioned above.

And you only need to do this if you are sending emails directly from your own web site / application. If you're just using someone else's mail system (like yahoo.com, gmail, hotmail, outlook.com, etc.) then you don't need to do any of this and can hopefully (!) assume that the provider has already set this up!

 

[northwest]

Edit to add: I had DKIM & SPF properly set up before the gmail issue started and still had problems because of the issue highlighted in the article above.

I had the same issue so it didn't just single you out. Now I get automatic reports from Microsoft's mailservers that my domains have passed the checks, essentially spamming me about myself! You cannot win some days. As has been mentioned above, this has been policy for some time now but only in the last twelve months has it been rigorously enforced.