Date: Tue, 1 Nov 2005 17:06:42 +0200 From: Ion-Mihai Tetcu <itetcu@people.tecnik93.com> To: ports@freebsd.org Subject: Re: dspam-3.6.0 on FreeBSD (was: Re: dspam for FreeBSD) Message-ID: <20051101170642.41e5ce0f@it.buh.cameradicommercio.ro> In-Reply-To: <20051027045655.2e3a435b@it.buh.tecnik93.com> References: <435F4E0C.8000209@ozlerplastik.com> <20051027045655.2e3a435b@it.buh.tecnik93.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 27 Oct 2005 04:56:55 +0300 Ion-Mihai Tetcu <itetcu@people.tecnik93.com> wrote: > > [ ports@ cc'ed as a safety measure for my inbox ] > > On Wed, 26 Oct 2005 12:36:12 +0300 > Ertan Kucukoglu <ertank@ozlerplastik.com> wrote: > > > Hi, > > > > I've found your e-mail address in Makefile for dspam port. > > > > I know that there is a recent new version of dspam. I wonder if it > > will be available in ports anytime soon. Would you advise please? > > > 3.6.0 is already available on FreeBSD as dspam-devel port. (As a note > it was added in our Ports Collection the same day the official release > got out - this time we beat all other OSes, for example debian still > hasn't it :) If you would be reading dspam-users mailing list (which > is something I recommend) you'd already know this (I'm active on > dspam-* lists and I've posted there on this subject); > > You an safely: > portupgrade -R -o mail/dspam-devel dspam-3.4\* > > > Reasons I haven't MFC it yet in mail/dspam: > - there are a lot of changes (like dynamic back-end support) which I > feel it's better to have them tested for a while before declaring them > safe (esp. the new hash_drv, esp. on more "exotic" arch like sparc > where on solaris and linux I have crash reports and a fix in cvs) > - there are a few bugs (in CGI) which I haven't have time to patch > - MaxMessageSize from dspam.conf also applies to clamav virus scanning > (if WITH_CLAMAV= yes) which IMO is a nice way for self-shooting; given > the way this is implemented now (see dspam.c) patching this elegantly > is not trivial. > (- there also is a memory leak report which I haven't been able to > reproduce yet.) I reproduced this, but I have no fix yet; the leak is about 120KB per message processed. So until either I or someone upstream manage to identify and fix this, I won't upgrade mail/dspam. Help, of course is welcomed. -- IOnut Unregistered ;) FreeBSD "user"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051101170642.41e5ce0f>