• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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