, the fix is pretty easy. However, that means that I
now have a patch that needs to be pushed upstream. How do I go about
doing that?
___
Dspam-devel mailing list
Dspam-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspam-devel
the
project is still alive...
- David Reagan
___
Dspam-devel mailing list
Dspam-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspam-devel
On Wed, 02 Jan 2019 18:11:05 +0100
dspam-devel--- via Dspam-devel wrote:
> dspam-devel@lists.sourceforge.net skrev den 2019-01-01 07:14:
> > I have adapted the daemon to use kqueue instead of select. If anyone
> > is interested in the patch.
I'm willing to give your patch a tr
dspam-devel@lists.sourceforge.net skrev den 2019-01-01 07:14:
I have adapted the daemon to use kqueue instead of select. If anyone
is interested in the patch.
if you knwo where maintainers are now aday, add it to them, sadly is
just i think none really use dspam anymore, i would had used
On Tue, Jan 01, 2019 at 09:56:42PM +0100, dspam-devel--- via Dspam-devel wrote:
> Hello Edgar,
>
>
> I am interested in this patch. Are you able to share this patch?
>
> --
> Kind Regards from Switzerland,
>
> Stevan Baji?
>
> On 01/01/2019 07:14, Edgar Pe
On Tue, Jan 01, 2019 at 09:56:42PM +0100, dspam-devel--- via Dspam-devel wrote:
> Hello Edgar,
>
>
> I am interested in this patch. Are you able to share this patch?
>
> --
> Kind Regards from Switzerland,
>
> Stevan Baji?
>
> On 01/01/2019 07:14, Edgar Pe
___
Dspam-devel mailing list
Dspam-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspam-devel
I have adapted the daemon to use kqueue instead of select. If anyone is
interested in the patch.
Thanks,
Edgar
___
Dspam-devel mailing list
Dspam-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspam-devel
a rule in
spamassassin to detect it
what are plans for dspam and dspam-milter ?
hope its not dead
--
___
Dspam-devel mailing list
Dspam-devel@lists.sourceforge.net
https
On Mon, Nov 24, 2014 at 11:02:58PM +, dspam-devel@lists.sourceforge.net
wrote:
Le 2014-11-22 15:50, dspam-devel@lists.sourceforge.net a écrit :
I would be interested in helping to keep it up to date. What do I need
to do to get access to make update to the source code repository
Le 2014-11-22 11:00, dspam-devel@lists.sourceforge.net a écrit :
What are the skills required to take on maintenance?
I have done a bit of C and perl coding and I've used dspam in the
past. I would like to use it again. Off course, I really never tried
to grasp a code base as big s dspam
Le 2014-11-22 15:50, dspam-devel@lists.sourceforge.net a écrit :
I would be interested in helping to keep it up to date. What do I need
to do to get access to make update to the source code repository?
Currently,
I just make all our fixes to local copies.
I think that's the right way
it years ago. It is really a shame it came to this point...
-Original Message-
From: dspam-devel@lists.sourceforge.net
Date: Sat, 22 Nov 2014 03:00:13
To: dspam-devel@lists.sourceforge.net
Reply-To: dspam-devel@lists.sourceforge.net
Subject: Re: [Dspam-devel] TrainPristine insufficient
significant headaches recently. My travails
are partially documented on the dspam-user mailing list. I come to
you, dspam-devel, to request that the documentation here be improved.
In particular, the note in these comments mentions dspam_train, but it
does not mention that using this option will also
Le 2014-11-21 17:03, dspam-devel@lists.sourceforge.net a écrit :
src/dspam.conf.in:
# TrainPristine: for systems where the original message remains
server side
# and can therefore be presented in pristine format for retraining.
This option
# will cause DSPAM to cease all writing
15 matches
Mail list logo
