Daniel L. Miller wrote:
Noel Jones wrote:
Looks as if the proxy filter has gotten out of sync with postfix.
I would suggest starting using it as a content_filter. Once you get
that working, you can see if it works with smtpd_proxy_filter.
I find it handy to use " -o syslog_name=postfix-something" in
master.cf to differentiate services; makes reading the logs easier.
content_filter gives me the same results (I could be wrong, probably am,
but I think content_filter is actually implemented as shorthand for a
relay operation). I never saw that syslog_name parameter before -
thanks. That makes logs so much clearer.
I'm going back and forth checking configs. I'm using close to a vanilla
Postfix config. I have no changes to any of the default restrictions.
I've setup this mail server with two NIC's, both on the same subnet.
Now that (I think) I've fixed my routing issues, traffic seems to work
properly (unless you think a faulty routing table is causing my current
problem). ASSP listens on 192.168.0.10, and Postfix on 192.168.0.11.
mynetworks includes 192.168.0.0/24.
Is there any other Postfix setting I need to check/change - or at this
point does the fault lie in my ASSP config?
The content_filter accepts and queues the mail, then relays
the message to the content_filter. This is a little simpler
than the smtpd_proxy_filter which makes simultaneous
connections to the originating client and the filter.
The postfix content_filter feature is widely used and
considered quite robust. I'll bet the ASSP folks say the same
thing...
A TCP capture of the incoming session should give more insight
where things go wrong.
Multiple NICs on the same subnet is asking for trouble. Any
way you can disable one to see if that helps?
-- Noel Jones
