This is a reply to an old (2021/11/11) message I found on
mail-archive.com, so it won't thread. The OP wrote:
I see this error message in my mail.log file:
Nov 11 19:37:52 mail postfix/smtpd[5942]: warning: connect to Milter
service local:opendmarc/opendmarc.sock: No such file or directory
In the main.cf file, I have this line:
smtpd_milters =
local:opendkim/opendkim.sock,local:opendmarc/opendmarc.sock,
local:spamass/spamass.sock
There were various replies along the lines of 'this syntax is invalid'.
However, this syntax is documented, and works on Ubuntu 22.04, at least
(the current MILTER_README.html says "On many systems, local is a
synonym for unix", and I've been doing this for many years).
I have one Ubuntu 22.04 system with this in main.cf:
smtpd_milters = inet:localhost:8891,local:opendmarc/opendmarc.sock
and this in opendmarc.conf:
Socket local:/var/spool/postfix/opendmarc/opendmarc.sock
This works, with mail.log reporting an opendmarc pass. Not particularly
interesting, but a second identical system didn't work, and gave exactly
the error message reported above. On the second system, there was an
existing socket file in /var/run/opendmarc, and this was preventing
opendmarc from creating the correct socket file, in
/var/spool/postfix/opendmarc. Restarting postfix and opendmarc had no
effect, but a reboot fixed the second system, and it now reports
opendmarc passes.
On the second system, I also tried changing main.cf to
smtpd_milters = inet:localhost:8891,unix:/opendmarc/opendmarc.sock
and this also works. MILTER_README.html states that "an absolute
pathname is interpreted relative to the Postfix queue directory", but it
seems that /any/ pathname, absolute or not, does this.
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
