Re: shell errors

On 10 Sep 2013, at 02:32 , Erik Christiansen <[email protected]> wrote:

> If the logging doesn't cast enough light, I'd comment each one out in
> turn, to rule it out. (Or half to begin with, to halve the search.)
> If none of them are the culprit, things become even more interesting.

The bash error was the read herring<1> that made tracking this down difficult. This is the line that caused the failure very late in the .procmailrc (the line is near the top):

TRAP='echo ""; formail -bl "$LASTFOLDER" ;echo "    Spam: $SPAM; echo "Deliverd: $LONGDATE$NL";'

It should read

TRAP='echo ""; formail -bl "$LASTFOLDER" ;echo "    Spam: $SPAM"; echo "Deliverd: $LONGDATE$NL";'


<1> that's a pun! A twisted, torturous pun!

That TRAP was overridden in nearly all cases, so it was only when a message fell through all the recipes to the end that it triggered. I found it before it triggered.

-- 
Were it not for frustration and humiliation
I suppose the human race would get ideas above its station.
   -Ogden Nash