Facebook
TwitterHey Pleskians!
We have a case, where a remote Mail user have a dmarc record as following:
This leads to an Error when a mail is sent to our Plesk server, the Mail is not bounced but also never delivered, and from the logs i would have assumed it got delivered, but it surely isn't.
I could reproduce the issue with an own domain on a remote server with false DMARC
Here an example what happens with the mail from the log
While the sender should improve their DNS, the mail should still get delivered, or at least bounced.
We have a case, where a remote Mail user have a dmarc record as following:
$ dig txt _dmarc.domain.com +short
"" "v=DMARC1"
This leads to an Error when a mail is sent to our Plesk server, the Mail is not bounced but also never delivered, and from the logs i would have assumed it got delivered, but it surely isn't.
I could reproduce the issue with an own domain on a remote server with false DMARC
$ dig txt _dmarc.wrongdmarc.com +short
"v=DMARC1"
Here an example what happens with the mail from the log
root@plesk1 ~ # grep 2214E181522D59 /var/log/maillog
Jun 23 09:35:30 plesk1 postfix/smtpd[32262]: 2214E181522D59: client=remoteHOst.com[]
Jun 23 09:35:30 plesk1 psa-pc-remote[1083]: 2214E181522D59: from=<[email protected]> to=<[email protected]>
Jun 23 09:35:30 plesk1 postfix/cleanup[13892]: 2214E181522D59: message-id=<[email protected]>
Jun 23 09:35:30 plesk1 psa-pc-remote[1083]: 2214E181522D59: py-limit-out: stderr: INFO:__main__:No SMTP AUTH and not running in sendmail context (incoming or unrestricted outgoing mail). SKIP message.
Jun 23 09:35:30 plesk1 psa-pc-remote[1083]: 2214E181522D59: py-limit-out: stderr: SKIP
Jun 23 09:35:30 plesk1 psa-pc-remote[1083]: 2214E181522D59: check-quota: stderr: SKIP
Jun 23 09:35:30 plesk1 psa-pc-remote[1083]: 2214E181522D59: spf: stderr: PASS
Jun 23 09:35:30 plesk1 postfix/qmgr[22287]: 2214E181522D59: from=<[email protected]>, size=3191, nrcpt=1 (queue active)
Jun 23 09:35:30 plesk1 postfix-local[31520]: 2214E181522D59: from=<[email protected]>, to=<[email protected]>, dirname=/var/qmail/mailnames
Jun 23 09:35:31 plesk1 postfix-local[31520]: 2214E181522D59: spam: stderr: PASS
Jun 23 09:35:31 plesk1postfix-local[31520]: 2214E181522D59: dk_check: stderr: PASS
Jun 23 09:35:31 plesk1 dmarc[32149]: 2214E181522D59: Wrong the essential DMARC policy parameters for 'sysdev.online': 'Found DMARC record lacked a required p= entry'
Jun 23 09:35:31 plesk1 dmarc[32149]: 2214E181522D59: DMARC: smtpdomain=sysdev.online maildomain=sysdev.online [email protected] stamp=1687505731 ip= adkim=unspecified aspf=unspecified p=UNSPECIFIED sp=UNSPECIFIED pct=100 align_dkim=fail align_spf=fail spfres=pass dkimres=pass dmarccheck=DMARC_POLICY_REJECT dmarcstatus=STOP
Jun 23 09:35:31 plesk1 postfix-local[31520]: 2214E181522D59: dmarc: stderr: STOP
Jun 23 09:35:31 plesk1 postfix/pipe[14080]: 2214E181522D59: to=<[email protected]>, relay=plesk_virtual, delay=22, delays=21/0/0/1.2, dsn=2.0.0, status=sent (delivered via plesk_virtual service)
Jun 23 09:35:31 plesk1 postfix/qmgr[22287]: 2214E181522D59: removed
While the sender should improve their DNS, the mail should still get delivered, or at least bounced.
