• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • 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.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved Outgoing email messages still DKIM signed when option is disabled for domain

Kaspar

API expert
Plesk Guru
Username:

TITLE

Outgoing email messages still DKIM signed when option is disabled for domain

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Centos 7.9
Plesk: 18.0.54.1

PROBLEM DESCRIPTION

When the option to sign outgoing email messages with DKIM is disabled for a domain emails are still signed.

STEPS TO REPRODUCE

1) On Tools & Settings > mail server settings > have the Allow signing outgoing mail settings enabled.
2) Add domain to Plesk, after creation go to Mail Settings of domain and disable the "Use DKIM spam protection system to sign outgoing email messages" option.
3) Create an email address, login to the email account via webmail (of use a mail client) and send an email.
4) Notice how the send email is actually DKIM signed.

ACTUAL RESULT

Send email is DKIM signed

EXPECTED RESULT

Email should not be signed with DKIM if option is disabled for the domain

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Developers were not able to reproduce it yet. Still testing. Could any other specific, custom configurations play a role?
 
Test engineers have completed tests, but were unable to reproduce the issue. They have checked the outgoing mail headers to determine whether a DKIM signature is present or not, but had not DKIM signature. They recommend to create a support ticket so that the case can be checked on the affected server by support staff.
 
Well this is embarrassing. After re-testing the issue it seems like the issue is actually (and strangely) on the receiving side (on which Plesk isn't used). I should have noticed that when testing. Sorry about that. Issue can be ignored and closed.
 
Last edited:
Back
Top