• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Local mails are marked as SPAM using the new DMARC feature

Thomas Poisl

Basic Pleskian
I recently upgraded to plesk 12.5 and tried the new DMARC feature for incoming mails "Enable DMARC to check incoming mail".

After that I noticed, that all mails that are send from my server to an email address, that is hosted on the server were marked as SPAM by DMARC.

My guess is that this is due to the fact, that the hostname of my virtual server is different from the hosted domains and provided by my ISP.

But the reverse entries for my IPs is pointing to the correct domain.

The ISP suggests not to change the server hostname in it's FAQ.

Do you have some advice for me, how to use the DMARC feature for incoming mail correctly?
 
Hi Thomas Poisl,

The ISP suggests not to change the server hostname in it's FAQ.
You can safely ignore that.

Do you have some advice for me, how to use the DMARC feature for incoming mail correctly?
You can use the "/etc/aliases" file on your server, to tell postfix for example, which sender eMail it should use.

Examples ( Ubuntu/Debian ):
Code:
# See man 5 aliases for format
root:          no-reply@YOUR-DOMAIN.COM
postmaster:    root
MAILER-DAEMON: root
fail2ban:    Fail2Ban@YOUR-DOMAIN.COM
watchdog:    watchdog@YOUR-DOMAIN.COM
www-data:    root

Examples ( CentOS/RHEL ):
Code:
# See man 5 aliases for format
root:          no-reply@YOUR-DOMAIN.COM
postmaster:    root
MAILER-DAEMON: root
fail2ban:    Fail2Ban@YOUR-DOMAIN.COM
watchdog:    watchdog@YOUR-DOMAIN.COM
apache:      root
 
Thanks for your quick reply.

I have now changed the hostname, without a problem.

After enabling DMARC check for incoming mails, I did a quick check and sent a mail from one local mail account to another, unfortunately it ended up in the spam folder.

Code:
dmarc[23875]: SPF record was not found in Authentication-Results:
dmarc[23875]: DKIM record was not found in Authentication-Results:
...
dmarc[23875]: DMARC: message moved to QUARANTINE for <some_local_mailbox>@<your-domain.com>


I re-checked my configuration send a mail to DKIM Test - DKIM Verify - DKIM Validator and everything seems fine.

Any idea what is going wrong?

Also it would be great to know, which SPF and DKIM record is looked up by plesk.

BTW: After changing the hostname I saw some erros like this:
Code:
spamd[16778]: plugin: eval failed: bayes: (in learn) locker: safe_lock: cannot create tmp lockfile <some_local_mailbox>@<our-domain.com>/.spamassassin/bayes.lock.<old_server_hostname>.16778 for <some_local_mailbox>@<your-domain.com>/.spamassassin/bayes.lock: Datei oder Verzeichnis nicht gefunden

Rerunning /usr/local/psa/admin/sbin/mchk seemed to solve this problem.
 
Back
Top