• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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