Le vendredi 13 novembre 2009 à 17:36 +0100, Steve a écrit : > -------- Original-Nachricht -------- > > Datum: Fri, 13 Nov 2009 17:15:35 +0100 > > Von: Julien Valroff <jul...@kirya.net> > > An: dspam-devel@lists.sourceforge.net > > Betreff: Re: [Dspam-devel] Requests. > > > Hi Steve et al, > > > Hallo Julien,
Hi again, > > > Le vendredi 13 novembre 2009 à 17:04 +0100, Steve a écrit : > > > -------- Original-Nachricht -------- > > > > Datum: Fri, 13 Nov 2009 12:30:46 -0300 > > > > Von: "Edgar Díaz Orellana" <eorel...@fulltimehosting.net> > > > > An: dspam-devel@lists.sourceforge.net > > > > Betreff: Re: [Dspam-devel] Requests. > > > > > > > Hi steve and folks. > > > > > > > Hallo Edgar, > > > > > > > > > > i'm refer about a have some info of what size had the processed email > > by > > > > dspam, not how is the max size of the processed email by dspam, there > > are > > > > 2 > > > > diferent things. > > > > > > > I know. But you wrote "because no spammer send an email with 10MB or > > > related". So if you already know that no spammer will send such big > > > messages then set the limit (MaxMessageSize) inside DSPAM to be at > > > 10MB or less. Then you know for sure that any message equal or bigger > > > then 10MB will NOT be checked by DSPAM. Do you understand what I mean? > > > > I hadn't thought to this feature until now, it seems actually quite > > interesting. > > > It's a life saver in production :) > > > > Messages over the MaxMessageSize still go through DSPAM but are not > > actually checked am I right? > > > Correct. DSPAM will even not add any headers to the message. It will > just take the message and see that it is over the MaxMessageSize and > send the message back as usual but not adding/modifying anything. > > > > What about Clamav check? > > > I don't know. Have to check the code. > > > > It could be problematic as infected mail could be larger than the > limit > > (just a guess). Maybe it could be worth adding the same limit for > > Clamav, what do you think? > > > ClamAV already has this implemented. It's called "StreamMaxLength". I > don't know if there is a way for DSPAM to check what the maximum is > before trying to send the message to ClamAV daemon. I need to read the > documentation and see if there is something like that implemented. If > it is then I can already tell you now that DSPAM does not check for > it. At least I have not stepped over it while working on the DSPAM > code. Actually, even if that option cannot be retrieved from DSPAM, I think it would be good to have one within DSPAM, so that messages above the MaxMessageSize limit can be checked by clamav (maybe the default value can be the same to begin with) I will add this to SF as a feature request so that it isn't forgotten. Cheers, Julien ------------------------------------------------------------------------------ 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-devel mailing list Dspam-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-devel
