View Single Post
  #3  
Old 6th March 2008, 08:24
pheniks pheniks is offline
Junior Member
 
Join Date: Mar 2008
Location: USA, Texas
Posts: 8
Thanks: 0
Thanked 1 Time in 1 Post
Default

Converting to inet:localhost:3381 / inet:3381@localhost seems to have solved the issue with clamav-milter. Now, I am getting the same issue with the spamass-milter. Would there be a similar fix for this and what port?

From Postfix Website:
Quote:
Milter error handling

The milter_default_action parameter specifies how Postfix handles Milter application errors. The default action is to respond with a temporary error status, so that the client will try again later. Specify "accept" if you want to receive mail as if the filter does not exist, and "reject" to reject mail with a permanent status.

/etc/postfix/main.cf:
# What to do in case of errors? Specify accept, reject, or tempfail.
milter_default_action = tempfail
I don't recommend using this on a production system. We install these milters for a reason and passing over them if they aren't cooperating may not be the best idea from the standpoint of knowing that there is an issue.

I tried this in the event that it might pass over the errors on the milter and let me know if postfix was operating properly without the failing milters. I still receive a 451 4.7.1 Service unavailable - try again later message from telnet-ing into the smtpd service.

Last edited by pheniks; 6th March 2008 at 08:53. Reason: Something from the Postfix Website RE: Milter Handling
Reply With Quote