procmail
[Top] [All Lists]

Re: Unexpected forward to pager problem

2001-06-08 09:27:04
When Bart Schaefer suggested to Tim Rice,

S> My only guess is that the pager is limiting the size of the transmission
S> *including* the message header, and that forwarding through procmail is
S> causing additional Received: headers to be added, which consumes that part
S> of the limited transmission size that used to be applied to the body.

Tim answered,

R> Humm, Could be, the Procmail headers are about double what the direct mail
R> headers are.

Procmail does not add any headers (except that it might lengthen 'From ' by
adding a '>From ' below it).  It may be reading an rcfile that has filtering
recipes whose commands add other headers.

The usual answer for these pager forwards problems is to filter a copy
through a formail command that keeps only a couple of the most valuable
headers (such as From: and Subject:) and pipes them and the body to $SENDMAIL
to the pager's address, much as Bart illustrated, but perhaps being more
severe in restricting the headers passed to the pager, such as

  :0c
  * ^TO_urgent(_at_)mydomain
  * ! ^FROM_DAEMON
  | formail -k -XFrom: -XSubject: | $SENDMAIL 111111(_at_)152mail(_dot_)com

Even Date: isn't important to preserve, because the pager will have its own
timestamp on the message.

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