Request for comments 3 - Re: MailScanner and password protected archives

DAve dave.list at pixelhammer.com
Wed Jul 25 14:04:08 IST 2007


Possibly related to "Re: MailScanner and password protected archives"

Steve Freegard wrote:
> Hi Jules,
> 
> Julian Field wrote:
>> Would this not be better than having a specific 'use-caution' flag 
>> with a definition that I create?
> 
> This is a great idea as it offers more than just the ability to set a 
> flag, but makes the whole thing extendable via a CustomFunction.
> 
> However I'm still mulling over what the original poster wanted to do, as 
> everything that has been described so far is already done by MCP (In v2 
> of MailWatch - users cannot 'see' MCP messages or release them), so 
> having having yet-another-flag for 'caution' is not really necessary 
> IMO.  But I'll happily change my mind one I've actually released v2 and 
> people can see what it actually does.
> 

I see a trend here, maybe it is just me. We (the MS community) have SA 
rules that catch viruses, we have Clam signatures that catch spam, we 
have MCP that catches stuff nobody wants to 'see'.

It looks like people want a way to decide which messages go to which 
quarantine based on the rule that was triggered, and not the tool that 
was used. Some messages caught by Clam should go into the spam 
quarantine, some messages caught by SA should go to the virus quarantine.

Possibly an override map that says "any rule matching this regex is 
actually treated as spam, any rule matching this regex is actually a 
virus". This would remove the need for special flags and custom 
functions. Create only two quarantines, one that is considered safe for 
release/viewing, one that is not. Then third party tools such as 
MailWatch could allow a user access to any message stored in quarantine 
'safe', and no access to any message in quarantine 'unsafe'. Regardless 
of what tool/rule/function put them there.

Sound right?

DAve



-- 
Three years now I've asked Google why they don't have a
logo change for Memorial Day. Why do they choose to do logos
for other non-international holidays, but nothing for
Veterans?

Maybe they forgot who made that choice possible.


More information about the MailScanner mailing list