Thank you again! I renamed the old hash database and restarted the service.
This cleared up the problem. I guess the hash database decided it wasn't going
to play anymore.
Glad to be back working.
Brad-> Date: Thu, 10 Apr 2008 19:27:09 +0200> From: [EMAIL PROTECTED]> To:
[email protected]> Subject: Re: [dspam-users] Command died
with signal 11> > brad hodges wrote:> >> > > > If my old data got corrupt, how
do I get the messages? Are you saying I should move all the information in my
/var/dspam/data directory someplace else?> >> > > What kind of storage do you
use for tokens ? If it is libhash_drv.so > (check dspam.conf), then you could
try moving > /var/dspam/<user>/<user>.sig to somewhere else. <user> is the
recipient > that provokes the "signal 11" messages. Similarly for mysql, make a
> backup and create empty tables from scratch. Restart dspam if it is > running
as a daemon. If the problem is with the data, mail should start > flowing right
away. To actually fix your old data somebody at expert > level would have to
advise.> > Meanwhile you should really look into /etc/postfix/main.cf and >
/etc/postfix/master.cf and try to spot where mail gets routed to dspam. > It
should not be more than a single line to change to get postfix to > deliver
directly to procmail. Keep the dspam line in there, but > commented with a #.>
As a rule I always keep the old version of config files, renamed to >
/etc/whatever.orig, so I can switch back with minimal hassle. Guess you > will
too next time :-).> > Deferred means your server declined the mail with a 4XX
code, your > correspondents server will normally keep trying for 3-5 days,
whereafter > your correspondent will receive a notification from his server
that mail > could not be delivered.> --> Håkon> >
