I am getting an error in sending emails from my own domain address but
via my ISP's server:
[SMTP] Cannot send message (Sending email "Re[2]: xxx" failed with
error: Email body not accepted due to the following reason:
"5.7.1 <END-OF-MESSAGE>: End-of-data rejected: SPF Incorrect
")
Any clues on where the error might be occurring based on:
My ISP is PlusNet.
I am sending it via my own domain via PlusNet (I have no idea how that
works)
I use em Client which has recently been upgraded.
It went successfully using my outlook.com address from the same email
client, where do I start looking first?
"5.7.1 <END-OF-MESSAGE>: End-of-data rejected: SPF Incorrect")You need an SPF record in the DNS for your domain, speak to whoever
I am sending it via my own domain via PlusNet
I am getting an error in sending emails from my own domain address
but via my ISP's server:
[SMTP] Cannot send message (Sending email "Re[2]: xxx" failed with
error: Email body not accepted due to the following reason:
"5.7.1 <END-OF-MESSAGE>: End-of-data rejected: SPF Incorrect
")
Any clues on where the error might be occurring based on:
My ISP is PlusNet.
I am sending it via my own domain via PlusNet (I have no idea how
that works)
I use em Client which has recently been upgraded.
It went successfully using my outlook.com address from the same
email client, where do I start looking first?
Jeff Gaines wrote
I am getting an error in sending emails from my own domain address
but via my ISP's server:
Not sure, but are the emails apparently originating from your own
domain or email address?
I've been plagued for the past couple of months with phishing emailsIf you have your own domain, you should set an SPF record that lists the servers authorised to send on your behalf, that should make it easier
that present themselves as coming from my domain email manager, and
spoof the "from" field to make it look as if they're coming from my
own address and domain. The claim is that my message storage space
is full or my message volume limit has been reached, and trying to
get me to click on a link to change my login details.
It's all nonsense, but the annoying thing is that since the spoofed
"from" address makes it appear that the emails originate from my own
domain, I haven't wanted to block them as spam in case the filter
just looks at the apparent address and I wind up blocking myself.
So I've just been manually deleting them, as I'm not sure how to
safely block them automatically.
I am getting an error in sending emails from my own domain address but
via my ISP's server:
My ISP is PlusNet.
If so, do you have an SPF and DMARC record set in DNS, and are you signing your outgoing emails with DKIM? If not, you will have serious
deliverability issues
Alan J. Wylie wrote:
If so, do you have an SPF and DMARC record set in DNS, and are you signing >> your outgoing emails with DKIM? If not, you will have serious
deliverability issues
I think you're stating it a little too strongly, implying that all
three of SPF, DKIM and DMARC are required.
Certainly email services have rightly been getting stricter in their requirements, but in general either SPF or DKIM will see mail
accepted, provided that everything matches, and for most users SPF is
easiest to organise.
I run a mailing list for my mountaineering club. Previously, mail was delivered fine with the From: address being that of the sender, no DMARC record and any DKIM signature being the original one from the senders
mail provider.
I am getting an error in sending emails from my own domain address but
via my ISP's server:
[SMTP] Cannot send message (Sending email "Re[2]: xxx" failed with
error: Email body not accepted due to the following reason:
"5.7.1 <END-OF-MESSAGE>: End-of-data rejected: SPF Incorrect
")
Any clues on where the error might be occurring based on:
My ISP is PlusNet.
I am sending it via my own domain via PlusNet (I have no idea how that
works)
I use em Client which has recently been upgraded.
It went successfully using my outlook.com address from the same email
client, where do I start looking first?
On 08/01/2025 16:48, Jeff Gaines wrote:
I am getting an error in sending emails from my own domain address but
via my ISP's server:
[SMTP] Cannot send message (Sending email "Re[2]: xxx" failed with error: >>Email body not accepted due to the following reason:
"5.7.1 <END-OF-MESSAGE>: End-of-data rejected: SPF Incorrect
")
Any clues on where the error might be occurring based on:
My ISP is PlusNet.
I am sending it via my own domain via PlusNet (I have no idea how that >>works)
I use em Client which has recently been upgraded.
It went successfully using my outlook.com address from the same email >>client, where do I start looking first?
The Sender Policy Framework (SPF) mechanism is a way that a domain can >advertise which SMTP servers will legitimately handle sending email for a >domain. It allows (among other things) the receiver to make an estimation
of how it is that a email is coming from a legit server. If the
originating SMTP server does not match that indicated in the SPF record,
then it is more likely that it is a spoof. Absence of a SPF record (or an >incorrect record) make it harder to get your email delivered.
I seem to recall plusnet tightened up on mail verification some time back, >and hence may be verifying that senders have a proper SPF record.
To see if you have a SPF record, open a command prompt, and enter:
nslookup -type=txt <yourdomainname>
You should have a txt record that looks like:
"v=spf1 include:_spf-internal.plus.net include:_spf-internal2.plus.net
~all"
That tells any server processing your email to lookup the server addresses >pull in the list of IP addresses contained in text records attached to
those two plusnet sub domains.
So if you don't see a record like that you need to add one in the DNS >management control panel of your domain registrar.
On 09/01/2025 in message <vln6db$31eg0$1@dont-email.me> John Rumm wrote:
On 08/01/2025 16:48, Jeff Gaines wrote:
I am getting an error in sending emails from my own domain address
but via my ISP's server:
[SMTP] Cannot send message (Sending email "Re[2]: xxx" failed with
error: Email body not accepted due to the following reason:
"5.7.1 <END-OF-MESSAGE>: End-of-data rejected: SPF Incorrect
")
Any clues on where the error might be occurring based on:
My ISP is PlusNet.
I am sending it via my own domain via PlusNet (I have no idea how
that works)
I use em Client which has recently been upgraded.
It went successfully using my outlook.com address from the same email
client, where do I start looking first?
The Sender Policy Framework (SPF) mechanism is a way that a domain can
advertise which SMTP servers will legitimately handle sending email
for a domain. It allows (among other things) the receiver to make an
estimation of how it is that a email is coming from a legit server. If
the originating SMTP server does not match that indicated in the SPF
record, then it is more likely that it is a spoof. Absence of a SPF
record (or an incorrect record) make it harder to get your email
delivered.
I seem to recall plusnet tightened up on mail verification some time
back, and hence may be verifying that senders have a proper SPF record.
To see if you have a SPF record, open a command prompt, and enter:
nslookup -type=txt <yourdomainname>
You should have a txt record that looks like:
"v=spf1 include:_spf-internal.plus.net include:_spf-internal2.plus.net
~all"
That tells any server processing your email to lookup the server
addresses pull in the list of IP addresses contained in text records
attached to those two plusnet sub domains.
So if you don't see a record like that you need to add one in the DNS
management control panel of your domain registrar.
Many thanks John :-)
I have found that email, it said:
"If your nameservers are managed by Heart Internet, there’s no need to
take any action - our team has already made the necessary updates for you."
So I ignored it.
However from following your advice it seems I have no SPF record so I followed Heart's instructions which say "Log in to your Domain Control
Panel and navigate to ‘DNS Management’.
There is no "DNS Management" to navigate to!
I will raise a ticket with them. Their admin is appalling but when I
tried to move away it seemed I had to set up my own records at Mythic
Beasts and that was way beyond me.
Might be worth me doing a wiki page on DIY email setups by the sounds of
it.
I will raise a ticket with [Heart]. Their admin is appalling but when I tried to move away it seemed I had to set up my own records at Mythic Beasts and that was way beyond me.
On 09/01/2025 09:41, Jeff Gaines wrote:
I will raise a ticket with [Heart]. Their admin is appalling but when I >>tried to move away it seemed I had to set up my own records at Mythic >>Beasts and that was way beyond me.
Setting up SPF for your domain hosted on Heart will be similar if you
don't use the EMail provided by Heart. If you don't use Heart's EMail
servers they don't know whose servers you do use, so they can't set SPF up >automatically for your domain.
It's really up to the people whose servers you do use to tell you what to
use to identify their mail servers, and up to the hosting company to tell
you how to put that into an SPF record on their DNS.
I find the help on Mythic Beasts's website very good, and their support >people are very helpful and responsive when the help isn't quite enough.
If you use Mythic Beasts for both mail and domain hosting then setting up
SPF and DKIM are one-click operations, if you don't then you have to do a >little work, but they do tell you what you need to do.
On 09/01/2025 in message <vlo87i$3agr2$1@dont-email.me> John Rumm wrote:
Might be worth me doing a wiki page on DIY email setups by the sounds of >>it.
Oh god, yes please, make sure it has a beginners' section for me!
HVS wrote:
Jeff Gaines wrote
I am getting an error in sending emails from my own domain
address but via my ISP's server:
Not sure, but are the emails apparently originating from your own
domain or email address?
He's not having problems with received email, but he's being
blocked from sending.
I've been plagued for the past couple of months with phishing
emails that present themselves as coming from my domain email
manager, and spoof the "from" field to make it look as if they're
coming from my own address and domain. The claim is that my
message storage space is full or my message volume limit has been
reached, and trying to get me to click on a link to change my
login details.
It's all nonsense, but the annoying thing is that since the
spoofed "from" address makes it appear that the emails originate
from my own domain, I haven't wanted to block them as spam in
case the filter just looks at the apparent address and I wind up
blocking myself.
So I've just been manually deleting them, as I'm not sure how to
safely block them automatically.
If you have your own domain, you should set an SPF record that
lists the servers authorised to send on your behalf, that should
make it easier for emails from unauthorised servers to be
rejected.
On 09/01/2025 in message <xn0p0liqk2k6y7d006@news.individual.net> Jeff
Gaines wrote:
On 09/01/2025 in message <vlo87i$3agr2$1@dont-email.me> John Rumm wrote:
Might be worth me doing a wiki page on DIY email setups by the sounds
of it.
Oh god, yes please, make sure it has a beginners' section for me!
Follow up.
Heart replied to the ticket within 10 minutes and said they would set up default SPF records so I think I was right in believing they should have
done this.
One domain is now fine, I suspect they only answered the first point so
I have jogged them that there are two domains affected.
On 09/01/2025 in message <vloomt$3df8k$1@dont-email.me> Daniel James wrote:
On 09/01/2025 09:41, Jeff Gaines wrote:
I will raise a ticket with [Heart]. Their admin is appalling but when
I tried to move away it seemed I had to set up my own records at
Mythic Beasts and that was way beyond me.
Setting up SPF for your domain hosted on Heart will be similar if you
don't use the EMail provided by Heart. If you don't use Heart's EMail
servers they don't know whose servers you do use, so they can't set
SPF up automatically for your domain.
It's really up to the people whose servers you do use to tell you what
to use to identify their mail servers, and up to the hosting company
to tell you how to put that into an SPF record on their DNS.
I find the help on Mythic Beasts's website very good, and their
support people are very helpful and responsive when the help isn't
quite enough. If you use Mythic Beasts for both mail and domain
hosting then setting up SPF and DKIM are one-click operations, if you
don't then you have to do a little work, but they do tell you what you
need to do.
I must admit I find it very confusing working out who does what!
Plusnet is my ISP, I only use their email address for correspondence
with them.
I have 2 x domains hosted with Heart but my email client is set up to
log on to the Heart servers so although I send email from my email
program I think Plusnet only connects me to the Internet, Heart does all
the addressing stuff.
I must admit I find it very confusing working out who does what!
Yup it can get confusing...
Plusnet is my ISP, I only use their email address for correspondence with >>them.
I have 2 x domains hosted with Heart but my email client is set up to log >>on to the Heart servers so although I send email from my email program I >>think Plusnet only connects me to the Internet, Heart does all the >>addressing stuff.
Earlier I got the impression that you might be trying to send mail for
your domain via the plusnet mail server (you did say "I am getting an
error in sending emails from my own domain address but via my ISP's >server"). You might have been able to get that to work in the past, but >plusnet would likely block it now.
However connecting to the mail servers that belong to the actual host of
your mailbox is the proper way to do it. In that case, all plusnet is
doing is providing the connection and play no further part in it.
I got the impression that you might be trying to send mail for your
domain via the plusnet mail server
John Rumm wrote:
I got the impression that you might be trying to send mail for your
domain via the plusnet mail server
That's how I read it too ...
In uk.d-i-y Andy Burns <usenet@andyburns.uk> wrote:
John Rumm wrote:
I got the impression that you might be trying to send mail for your >>>domain via the plusnet mail server
That's how I read it too ...
Me too.
The general rule of thumb is that email should go out by the same provider >that it comes in, ie if you host example.com at XYZ Hosting, you should
send mail that claims to be from you@example.com via XYZ Hosting. XYZ >Hosting should take care of the necessary SPF/etc to make this possible >(although check their control panel in case it's a setting you need to >enable).
Most mail clients can accept settings for an SMTP server per account. Some >older ones can't, so unfortunately they aren't suitable for modern use.[*]
Theo
[*] You could I suppose run a local smarthost on a RPi or something whose
job it is to accept messages from your old client and work out which
upstream server to send the messages to. That is left as a DIY for the >reader.
I suspect "I am sending it via my own domain via PlusNet (I have no idea
how that works)" is causing confusion
Anyway it works now!
Jeff Gaines wrote:
I suspect "I am sending it via my own domain via PlusNet (I have no idea >>how that works)" is causing confusion
I think the actual confusion is from "sending emails from my own domain >address but via my ISP's server" which to me implies relay.plus.net
Anyway it works now!
I thought you sorted it a while back by moving away from Heart?
In uk.d-i-y Jeff Gaines <jgnewsid@outlook.com> wrote:
On 10/01/2025 in message <luckvlF70ltU1@mid.individual.net> Andy Burns >>wrote:
Jeff Gaines wrote:
I suspect "I am sending it via my own domain via PlusNet (I have no idea >>>>how that works)" is causing confusion
I think the actual confusion is from "sending emails from my own domain >>>address but via my ISP's server" which to me implies relay.plus.net
Anyway it works now!
I thought you sorted it a while back by moving away from Heart?
That failed because Mythic Beasts expected me to update MX records and >>that's not for me. If there was a way to transfer by getting a PIC or MAC >>or whatever I would consider it but I have a spread of email accounts so >>one will usually work!
It sounds like you moved the hosting but you didn't move the domain >registration. If you move the domain to Mythic Beasts as well, they can >handle the DNS for you. If you don't move the domain, you have to edit the >DNS yourself (either adding DNS records like MXes manually, or changing the >DNS servers wholesale to point to Mythic's DNS server).
There's no 'one touch switch' processes for domains, you're expect to know >what you're doing. The best you can do is move the domain registration (at >which point everything will stop working, temporarily) and then ask the new >host to set everything up their way. That does not include transferring >across old websites or email boxes unless you specifically ask them to.
Theo
On 10/01/2025 in message <luckvlF70ltU1@mid.individual.net> Andy Burns
wrote:
Jeff Gaines wrote:
I suspect "I am sending it via my own domain via PlusNet (I have no idea >>how that works)" is causing confusion
I think the actual confusion is from "sending emails from my own domain >address but via my ISP's server" which to me implies relay.plus.net
Anyway it works now!
I thought you sorted it a while back by moving away from Heart?
That failed because Mythic Beasts expected me to update MX records and
that's not for me. If there was a way to transfer by getting a PIC or MAC
or whatever I would consider it but I have a spread of email accounts so
one will usually work!
I already had a domain hosted with Mythic Beasts which I had transferred
from Heart
Jeff Gaines wrote:
I already had a domain hosted with Mythic Beasts which I had transferred >>from Heart
Previously Heart got gobbled up by GoDaddy (as part of Host Europe) but
now they seem to have become part of <https://your.online> which, perhaps >worryingly, seems to be offline ...
On 10/01/2025 in message <BSw*1re4z@news.chiark.greenend.org.uk> Theo
wrote:
In uk.d-i-y Andy Burns <usenet@andyburns.uk> wrote:
John Rumm wrote:
I got the impression that you might be trying to send mail for your
domain via the plusnet mail server
That's how I read it too ...
Me too.
The general rule of thumb is that email should go out by the same
provider
that it comes in, ie if you host example.com at XYZ Hosting, you should
send mail that claims to be from you@example.com via XYZ Hosting. XYZ
Hosting should take care of the necessary SPF/etc to make this possible
(although check their control panel in case it's a setting you need to
enable).
Most mail clients can accept settings for an SMTP server per account.
Some
older ones can't, so unfortunately they aren't suitable for modern
use.[*]
Theo
[*] You could I suppose run a local smarthost on a RPi or something whose
job it is to accept messages from your old client and work out which
upstream server to send the messages to. That is left as a DIY for the
reader.
I have to say this is beyond me, I said:
"Any clues on where the error might be occurring based on:
My ISP is PlusNet.
I am sending it via my own domain via PlusNet (I have no idea how that
works)
I use em Client which has recently been upgraded.
It went successfully using my outlook.com address from the same email
client, where do I start looking first?"
I suspect "I am sending it via my own domain via PlusNet (I have no idea
how that works)" is causing confusion, my ISP is PlusNet so that's how I
get on to the Internet, the details in my email program are the Heart Internet details. Seems I am connecting to my domain server via my
PlusNet connection?
Anyway it works now!
On 10/01/2025 12:31, Jeff Gaines wrote:
On 10/01/2025 in message <BSw*1re4z@news.chiark.greenend.org.uk> Theo >>wrote:
In uk.d-i-y Andy Burns <usenet@andyburns.uk> wrote:
John Rumm wrote:
I got the impression that you might be trying to send mail for your >>>>>domain via the plusnet mail server
That's how I read it too ...
Me too.
The general rule of thumb is that email should go out by the same >>>provider
that it comes in, ie if you host example.com at XYZ Hosting, you should >>>send mail that claims to be from you@example.com via XYZ Hosting. XYZ >>>Hosting should take care of the necessary SPF/etc to make this possible >>>(although check their control panel in case it's a setting you need to >>>enable).
Most mail clients can accept settings for an SMTP server per account. >>>Some
older ones can't, so unfortunately they aren't suitable for modern >>>use.[*]
Theo
[*] You could I suppose run a local smarthost on a RPi or something whose >>>job it is to accept messages from your old client and work out which >>>upstream server to send the messages to. That is left as a DIY for the >>>reader.
I have to say this is beyond me, I said:
"Any clues on where the error might be occurring based on:
My ISP is PlusNet.
I am sending it via my own domain via PlusNet (I have no idea how that >>works)
I use em Client which has recently been upgraded.
It went successfully using my outlook.com address from the same email >>client, where do I start looking first?"
I suspect "I am sending it via my own domain via PlusNet (I have no idea >>how that works)" is causing confusion, my ISP is PlusNet so that's how I >>get on to the Internet, the details in my email program are the Heart >>Internet details. Seems I am connecting to my domain server via my
PlusNet connection?
Anyway it works now!
I used EM Client for a couple of email addresses for several years. It's
free for 2 addresses. Don't need calendar, chat etc.
When Microsoft updated their authentication EM had to update their client
& the emails failed.
Luckily I managed to get the emails to authenticate with another client. >Can't remember which but I can look it up if needed. I should also say
that these previously working emails wouldn't authenticate with
Thunderbird, Betterbird or several other clients that I tried.
Several months later I tried EM Client again & the addresses authenticated.
- https://www.emclient.com/
On 11/01/2025 in message <vltflc$ih20$1@dont-email.me> wasbit wrote:
On 10/01/2025 12:31, Jeff Gaines wrote:
On 10/01/2025 in message <BSw*1re4z@news.chiark.greenend.org.uk> Theo
wrote:
In uk.d-i-y Andy Burns <usenet@andyburns.uk> wrote:
John Rumm wrote:
I got the impression that you might be trying to send mail for your >>>>>> domain via the plusnet mail server
That's how I read it too ...
Me too.
The general rule of thumb is that email should go out by the same
provider
that it comes in, ie if you host example.com at XYZ Hosting, you should >>>> send mail that claims to be from you@example.com via XYZ Hosting. XYZ >>>> Hosting should take care of the necessary SPF/etc to make this possible >>>> (although check their control panel in case it's a setting you need to >>>> enable).
Most mail clients can accept settings for an SMTP server per
account. Some
older ones can't, so unfortunately they aren't suitable for modern
use.[*]
Theo
[*] You could I suppose run a local smarthost on a RPi or something
whose
job it is to accept messages from your old client and work out which
upstream server to send the messages to. That is left as a DIY for the >>>> reader.
I have to say this is beyond me, I said:
"Any clues on where the error might be occurring based on:
My ISP is PlusNet.
I am sending it via my own domain via PlusNet (I have no idea how
that works)
I use em Client which has recently been upgraded.
It went successfully using my outlook.com address from the same email
client, where do I start looking first?"
I suspect "I am sending it via my own domain via PlusNet (I have no
idea how that works)" is causing confusion, my ISP is PlusNet so
that's how I get on to the Internet, the details in my email program
are the Heart Internet details. Seems I am connecting to my domain
server via my PlusNet connection?
Anyway it works now!
I used EM Client for a couple of email addresses for several years.
It's free for 2 addresses. Don't need calendar, chat etc.
When Microsoft updated their authentication EM had to update their
client & the emails failed.
Luckily I managed to get the emails to authenticate with another
client. Can't remember which but I can look it up if needed. I should
also say that these previously working emails wouldn't authenticate
with Thunderbird, Betterbird or several other clients that I tried.
Several months later I tried EM Client again & the addresses
authenticated.
- https://www.emclient.com/
eM Client does keep up to date BUT sometimes only via a new version so
there is a cost depending on how many email accounts you need. At the
last update (v10) they introduced a personal licence covering 3 x
computers which seemed a good deal.
In respect of authentication I have closed all my Yahoo accounts, they changed their process so frequently nobody could keep up.
The only issue I have with MSFT (outlook.com) is they demand re- authentication on my Android devices every three months which is a pain
as I use long password safe produced passwords and re-entering that is a killer!
So far Gmail seems OK...
The only issue I have with MSFT (outlook.com) is they demand re- >>authentication on my Android devices every three months which is a pain
as I use long password safe produced passwords and re-entering that is a >>killer!
You should be able to setup 2FA for authentication to save re-entering the >password.
However from following your advice it seems I have no SPF record so I followed Heart's instructions which say "Log in to your Domain Control
Panel and navigate to ‘DNS Management’.
There is no "DNS Management" to navigate to!
I will raise a ticket with them. Their admin is appalling but when I
tried to move away it seemed I had to set up my own records at Mythic
Beasts and that was way beyond me.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 415 |
Nodes: | 16 (1 / 15) |
Uptime: | 34:36:54 |
Calls: | 8,719 |
Calls today: | 2 |
Files: | 13,276 |
Messages: | 5,956,023 |