dspam-devel Mailing List for DSPAM
Brought to you by:
paulcockings,
sbajic
You can subscribe to this list here.
2009 |
Jan
|
Feb
(8) |
Mar
(13) |
Apr
(21) |
May
(70) |
Jun
(92) |
Jul
(125) |
Aug
(149) |
Sep
(52) |
Oct
(86) |
Nov
(116) |
Dec
(163) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2010 |
Jan
(113) |
Feb
(28) |
Mar
(24) |
Apr
(107) |
May
(59) |
Jun
(9) |
Jul
(38) |
Aug
(503) |
Sep
(16) |
Oct
(12) |
Nov
(19) |
Dec
(17) |
2011 |
Jan
(2) |
Feb
(20) |
Mar
(2) |
Apr
(3) |
May
(36) |
Jun
(40) |
Jul
(2) |
Aug
(76) |
Sep
(10) |
Oct
(10) |
Nov
(14) |
Dec
(8) |
2012 |
Jan
(1) |
Feb
(9) |
Mar
(4) |
Apr
(9) |
May
(8) |
Jun
(15) |
Jul
|
Aug
(18) |
Sep
(6) |
Oct
(6) |
Nov
(5) |
Dec
(6) |
2013 |
Jan
(16) |
Feb
(13) |
Mar
(5) |
Apr
(1) |
May
|
Jun
(17) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
|
2014 |
Jan
(4) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(5) |
Aug
(1) |
Sep
|
Oct
|
Nov
(7) |
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2019 |
Jan
(5) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
From: <dsp...@li...> - 2021-12-23 15:32:30
|
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 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? |
From: <dsp...@li...> - 2020-08-21 22:59:35
|
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 personal email server. I'm working on a project to update that server, and I thought I'd try getting dspam running on Ubuntu 20.04. I got stalled by compilation errors (just posted a bug report), and there are no packages for dspam. Anyway, I've really appreciated dspam over the years. So I'm hoping the project is still alive... - David Reagan |
From: <dsp...@li...> - 2019-02-14 17:58:52
|
On Wed, 02 Jan 2019 18:11:05 +0100 dspam-devel--- via Dspam-devel <dsp...@li...> wrote: > dsp...@li... 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 try :) > 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 if it > was more maintained, and helpfull integradeing milter to dspam so it > have more simple setup then it currently have, i know from a gentoo > dev side that dspam-milter exists, but it would need more work to > make it more stable, and since i think lots of distros is precompiled > problems this takes even more time, since more maintainers say why > should we add it, none of the other precompiled problems do it > > all that sayed, i have had fun using dspam and dspam milter on > gentoo, self maintained ebuilds in fidonet overlay, currently i have > removed them possible i could add them back and hope for proxy > maintainer helps with them, would be nice if thay go into gentoo > portage > > thanks for your work, if just more did that it would be better Well, it's still in the FreeBSD Ports Tree and also available to install via packages. I recently installed it on a FreeBSD 12 with MySQL 5.7 with InnoDB tables as backed, running as content filter for Postfix. (Found a few little things to fix, like defaulting mysql to innodb and some cosmetic fixed in the docs, but I lost my SF account a few years back. Stevan, do you still have yours?) For reference: # dspam --version DSPAM Anti-Spam Suite 3.10.2 (agent/library) Copyright (C) 2002-2012 DSPAM Project http://dspam.sourceforge.net. DSPAM may be copied only under the terms of the GNU Affero General Public License, a copy of which can be found with the DSPAM distribution kit. Configuration parameters: '--sysconfdir=/usr/local/etc' '--with-logdir=/var/log/dspam' '--with-dspam-home=/var/db/dspam' '--with-dspam-home-owner=dspam' '--with-dspam-home-group=dspam' '--with-dspam-home-mode=0770' '--with-dspam-owner=dspam' '--with-dspam-group=dspam' '--enable-syslog' '--enable-debug' '--enable-preferences-extension' '--enable-daemon' '--enable-clamav' '--with-mysql-includes=/usr/local/include/mysql' '--with-mysql-libraries=/usr/local/lib/mysql' '--with-storage-driver=mysql_drv' '--enable-virtual-users' '--enable-long-usernames' '--with-dspam-mode=4511' '--prefix=/usr/local' '--localstatedir=/var' '--mandir=/usr/local/man' '--infodir=/usr/local/info/' '--build=amd64-portbld-freebsd12.0' 'build_alias=amd64-portbld-freebsd12.0' 'CC=cc' 'CFLAGS=-O2 -pipe -fstack-protector -fno-strict-aliasing ' 'LDFLAGS= -L/usr/local/lib -fstack-protector ' 'LIBS=' 'CPPFLAGS=-I/usr/local/include' 'CPP=cpp' # cpp --version FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM 6.0.1) Target: x86_64-unknown-freebsd12.0 Thread model: posix InstalledDir: /usr/bin -- IOnut |
From: <dsp...@li...> - 2019-01-02 17:30:17
|
dsp...@li... 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 if it was more maintained, and helpfull integradeing milter to dspam so it have more simple setup then it currently have, i know from a gentoo dev side that dspam-milter exists, but it would need more work to make it more stable, and since i think lots of distros is precompiled problems this takes even more time, since more maintainers say why should we add it, none of the other precompiled problems do it all that sayed, i have had fun using dspam and dspam milter on gentoo, self maintained ebuilds in fidonet overlay, currently i have removed them possible i could add them back and hope for proxy maintainer helps with them, would be nice if thay go into gentoo portage thanks for your work, if just more did that it would be better |
From: <dsp...@li...> - 2019-01-01 22:31:40
|
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 Pettijohn wrote: > > I have adapted the daemon to use kqueue instead of select. If anyone is interested in the patch. > > > > Thanks, > > > > Edgar > > > > _______________________________________________ > Dspam-devel mailing list > Dsp...@li... > https://lists.sourceforge.net/lists/listinfo/dspam-devel Sorry, forgot to add I was also halfway thinking about rewriting to use libevent so that the best `notification' method available would automagically be used. Edgar |
From: <dsp...@li...> - 2019-01-01 22:30:06
|
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 Pettijohn wrote: > > I have adapted the daemon to use kqueue instead of select. If anyone is interested in the patch. > > > > Thanks, > > > > Edgar > > > > _______________________________________________ > Dspam-devel mailing list > Dsp...@li... > https://lists.sourceforge.net/lists/listinfo/dspam-devel I haven't integrated into the build system yet. I'm still on the fence if I'm going to use dspam or not. So I will probably test it out a bit before putting more effort into it. So basically this patch just replaces daemon_listen() with a new daemon_listen() and includes the sys/event.h header unconditionally. If it is of interest then I will gladly put forth the additional effort. Edgar |
From: <dsp...@li...> - 2019-01-01 21:15:56
|
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 Pettijohn wrote: > I have adapted the daemon to use kqueue instead of select. If anyone is interested in the patch. > > Thanks, > > Edgar |
From: <dsp...@li...> - 2019-01-01 06:14:49
|
I have adapted the daemon to use kqueue instead of select. If anyone is interested in the patch. Thanks, Edgar |
From: <dsp...@li...> - 2016-09-20 01:58:11
|
i like to know if that was really what i think about to see made possible, if its url repution, as bayes poison is well known trick from spammers now, then it could possible fight back with url repution, and the bayes poison signature :=) i will not reweal the poison, but i can tell how i make a rule in spamassassin to detect it what are plans for dspam and dspam-milter ? hope its not dead |
From: <dsp...@li...> - 2014-11-25 14:24:19
|
On Mon, Nov 24, 2014 at 11:02:58PM +0000, dsp...@li... wrote: > Le 2014-11-22 15:50, dsp...@li... 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 to start. I doubt you will be given the > maintainance of the official repository right away. Usually commit right > is given after writing some good patches for some time. I'd recommend to > advertize your repository, listing what commit you have done. > > Where can I find the URL of that repository? > > Best regards, > > Thomas > We have just started working with the latest version and still need to set up a git repository. Then we will be evaluating are current set of changes that we have to the 3.6 tree to verify that they are either not needed or still an outstanding issue. Once that is done, we will publish it. I do agree that we need more than a single individual to keep it moving. I just want to get the process started so that we can have some continuity. Regards, Ken |
From: <dsp...@li...> - 2014-11-24 23:03:05
|
Le 2014-11-22 15:50, dsp...@li... 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 to start. I doubt you will be given the maintainance of the official repository right away. Usually commit right is given after writing some good patches for some time. I'd recommend to advertize your repository, listing what commit you have done. Where can I find the URL of that repository? Best regards, Thomas |
From: <dsp...@li...> - 2014-11-24 22:57:44
|
Le 2014-11-22 11:00, dsp...@li... 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... But somehow, I feel tempted. > And I was really happy when I used it years ago. It is really a shame > it came to this point... Before talking about skills I think you need to ask yourself if the objective of the software are aligned with you. This software already have a large userbase and users would be lost if the software were to change of focus. Taking on maintainance needs some commitment. Now don't worry too much about the codebase, these things can be learned. You can start by looking at easy bugs that are reported and fix those. For instance typos so that you will get familiar with the directory structure of dspam. There is probably also a bit of bugs with patches included. You can take a look at those but I know some are a bit complex. I think the most important is to pay attention at the security side. dspam is made to run on server and work on untrusted input (malformed message can reach dspam). This means you need to look at any patch thinking about all the things that might happen. Anything should be bounded in size: no strcpy, strlen etc. since the input could be arbitrarely large. I think the best for dspam would be if several people could be actively maintaining it. There could be code review to increase the likelyhood of catching a bug in a patch for instance. After it's just C, some bits of HTML and perl I think for the webfrontend, SQL for the database and be able to read an RFC and follow it to the letter. The best way would be to host a clone of the git repository somewhere else and start fixing the bugs in the database. Then after some time you can show you work and ask the domain owner to let you maintain dspam officially. What you would have done before would be proof that you are capable. Feel free to advertise your repository, I'm sure there would be many users willing to give it a try. If you come to look at the patches I wrote (most of them are not applied yet and sit in the bugtracker), I'd be happy to answer any questions you might have about them. Best regards, Thomas [maintainer of dspam Debian package] |
From: <dsp...@li...> - 2014-11-22 15:51:06
|
On Sat, Nov 22, 2014 at 03:00:13AM +0000, dsp...@li... wrote: > Le 2014-11-21 17:03, dsp...@li... 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 of signatures and DSPAM > > headers to the > > # message, and deliver the message in as pristine format as possible. > > This mode > > # REQUIRES that the original message in its pristine format (as of > > delivery) > > # be presented for retraining, as in the case of webmail, imap, or > > other > > # applications where the message is actually kept server-side during > > reading, > > # and is preserved. DO NOT use this switch unless the original > > message can be > > # presented for retraining with the ORIGINAL HEADERS and NO > > MODIFICATIONS. > > # > > # NOTE: You can't use this setting with dspam_trian; if you're going > > to use it, > > # wait until after you train any corpora. > > # > > #TrainPristine on > > > > This option caused me some 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 break > > reclassification through the web frontend along with any other tools > > that try to use `dspam --signature=...` > > Indeed. It could be a bit more exhaustive. > > > > > Additionally... > > > > src/dspam.c: > > LOGDEBUG ("saving signature as %s", ATX->signature); > > > > if (CTX->classification == DSR_NONE && CTX->training_mode != > > DST_NOTRAIN) > > { > > if (!ATX->train_pristine) { > > int x = _ds_set_signature (CTX, CTX->signature, > > ATX->signature); > > if (x) { > > LOG(LOG_WARNING, "_ds_set_signature() failed with error > > %d", x); > > } > > } > > } > > > > The LOGDEBUG message here is very misleading since the signature > > doesn't actually get saved all the time. Those three conditions can > > prevent saving of the signature. There should probably be two > > separate > > LOGDEBUG here, the second one inside the conditionals. > > True again. > > > > > Would the sourceforge issue tracker, or a submitted patchset, be an > > appropriate place to pursue this conversation? > > There is nobody maintaining dspam anymore, so nobody to merge, less > write, a patch. But if you feel like taking on the maintainance > altogether then please be my guest, you'd make many people happy. > > Best regards, > > Thomas > 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. Regards, Ken |
From: <dsp...@li...> - 2014-11-22 11:00:06
|
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 used it years ago. It is really a shame it came to this point... -----Original Message----- From: dsp...@li... Date: Sat, 22 Nov 2014 03:00:13 To: <dsp...@li...> Reply-To: dsp...@li... Subject: Re: [Dspam-devel] TrainPristine insufficient explanation in conf comments and debug logging Le 2014-11-21 17:03, dsp...@li... 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 of signatures and DSPAM > headers to the > # message, and deliver the message in as pristine format as possible. > This mode > # REQUIRES that the original message in its pristine format (as of > delivery) > # be presented for retraining, as in the case of webmail, imap, or > other > # applications where the message is actually kept server-side during > reading, > # and is preserved. DO NOT use this switch unless the original > message can be > # presented for retraining with the ORIGINAL HEADERS and NO > MODIFICATIONS. > # > # NOTE: You can't use this setting with dspam_trian; if you're going > to use it, > # wait until after you train any corpora. > # > #TrainPristine on > > This option caused me some 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 break > reclassification through the web frontend along with any other tools > that try to use `dspam --signature=...` Indeed. It could be a bit more exhaustive. > > Additionally... > > src/dspam.c: > LOGDEBUG ("saving signature as %s", ATX->signature); > > if (CTX->classification == DSR_NONE && CTX->training_mode != > DST_NOTRAIN) > { > if (!ATX->train_pristine) { > int x = _ds_set_signature (CTX, CTX->signature, > ATX->signature); > if (x) { > LOG(LOG_WARNING, "_ds_set_signature() failed with error > %d", x); > } > } > } > > The LOGDEBUG message here is very misleading since the signature > doesn't actually get saved all the time. Those three conditions can > prevent saving of the signature. There should probably be two > separate > LOGDEBUG here, the second one inside the conditionals. True again. > > Would the sourceforge issue tracker, or a submitted patchset, be an > appropriate place to pursue this conversation? There is nobody maintaining dspam anymore, so nobody to merge, less write, a patch. But if you feel like taking on the maintainance altogether then please be my guest, you'd make many people happy. Best regards, Thomas ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk _______________________________________________ Dspam-devel mailing list Dsp...@li... https://lists.sourceforge.net/lists/listinfo/dspam-devel |
From: <dsp...@li...> - 2014-11-22 03:18:36
|
Le 2014-11-21 17:03, dsp...@li... 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 of signatures and DSPAM > headers to the > # message, and deliver the message in as pristine format as possible. > This mode > # REQUIRES that the original message in its pristine format (as of > delivery) > # be presented for retraining, as in the case of webmail, imap, or > other > # applications where the message is actually kept server-side during > reading, > # and is preserved. DO NOT use this switch unless the original > message can be > # presented for retraining with the ORIGINAL HEADERS and NO > MODIFICATIONS. > # > # NOTE: You can't use this setting with dspam_trian; if you're going > to use it, > # wait until after you train any corpora. > # > #TrainPristine on > > This option caused me some 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 break > reclassification through the web frontend along with any other tools > that try to use `dspam --signature=...` Indeed. It could be a bit more exhaustive. > > Additionally... > > src/dspam.c: > LOGDEBUG ("saving signature as %s", ATX->signature); > > if (CTX->classification == DSR_NONE && CTX->training_mode != > DST_NOTRAIN) > { > if (!ATX->train_pristine) { > int x = _ds_set_signature (CTX, CTX->signature, > ATX->signature); > if (x) { > LOG(LOG_WARNING, "_ds_set_signature() failed with error > %d", x); > } > } > } > > The LOGDEBUG message here is very misleading since the signature > doesn't actually get saved all the time. Those three conditions can > prevent saving of the signature. There should probably be two > separate > LOGDEBUG here, the second one inside the conditionals. True again. > > Would the sourceforge issue tracker, or a submitted patchset, be an > appropriate place to pursue this conversation? There is nobody maintaining dspam anymore, so nobody to merge, less write, a patch. But if you feel like taking on the maintainance altogether then please be my guest, you'd make many people happy. Best regards, Thomas |
From: <dsp...@li...> - 2014-11-21 17:03:36
|
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 pristine format as possible. This mode # REQUIRES that the original message in its pristine format (as of delivery) # be presented for retraining, as in the case of webmail, imap, or other # applications where the message is actually kept server-side during reading, # and is preserved. DO NOT use this switch unless the original message can be # presented for retraining with the ORIGINAL HEADERS and NO MODIFICATIONS. # # NOTE: You can't use this setting with dspam_trian; if you're going to use it, # wait until after you train any corpora. # #TrainPristine on This option caused me some 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 break reclassification through the web frontend along with any other tools that try to use `dspam --signature=...` Additionally... src/dspam.c: LOGDEBUG ("saving signature as %s", ATX->signature); if (CTX->classification == DSR_NONE && CTX->training_mode != DST_NOTRAIN) { if (!ATX->train_pristine) { int x = _ds_set_signature (CTX, CTX->signature, ATX->signature); if (x) { LOG(LOG_WARNING, "_ds_set_signature() failed with error %d", x); } } } The LOGDEBUG message here is very misleading since the signature doesn't actually get saved all the time. Those three conditions can prevent saving of the signature. There should probably be two separate LOGDEBUG here, the second one inside the conditionals. Would the sourceforge issue tracker, or a submitted patchset, be an appropriate place to pursue this conversation? |
From: Helio L. Jr <hel...@gm...> - 2014-08-22 14:19:42
|
Hi folks, in the documentation I have found the example04: ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- CTX = dspam_create (USERNAME, NULL, dspam_home, DSM_CLASSIFY,//DSM_PROCESS DSF_SIGNATURE| DSF_NOISE); ( ... some more code ...) if (CTX->signature == NULL) { printf ("No signature provided\n"); } else { /* Copy to a safe place */ SIG.data = malloc (CTX->signature->length); if (SIG.data != NULL) memcpy (SIG.data, CTX->signature->data, CTX->signature->length); } SIG. length = CTX->signature->length; ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- but when I try to print out what the signature is (as pure text, a char array): ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- printf("Signature returned by dspam= %s",CTX->signature); ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- it prints unrecognisable characters and the strlen(CTX->signature) returns 0 How can I get the signature from DSPAM, using LIBDSPAM? Helio Luchtenberg Junior. |
From: Thomas Preud'h. <ro...@ce...> - 2014-07-14 14:22:17
|
Le lundi 14 juillet 2014, 21:56:29 Thomas Preud'homme a écrit : > Le mercredi 09 juillet 2014, 16:04:24 Tom Hendrikx a écrit : > > Hello DSPAM community, > > > > After a few years of being active in the DSPAM community, I've decided > > to leave the project. Unlike others who silently stopped responding to > > mails and other inquiries, I'm documenting my reasons in the hopes > > that it might be of help/interest to others. By the way, maybe a news could be written about this? I know it's not the kind of news that is usually put forward but that might (let's hope) push someone to step up. Best regards, Thomas |
From: Thomas Preud'h. <ro...@ce...> - 2014-07-14 14:14:30
|
Le mercredi 09 juillet 2014, 16:04:24 Tom Hendrikx a écrit : > Hello DSPAM community, > > After a few years of being active in the DSPAM community, I've decided > to leave the project. Unlike others who silently stopped responding to > mails and other inquiries, I'm documenting my reasons in the hopes > that it might be of help/interest to others. Given the above and my previous mail to check the status of dspam development, it should come to no surprise to people that I plan to request a removal of dspam from the unstable suite which will lead to dspam being absent of the next Debian stable release and next Ubuntu release as well (of course it could still be in a PPA). Be sure that I don't enjoy this decision as my personal emails are filtered by dspam but the Debian packaging already carry quite a few patches and now it's clear that it will only grow. I'll keep the git tree of the packaging around for a while so that if somebody decides to step up I can reintroduce dspam quickly in the archive but this would need to happen before october for dspam to be part of the next stable release of Debian and probably a bit before that for Ubuntu. Tom, thanks for your hard work on Dspam, it is really appreciated. Best regards, Thomas |
From: Terry B. <te...@do...> - 2014-07-10 00:43:53
|
On Jul 9, 2014, at 7:04 AM, Tom Hendrikx <to...@wh...> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Hello DSPAM community, > > After a few years of being active in the DSPAM community, I've decided > to leave the project. Unlike others who silently stopped responding to > mails and other inquiries, I'm documenting my reasons in the hopes > that it might be of help/interest to others. Thank you Tom. What you describe is unfortunately what I assumed was happening. Maybe this is the place to start discussing alternatives for the benefit of all current DSPAM users. I'd be very interested to hear what you're considering as a replacement. -Terry Terry Barnum digital OutPost http://www.dop.com |
From: Hendrik V. <hv...@gm...> - 2014-07-09 20:08:40
|
Hi TOm, Though I also love the DSPAMdesign and mechanism(s), spamassasin with it's filters have been a de facto mail filter that almost everybody uses, and that adds to DSPAM's "unknown" status and being forgotten by mail administrators ;( Sorry to see another good project wither away :( Hendrik On Wed, Jul 9, 2014 at 4:04 PM, Tom Hendrikx <to...@wh...> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > > Hello DSPAM community, > > After a few years of being active in the DSPAM community, I've decided > to leave the project. Unlike others who silently stopped responding to > mails and other inquiries, I'm documenting my reasons in the hopes > that it might be of help/interest to others. > > When I actively joined the DSPAM project, it was in need of some new > blood that helped out on development and other tasks, after most of > the original participants of the community takeover from Sensory > Networks somehow silently abandoned the project for reasons unknown > (to me). > > After being active for a few years, I think I've seen most of the > problems in the DSPAM project, and tried to address a few without > result. The main issues I learned are listed below. > > 1. No active development > - ------------------------ > There is no one working on the DSPAM code. There are numerous bug > reports and feature requests that could be addressed, and some parts > in DSPAM have been ripe for refactoring or rewriting for a long time, > but nobody is putting any effort into it. There is currently only one > developer 'active' within the project, but you rarely see activity > from this person. > The most code changes in the last 2(?) years are from patches > contributed through debian bugreports (thank you, debian maintainer). > The fact that no one within the project is actively working on the > code, creates a sort of chicken-or-egg problem: without existing > activity, no major outside contributions can be expected, since no one > is interested in becoming the new sole responsible developer in the > project. > > 2. No value seen in making DSPAM more transparent > - ------------------------------------------------- > On several occasions I've raised my voice on making DSPAM more usable > to new users, for instance by making error messages more informative, > or adding logging of normal operation (i.e. non-errors) so people get > a better hang of the product. Changes like this don't 'improve' DSPAM > filtering, but the they do make the software easier to use, and its > operation more transparent to new and experienced users. > Finding issues in software is easier when you actually understand what > it's trying to do, which in turn could result in more active users, > more useful bug reports, possible more contributed patches and in the > end maybe even more developers. > Right now DSPAM acts like a sort of black box for anyone not familiar > with the source code, and that discourages investigation of odd > behavior, which could be any of: configuration errors, bugs or missing > (but expected) features. > > 3. No drive on changing the status quo > - -------------------------------------- > The situation that DSPAM is in right now, a sort of dormant or zombie > (not dead but far from alive) status, is not good. It doesn't attract > new users, it doesn't attract new developers, actually it only only > supports existing, experienced users. Nobody in the community, both in > the project maintainers as in the users community, seems to be > interested in changing that. > Based on my observations, that seems that people seem to think that > DSPAM is either feature-complete and bug-free, or they just lack the > motivation/energy/time/whatever to contribute anything. > > Because I care about DSPAM, in the years I've active within the > project all of these issues have bothered me multiple times. I've > tried to address stuff that I could address, or tried to raise > awareness for other things. I didn't get much done though. > - From this I can only conclude that DSPAM is a sort of dead project. > Just like I wouldn't like to get myself (or my company, for instance) > depending on a piece of software in this state, I think that nobody > should get the impression that DSPAM is supported by an active > community, when that support actually never goes beyond answering easy > questions on the users mailing list. > > Therefore I'm resigning as DSPAM release manager, and will remove > myself as project admin from the sourceforge project. I hope others > will take up responsibility for the work I leave behind (and > unattended tasks listed above, or any tasks I didn't point out), so > maybe DPAM will become an active project in the future. > > Kind regards, > Tom Hendrikx > > > PS: I tried to address some of the issues listed above (logging of > regular operation, transparent code (including documentation), easier > ways of contribution) outside of the DSPAM code base itself, which > finally resulted in dspam-milter[1]. I'll continue to develop and > support that software, probably until I'll stop using DSPAM myself. If > I would ever abandon the project, proper notice (just like this one) > will be given. > > [1] https://github.com/whyscream/dspam-milter > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQIcBAEBCAAGBQJTvUviAAoJEJPfMZ19VO/1rBUQANmP1DCmqUMSJ82QnnfnmeBA > nsZmkijQvdvgvqvaitTWs/KpmtlzeojVpxZlRlvCciigqW9kHR1qgvqRBRl246z9 > NZ6EedGIH8yNJbrRTg+KZrFC6UFfg0H6rcGAnwVZoP8xEW0ysND0plnZmCOolXr9 > uApBJw3yPtgNTA4zMAqSnPcHckIvVXSsPqe8Wfw/4Ko1c8UBTk9dTqxBWTIV9bQQ > W3JgdE1m41ihNbWWX9v6Yf9CQqlsow6NeMmxUe/JcD8dhBW1sggxNlTFH+W0a7tw > 1KFSVb8DLo8fWkhNkWytsGxdOoqzgdnk+FyKjKMfcbba/HyrrgI2Q9VJuRnztwVw > Nv3jCUIEbPsikUfBytfkUK3ex3/MisuFhN8BR+Ei+mi3ELTC4CXDUINbNR4uD2A8 > 9WxoBzW5kkr39Yj+AiXnaNsPUDgFpE7bo8500nqkYoKxEe0/psvacfIjPqF2EslF > mzPU7xjmDeXxwelLWVK8Cr0YHVH0J+pEUxq5jd1+Iy0DD7ySGeIb9Uzu9o69f730 > Wg95v/Ijpea4P9mFQdcYppUm5HwbbYwWfB6eQmg4tkh2zXebRXhnvAxN+N94k03c > VdJaTzxXuX/29TPB5CZ7B7BxhwpXv4Aw8AXHcejn4aeIoHz7JmNi0WO6a/Sy0qFs > noK/MrcJsnh3TPcp9HZT > =lxQ5 > -----END PGP SIGNATURE----- > > ------------------------------------------------------------------------------ > Open source business process management suite built on Java and Eclipse > Turn processes into business applications with Bonita BPM Community Edition > Quickly connect people, data, and systems into organized workflows > Winner of BOSSIE, CODIE, OW2 and Gartner awards > http://p.sf.net/sfu/Bonitasoft > _______________________________________________ > Dspam-devel mailing list > Dsp...@li... > https://lists.sourceforge.net/lists/listinfo/dspam-devel |
From: Tom H. <to...@wh...> - 2014-07-09 14:04:35
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello DSPAM community, After a few years of being active in the DSPAM community, I've decided to leave the project. Unlike others who silently stopped responding to mails and other inquiries, I'm documenting my reasons in the hopes that it might be of help/interest to others. When I actively joined the DSPAM project, it was in need of some new blood that helped out on development and other tasks, after most of the original participants of the community takeover from Sensory Networks somehow silently abandoned the project for reasons unknown (to me). After being active for a few years, I think I've seen most of the problems in the DSPAM project, and tried to address a few without result. The main issues I learned are listed below. 1. No active development - ------------------------ There is no one working on the DSPAM code. There are numerous bug reports and feature requests that could be addressed, and some parts in DSPAM have been ripe for refactoring or rewriting for a long time, but nobody is putting any effort into it. There is currently only one developer 'active' within the project, but you rarely see activity from this person. The most code changes in the last 2(?) years are from patches contributed through debian bugreports (thank you, debian maintainer). The fact that no one within the project is actively working on the code, creates a sort of chicken-or-egg problem: without existing activity, no major outside contributions can be expected, since no one is interested in becoming the new sole responsible developer in the project. 2. No value seen in making DSPAM more transparent - ------------------------------------------------- On several occasions I've raised my voice on making DSPAM more usable to new users, for instance by making error messages more informative, or adding logging of normal operation (i.e. non-errors) so people get a better hang of the product. Changes like this don't 'improve' DSPAM filtering, but the they do make the software easier to use, and its operation more transparent to new and experienced users. Finding issues in software is easier when you actually understand what it's trying to do, which in turn could result in more active users, more useful bug reports, possible more contributed patches and in the end maybe even more developers. Right now DSPAM acts like a sort of black box for anyone not familiar with the source code, and that discourages investigation of odd behavior, which could be any of: configuration errors, bugs or missing (but expected) features. 3. No drive on changing the status quo - -------------------------------------- The situation that DSPAM is in right now, a sort of dormant or zombie (not dead but far from alive) status, is not good. It doesn't attract new users, it doesn't attract new developers, actually it only only supports existing, experienced users. Nobody in the community, both in the project maintainers as in the users community, seems to be interested in changing that. Based on my observations, that seems that people seem to think that DSPAM is either feature-complete and bug-free, or they just lack the motivation/energy/time/whatever to contribute anything. Because I care about DSPAM, in the years I've active within the project all of these issues have bothered me multiple times. I've tried to address stuff that I could address, or tried to raise awareness for other things. I didn't get much done though. - From this I can only conclude that DSPAM is a sort of dead project. Just like I wouldn't like to get myself (or my company, for instance) depending on a piece of software in this state, I think that nobody should get the impression that DSPAM is supported by an active community, when that support actually never goes beyond answering easy questions on the users mailing list. Therefore I'm resigning as DSPAM release manager, and will remove myself as project admin from the sourceforge project. I hope others will take up responsibility for the work I leave behind (and unattended tasks listed above, or any tasks I didn't point out), so maybe DPAM will become an active project in the future. Kind regards, Tom Hendrikx PS: I tried to address some of the issues listed above (logging of regular operation, transparent code (including documentation), easier ways of contribution) outside of the DSPAM code base itself, which finally resulted in dspam-milter[1]. I'll continue to develop and support that software, probably until I'll stop using DSPAM myself. If I would ever abandon the project, proper notice (just like this one) will be given. [1] https://github.com/whyscream/dspam-milter -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTvUviAAoJEJPfMZ19VO/1rBUQANmP1DCmqUMSJ82QnnfnmeBA nsZmkijQvdvgvqvaitTWs/KpmtlzeojVpxZlRlvCciigqW9kHR1qgvqRBRl246z9 NZ6EedGIH8yNJbrRTg+KZrFC6UFfg0H6rcGAnwVZoP8xEW0ysND0plnZmCOolXr9 uApBJw3yPtgNTA4zMAqSnPcHckIvVXSsPqe8Wfw/4Ko1c8UBTk9dTqxBWTIV9bQQ W3JgdE1m41ihNbWWX9v6Yf9CQqlsow6NeMmxUe/JcD8dhBW1sggxNlTFH+W0a7tw 1KFSVb8DLo8fWkhNkWytsGxdOoqzgdnk+FyKjKMfcbba/HyrrgI2Q9VJuRnztwVw Nv3jCUIEbPsikUfBytfkUK3ex3/MisuFhN8BR+Ei+mi3ELTC4CXDUINbNR4uD2A8 9WxoBzW5kkr39Yj+AiXnaNsPUDgFpE7bo8500nqkYoKxEe0/psvacfIjPqF2EslF mzPU7xjmDeXxwelLWVK8Cr0YHVH0J+pEUxq5jd1+Iy0DD7ySGeIb9Uzu9o69f730 Wg95v/Ijpea4P9mFQdcYppUm5HwbbYwWfB6eQmg4tkh2zXebRXhnvAxN+N94k03c VdJaTzxXuX/29TPB5CZ7B7BxhwpXv4Aw8AXHcejn4aeIoHz7JmNi0WO6a/Sy0qFs noK/MrcJsnh3TPcp9HZT =lxQ5 -----END PGP SIGNATURE----- |
From: Tom H. <to...@wh...> - 2014-01-03 13:09:29
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 03-01-14 03:49, Thomas Preud'homme wrote: > Le jeudi 2 janvier 2014, 14:51:41 Tom Hendrikx a écrit : >> >> As stated in the thread with Thomas, the problem is not in way >> patches can or could be reviewed. The manpower to do so is >> missing, and there are some patches out there that fix problems >> in code that nobody is (or should be) running, f.i. the css-file >> backend. > > Right, I said I would change the default in Debian but forgot about > that. I need to evaluate the impact of such a change and decide > whether to go for mysql / mariadb or postgresql. Would you > recommend one over the other? > I realize that this is a big change, that is probably not made easiy. As far as I know, the mysql backend has the most work in it as should be the most used/tested/bugfixed backend we have. I use pgsql myself without major issues (but it has some minor caveats). As for the mysql/mariadb differences: there was a recent thread in the dspam-user mailinglist on that. >> >> Applying the patch might solve the contributer's problem, but >> since nobody in the DSPAM team is using the code in production, >> it's really hard to test whether it actually works (or doesn't >> break anything else). > > I completely understand. However I can tell that people complained > about this problem and when it was solved incorrectly new bug > reports poped up. Then when it got properly fixed (last patch) all > bug report were closed and no new were reopened. On the contrary, I > got emails stating that everything works now. That's good to hear. > > Anyway I noticed the change of status of 2 of my bug report so > thank you a lot for reviewing my patch. No problem :) > > Best regards, > > Thomas > > ------------------------------------------------------------------------------ > > Rapidly troubleshoot problems before they affect your business. Most IT > organizations don't have a clear picture of how application > performance affects their revenue. With AppDynamics, you get 100% > visibility into your Java,.NET, & PHP application. Start your > 15-day FREE TRIAL of AppDynamics Pro! > http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk > > _______________________________________________ > Dspam-devel mailing list Dsp...@li... > https://lists.sourceforge.net/lists/listinfo/dspam-devel > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJSxrZ/AAoJEJPfMZ19VO/1tioQAIojr01+dFm9OwxECnymjxjU MN8ucMaJMTpvV3vOwMx0yHUVUeEk1Ka/J9QSeWzUU6gZxn4yK62vtbGDbP8bnaqC PwUb6517oUDxlrgIgBcwlNah5IalF3FFaihOw1N2re2zBQWyu+711gHrJKSg0jxB y/fpLnILZqbocOCE75Gkxfx16mrK8o0ceWQpclivjD79gCnRCAtXePX9WB8sORLY upadFUjCHXrPDK76k5bWf3oEpVvXWW05dEsg4Ngds3J/pyF+SchYQV4Vd17psE1T XwYCwSd4G1UxA23keSPcGM+U2YWZaSnxq/vtOjONAekxr9VdsjigeanviMDFG2Dz Qy2dBry0/xSl1fei+fTfjp6S5n+LhcLDFSfvE5xcR9YK0VCsaGrpmEijTiB3oDoV +UkkDDBoeEaLJwjQRiY/O+ahs3XVRh9PuANjgShihEIApp2SqgKh2UORPIRAFUsz 5jT4zvezQ9wc1Jvyg1SuhPNADbloMYg8y0TvO6dg7+Lva3bfrNWS7blgHJQgm8Rx ij8q9tHTCh7Da4ALzuP0puXsQjXWOcXAKvjdrLLuX7sbW5Aoxd7uhJGC0T0s5LKS PMxuwV5Ij2kfavnWUct6iUClH/B8cWDy5X7cxtdPLkWnW0FpoIzzfDCU0ZDLOPQx cpDIgrzR/yUaTK8/TSGy =qKkP -----END PGP SIGNATURE----- |
From: Thomas Preud'h. <ro...@ce...> - 2014-01-03 02:49:27
|
Le jeudi 2 janvier 2014, 14:51:41 Tom Hendrikx a écrit : > > As stated in the thread with Thomas, the problem is not in way patches > can or could be reviewed. The manpower to do so is missing, and there > are some patches out there that fix problems in code that nobody is > (or should be) running, f.i. the css-file backend. Right, I said I would change the default in Debian but forgot about that. I need to evaluate the impact of such a change and decide whether to go for mysql / mariadb or postgresql. Would you recommend one over the other? > > Applying the patch might solve the contributer's problem, but since > nobody in the DSPAM team is using the code in production, it's really > hard to test whether it actually works (or doesn't break anything else). I completely understand. However I can tell that people complained about this problem and when it was solved incorrectly new bug reports poped up. Then when it got properly fixed (last patch) all bug report were closed and no new were reopened. On the contrary, I got emails stating that everything works now. Anyway I noticed the change of status of 2 of my bug report so thank you a lot for reviewing my patch. Best regards, Thomas |
From: Tom H. <to...@wh...> - 2014-01-02 13:51:51
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 02-01-14 12:05, kael wrote: > Hi there, > > I've seen in the few last emails on this list that there is no > active development on dspam. That shouldn't be an issue if no new > feature is planned. > > But as Thomas Preud'homme (debian maintainer) explained, the > problem is that bug fixes are not included upstream. > > Do you know what could be done to change that state ? How can we > help you ? (we=people using dspam and ready to help improving it) > > Maybe a migration to github (or something like that) would ease the > process of reviewing patches ? > Hi Mickael, Thanks for your interest in making dspam better. As stated in the thread with Thomas, the problem is not in way patches can or could be reviewed. The manpower to do so is missing, and there are some patches out there that fix problems in code that nobody is (or should be) running, f.i. the css-file backend. Applying the patch might solve the contributer's problem, but since nobody in the DSPAM team is using the code in production, it's really hard to test whether it actually works (or doesn't break anything else). Moving to github could help, but in the end 80% of the github feature set is already available on sourceforge. However, nobody outside the dev team is commenting on bugs and/or reviewing patches there, which doesn't get my hopes up for improvement on a different scm platform. Tom -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJSxW7tAAoJEJPfMZ19VO/1PBEP/iYomnYfkRI4vYjGf9eTduN7 ib73GUMcUC7VcSGjkPcnJhPNTSxruspajsqJcgHqHqbDYJ4Zje+Iuo97K8bVi4/p b3ES59B7E8FjgYyGTMdayfBVVzq61iJTjeAoD6H5tqRIgVZ9PSJK+A1DilEDVbLJ xkCZ/z8FUtgAg1XlpDksMRkeh88mvsA8+61xfwIXZScItrhqxKNaiWNr+Af3Tzpi F3X/DOdCflAqQ6ji1Xnue92di/DGv64PTudxnoJ1ytfjvLGFLUyrDa3F4/ekmsJW DjhD+88rbno/a/wolq9RvmnKTxC/tJQQVcyxyIm0uhv22JfbGQuyyU6ynEcUdGFJ 03saM57eIeoECdEZQz3nT69wBuEW8qs1L70KoCktoccJIl9SH6OhSSklORYJIhvl tTgcpmVtx2FWXNPRu4sPxMdBuaiEwwC+QBEvSXuPhUBdlBpCZgZGWvlesSB8v8Vw 6n4+XVdZI4X6lifhrGIMUUS7E0v5XaRUdPru6hUEJfHEkj7GU3N7Gno+UHA2bPWp CpmgfIwe+ljQwlvb9IEMZ0GhLijw5wOpl4DybfaUjUH0KXJLKixT2eOUkOkeLZuC YRM7MNBbgXnfaw+/Cb41PsOalBERgllWK1+Tdto/ZYanIEFUUiUAOLfEvrPngg+s 3R8dPKZ/1n73daa0BjuL =7itu -----END PGP SIGNATURE----- |