Shouldn't the lockfile on the -inner- portion be sufficient? I believe it
should. However ... there may be another problem.
Look at this bit from procmailex(5):
] In order to make sure the lockfile is not removed until the pipe has
] finished, you have to specify option `w'; otherwise the lockfile would
] be removed as soon as the pipe has accepted the mail.
I'd think that changing the existing ":0:" to be ":0 w:" should be
sufficient.
However, if it only happens to those particular messages, perhaps it's a
problem with 'From ' parsing. Can you look at your mailbox (before popping
it) and see if the split messages are happening when there is a line
beginning with 'From ' line in the body of your mail?
On 16 Feb 2002, Craig Hughes wrote:
> The problem is in your procmail recipe. You need a lockfile, or else
> two spamassassin running at the same time could both be simulatneously
> redirecting to your "kid" mailbox, interleaving their contents. Change
> the first line to:
>
> :0:
>
> and you should be fixed.
>
> On Sat, 2002-02-16 at 13:10, Kevin Dangoor wrote:
> > From: "Charlie Watts" <[EMAIL PROTECTED]>
> > > On Sat, 16 Feb 2002, Kevin Dangoor wrote:
> > >
> > > > I get a couple of mass-mailed newsletters that get mangled by
> > > > SpamAssassin. SA is the only filter I'm running, so it must be
> > > > responsible... it is possible that there is something that I can change
> > > > in the config that would fix this. I'm using Outlook Express as my mail
> > > > reader. The symptom that I'm seeing is that part of the message will
> > > > show up normally, and the end part of the message will show up as a
> > > > separate email that is missing headers.
> > >
> > > What version of SpamAssassin are you running?
> >
> > Sorry... I should know to provide the basic info :)
> >
> > I'm using 2.01. I've been using SpamAssassin for some time, and this is
> > actually not a new problem... I've just been too lazy to report it. This was
> > happening in the earlier versions I've used (starting with 1.3).
> >
> > > Describe how SpamAssassin is integrated into your system ... Procmail? You
> > > must be using mbox delivery for messages to get split up like that.
> >
> > Yep, procmail and mbox. My hosting company is using procmail to split mail
> > between multiple accounts to my domain. Here's the specific recipe I'm using
> > for SA:
> >
> > :0
> > * $RECIP ?? ^^kid@$DOMAIN
> > {
> > :0:
> > | perl -I../www/blognet/lib ../spamassassin -c ~/.spamassassin -P >>
> > kid
> >
> >
> > }
> >
> > > Turn off SpamAssassin for a day - does the problem go away?
> >
> > Turn off SpamAssassin? Oh no! :)
> >
> > Seriously, though, this problem began after I installed SA with no other
> > changes to the system. Perhaps there is something wrong with my procmail
> > recipe.
> >
> > Kevin
> >
> >
> > _______________________________________________
> > Spamassassin-talk mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
> >
> >
>
>
--
Charlie Watts
[EMAIL PROTECTED]
Frontier Internet, Inc.
http://www.frontier.net/
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
