Re: [Dspam-devel] [Dspam-user] TB DSPAM Extension - TB3 support

2010-05-03 Thread dspam
>> The binary package is available here: >> http://hmonteiro.net/files/dspam/tb/dspam-thunderbird-extension.xpi > Anyone got any feedback? Either good or bad? Hi Hugo, The add-on installs Ok in TB3.04 on Kubuntu 10.04 x64 I can't test the functions yet as I have t

Re: [Dspam-devel] [Dspam-user] Installing the DSpamAddin for Outlook

2010-07-08 Thread dspam
On Wed, 7 Jul 2010 23:56:05 +0300, "Dudi Goldenberg" wrote: >>Open Outlook Nothing different, >>Check the start menu - Nothing extra >>I do have a bunch of files in C:\Program Files\DSpam AddIn >> >>If any users of the addin can give me some pointers

[Dspam-devel] TrainPristine insufficient explanation in conf comments and debug logging

2014-11-21 Thread dspam-devel
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 of signatures and DSPAM headers to the # message, and deliver the message in as

Re: [Dspam-devel] TrainPristine insufficient explanation in conf comments and debug logging

2014-11-21 Thread dspam-devel
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 ce

Re: [Dspam-devel] TrainPristine insufficient explanation in conf comments and debug logging

2014-11-22 Thread dspam-devel
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... But somehow, I feel tempted. And I was really happy when I

Re: [Dspam-devel] TrainPristine insufficient explanation in conf comments and debug logging

2014-11-22 Thread dspam-devel
On Sat, Nov 22, 2014 at 03:00:13AM +, dspam-devel@lists.sourceforge.net wrote: > 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 ca

Re: [Dspam-devel] TrainPristine insufficient explanation in conf comments and debug logging

2014-11-24 Thread dspam-devel
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

Re: [Dspam-devel] TrainPristine insufficient explanation in conf comments and debug logging

2014-11-24 Thread dspam-devel
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 t

Re: [Dspam-devel] TrainPristine insufficient explanation in conf comments and debug logging

2014-11-25 Thread dspam-devel
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

[Dspam-devel] rabl

2016-09-19 Thread 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

[Dspam-devel] Kqueue

2019-01-01 Thread 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

Re: [Dspam-devel] Kqueue

2019-01-01 Thread dspam-devel
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

Re: [Dspam-devel] Kqueue

2019-01-01 Thread dspam-devel
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

Re: [Dspam-devel] Kqueue

2019-02-14 Thread 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

[Dspam-devel] What is the status of development?

2020-08-21 Thread dspam-devel
Hey all, So, apologies for this being my first email... The development of dspam seems to have stalled. At least judging from the lack of traffic on the mailing lists and bug tracker. Are there any maintainers still working on this project? I've been using dspam for years on my per

Re: [Dspam-devel] Kqueue

2019-01-01 Thread dspam-devel--- via Dspam-devel
___ Dspam-devel mailing list Dspam-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-devel

Re: [Dspam-devel] Kqueue

2019-01-02 Thread dspam-devel--- via Dspam-devel
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 it

[Dspam-devel] I have a patch, what's the procedure for getting it approved?

2021-12-23 Thread dspam-devel--- via Dspam-devel
I was moving my email to a new server and as part of that process I  was building dspam.  The compilation failed due to a combination of some poor programming practices and an actual mistake in the source plus a change in the tolerance of the compiler to that practice. On the other hand, the