• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved DKIM Config

NicolaiVdS

New Pleskian
Hello,

I have followed this (https://matoski.com/article/spf-dk-dkim-plesk-debian/) guide to setup DKIM on plek but i keep getting errors and cant find the issue.

this is the respons when i mail heck-auth@verifier.port25.com

Code:
==========================================================
Summary of Results
==========================================================
SPF check:          pass
DomainKeys check:   neutral
DKIM check:         fail
DKIM check:         permerror
SpamAssassin check: ham

full respons
http://hastebin.com/atixurezaw.txt
 
DKIM is fixed in the tut it say's to add this
Code:
smtpd_milters = , inet:127.0.0.1:8891, inet:127.0.0.1:12768
this causes problems with postfix i changed it to
Code:
smtpd_milters = , inet:127.0.0.1:8891
and made sure the openDKIM is also using
Code:
Socket inet:8891@localhost
in its config file.

all i have to resolve is the DomainKeys: neutral error
 
Hi NicolaiVdS,

well, you will experience other issues now, because you left out the Plesk "pc-remote" - milter now, by leaving out "inet:127.0.0.1:12768". The correct setting would be:
Code:
smtpd_milters = , inet:127.0.0.1:12768, inet:127.0.0.1:8891

Plesk documentation ( KB - article 129288 ):
The service pc-remote here is essential for mail service on the server. In fact, Postfix will not accept incoming messages and will not process the mail queue if this service is absent or down. Postfix connects to the pc-remote service when the sender connects to the server, before the message is saved into the mail queue, before the message is sent to a remote server, and before the message is delivered to the local mailbox. Each time, Postfix submits the message to pc-remote and waits for a response.

If the message passes all filters of a particular stage of mail delivery, pc-remote gives it a go and Postfix continues the delivery.

If the message is matched by one of the filters, pc-remote might tell Postfix to reject the message (e.g., When Postfix receives mail for a mailbox that is over quota, the pc-remotemilter will reject the message), or will return the message to Postfix modified (e.g., with an added header).

Please note that pc-remote milter works only together with Postfix. This milter will be automatically removed if the "Qmail" service is used.
 
Hi NicolaiVdS,

well, you will experience other issues now, because you left out the Plesk "pc-remote" - milter now, by leaving out "inet:127.0.0.1:12768". The correct setting would be:
Code:
smtpd_milters = , inet:127.0.0.1:12768, inet:127.0.0.1:8891

Plesk documentation ( KB - article 129288 ):


ok thanks most of the issues are fixed now all thats left is
Code:
DomainKeys check:   neutral
and
Code:
SpamAssassin check: ham
any ideas how to fix these ?

http://hastebin.com/yorocevaxe.txt
 
Hi NicolaiVdS,

why do you think that
SpamAssassin check: ham

is an issue, that has to be fixed? ham = NO spam / spam = spam


Your current test with the help of "port25.com" has several tests, one is a "DomainKeys" - test, but you have only installed "DKIM" on your server. In previous Plesk versions, Plesk used "DomainKeys" to sign eMails, but with Plesk Onyx, you are now going to sign eMails with "DKIM". Both procedures are similar, but not the very same. ;)
 
Last edited by a moderator:
Back
Top