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.
On 13.10.18 09:59, pg...@dev-mail.net wrote:
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"
That's why I say it's useless and that's also why the sending IP can't be
passed to milter - here, the sending IP is 127.0.0.1.
If you need to pass original IP to milter, you must use that milter when
receiving mail from client, on port 25 (or any other port you use when
receiving mail).
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?
"useless" does not necessarily mean "not working". However, it does not work
for auth-milter as you mentioned and I am explaining why.
As I said, the point of milter is to be able to filter message at SMTP
level.
You seem to receive mail via other connection on other port and push it
further throuch port 10010 on localhost.
Either it is useless, or it makes milters useless.
Maybe you should explain why are you receiving mail in this strange way.
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
2B|!2B, that's a question!
