On Wed, Aug 19, 2015 at 01:38:34PM -0500, Paul Schmehl wrote:
> I do this once in a blue moon, so troubleshooting problems requires me to
> dive back into man pages and try to understand what's going on. The error
> that I think is telling me what the problem is is: Aug 19 18:31:43 mail
> postfix/qmgr[41135]: warning: connect to transport private/filter:
> Connection refused
If you're still seeing that, you've not read the FILTER_README
reference closely enough.
http://www.postfix.org/FILTER_README.html#simple_turnoff
Turning off the simple content filter
To turn off "simple" content filtering:
* Edit the master.cf file, remove the "-o content_filter=filter:dummy"
text from the entry that defines the Postfix SMTP server.
* Execute "postsuper -r ALL" to remove content filter request records
from existing queue files.
* Execute another "postfix reload".
> status=deferred (mail transport unavailable)
>
> So I think filter is what the problem is. Here is what I have NOW in
> master.cf: (I tried changing from the filter.sh script to running mail
> directory through the spamassassin daemon.)
You should perhaps first get things working without any filters,
and then add a filter to a working system, carefully checking
each step.
> There's obviously something wrong in here, but what is is escapes me. I
> need help.
The content_filter setting is part of each message queue file, to
reset the content filter, you need to run "postsuper -r ALL" as
root.
You're having filter problems, you need to wrap your mind around
the "simple filter" portion of the FILTER_README document.
--
Viktor.
