• We value your experience with Plesk during 2025
    Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025.
    Please take this short survey:
    https://survey.webpros.com/

Search results

  1. B

    Resolved DMARC function failure

    Issue resolved. The issue was with a server from the supplier which gave mixed responses on the _dmarc request; one respose with "v=DMARC1; p=quarantaine; ..." and next with "v=DMARC1; p=quarantine;...."
  2. B

    Resolved DMARC function failure

    Digging further I came to the conclusion that what is shown in the Plesk panel as DNS records is not the same what I recover via the commandline. The Plesk screen shows: v=DMARC1; p=quarantine; sp=quarantine; rua=mailto:abuse@domain1.net; ruf=mailto:abuse@domain1.net The 'dig TXT...
  3. B

    Resolved DMARC function failure

    Correction, there was a typo mentioned but after correction it that didn't change the outcome.
  4. B

    Resolved DMARC function failure

    Yes, did and it showed no errors. It validated. But as I wrote the DMARC policy has been working for more then a year and I haven't changed the policy setting (defined in the DNS record) for a long time.
  5. B

    Resolved DMARC function failure

    Additional. If I check the authentication result when sendin a message to Google I get the results: dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=domain1.net
  6. B

    Resolved DMARC function failure

    I am running Plesk Obsidian 18.0.34 Update #2 on Centos 7.9. It has two domains installed. I noticed that I had a problem with my mailserver when a couple of users complained about not being able to send mails to other mailboxes within the same domain and to mailboxes in the other domain on the...
Back
Top