• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Resolved Google to soon require ARC for forwarded messages

If I can't do anything else, I will use "relaxed" DMARC, I will explain to the domain owner that isn't possible right now to use strict.

I didn't really notice that example.com didn't have a DMARC on the main domain because was passing all the tests. It never worked with strict mode, I just didn't realise about the the lack of DMARC.
 
"relaxed" mode is the correct mode to use, in your case, and generally in most others, since subdomains are being used in the sending of the mail.
 
I don't quite get why SPF & SRS weren't enough. They were simple. They specified where a domain's email could come from and enabled forwarding to work.
The thing is that enabling forwarding to work with spf also allows spamming to work.
 
Back
Top