[Dspam-devel] TrainPristine insufficient explanation in conf comments and debug logging
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?
--
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
Dspam-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspam-devel
Re: [Dspam-devel] TrainPristine insufficient explanation in conf comments and debug logging
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 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
Dspam-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspam-devel
Re: [Dspam-devel] TrainPristine insufficient explanation in conf comments and debug logging
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: dspam-devel@lists.sourceforge.net
Date: Sat, 22 Nov 2014 03:00:13
To:
Reply-To: dspam-devel@lists.sourceforge.net
Subject: Re: [Dspam-devel] TrainPristine insufficient explanation in conf
comments and debug logging
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 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
Dspam-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspam-devel
--
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
Dspam-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspam-devel
Re: [Dspam-devel] TrainPristine insufficient explanation in conf comments and debug logging
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 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
----------
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
Dspam-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspam-devel
Re: [Dspam-devel] TrainPristine insufficient explanation in conf comments and debug logging
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... 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] -- 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 Dspam-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-devel
Re: [Dspam-devel] TrainPristine insufficient explanation in conf comments and debug logging
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 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 -- 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 Dspam-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-devel
Re: [Dspam-devel] TrainPristine insufficient explanation in conf comments and debug logging
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? > > 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 -- 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 Dspam-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-devel
[Dspam-devel] rabl
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 -- ___ Dspam-devel mailing list Dspam-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-devel
[Dspam-devel] Kqueue
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
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
> Dspam-devel@lists.sourceforge.net
> 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
--- daemon.c2012-04-11 13:48:33.0 -0500
+++ /home/edgar/dspam/dspam-3.10.2/src/daemon.c 2019-01-01 15:55:39.119888537
-0600
@@ -36,11 +36,13 @@
#define RSET(A)( A && !strcmp(A, "RSET") )
+#include
#include
#include
#include
#include
#include
+#include /* for kqueue */
#include
#include
#include
@@ -86,18 +88,17 @@
* RETURN VALUES
* returns 0 on success
*/
-
int daemon_listen(DRIVER_CTX *DTX) {
struct sockaddr_in local_addr, remote_addr;
THREAD_CTX *TTX = NULL;
- fd_set master, read_fds;
pthread_attr_t attr;
- struct timeval tv;
- int fdmax, yes = 1;
+ struct timespec to = { 10, 0 };
+ struct kevent ev;
+ int yes = 1;
int domain = 0; /* listening on domain socket? */
int listener;/* listener fd */
- int i;
- int port = 24, queue = 32; /* default port and queue size */
+ int port = 2424, queue = 32; /* default port and queue size */
+ int kq, nev;
signal(SIGPIPE, SIG_IGN);
signal(SIGINT, process_signal);
@@ -114,9 +115,10 @@
domain = 1;
/* initialize */
-
- FD_ZERO(&master);
- FD_ZERO(&read_fds);
+ if ((kq = kqueue()) == -1) {
+LOG(LOG_CRIT, ERR_DAEMON_KQ, strerror(errno));
+return(EFAILURE);
+ }
pthread_attr_init(&attr);
pthread_attr_setdetachstate(&attr, PTHREAD_CREATE_DETACHED);
@@ -200,16 +202,12 @@
return(EFAILURE);
}
- FD_SET(listener, &master);
- fdmax = listener;
+ EV_SET(&ev, listener, EVFILT_READ, EV_ADD|EV_ENABLE, 0, 0, 0);
+ kevent(kq, &ev, 1, NULL, 0, &to);
/* Process new connections (until death or reload) */
for(;;) {
-read_fds = master;
-tv.tv_sec = 2;
-tv.tv_usec = 0;
-
if (__daemon_run == 0) {
close(listener);
@@ -219,80 +217,80 @@
return 0;
}
-if (select(fdmax+1, &read_fds, NULL, NULL, &tv)>0) {
-
+nev = kevent(kq, NULL, 0, &ev, 1, &to);
+if (nev == -1)
+ err(1, "kevent");
+if (nev == 0)
+ continue;
+else {
/* Process read-ready connections */
-
- for(i=0;i<=fdmax;i++) {
-if (FD_ISSET(i, &read_fds)) {
-
- /* Accept new connections */
-
- if (i == listener) {
-int newfd;
-int addrlen = sizeof(remote_addr);
-
-if ((newfd = accept(listener,
-(struct sockaddr *)&remote_addr,
-(socklen_t *) &addrlen)) == -1)
-{
+ if ((int)ev.ident == listener) {
+/* Accept new connections */
+int newfd;
+int addrlen = sizeof(remote_addr);
+
+if ((newfd = accept(listener,
+ (struct sockaddr *)&remote_addr,
+ (socklen_t *) &addrlen)) == -1)
+{
LOG(LOG_WARNING, ERR_DAEMON_ACCEPT, strerror(errno));
continue;
#ifdef DEBUG
-} else if (!domain) {
- char buff[32];
- LOGDEBUG("connection id %d from %s.", newfd,
+} else if (!domain) {
+ char buff[32];
+ LOGDEBUG("connection id %d from %s.", newfd,
#ifdef HAVE_INET_NTOA_R_2
- inet_ntoa_r(remote_addr.sin_addr, buff)
+ inet_ntoa_r(remote_addr.sin_addr, buff)
#else
- inet_ntoa_r(remote_addr.sin_addr, buff, sizeof(buff))
+ inet_ntoa_r(remote_addr.sin_addr, buff, sizeof(buff))
#endif
- );
+ );
#endif
-}
-fcntl(newfd, F_SETFL, O_RDWR);
-setsockopt(newfd,SOL_SOCKET,TCP_NODELAY,&yes,sizeof(int));
-
-/*
- * Since processing time varies, each new connection gets its own
- * thread, so we cre
Re: [Dspam-devel] Kqueue
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 > Dspam-devel@lists.sourceforge.net > 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 ___ Dspam-devel mailing list Dspam-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-devel
Re: [Dspam-devel] Kqueue
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 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 ___ Dspam-devel mailing list Dspam-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-devel
[Dspam-devel] What is the status of development?
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 _______ Dspam-devel mailing list Dspam-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-devel
Re: [Dspam-devel] Kqueue
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 Dspam-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-devel
Re: [Dspam-devel] Kqueue
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 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 ___ Dspam-devel mailing list Dspam-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-devel
[Dspam-devel] I have a patch, what's the procedure for getting it approved?
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? ___ Dspam-devel mailing list Dspam-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-devel
