In reply to a post by savamac:

despite numerous facile / insulting / hostile posts in this thread

don't you just love it?!

So having worked in IT for thirty five years you should have been aware of Sender Policy Framework and the rather long time it has taken to implement it.

http://windowsitpro.com/exchange-server/sender-polic...

That particular document dates to 2004.... you've only had thirteen years to get ready for it.

In reply to a post by marjohn56:

So having worked in IT for thirty five years you should have been aware of Sender Policy Framework and the rather long time it has taken to implement it.

http://windowsitpro.com/exchange-server/sender-polic...

That particular document dates to 2004.... you've only had thirteen years to get ready for it.

Never heard of it.

I can't see a reason to implement it as it doesn't solve the spam problem.

In reply to a post by BatBoy:

I can't see a reason to implement it as it doesn't solve the spam problem.

Its one of many small steps on the path. Each one has a small amount of impact.

In reply to a post by savamac:

PS I almost couldn't be bothered posting any more to this thread.... I worked in IT for 35 years (with a lot of experience of change management), and am not impressed by the quality of systems and "enhancements" foisted on the general public - there seems to be limited (if any) testing of changes, with regression planning being an afterthought.

35 years is an impressive time. Whilst change managers see a lot of stuff, this is a a technical attribute of email systems that SHOULD be sorted by your service provider, and as you found yours wasn't. Voting with your wallet is the best approach.

I thought the sensible thing would be to contact Zen and get a list of things (in simple terms) to ask a forwarding provider.

No! After a chat session for nearly an hour I was told to query their Sender_Rewriting_Scheme. Not very much help if you are technically challenged.

In reply to a post by Ohmygawd:

Here's the response from Zen, pretty much confirms what I thought, I cannot continue to use forwarding.

Thanks for getting in touch. The only way to enable forwarding of emails without rejection by us is for the forwarding mail server to enable sender rewriting, which would resolve the issue:

- http://www.openspf.org/SRS
- https://en.wikipedia.org/wiki/Sender_Rewriting_Scheme

So it may be worth asking your domain provider if they would be willing to do this. Alternatively you would likely need to disable forwarding and collect the mail from somewhere directly.

The current issue is being caused by the fact that the forwarding email server is technically impersonating the original sender addresses when it forwards the message. If the sender domain has an SPF record present, telling us to reject any emails from their domain name which haven't been sent from their mail server, we will now do so.

I've now sorted out POP3 and smtp with my web hosting company who were very helpful and efficient so the issue is now resolved. I'm still a bit narked that Zen didn't seem to realise what a devastating effect this policy implementation would have on any customer who is using forwarding and I strongly expect there are number of users out there who are wondering why they are no longer receiving many emails. The odd thing is that some emails were getting through, just enough to make you think there's nothing wrong.

I know it's a year over but can I ask what you actually did as I'm using zen and 1&1 and I use a catch all email from my domain the same thing I've been doing since 2002 then forward to ISP provided email and I've got some companies trying to send me emails that I want but i never get them and they are returned to company rejected. This started about the same time as this thread but SRS is supposed to have been enabled in 2015 with 1&1 so I am at a loss as to why a few that I know of are having emails sent back to them and blocked.

ZEN is my ISP currently since 2012


Thanks if you ever see this that is.

This email thing is a real pain. I expect better from Zen.

I can set things up and it all works when I test it and then for months afterwards.

Then, without any warning, it stops. !!

Come on Zen. We need forwarding to either work or not.

This intermittent rubbish is no good at all

In reply to a post by Sandgrounder:

This email thing is a real pain. I expect better from Zen.

I can set things up and it all works when I test it and then for months afterwards.

Then, without any warning, it stops. !!

Come on Zen. We need forwarding to either work or not.

This intermittent rubbish is no good at all

They might of just updated their mail service software.

We run our own mail services on our rack server in a datacentre located in France, it was working fine with SPF, DKIM and DMARC, even with forwarding etc.

Then we updated our mail software on our server then all forwarded emails were being either rejected or placed in the recipients spam folder depending on the DMARC settings for that domain.

So we had to install SRS (Sender Rewriting Scheme) now this fixed the forwarding emails.

But that now broke the normal emails due to it was altering the headers due to the sending domain differed from the mail servers domain.

So to fix this we had to add all email addresses (that are not forwarded and that we don't want the headers altered) to a list in a file for the mail service to use.

So now all works fine.

Zen probably won't do this due to how much work it will take, especially if they allow their customers to add virtual email addresses.

Paul