Greg asked,
| procmail: Couldn't determine implicit lockfile from " $FORMAIL -A"X-Sorted:
| Default" >>$DEFAULT"
| procmail: Locking ".lock"
Apparently you had DEFAULT unset or null.
| procmail: Executing " $FORMAIL -A"X-Sorted: Default" >>$DEFAULT"
| /bin/sh: : Ambiguous redirect
| procmail: Program failure (1) of " $FORMAIL -A"X-Sorted: Default"
| >>$DEFAULT"
| procmail: Unlocking ".lock"
Yup, that's how it looks. Same for the BULKFOLDER variable:
| procmail: Couldn't determine implicit lockfile from " $FORMAIL -A"X-Sorted:
| Bulk" >>$BULKFOLDER"
| procmail: Locking ".lock"
| procmail: Executing " $FORMAIL -A"X-Sorted: Bulk" >>$BULKFOLDER"
| /bin/sh: : Ambiguous redirect
| procmail: Program failure (1) of " $FORMAIL -A"X-Sorted: Bulk"
| >>$BULKFOLDER"
| procmail: Assigning "LASTFOLDER= $FORMAIL -A"X-Sorted: Bulk" >>$BULKFOLDER"
| procmail: Unlocking ".lock"
DEFAULT, unless you're calling procmail with the -m option, should be set
at startup and not cause that problem unless you specifically unset it.
BULKFOLDER, however, is a variable you'd need to set on your own, so it would
be unset if you haven't set it.