I found this near the bottom of the procmailrc.5 man page. It seems to
indicate that Bcc'd mail should be caught and routed properly.
----------
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-Z])?)', which should
catch all destination specifications.
----------
However, THIS receipe:
:0
* ^TO(_dot_)*sheryl(_at_)aecinfo(_dot_)com
! aec(_at_)inforamp(_dot_)net
does NOT catch mail that is BCC'd to sheryl(_at_)aecinfo(_dot_)com(_dot_) Why?
Tests reveal that To's and CC's get handled properly. But BCC's do not -
possibly because the BCC info is hidden in the header so it is not properly
read by procmail (??). It seems that any mail processor **must** be able to
properly handle BCC's. What am I missing?
Mark.
AEC InfoCenter Inc.