Steve wrote: > -------- Original-Nachricht -------- > >> Datum: Tue, 28 Jul 2009 15:31:09 -0500 >> Von: Troy Ayers <[email protected]> >> An: >> CC: [email protected] >> Betreff: Re: [Dspam-user] Dealing SPAM >> > > >> Julien Valroff wrote: >> >>> Le mardi 28 juillet 2009 à 19:52 +0200, Steve a écrit : >>> >>> >>>> -------- Original-Nachricht -------- >>>> >>>> >>>>> Datum: Tue, 28 Jul 2009 12:49:37 -0400 >>>>> Von: Roman Gelfand <[email protected]> >>>>> An: [email protected] >>>>> Betreff: [Dspam-user] Dealing SPAM >>>>> >>>>> I am not sure if I understood this correctly... Upon determination >>>>> >> that >> >>>>> email is spam, the mail spam email could be either forwarded with a >>>>> >> tag in >> >>>>> header or quarantined. If this is true, is there a way to tell dspam >>>>> >> to >> >>>>> drop conneciton, without storing email anywhere, upon determination >>>>> >> that >> >>>>> email is span? >>>>> >>>>> >>>>> >>>> No. There is no such thing. I know that functionality been requested in >>>> >> the past. Something like: >> >>>> If result = spam and confidence factor >= 0.50 and probability >= 0.75 >>>> >> then log and drop message >> >>>> >>>> >>> Wouldn't this be MDA's responsibility? >>> >>> This feature would be interesting if it could (also) be set on a >>> per-user/group basis, with the possibility to configure this from the >>> webui. >>> >>> >>> >> What if an email is addressed to multiple recipients? And if some of >> the users' dspam training says the message is spam, some say it's not, >> or some users are not opted-in or are opted-out, who wins? >> >> > The current user wins. DSPAM only knows about one user and that is the one > currently being processed by DSPAM. So if DSPAM drops that mail then only for > that user. Other users have their own instance of DSPAM running and doing the > work for them. > > >
That is almost absolutely true =). It surely is true for DSPAM execution at the MDA/LDA or whenever DSPAM is called after multiplexing the message, which will eventually happen if it has multiple recipients. BUT there are some cases when that is not the case. If DSPAM is being used to check messages at SMTP level, so you can reject the message with a 4XX or 5XX SMTP error code for instance (simscan or qmail-scanner come to my mind), AND the sending SMTP server has chosen to send the message with multiple recipients (some do that, some don't), then you have a problem. In my very personal opinion, if you want an hassle free setup, don't use DSPAM/SpamAssassin to block messages at SMTP level. There are better ways to stop Spam at that level, and leave DSPAM to process the messages that do get through those earlier barriers. That approach will also save you lot's of CPU cycles and DSPAM backend storage. Regards, Hugo Monteiro. -- ci.fct.unl.pt:~# cat .signature Hugo Monteiro Email : [email protected] Telefone : +351 212948300 Ext.15307 Web : http://hmonteiro.net Centro de Informática Faculdade de Ciências e Tecnologia da Universidade Nova de Lisboa Quinta da Torre 2829-516 Caparica Portugal Telefone: +351 212948596 Fax: +351 212948548 www.ci.fct.unl.pt [email protected] ci.fct.unl.pt:~# _ ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Dspam-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspam-user
