On 12/10/2010 3:20 PM, Philip A Colvin wrote:
Mr Jones,
Thanks for the quick reply. I have read the MILTER_README, but
it's just not clicking yet for me.
I have tried putting smtpd_milters = inet:localhost:10025 in
the main.cf file but in the logs I then get a connection
refused for the port.
Please don't top-post.
MIMEDefang must be running and listening on the port you tell
postfix to use; the two ports must match for them to
communicate.
Or if MIMEDefang is using a unix socket, the path used must
match the path given to postfix, and postfix must have file
system permissions to access the socket.
From what I have read from other content
filter setups, you need to add something like this to the
master.cf:
Don't confuse milters with content filters. Although they can
perform most of the same functions, the setup and
implementation are completely different.
Disregard any how-to's you read that talked about content filters.
127.0.0.1:10025 inet n - - - - smtpd
-o content_filter=
...
The above settings are for a content_filter, such as
amavisd-new. You don't use those settings with a milter.
The only postfix change necessary is adding the smtpd_milters
parameter to main.cf.
The port you use must be the port that you configure
MIMEDefang to listen on. That's set in the MIMEDefang config.
-- Noel Jones
