content_filter=filter:dummy This filter has been running for years, massaging all messages as we require, and must continue to run on all messages. Microsoft Exchange users require this, and must receive all messages.
content_filter=autoresponder One virtual email address must generate an autoresponder message on off hours - in addition to delivering to Exchange users. ~ Mike On Mon, Oct 15, 2018 at 1:47 PM Wietse Venema <wie...@porcupine.org> wrote: > Mike Schleif: > > CentOS Linux release 7.5.1804 (Core) > > mail_version = 2.10.1 > > > > Several years funning one content filter: > > 127.0.0.1:10025 inet n - n - - smtpd > > -o content_filter=filter:dummy > > ... > > > > Now, we need an autoresponder for one incoming address. Trying to use > this: > > > https://www.howtoforge.com/how-to-set-up-a-postfix-autoresponder-with-autoresponse > > > > Tried adding second line to above: > > 127.0.0.1:10025 inet n - n - - smtpd > > -o content_filter=filter:dummy > > -o content_filter=autoresponder:dummy > > This will set content_filter to the last specified value. Postfix > parameters are scalars, not lists (list are specified with tables, > and there is no list-based variant of the content_filter variabe). > > What do you mean with parallel? There is only one mail flow, so > it can flow through only one filter at a time. > > Therefore, the answer depends on what you want: apply one of the > two filters or both filters (in series). > > Wietse >