• 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.

Issue DMARC Issue with Email Forwarding

rkonur

New Pleskian
Server operating system version
AlmaLinux 8.10
Plesk version and microupdate number
18.0.80
Hello, email forwarding isn't working properly in the Plesk panel.

Forwarding works for emails sent locally, but it doesn't work for emails coming from outside, and they are marked as DMARC FAIL.

The original email has a DMARC PASS, while the forwarded email has a DMARC FAIL;
SRS is active and working.

For example:
An email sent from outside the network is sent to [email protected]. This email is forwarded to [email protected] and [email protected],[email protected] (local emails). The original email arrives in the INBOX. The forwarded emails, however, end up in the SPAM folder. Spam score: 0.6; not spam.

An email sent from within the system to Mail:[email protected] is delivered correctly to [email protected] and [email protected],[email protected].

I’m sharing two different header entries. One shows DMARC FAIL, and the other shows DMARC PASS.

The email marked “DMARC:FAIL” is the forwarded email.
 

Attachments

  • forward.png
    forward.png
    108 KB · Views: 8
  • original.png
    original.png
    114.3 KB · Views: 8
Back
Top