On Fri, Dec 04, 2015 at 12:48:16PM -0800, Vicki Brown wrote:
> I am attempting to understand "http://www.postfix.org/FILTER_README.html";
>
> Instructions for a "Simple"content filter suggest adding
> -o content_filter=filter:dummy
> to the master.cf entry that defines the Postfix SMTP server.
Correct.
> I'm unsure what I should use here, especially given that Apple says these
> lines are all auto-generated and should not be modified:
*After* defining a corresponding "filter" transport as described
in the README file, verbatim what is written in FILTER_README.html,
despite whatever Apple might lead you to believe.
> # ==== Begin auto-generated section ========================================
> # This section of the master.cf file is auto-generated by the Server Admin
> # Mail backend plugin whenever mails settings are modified.
> smtp inet n - n - 1 postscreen
> # -o content_filter=filter:dummy
Either disable the plugin, or configure it enable the content_filter.
> Alternatively, I could use the Advanced content filter. If I understand
> what I'm reading correctly, this appears to be relatively simple to plug
> into master.cf, and it's what Apple would use if I turned on their Spam
> checking with amavis,
The advanced filter is also more efficient.
> Before anyone asks: Wy not just use the Spam Checking Apple includes in
> Server, the answer is: I want more control than just 'tag and deliver'.
Perhaps that's also configurable with the bundled filter, but not
that content_filters can't reject mail (it is too late). You need
a proxy filter or milter to reject. If you want to quarantine,
that's still possible with suitable content_filter software,
otherwise it is tag and deliver (or, not recommended: discard).
--
Viktor.
