Re: [AMaViS-user] README.postfix/FILTER_README.html differences

[Shaun T. E. <st...@sm...>]

> The newer option receive_override_options and smtp_send_xforward_command
> are mentioned but not relied on. The amavisd service is usually started
> from some startup script and not from Postfix spawn. The content_filter
> can be either global or specified in the Postfix service of FILTER option.

Perhaps I should have been more specific, when I originally posted. I 
had read both documents, and what I saw in the new postfix document 
looked like a very different way of running the filter than I had seen 
before - spawning it, instead of it running standalone. Also, the 
configuration of it look different in that the postfix document adds 
another line to the filter setup in master.cf - the scan line - so that 
three lines were needed to use the filter. Plus the two new options you 
mentioned above.

Seeing all these differences in the postfix file, with it's setup of an 
advanced filter much different from the way amavisd-new is traditionally 
set up, confused me. I was left wondering if it should be set up in the 
traditional manner, or if there were merits to setting it up in the 
manner the postfix document described.

I simply want the best configuration of amavisd-new, as a post-queue 
content filter in postfix, utilizing any of the newest postfix features 
that might make it an even more effective filter than it already is, 
which is why I was reading both documents.

	-ste