procmail
[Top] [All Lists]

Re: 3.11pre7: LOGABSTRACT bug

1997-07-03 12:11:00
Stefan Monnier wrote,

| it seems that LOGABSTRACT=all doesn't quite work with 3.11pre7.
| More specifically, it doesn't log anything for pipe recipes, even though the
| manpage specifically says that an entry is logged for every successfull
| delivering-recipe.

It does log pipes and forwards if that's the last thing procmail does.  If
procmail pipes or forwards a copy based on a recipe with a `c' flag, then
LOGABSTRACT=all fails to operated properly and doesn't log the action.

The rather inefficient workaround is to spawn a clone: change

    :0c other flags
    * conditions
    | command # or ! addresses

to this otherwise ridiculous syntax:

    :0c condition-related flags
    * conditions
    {
     # only way to make 3.11pre7 log piping or forwarding of a copy
     :0 action-related flags
     | command # or ! addresses
    }

That way the delivery of the copy is the last thing that the clone procmail
will do, so the clone will log it.

Note that this is not necessary when a copy is delivered by procmail's saving
it to a folder.  Then LOGABSTRACT=all works properly.  In fact, in some situ-
ations I've solved the problem simply by changing this:

     :0c flags
     * conditions
     | command # or ! addresses
      :0A:
      folder

to this:

    :0c condition-related flags:
    * conditions
    folder
     :0A action-related flags
     | command # or ! addresses


<Prev in Thread] Current Thread [Next in Thread>