Sent: Saturday, February 16, 2002 4:45 PM
Subject: Re: [SAtalk] Mangled messages
> 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
The other thing I'd suggest is to let procmail deliver the mail, rather
than having the shell do it (using the redirect to the mbox method), ie
something like:
:0
* $RECIP ?? ^^kid@$DOMAIN
{
:0fw
| perl -I../www/blognet/lib ../spamassassin -c ~/.spamassassin
-P
:0:
> I'd think that changing the existing ":0:" to be ":0 w:" should be
> sufficient.
I'll do this, but I don't think this is a multiple writers issue, given the
consistency with certain messages having this problem. (I don't get *that*
much mail that I have lots trying to come in at the same time :
On Sat, 2002-02-16 at 13:45, Charlie Watts wrote:
> Shouldn't the lockfile on the -inner- portion be sufficient? I believe it
> should. However ... there may be another problem.
Ooops, didn't see that -- agree on the "w" flag though.
> However, if it only happens to those particular messages, pe
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 lockfi
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
On Sat, 16 Feb 2002, Kevin Dangoor wrote:
> {
> :0:
> | perl -I../www/blognet/lib ../spamassassin -c ~/.spamassassin -P >>
> kid
>
>
> }
Have you noticed if you are receiving multiple
messages at the same time when the corruption
occurs? As if one is being processed while a
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 chan
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 O
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 O
Hi,
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
11 matches
Mail list logo
