From: D.J. Fan (mr88talenthotmail.com)
Date: Fri Aug 26 2005 - 15:00:45 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

>Also:
>
>>smtp inet n - n - - smtpd
>> -o content_filter=
>
>>66.45.96.10:smtp inet n - n - - smtpd
>> -o content_filter=smtp-amavis:[127.0.0.1]:10024
>
>>smtp unix - - n - - smtp
>> -o smtp_helo_timeout=3
>> -o smtp_connect_timeout=3
>
>>And send mail from our filtering service to 66.45.96.10 and have all
>>outgoing mail send to the main IP. Will this do what I need?
>
>Isn't this backwards? If your filtering service sends mail to 66.45.96.10,
>won't it get filtered again?
>Wouldn't you have to set your MUAs to send mail to 66.45.96.10?
>
>D.J. Fan
>

So, I guess this should be reversed to match your statement:

smtp inet n - n - - smtpd
  -o content_filter=smtp-amavis:[127.0.0.1]:10024

66.45.96.10:smtp inet n - n - - smtpd
  -o content_filter=

I'm missing part of the picture, you said:
1) "Our incoming mail is filtered"
2) "I'd like to virus filter outgoing mail (especially since this will be
the only check mail from one of our clients to one of our clients recieves)"

Is the sending client on your network?
If statement 1 is true, and the sending client is NOT on your network, then
wouldn't their mail also go through your outsourced filter? Or is statement
1 true for most, but not all senders?

Lastly, if you are only doing virus filtering, I would consider doing it for
both incoming and outgoing anyway. Strip amavisd-new down to bypass
everything except virus scanning. It has been shown that defense in depth is
a good thing when it comes to virus filtering. Simply insure you do not use
the same virus scanner as your outsourced filter.

D.J. Fan

_________________________________________________________________
On the road to retirement? Check out MSN Life Events for advice on how to
get there! http://lifeevents.msn.com/category.aspx?cid=Retirement

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]