On 10/13/18 9:46 AM, Matus UHLAR - fantomas wrote:> this is useless. milter is designed to be run directly at messsage > receiving, not during further processing.
I've had a production system with a different set of milters in 'the same place' in Postfix config running for quite awhile: ... [127.0.0.1]:10010 inet n - n - - smtpd -o smtpd_banner=localhost.10010 -o syslog_name=postfix/in-preQ -o milter_protocol=6 -o smtpd_milters=unix:/var/run/clamav/clamav-milter.socket,unix:/var/run/opendkim/opendkim.sock,/var/run/opendmarc/opendmarc.sock,unix:/var/run/milter-regex/milter-regex.sock -o content_filter=amavisfeed:[127.0.0.1]:20010 -o mynetworks=127.0.0.0/8 ... it's been processing inbound dkim/dmarc for ages. as well as clamav scanning & milter-regex processing. NONE of which, clearly, are "on port 25" Can you clarify why/how that's been working vs. your comments that it's "useless" in that location, and must be moved to port 25?
