Starting on October 19, 2021, we will enable single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
To be prepared for this change and to avoid the need to register during your next ticket submission after the change, we encourage you to create an account here before October 19 using the same email address as your current Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account. You will continue to use ZenDesk authentication until we switch over to single-sign-on on October 19th.

Articles in this section

See more

MXToolbox Health Checker reports warning for a domain in Plesk: DMARC Quarantine/Reject policy not enabled

Avatar
Kuzma Ivanov
Updated
Follow
Plesk for Linux kb: how-to ABT: Group B

Applicable to:

  • Plesk for Linux

Symptoms

MXToolbox Health Checker reports the following warning for a domain in Plesk:

PLESK_INFO: DMARC Quarantine/Reject policy not enabled


1.png

Cause

By default, DMARC policy in Plesk is set to "none" (p= option):

CONFIG_TEXT: _dmarc.example.com.        TXT        v=DMARC1; p=none

Quarantine/reject policies can be configured if required. These policies request more aggressive protective actions by receivers and should be configured with care.

Resolution

This warning can be ignored.

Alternatively, configure the DMARC policy for the domain:

  1. Log in to Plesk.

  2. Go to Domains > example.com > DNS Settings.

  3. Click on the following DNS record and change the p status to quarantine or reject:

    PLESK_INFO: _dmarc.example.com. TXT v=DMARC1; p=none

  4. Apply the changes and click Update.

 

Additional Information

According to https://dmarc.org/wiki/FAQ:

PLESK_INFO: It is highly recommended that you start with a DMARC “p=none” record in order to monitor the results before moving on to a quarantine or reject policy. The goal of DMARC, when your policy is “p=reject”, is to get the receiver to reject emails that don’t come from your email infrastructure, not to help them make a decision about whether the email you did send is spam.

However, if your policy is “p=quarantine” and you have configuration issues, your mail will be placed in the spam folder because that is what you are asking for.

With a policy of “p=none”, DMARC does not change in any way how your email is handled at the receiver.

More information about these policies you may read here:

Comments

2 comments

Sort by Date Votes
  • Avatar
    Edwynn Flores Martínez

     

    What is the solution, if I see this image on https://mxtoolbox.com/ (The results are check on Green)

    My dmarc is correct in DNS setting

    _dmarc.example.com.        TXT        v=DMARC1; p=none

    I have tried mail-tester.com and I have a 10/10 rating, but it also asks me that the email is not authenticated

     

    0
    Comment actions Permalink
  • Avatar
    Anton Maslov

    Hello Edwynn Flores Martínez - you may ignore this warning. Currently, your policy "none" means if DMARC fail you still recommend accepting message from your domain. MX Toolbox recommends using more strict settings: either “p=quarantine” (will move to SPAM) or “p=reject” (will not accept at all) if DMARC fails.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles