On Fri, 30 Jul 2010 09:19:53 +0200 Marko Weber <we...@zackbummfertig.de> wrote:
> > On Thu, 29 Jul 2010 21:03:22 +0100, Paul Cockings <ds...@cytringan.co.uk> > wrote: > > Stevan Bajić wrote: > >> Since you are anyway willing to code something like that, then why not > >> looking at the current DSPAM quarantine code and extend it so that the > >> desired functionality can be controlled on a per user basis (for > example > >> with preferences) and then contribute back that code to the DSPAM > >> community project? > > > > now I would just kiss your feet if that was include feature request: > > > > > https://sourceforge.net/tracker/?func=detail&aid=3032012&group_id=250683&atid=1126468 > > Hello Paul, > i am new to Exchange and MS, i just setup a 2008 sbs the last days. (with > help from steve) > Yeah, yeah, yeah. The system got locked yesterday and you forgot to tell me the password, so I could not finish the network configuration for you. Mail me the password so I can finish that Win2K8 SBS that you have there running on Linux KVM. > I just checked Exchange for some Options ( here at work not on my setup > server) and see you can do "Transport Rules" (exchange 2007). > You can do "If Header Contains Text" ( you can do here X-Spam=YES at > example) THEN move mail to => <yourchoosenfiolder>. > Thats an global set rule. You can also let your clients do rules, they > will be saved like sieve rules per user then. > > So my ideas is = you should be able to Filter Mails for Spam Header AND > Virus Header, if a Mail conrains Virus you can do rules for "IF Header Text > <x-Virus> THEN move mail to........ > > You can also tag / delete / .......... > > So why invent the wheel new when its already there and you just have to > use it =? > It is not the same. Paul want's virus infected mails TO NOT be delivered. That is his point. He wants the virus infected mails to stay in DSPAM quarantine while all other Spam mails to be delivered to the final destination. Anyway... DSPAM does not know anything other then a mail either beeing SPAM or HAM or NONE. That's it. Nothing about Virus nor Whitelisted nor Blacklisted nor Blocklisted. So adding that code to allow different delivery based on CLASS and not on RESULT would cascade a bunch of new configuration options (aka: spamAction, virusAction, blocklistAction, blacklistAction, innocentAction, whitelistAction). And I really don't know if this is beneficial at all? I see so many users already struggeling with the complexety of stock DSPAM that I have become in the past months very sensitive in extending DSPAM to allow more configuration options. > Just grab the money u are willing to spent and give to any social projects > like pooer children in neighbourhood or any other....it would be better > placed i think. > > your feature request i think is available with all the "onboard" tools. > > maybe i am wrong, then tell me, i am open for thoughts and ideas > > marko > > (gotta rush, coffee is ready) > -- Kind Regards from Switzerland, Stevan Bajić ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _______________________________________________ Dspam-user mailing list Dspam-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-user
