Re: FW: Problems configuring postfix on a new machine

At 07:06 PM 10/15/04, Kurt Buff wrote:
>Noel said...
> >
> > At 12:54 PM 10/15/04, Kurt Buff wrote:
> >
> > >2) test emails (no special content) sent via blat from an allowed
> > >workstation get through, but an eicar test message gets
> > dropped no matter
> > >which IP address I connect with. Only messages passing
> > through the inbound
> > >IP address instance should be so dropped. Again, this
> > indicates the the
> > >installation is almost right, but not quite.
> > >
> >
> >
> > Set the content filter only on the inbound smtpd service.
> > - remove the content_filter parameter from main.cf
> > - add "-o content_filter=smtp-amavis:[127.0.0.1]:10024" to
> > the master.cf
>
>Uh, should this be
>
>"-o content_filter=smtp-amavis:[127.0.0.1]:10025"
>
>instead? That's what I tried, and it only seemed to turn off the filter
>completely.
>

[sorry for the delayed response]

Of course not. If you use the postfix reinjection port as your
content_filter, all you accomplish is passing mail through postfix twice.
-o content_filter=smtp-amavis:[127.0.0.1]:10024
is what you should be using in master.cf on your inbound smtpd service.

As an alternative, you can use
-o content_filter=
on the outbound smtpd service to disable it there, and leave it defined in
main.cf.

You may need to comment out the default smtpd service in master.cf if you
are defining your own.
It's the one that looks like "smtp .... smtpd" near the top.


> > It might make more sense to use amavisd-new's controls to skip spam
> > scanning of mail originating from inside your network. While
> > it makes
> > sense to skip spam scanning of outgoing mail, virus scanning
> > outgoing mail
> > doesn't take much time or resources, and can prevent accidents.
>
>Good idea - point me to some docs on doing this?

All the info you need is in the amavisd-new docs; README.postfix and
comments in the amavisd.conf file.
If you still can't get it, ask for help on the amavis-users list.


--
Noel Jones