A DMARC policy allows a sender to indicate that their emails are protected by SPF and/or DKIM, and give instruction if neither of those authentication methods passes. Please be sure you have a DKIM and SPF set before using DMARC.
You are not allowed to send a message with this address
DMARC DNS entry found for the domain _dmarc.byvoz.comm :
When I had created my server myself (without HestiaCP), I had a perfect score with OpenDKIM, with Hestia, I am downright at 0 and we have no control over that in HestiaCP (/etc/opendkim.conf does not exist not even …)
Why offer DKIM support if it’s badly done, I wonder …
Yes and no DKIM creates invalid signatures (all mail server testing services say the same thing.
Putting DKIM to put DKIM is useless if the result is incorrect.
Moreover, when I want to put SSL on the mail domain, I get an error
Error: Let’s Encrypt validation status 400 (mail.linkfor.run). Details: Unable to update challenge :: authorization must be pending
With Hestia, it’s cool there are lots of things you don’t have to do manually but there are errors everywhere that you have to go back to and waste a lot of time. For my next server, I won’t use Hestia anymore, too much trouble and not flexible enough.
Well, then probaly you missed something which is required according to the docs. If you don’t create the needed records or following the requirements it’s basicly your fault .
Anyway, it doesnt make sense to hijack an 1 year old thread - if you want to get help for that related LE400 issue, please have a look at the docs. If you can’t get it running, you’re free to open a new thread.