On Friday 23 August 2002 05:42 pm, Butch Evans wrote: > I will be using amavisd, but in the following manner... > ALL OUTGOING MAIL: filtered through amavis (mcafee) > INCOMING MAIL: spam/virus filters if a subscriber wants it.
If you look at amavisd-new-20020630 you will see it does all this for you. It does the OUTGOING filtering automagically. For INCOMING you can check the database for rules for scanning with Spamassassin, or anti-virus. > > My intent is to (eventually) have mail sent to a perl script that first > scans for viruii, then (if not infected) sent to spamassassin, then > reinjected to dbmail. I realize that this causes a delay in mail > delivery, but it is not a very long delay, and will allow me to set this > up as a subscription service. I suppose I could do the same thing on > the front end (similar to what you have done at the link you provided), > but I would like to see if I can make it work from dbmail. To make it work from dbmail just add the required "policy" table to your database and then you assign each alias to a policy group. It is really easy to set up and eventually you can allow the customers access to their own policy group and they can change the settings on this themselves. Check out this document from amavisd-new: http://www.ijs.si/software/amavisd/README.lookups Near the bottom it talks about the database stuff for customizing. This is what we are doing and it works slick. -- Bret Baptist Systems and Technical Support Specialist [EMAIL PROTECTED] Internet Exposure, Inc. http://www.iexposure.com (612)676-1946 x17 Web Development-Web Marketing-ISP Services ------------------------------------------ Today is the tomorrow you worried about yesterday.
