Hi,
Before I bother Richard at Orpheus, has anyone else experienced this?
Somtimes, Google refuses to allow mail to arrive or be accepted from my domains. This is not consistent.
So you need to talk to your hosting company to get your SPF and DKIM
records created on your domains ASAP.
On 18 Oct, Chris Hughes wrote in message
<3e7559f55a.chris@mytardis>:
So you need to talk to your hosting company to get your SPF and DKIM
records created on your domains ASAP.
You will also need to take care that you only send email out through the
SMTP relay that is associated with your email domain.
SPF is about the recipient (Google, in this case) looking at the domain part of an incoming email, pulling up the associated SPF record, and then
checking that the originating relay is covered by that record. Unless you make special arrangements, this is only likely to be true for the relay provided by the host of your domain's email service.
The date being 18 Oct 2023, Steve Fryatt <news@stevefryatt.org.uk> decided
to write:
On 18 Oct, Chris Hughes wrote in message
<3e7559f55a.chris@mytardis>:
So you need to talk to your hosting company to get your SPF and DKIM
records created on your domains ASAP.
That's if they can understand the problem and provide the fix!
You will also need to take care that you only send email out through the
SMTP relay that is associated with your email domain.
SPF is about the recipient (Google, in this case) looking at the domain part >> of an incoming email, pulling up the associated SPF record, and then
checking that the originating relay is covered by that record. Unless you
make special arrangements, this is only likely to be true for the relay
provided by the host of your domain's email service.
I've now got round this problem by adding a Sender: header which includes
the domain from which I'm actually sending the message.
The From: header can be in a different domain such as the organisation
you're sending mail on behalf of.
So for example I might have:
From: Richard Porter <richard@minimarcos.org.uk>
Sender: ricp@minijem.plus.com
where I'm sending via relay.plus.net. The recipient would normally just
see the From: address.
I'm currently struggling to get NetFetch working so I can send from
multiple STMP servers. POPstar can only send to one.
I've now got round this problem by adding a Sender: header which includes
the domain from which I'm actually sending the message.
The date being 19 Oct 2023, Chris Hughes <news13@noonehere.co.uk> decided
to write:
If a hosting compnay does not understand how to add an SPF record and DKIM etc. then they are not a 'skilled' organisation.
The problem is that the people on the help desk aren't the ones that are familiar the software and protocols.
If a hosting compnay does not understand how to add an SPF record and DKIM etc. then they are not a 'skilled' organisation.
I'm currently struggling to get NetFetch working so I can send from
multiple STMP servers. POPstar can only send to one.
I am in the process of writting an article on how to do this. In the meantime if you want to contact me direct I can probably help you.
It looks like you do have an SPF record:
minimarcos.org.uk. 3600 IN TXT "v=spf1 ip4:5.77.32.195 +a ~all"
which says that your genuine emails will come from the SMTP server at 5.77.32.195
That server appears to be a CPanel instance at https://newvictorious.theukhost.net:2083/ which is presumably your webmail host and, as mail.minimarcos.org.uk, your SMTP server.
So it seems like your hosting company has set things up for you, but you
need to configure your email program to send your SMTP mail via mail.minimarcos.org.uk rather than another SMTP server. If you do that you should be obeying the SPF on your domain and you shouldn't have such problems.
Adding a Sender: header won't cut it, I'm afraid - any spammer worth their salt would already be sending one of those.
"We have checked our servers and can see no reason for the rejection even
an external checker agrees that the domain has SPF and DKIM. I am sorry
but you will have to discuss this with Google, especially as other emails
on the domain get through with no issues. It may be that they don't like
the address being so short and neat, but that's just an odd thought.
Regards Richard"
An update.
I contacted my domain host, in this case Richard at Orpheus.
Here's his reply which he is happy to share.
"We have checked our servers and can see no reason for the rejection
even an external checker agrees that the domain has SPF and DKIM. I am
sorry but you will have to discuss this with Google, especially as other emails on the domain get through with no issues. It may be that they
don't like the address being so short and neat, but that's just an odd thought. Regards Richard"
Received: from FAST.plusdsl.net (182.30.200.146.dyn.plus.net [146.200.30.182])
(authenticated bits=0)
by newrex.genesysnet.co.uk (8.15.2/8.15.2) with ESMTPA id
39JCfsts3756075
for <chris@noonehere.co.uk>; Thu, 19 Oct 2023 13:41:54 +0100
So it appears you are not actually sending direct from your npost.uk
domain, but posting via PlusNet (who you used to be with when posted using your waitrose.com address (John Lewis Broadband))
Doing a Whois lookup on 182.30.200.146.dyn.plus.net says it belongs to
Amazon !
While 146.200.30.182 belongs to PlusNet
An update.
I contacted my domain host, in this case Richard at Orpheus.
Here's his reply which he is happy to share.
"We have checked our servers and can see no reason for the rejection
even an external checker agrees that the domain has SPF and DKIM. I am
sorry but you will have to discuss this with Google, especially as other emails on the domain get through with no issues. It may be that they
don't like the address being so short and neat, but that's just an odd thought. Regards Richard"
To explain, I have three e-address at my domain npost.uk thus:-
cjazz
mec
gr
Chris Hughes <news13@noonehere.co.uk> wrote:
Received: from FAST.plusdsl.net (182.30.200.146.dyn.plus.net
[146.200.30.182])
(authenticated bits=0)
by newrex.genesysnet.co.uk (8.15.2/8.15.2) with ESMTPA id
39JCfsts3756075
for <chris@noonehere.co.uk>; Thu, 19 Oct 2023 13:41:54 +0100
So it appears you are not actually sending direct from your npost.uk
domain, but posting via PlusNet (who you used to be with when posted using >> your waitrose.com address (John Lewis Broadband))
Doing a Whois lookup on 182.30.200.146.dyn.plus.net says it belongs to
Amazon !
While 146.200.30.182 belongs to PlusNet
I think 146.200.30.182 is the IP address of Chris' Plusnet home broadband router. He uses this to connect to the SMTP server at Orpheus, which is newrex.genesysnet.co.uk, and hosts the npost.uk domain.
That looks fine. It's the next stage onwards that's important for SPF checks, and we aren't seeing that here.
In message <f6n*w+otz@news.chiark.greenend.org.uk> Theo
<theom+news@chiark.greenend.org.uk> wrote:
Chris Hughes <news13@noonehere.co.uk> wrote:
Received: from FAST.plusdsl.net (182.30.200.146.dyn.plus.net
[146.200.30.182]) (authenticated bits=0) by newrex.genesysnet.co.uk
(8.15.2/8.15.2) with ESMTPA id 39JCfsts3756075 for
<chris@noonehere.co.uk>; Thu, 19 Oct 2023 13:41:54 +0100
So it appears you are not actually sending direct from your npost.uk
domain, but posting via PlusNet (who you used to be with when posted
using your waitrose.com address (John Lewis Broadband))
Doing a Whois lookup on 182.30.200.146.dyn.plus.net says it belongs
to Amazon ! While 146.200.30.182 belongs to PlusNet
I think 146.200.30.182 is the IP address of Chris' Plusnet home
broadband router. He uses this to connect to the SMTP server at
Orpheus, which is newrex.genesysnet.co.uk, and hosts the npost.uk
domain. That looks fine. It's the next stage onwards that's
important for SPF checks, and we aren't seeing that here.
He is not a PlusNet (John Lewis broadband) customer anymore! So should
not be using a PlusNet address I would say. His provider is Orpheus,
not PlusNet.
I still have the georgia.rambler at gmail account but have set that to automatically forward all the mail to my gr domain.
On 2023-10-21, Chris Newman <mec@npost.uk> wrote:
I still have the georgia.rambler at gmail account but have set that to automatically forward all the mail to my gr domain.
I'd found one relating to booking jazz bands which looked as if it might
be connected.
Either way, though. When an email arrives at your gr at npost account,
having been forwarded on by Gmail, what happens if you reply to it?
Do you reply from the npost address, or does Pluto (?) notice that the
To of the original email was set to an @gmail.com address and then set
the From of the reply so that it looks as if you're replying from the
same Gmail account?
If the latter, then that's your problem. In this era of SPF, you can't
spoof email accounts like that unless you have NetFetch set to route
all emails with an @gmail.com From address through Google's SMTP relay instead of your Orpheus one.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 307 |
Nodes: | 16 (2 / 14) |
Uptime: | 120:22:47 |
Calls: | 6,854 |
Files: | 12,358 |
Messages: | 5,416,991 |