Hi Wietse,
Yes..i've read this.
So i'm trying chaining the content filters according to the Postfix book of
O'reilly. I think this will be the solution to my configuration problem.
Let's explain this in a basic mail-flow chart [portnr]:
mail -> [25] smtpd 1 -> qmgr -> [10025] filter-daemon -> [10026] smtpd 2 ->
[10027] filter-daemon -> [10027] smtpd 3
Even when I'm trying to do the first filter via this way, I get an error in
logs saying: connect to 127.0.0.1[127.0.0.1]:10025: Connection refused
What I configured:
main.cf
content_filter = disclaimer:[127.0.0.1]:10025
master.cf
smtp inet n - - - - smtpd
disclaimer unix - - n - - smtp
-o myhostname=localhost
#------------------------------------
localhost:10026 inet n - n - - smtp
-o content_filter=dfilt:
What am I missing and how chaining another filter which will transfer the
message back to que manager.
Kind regards,
Roland
On Thu, Oct 13, 2011 at 2:23 PM, Wietse Venema <wie...@porcupine.org> wrote:
> Roland de Lepper:
> > Hi,
> >
> > We have Postfix running for a while in combination with Zarafa.
> >
> > In Postfix I configured a disclaimer for every outgoing email. To
> complete
> > this, I had to add an entry in the master.cf file like this:
> >
> > *smtp inet n - - - - smtpd
> > -o content_filter=dfilt:*
> >
> > This is all running fine, but now I want to add another entry to that
> > parameter in master.cf for the autoresponse for certain addresses:
> >
> > *smtp inet n - - - - smtpd
> > -o content_filter=autoresponder:dummy
> > -o content_filter=dfilt:*
> >
> > Unfortunatly, for me, it will only "execute" the last parameter and not
> > both.
>
> Postfix parameters behave as documented.
>
> Wietse
>
> MASTER(5)
> MASTER(5)
> ...
> -o name=value
> Override the named main.cf configuration
> parameter. The parameter value can refer
> to other parameters as $name etc., just like
> in main.cf. See postconf(5) for syntax.
>
> POSTCONF(5)
> POSTCONF(5)
> ...
> o When the same parameter is defined multiple
> times, only the last instance is remembered.
>
