Gmail and SPF

[Chris J Dixon]

I use Forte Agent to send email, via Virgin's mail servers, with
replies forwarded via my own domain email address.

I have set up the Gmail app password, which has been working

Action: failed
Final-Recipient: xxxxxxxxxxxxxxxx
Status: 5.0.0
Remote-MTA: dns; gmail-smtp-in.l.google.com
Diagnostic-Code: smtp; 550-5.7.26 Your email has been blocked because the sender is unauthenticated.
550-5.7.26 Gmail requires all senders to authenticate with either SPF or DKIM.
550-5.7.26
550-5.7.26 DKIM = did not pass
550-5.7.26 SPF [cdixon.me.uk] with ip: [84.116.50.34] = did not pass
550-5.7.26
550-5.7.26 For instructions on setting up authentication, go to
550 5.7.26 https://support.google.com/mail/answer/81126#authentication ffacd0b85a97d-37d4b989e98si2592841f8f.501 - gsmtp

The IP address varies in different messages, all allocated by
Virgin's mail server, and clearly not unique to me.

I have read the various pages of instructions, including one on
my host:
<https://www.heartinternet.uk/support/article/how-do-i-add-spf-records-to-my-site.html>

but find myself totally unable to understand exactly what to do.
It also seems like trial and error is not a good way to go, if I
correctly understand that updated entries can take up to 48 hours
to propagate.

If I send directly from Virgin's online mail page, there are no
issues.

Chris

[Chris Green]

Post by Chris J Dixon
I use Forte Agent to send email, via Virgin's mail servers, with
replies forwarded via my own domain email address.
I have set up the Gmail app password, which has been working

Action: failed
Final-Recipient: xxxxxxxxxxxxxxxx
Status: 5.0.0
Remote-MTA: dns; gmail-smtp-in.l.google.com
Diagnostic-Code: smtp; 550-5.7.26 Your email has been blocked because

the sender is unauthenticated.

550-5.7.26 Gmail requires all senders to authenticate with either SPF or DKIM.
550-5.7.26
550-5.7.26 DKIM = did not pass
550-5.7.26 SPF [cdixon.me.uk] with ip: [84.116.50.34] = did not pass
550-5.7.26
550-5.7.26 For instructions on setting up authentication, go to
550 5.7.26 https://support.google.com/mail/answer/81126#authentication

ffacd0b85a97d-37d4b989e98si2592841f8f.501 - gsmtp
The IP address varies in different messages, all allocated by
Virgin's mail server, and clearly not unique to me.
I have read the various pages of instructions, including one on
<https://www.heartinternet.uk/support/article/how-do-i-add-spf-records-to-my-site.html>
but find myself totally unable to understand exactly what to do.
It also seems like trial and error is not a good way to go, if I
correctly understand that updated entries can take up to 48 hours
to propagate.
If I send directly from Virgin's online mail page, there are no
issues.

It's the configuration at Virgin's mail servers that is either
misconfigured or simply not doing DKIM/SPF. You need to get them to
sort it out, best of luck. A web search for "SPF/DKIM on Virgin"
might get you some help.

[Andy Burns]

Post by Chris Green
It's the configuration at Virgin's mail servers that is either
misconfigured or simply not doing DKIM/SPF.

Not really, SPF is a job for the receiver's email servers and the
sender's DNS servers.

[Andy Burns]

Post by Andy Burns

Post by Chris Green
It's the configuration at Virgin's mail servers that is either
misconfigured or simply not doing DKIM/SPF.

Not really, SPF is a job for the receiver's email servers and the
sender's DNS servers.

For completeness, DKIM does also involve the sender's email servers.

[Chris Green]

Post by Andy Burns

Post by Andy Burns

Post by Chris Green
It's the configuration at Virgin's mail servers that is either
misconfigured or simply not doing DKIM/SPF.

Not really, SPF is a job for the receiver's email servers and the
sender's DNS servers.

For completeness, DKIM does also involve the sender's email servers.

I.e. Virgin.

[Chris Green]

Post by Andy Burns

Post by Chris Green
It's the configuration at Virgin's mail servers that is either
misconfigured or simply not doing DKIM/SPF.

Not really, SPF is a job for the receiver's email servers and the
sender's DNS servers.

Yes, but the sender in this case is Virgin, being used as a 'smart
host'.

[Andy Burns]

Post by Chris Green

Post by Andy Burns

Post by Andy Burns
SPF is a job for the receiver's email servers and the

sender's DNS servers.

Yes, but the sender in this case is Virgin, being used as a 'smart
host'.

Most vanity domains won't be using DKIM, and Virgin are not hosting the
sender's DNS, Heart are, and if you lookup SPF records, you'll see there
isn't one, which is why Gmail is complaining ... in short Virgin are not
to blame.

[p.s. how did the subject end up in the groups list?]