PGNet Dev:
> my postfix instance config currently includes my list of milters
>
> -o
> smtpd_milters=unix:/run/opendkim/opendkim.sock,unix:/run/opendmarc/opendmarc.sock,unix:/run/milter-regex/milter-regex.sock,unix:/run/clamav/clamav-milter.sock,unix:/run/spamass-milter/spamass-milter.sock
>
> for a rejection by any given milter, i see in cleanup log
>
> Jun 11 04:33:18 mx postfix/cleanup[18542]: 49jV46213qzy59:
> milter-reject: END-OF-MESSAGE from localhost[127.0.0.1]: 5.7.1 Service
> unavailable; from=<[email protected]> to=<[email protected]> proto=ESMTP
> helo=<cloud3.deltareclame.nl>
>
> can postfix logging itself identify the specific milter that fails/rejects?
To find out WHY mail was rejected, the Milter needs to log what it
is doing, or say something other than "Service unavailable". The
IP address and port are poor substitutes for that.
> e.g., in this^ case, it's
>
> unix:/run/spamass-milter/spamass-milter.sock
>
> i can configure reject messages in (some) milters to provide identifying
> detail, but that reply gets passed on to external connection.
>
> any way to log that detail only _privately_?
Postfix logs are private. They should be read by authorized personnel
only.
Wietse
