Outgoing mail rejected from today

[#1]

Today my outgoing mail has started to be rejected by your relay. Even the bounce messages are being rejected!

I have three domains, each of which needs an outgoing VM server to attach the appropriate DKIM signature. I have to send them through your relay because that is your policy resulting in a listing in Spamhaus and similar lists for my IP address. However, it seems you're now rejecting my mail because it comes from my own domains, which it must do in order to have a consistent reply address, since you no longer provide an incoming mailbox.

The log is as follows:

I need my mail working as this is a time-sensitive grant application for a £60,000 grant for church repairs and it needs to be in tomorrow.

Moderator's note:
Personal information removed (to an area staff can see) as per Forum rules.

[#2]

If your communication requirements are urgent, then using webmail might be a pragmatic mitigation.  You can set the sender identity to be anything you need so long as the sender domain has a SPF configuration to send via the PlusNET relay.

Self hosted SMTP servers MUST use smart relay.

What do you mean by no longer provide an incoming mailbox?

[#3]

What do you mean by "smart relay". Postfix main.cf had the line:

relayhost = [relay.plus.net]

Is that what you meant?

I introduced this because complying with PN's general policy seemed preferable to trying to remove my IP from blocklists. However, yesterday it stopped working and my mail was rejected by the relay with "550 5.7.1   Unknown sender (in reply to RCPT TO command)".

A year or two ago this forum was full of messages, including from staff, pointing out PN is an Internet connection service and that e-mail was never part of the core offering and was being removed. Users must make their own arrangements to receive incoming e-mail, either by signing up to services like hotmail or gmail or by running their own incoming servers if they knew how. I took the instruction and brought my e-mail onto my own machines. I also understood at that time PN 's webmail was being closed.

As a workaround I have delisted my IP at Spamhaus and commented the relayhost line in main.cf, but I realise that's not ideal. At least it gets my mail moving again for now.

[#4]

You are picking up on a long history, much of which never came to pass (just switching off email) and has been replaced by a plan to migrate the email services to an alternative provider.

The plan is now in-flight: brands are being moved in phases and within that there have been architecture changes to prepare for the brands which have not yet 'entered' the programme.

Which brand are you using?

[#5]

Thanks for the information. I really don't know anything about this. I just followed the advice given at the time and carried on with my life.

I generally visit the forum when something goes wrong or if I'm extremely bored. My expectation as a customer is that what works will continue to work and I shouldn't need to mess around with it. How PN go about it is their concern, not mine, so long as users aren't impacted. If something is going to affect me I'd expect to be warned in advance.

Having my own servers gives me control and means I rarely get spam and everything works reliably with full control over things like DKIM, without relying on the whims of suppliers when they change their mind about implementation. However, when my IP was relisted by Spamhaus a few months ago because their exemption resets at least annually I read their note on PN's policy and decided to use the official method rather than delist again. That worked until yesterday. Maybe it was a mistake. Maybe I'm better in full control. I'm not sure now.

[#6]

That depends on the precise issue you encountered yesterday.  There is an active incident related to volume sending which has impacted all users.  It is part of the volume anti-spam measures; I suspect that the scope of the quota application has changed due to migration preparations.  The issue remains under investigation.