http://bugzilla.spamassassin.org/show_bug.cgi?id=3750
------- Additional Comments From [EMAIL PROTECTED] 2004-09-05 04:51 ------- Subject: Re: decode_attachments not used At 00:00 05/09/2004, you wrote: >http://bugzilla.spamassassin.org/show_bug.cgi?id=3750 > > > > > >------- Additional Comments From [EMAIL PROTECTED] 2004-09-04 16:00 ------- >Subject: Re: decode_attachments not used > >On Sat, Sep 04, 2004 at 03:45:09PM -0700, >[EMAIL PROTECTED] wrote: > > Just had another think. What I need is to be able to apply all the SA > rules in > > the current object to non-text attachments. 2.6x only worked on text > attachments > >Well, what you really want is to apply all of _your_ rules to all attachments. >You definitely don't want the standard SA rules to do so. Correct. What I am doing is using the SA engine as a tool working with a totally separate rulebase, which looks for specific things anywhere in the decoded message, including any readable ascii contained in Word documents and things like that. Corporates like to have "keyword spotting" in their security products so they can watch out for key project codenames and stuff like that. So I have a few rules which look for specific keywords in the entire message (including binary attachments) and quarantine messages containing them. I don't personally think keyword-spotting is very useful at all, but the corporates like it and they use it as a key differentiator between competing products. So I do it for them. > > (and html and variants of course). I need to apply my rules to *all* > > attachments, regardless of whether they are text or not. I need to work on > > Microsoft Word document attachments, Excel spreadsheets, all sorts of > stuff like > > that. > > > > Will 3.x work on all binary attachments? If not, how do I pursuade it > to do it? > >Not for standard rule types (header, body, rawbody, uri), and you can't. The >code very deliberatly only looks at leaf node text/* and message/* parts. So I see. >It sounds like you want to write a plugin that has custom eval code to go >through the message parts and apply your non-text-based rules. I may have to write it like this. Fortunately the plugin architecture looks fairly easy to use. Many thanks for your help. -- Julian Field Teaching Systems Manager [EMAIL PROTECTED] Dept. of Electronics & Computer Science Tel. 023 8059 2817 University of Southampton Southampton SO17 1BJ ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
