I am tasked by a client with adding a feature to their spam/AV
scanning system to scan incoming mail for keywords, on a per-domain
basis, so that the domain admin can blacklist certain keywords in mail.
(Possibly whitelist based on keywords, also.) Regardless of the merits
of this suggestion - I don't think it's such a good idea, honestly, but
I can see why their users might think it is - is there a good way to
fit such a scanner into amavisd?
I could scan the mail using a script written to fit into the AV
scanning interface, but if I don't want it blocked as a virus, I'm not
sure how to force addition of a special header?
I don't need to make amavisd itself do the blacklisting; I could
intercept and block it at a later phase in processing. I just need to
do the scanning and add a custom header indicating whether it matched
something. It would be convenient to do it under amavisd, because the
mail's there and all decoded into parts anyway... but I'm not sure
where is a good place to wire it in. (As part of this project, I will
be upgrading to the latest amavisd available in FreeBSD ports, BTW.)
Any suggestions?
-- Clifton
--
Clifton Royston -- [EMAIL PROTECTED] / [EMAIL PROTECTED]
President - I and I Computing * http://www.iandicomputing.com/
Custom programming, network design, systems and network consulting services
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
