SRS can fix most of the Forwarding issues, but can also cause new ones.

Also with DMARC you can have it send reports for the day before of passed and failed emails arriving at the other mail services, this can be handy when setting up.

Paul

The fault is with you for forwarding email, I am afraid.

Thanks - it usually is.
It's just that this has worked well for years and now sudddenly goes wrong.

It will be a lot of work for me if I migrate the domain but may have to be faced. What I would need to be sure of though is if I do migrate to Zen as the domian host and keep my email service there that this particular problem will be removed.

Can anyone assure me that tis should be the case?

Regards

In reply to a post by ronjohnreid:

It's just that this has worked well for years and now sudddenly goes wrong.

Just what happened with me.

In reply to a post by ronjohnreid:

What I would need to be sure of though is if I do migrate to Zen as the domain host and keep my email service there that this particular problem will be removed. Can anyone assure me that this should be the case?

No. But I can tell you that it worked for me with two domains.

Thanks

I'll bite the bullet and try doing it when I have a couple of clear days

Ron

In reply to a post by ronjohnreid:

Just to clarify

Zen provides my email service and I send through Zen SMTP

I use a tld (*.org) originally registered with netnames many years ago and later taken over by speednames.uk

This is used to provide multiple email addresses (1@*.org etc) which redirect to Zen

Some emails are rejected by Zen, others not. By their nature, it is not possible to know the proportion rejected.

Speednames hosts email as well as just forwarding it. Why not host email fully on Speednames rather than forwarding to Zen accounts? I suppose it may be a question of cost.

Hi

It is not the hosting that is the problem.

The domain owner needs to set up an SPF record to say which servers can legitimately send email for that domain, simple as that. https://postmarkapp.com/guides/spf

You can move the domain or change servers all you like, but until the person who administers the domain adds a SPF TXT record, nothing changes, as emails still leave with no SPF in place and so will more likely got flagged as SPAM.

Regards

Phil

In reply to a post by PhilipD:

It is not the hosting that is the problem.

The domain owner needs to set up an SPF record to say which servers can legitimately send email for that domain, simple as that. https://postmarkapp.com/guides/spf

You can move the domain or change servers all you like, but until the person who administers the domain adds a SPF TXT record, nothing changes, as emails still leave with no SPF in place and so will more likely got flagged as SPAM.

With all due respect, you've misinterpreted the problem. The problem that the OP has is with incoming email from external domains he does not own because it is forwarded to his Zen email account from speednames.uk (the MX hosts for his domain).

Speednames.uk isn't using Sender Rewriting Scheme so emails forwarded to the Zen account have server headers which don't match the originating domain's SPF record. Zen quite correctly rejects these if the originating domain has a DMARC record requiring this - which is, in my opinion, good practice.

So, yes, it's a hosting problem. If the MX host (speednames.uk) is the same as the IMAP/POP3/Webmail host where the email is picked up from, then there's no forwarding and nothing breaks SPF/DMARC policy.

In reply to a post by PaulKirby:

SRS can fix most of the Forwarding issues, but can also cause new ones.

I agree entirely. It's best to avoid forwarding these days if at all possible.