[dspam-users] thanks for dspam, my experiences on FreeBSD, suggestions

Ion-Mihai Tetcu itetcu at apropo.ro
Thu Apr 29 00:43:25 PDT 2004


On Wed, 28 Apr 2004 12:30:10 -0700
Gary Kline <kline at thought.org> wrote:

> On Wed, Apr 28, 2004 at 09:32:20AM +0300, Ion-Mihai Tetcu wrote:
> > On Wed, 28 Apr 2004 07:44:54 +0200
> > Andreas Klemm <andreas at FreeBSD.org> wrote:
> > 
> > > On Tue, Apr 27, 2004 at 02:42:47AM +0300, Ion-Mihai Tetcu wrote:
> > > > 
> > > > [ dspam-users at nuclearelephant.com dropped ]
> > > > 
> > > > What about a dspam-devel port ?
> > > 
> > > Would be beneficial.
> > > 
> > > q: could that port be arranged, so that it can be installed with
> > > the-stable version in parallel ?
> > 
> > Yes, that's how I'm using it. You would share the database, I think,
> > or have to copy it manually. I managed to automate that, but I'm
> > afraid it is not portable. Anyway it should not be a problem.
> > 
> > > When testing new features with a test user Id like to keep a
> > > stable anti spam environment.
> > 
> > Well, I have a local port that should be portlint'ed a little.
> > Currently is using unstable releases + some local patches, but I
> > could made it pull out sources from the cvs instead.
> > 
> > So what would people prefer the port to use:
> > - unstable releases + patches on major bugs (pro: it should always
> > work; con: patches would have to be made and *submited* in our cvs -
> > which could take a while)
> > - known to be working cvs snapshots (pro: more close to head)
> > - cvs head (pro: the blending edge with all new features; con: well,
> > you know, it could wipe out everything, as the maintainer will have
> > little control)
> > 
> 	
> 	Hope I am not highjacking this thread (at least not totally),
> 	but is there any summary of things-to-do to get dspam running?
> 	to get it in 'learn' mode??  No far I have created a list of
> 	trusted users/groups.  Now what?

Without more details, we cannot help you.

Dspam's documentation should be rewrote, and it is on my to do list, but
it will happen for the 3.x.
 
> 	Re a -devel port, my experience with most of the devel suites
> 	is that they are risky (to put it politely:).  I would advise
> 	anybody who installs a -devel port of anything to have the
> 	stable/tested port around....   

Agree. For example the 3.x showed, where dspam has been rewrote, showed
some regressions.

But since all new features are added on the devel branch and some people
could make good use of them, this -devel port will help them. And it
would give a chance for changes to be easily tested on FreeBSD before
they are in the stable release. The bug in my PR is happening only on
FreeBSD (it seems that our strsep(3) slightly differs from those on some
linux, despite the their claim that it is from bsd).



-- 
IOnut
Unregistered ;) FreeBSD "user"



More information about the freebsd-ports mailing list