Hi all, Thanks for your help. I was on vacation, so I didn't have much time to log on and check my Email. In any case, the error I see in Postfix's log is this:
Jul 23 03:37:41 servername postfix/lmtp[99283]: 8D07811684: to=<[EMAIL PROTECTED]>, relay=none, delay=17, delays=17/0.01/0/0, dsn=4.4.1, status=deferred (connect to servername.example.com[dspam/socket]: Connection refused) I've forced logging to be off. FreeBSD is 7.0-STABLE (amd64), running on HP 380DL with dual Xeon's. That's the 64-bit version of FreeBSD. By the way, the above DSPAM session ran alone as I didn't connect Postfix to it. Just to see if it dies by itself, or because of external sources like Postfix. By telnet'ing to a specific port specified in master.cf, I can selectively re-route messages through it (like the one above, which failed -- deferred). All regular messages are re-routed without DSPAM. So I guess DSPAM dies all by itself after few days... Anyone got an idea how to debug this? Noor P.S.: The below patch is still relevant for my case? On Wed, 09 Jul 2008 21:02:02 +0200, "Steve" <[EMAIL PROTECTED]> wrote: > > -------- Original-Nachricht -------- >> Datum: Wed, 09 Jul 2008 09:50:01 -0500 >> Von: Troy Ayers <[EMAIL PROTECTED]> >> An: dspam-users <[email protected]> >> Betreff: Re: [dspam-users] DSPAM on FreeBSD 7-STABLE freezes after 1-2 > days > >> Ion-Mihai Tetcu wrote: >> > On Tue, 08 Jul 2008 13:03:47 -0500 >> > Troy Ayers <[EMAIL PROTECTED]> wrote: >> > >> > >> >> Noor Dawod wrote: >> >> >> >>> Hello folks, >> >>> >> >>> I have DSPAM run on FreeBSD 7-STABLE with latest Postfix, Postgrey, >> >>> Dovecot and Amavisd. The DSPAM is running as a content filter >> >>> defined in master.cf (--daemon option). >> >>> Every one or two days, the DSPAM daemon stops listening to incoming >> >>> connections and Postfix defers all deliverable messages because >> >>> DSPAM doesn't accept connections. >> >>> >> >>> Anyone has an idea what to do in order to debug this problem? >> >>> >> >>> Thanks, >> >>> >> >>> /Comrax >> >>> >> >>> >> >> I don't have any ideas on debugging the problem. IIRC, some previous >> >> version of dspam would freeze unless logging was disabled. Try >> >> disable logging? (I can't find any archived messages to backup my >> >> assertion though) >> >> >> >> I'm curious. You running 64bit version of Freebsd? >> >> >> >> What version of DSPAM? >> >> >> >> At any rate I use dspam but not deamonized, because of stability >> >> problems such as what you describe. >> >> >> > >> > Can you elaborate? I'm not sure, but I don't remember a bug report >> > about this. Did I miss you email or forgot about it? >> > >> > >> There not much to tell really. In my case I was running dspam 3.6.4 >> (later I tried 3.6.6 then 3.6.8), on RHEL4 on X86_64. >> >> http://mailing-list.nuclearelephant.com/2883.html >> >> At the time, I believe there was no facility to file a bug report. >> > I think this was due the bug in bnr debugging and was/is fixed with this > patch: > --- src/libdspam.c 2006-07-17 02:14:02.000000000 +0200 > +++ src/libdspam.fix_bnr_debug.c 2007-12-10 20:33:53.905085288 > +0100 > @@ -986,8 +986,10 @@ > if (CTX->flags & DSF_NOISE) { > nobnr_result = _ds_calc_result(CTX, heap_nobnr, diction); > > - if (CTX->factors) > + if (CTX->factors) { > _ds_factor_destroy(CTX->factors); > + CTX->factors = NULL; > + } > CTX->result = x; > CTX->probability = DSP_UNCALCULATED; > } > > >> >> -Troy >> >> >> >> > > -- > Psssst! Schon vom neuen GMX MultiMessenger gehört? > Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger > > !DSPAM:1011,48867ff9150921702376303!
