I just recently compiled procmail v3.11pre6 on two different UNiX
platforms (SunOS [SunOS 4.1.3_U1 9 sun4m] and LiNUX [I don't have the
`uname -a` output handy, but I can get it if you need it]). I noted that
the `man` page for 'procmailrc.5' seems wrong in a section of it. In
particular:
***** BEGIN -- procmailrc from v3.11pre6 *****
[snip]
MISCELLANEOUS
If the regular expression contains `^TO_' it will be sub-
stituted by `(^((Original-)?(Resent-)?(To', which should
catch all destination specifications containing a specific
address.
If the regular expression contains `^TO' it will be sub-
stituted by `(^((Original-)?(Resent-)?(To', which should
catch all destination specifications containing a specific
word.
If the regular expression contains `^FROM_DAEMON' it will
be substituted by `(^(Precedence', which should catch
mails coming from most daemons (how's that for a regular
expression :-).
If the regular expression contains `^FROM_MAILER' it will
be substituted by `(^(((Resent-)?(From' (a stripped down
version of `^FROM_DAEMON'), which should catch mails
coming from most mailer-daemons.
[snip]
***** END -- procmailrc from v3.11pre6 *****
Here's the output from v3.11pre4:
***** BEGIN -- procmailrc from v3.11pre4 *****
[snip]
MISCELLANEOUS
If the regular expression contains `^TO_' it will be substi-
tuted by `(^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope
|Apparently(-Resent)?)-To):(.*[^-a-zA-Z0-9_.])?)', which
should catch all destination specifications containing a
specific address.
If the regular expression contains `^TO' it will be substi-
tuted by `(^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope
|Apparently(-Resent)?)-To):(.*[^a-zA-Z])?)', which should
catch all destination specifications containing a specific
word.
If the regular expression contains `^FROM_DAEMON' it will be
substituted by `(^(Precedence:.*(junk|bulk|list)|To:
Multiple recipients of |(((Resent-)?(From|Sender)|X-
Envelope-From):|>?From )([^>]*[^((_dot_)%(_at_)a-z0-
9])?(Post(ma?(st(e?r)?|n)|office)|(send)?Mail(er)?|daemon
|mmdf|n?uucp|LIST(SERV|proc)|NETSERV|owner|r(e(quest|sponse)
|oot)|b(ounce|bs\.smtp)|echo|mirror|s(erv(ices?|er)|mtp)
|A(dmin(istrator)?|MMGR|utoanswer))(([^).!:a-z0-9][-_a-z0-
9]*)?[%@>\t ][^<)]*(\(.*\).*)?)?$([^>]|$)))', which should
catch mails coming from most daemons (how's that for a
regular expression :-).
If the regular expression contains `^FROM_MAILER' it will be
substituted by `(^(((Resent-)?(From|Sender)|X-Envelope-From):
|>?From )([^>]*[^((_dot_)%(_at_)a-z0-9])?(Post(ma(st(er)?|n)|office)
|(send)?Mail(er)?|daemon|mmdf|n?uucp|r(esponse|oot)
|(bbs\.)?smtp|serv(ices?|er)|A(dmin(istrator)?|MMGR))(([^).!
:a-z0-9][-_a-z0-9]*)?[%@>\t ][^<)]*(\(.*\).*)?)?$([^>]|$))'
(a stripped down version of `^FROM_DAEMON'), which should
catch mails coming from most mailer-daemons.
[snip]
***** END -- procmailrc for v3.11pre4 *****
Now, if there's been no change in the "procmailrc" man page, then no big
deal -- I can just copy the old version over. If there has been a change,
I don't want to miss a feature/bug fix listed in it. I don't *think* it's
a problem on my end because it *seemed* to compile fine on both platforms.
Any advice/suggestions/insight? procmail (both versions I've been
speaking of) seem to substitute the macros properly, it's just the man
pages that are tweaked.
Lates!
---------------------------------------------------------------------------
Tim <bodysurf(_at_)pobox(_dot_)com>
mailto:bodysurf(_at_)pobox(_dot_)com
Finger bodysurf(_at_)pobox(_dot_)com for my PGP public key (Bits 1024/KeyID
09DA5C49).
PGP Key FPrint (09/03/94): 4C 97 F1 FA 70 55 68 91 49 D1 AD F2 DD 63 0C 15
---------------------> Please PGP encrypt your email <---------------------