Re: problem with spamassassin and following rules (Was: Re: OT)
Ligesh <gxlists <at> gmail.com>
2005-07-31 23:58:59 GMT
On Sun, Jul 31, 2005 at 11:36:03PM +0200, Dallman Ross wrote:
> On Mon, Aug 01, 2005 at 02:11:14AM +0530, Ligesh wrote:
> > On Sun, Jul 31, 2005 at 08:44:53PM +0200, Dallman Ross wrote:
> > But seeing the behaviour with strace, I think if I run it
> > through gdb, the bug may not show up. This is one of the most
> > frustrating kind of bugs; ones that disappear in the presence
> > of a debugger. It is most likely a timing issue. The wait()
> > function may not be working properly, and the checks are
> > happening before spamassassin properly returns or something. I
> > do not know the architecture of procmail so I cannot comment
> > more.
> Think about what you're saying: you're saying procmail doesn't
> work with spamassassin. Well, tens of thousands of uses run
> spamassassin from procmail hundreds or thousands of times a day.
> Where are these thousands of frustrated users, then, with their
> bug reports? SA has been around for four years now. I've been
> on this list for eleven, myself. I'm not the oldest user
> around here, by any means, either.
I am not saying that procmail doesn't work with spamassassin, but rather there is a very specific bug which
gets triggered on very particular circumstances. I am not the only one. There were 2 other people who
complained, but neither of them has later attributed it to config mistakes. And one guy specifically said
the config works on another machine, but on one machine somehow this weird behaviour is displayed.
Anyway, here's what's happening in the code. The "themail.p" variable becomes just an "F" once spamasssin