procmail
[Top] [All Lists]

.procmailrc Flags

2000-06-24 21:35:04
I have a very serious complaint with the flags in a .procmailrc file. 
With the following example, I'll prove my point.  To start with, I'd
like to state that everyone knows how important CPU time has on the
system.  It's probably the number one factor in processing.

In the following example I want to draw your attention to the flags. 
This is significant, because in the Example, I must use the "h" flag
or the body of the message will travel along with the intended
message, but that doesn't come without a price.  I must use the last
/dev/null recipe to destroy the body or it will try some unexpected
stunt: e.g. save itself to a file/folder, which it did several times.
(Keep in mind, it was without a header.)

Example:

  :0 fh
  | ($FORMAIL -rt                                            \
    -I "Message-ID:"                                         \
    -I "X-Precedence: Personal Mail"                         \
    -I "X-Loop: $MDEST"                                      \
    -I "Subject: Message Distribution"                       \
    -I "To: $MDEST"                                         ;\
    echo "Message distributed to $MAGENT~>Personal folder." ;\
    echo; echo -e "\tRe:\n\t$MSUBJ\n\t$MFROM"               ;\
    cat $HOME/mail/.signature-notice                         \
    ) | $SENDMAIL -oi -t

  :0:
  /dev/null

I've run every experiment that I could think of to bring about a
different type of recipe, but it is impossible.  Nevertheless, I
immensely appreciate the assistance I've received on this mailing
list.  This is the reason for much of my recent inquires stemming from
the above dilemma, which is out of control -- not on my part, but the
making of .procmailrc.

Either we leave in the "b" and "h" flags, which is very beneficial, or
we eliminate them completely, but then we'll be right back with the
loss of time factoring.

I'm wondering, how do each of you feel towards this situation?  Are
you in favor or against and why?

I understand that the next version of Procmail will eliminate the "b"
and "h" flags in nested loops entirely, but there will always be
mailing lists that tax CPU time because of lengthy messages and
filtering resulting from due processing.

Note: When you reply to this message, please include
      the mailing list and my address.

*********************************************************************
Signed,
SoloCDM

_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail

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