On 12/10/10 6:36 PM, Bill Cole wrote:
Philip A Colvin wrote, On 12/10/10 5:13 PM:
[...]
Now things are getting a bit clearer. Thank you for the information.
I'll dig through the MIMEDefang config and set the port and then match
it in the main.cf.
Are there any ports that should be avoided? I did see a commented
setting in MIMEDefang using port 4567. I'm guessing that is just an
example.
MIMEDefang normally uses a unix domain socket, not a TCP listener on the
loopback. That socket will usually be
/var/spool/MIMEDefang/mimedefang.sock which would mean that you need
this line in Postfix's main.cf:
smtpd_milters = unix:/var/spool/MIMEDefang/mimedefang.sock
The socket name for MD is normally configured in the startup script.
Assuming you use a common OS/distribution, that should be in
/etc/init.d, /etc/rc.d, /etc/rc.d/init.d or /usr/local/etc/rc.d and the
relevant shell variable (if your script is based on the MD
distribution's example) is $SOCKET.
I think I may be getting closer, but ran into a bit of problem. I have
put smtpd_milters = unix:/var/spool/MIMEDefang/mimedefang.sock in the
main.cf. Now I get this in the log and no mail goes through:
postfix/smtpd[2075]: warning: connect to Milter service
unix:/var/spool/MIMEDefang/mimedefang.sock: No such file or directory
I checked the permissions of the /var/spool/MIMEDefang directory and the
contents and they all have the user and group set to defang.
Any thoughts?
Thanks again.
Phil Colvin
