Aha.  That was my exact experience.  I had just forgotten about how
removing the globalgroup had "fixed" it.  My users can't do without the
global group though so that's not a long-term option.  But that may help
me to dig into the 3.6.8 code to see what may have been changed in 3.8.0
that could fix this.

Although the posting to the list about a segfault in 3.8.0 with
globalgroups may mean that it isn't totally fixed just yet...

-Jason

> Jason Axley wrote:
<snip>

> Some people (myself included) discovered a problem with DSpam 3.6.8.  If
> DSpam were setup with MySQL and a Merged Group the daemon would
> segfault. If the merged group was removed the daemon ran without error.
> I'm unsure what was causing the error, but some reported that the
> segfault would occur on messages containing foreign language characters.
> I was never able to verify this.
>
> I'm happy to report that after upgrading to DSpam 3.8.0 the Merged Group
> segfault seems to be fixed.
>
> Not sure if this was your exact problem, but I'm glad to hear that 3.8.0
> is working well for you.
>
> -Jeff Harris
>
> !DSPAM:4,474b148732574643617570!
>
>


Reply via email to