OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
Re: remote content_filter

From: Matthew Tice (mjticegmail.com)
Date: Wed Apr 09 2008 - 14:02:48 CDT


On Wed, Apr 9, 2008 at 12:48 PM, mouss <moussnetoyen.net> wrote:

> Noel Jones wrote:
>
> > Matthew Tice wrote:
> >
> > > Hello,
> > >
> > > It seems that all the documentation I come across show how to setup a
> > > local content_filter. I can't seem to get postfix to connect to a remove
> > > machine (running amavisd-new). Here is what I have in my master.cf <
> > > http://master.cf> file:
> > >
> > > smtp inet n - n - 200 smtpd
> > > -o content_filter=scan:[10.30.10.70]:10024
> > > -o receive_override_options=no_address_mappings
> > >
> > > On the content_filter line I've tried numerous permutations of that.
> > > Each time I try it the log files complains:
> > >
> > > warning: connect to transport scan: No such file or directory. I know
> > > I'm missing something simple here - what though?
> > > Any help would be greatly appreciated.
> > >
> > > Matt
> > >
> >
> > Your master.cf on the sending machine needs to define a "scan" transport
> > as a copy of the smtp transport with appropriate options set for
> > amavisd-new.
> >
> > In the current README.postfix, the name used is amavisfeed, but the
> > function is the same.
> >
> > http://www.ijs.si/software/amavisd/README.postfix.html
> > section 2.2.2
> >
> >
> also don't forget to configure amavisd-new to listen on 10.30.10.70.

Yup that was it, thanks everyone. That amavisfeed was staring at me the
whole time - it didn't make sense to me but now it does.

Matt