Re: Sudden instability

[SG]

So what's the verdict? I'm using a FreeBSD package... my sa/milt seems
to stop working, is it crashing? Was it a new spammer's header? Is the
solution to upgrade to the latest? Can i just get the latest from
cvssup - will I have to reconfigure? BTW - I have envelope on, and it
still crashes. Interesting there hasn't been more on this, could it be
Todd and I are the only ones using the older version?

Thanks!
sg

On Sat, 3 Jul 2004 00:43:15 -0700, Todd Lyons <address@hidden> wrote:
> Dan Nelson wanted us to know:
> 
> >> >It could be that there's a new spam sender out there with unusual
> >> >header or HELO information that happens to crash the milter.  The
> >> >report_safe stuff shouldn't make any difference.  I believe the
> >> >redhat
> >> Turns out that it did.  I reverted the change on mx1 and mx3, leaving
> >> mx2 as the only machine with the report_safe 0 setting.  Over the
> >> past 24 hours, only mx2 has crashed (about 5 times since this time
> >> yesterday).
> >That's interesting.  Spamass-milter actually replaces the body on spams
> >even if it's unchanged, so the only real difference between your before
> >and after cases should have been the replacement of Content-Type:,
> >which shouldn't really make any difference.  I don't run report_safe on
> >my systems so I have never personally run through this codepath.  I'll
> >turn it on on my personal box, but I only get ~20 spams a day so it may
> >take a while to die :)
> >> I don't think I used the RedHat RPM, I rolled my own.  I can't find
> >> my srpm or my spec file any more, I think I built it on a box that
> >> we've since reimaged to a Gentoo box.
> >Then you may be missing the "empty-body" patch, which fixed a crash on
> >a message with no body at all.
> 
> There's a very good possibility that is true.  I took a CVS snapshot
> from this afternoon, compiled it, installed it on one of my 3 boxen,
> then reenabled the report_safe 0 setting.  So far it has run with no
> crashes.  If it makes it through the weekend, I will put it on all of
> the boxen and give you a report middle of next week.
> 
> >Valgrind is easy to use.  You just stick "valgrind" in front of the
> >commandline and it does the rest.  Newer valgrinds require the
> 
> Yeah I played with it a bit this afternoon. It's quite nice.  I think
> that you're right above though.  I was running pristine 0.2.0 code, so
> none of the recent fixes in CVS had made its way into my code.  I think
> that I'm going to be much better off now.  How much, I will report next
> week.
> 
> I also hang out in the #Mandrake, #Clamav, and #Spamassassin channels on
> irc.freenode.net.  You can usually catch me there.
> --
> Regards...              Todd
>  We should not be building surveillance technology into standards.
>  Law enforcement was not supposed to be easy.  Where it is easy,
>  it's called a police state.             -- Jeff Schiller on NANOG
> Linux kernel 2.6.3-8mdkenterprise   3 users,  load average: 0.00, 0.01, 0.00
> 
> 
> 
> 
> _______________________________________________
> Spamass-milt-list mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/spamass-milt-list
>