[Cc's to Doug Muth <dmuth+3294902021997005238690764911520398(_at_)ot(_dot_)com>
and guenther(_at_)gac(_dot_)edu removed.]
On Mon Feb 03 1997, Zbigniew Baniewski wrote:
I've checked, that procmail itself is called and it's working properly.
I simply used short .procmailrc, which contained:
:0 h c
* ! ^FROM_DAEMON
* ! ^X-Loop: zb(_at_)ispid(_dot_)com(_dot_)pl
|(/usr/local/bin/formail -r \
-A "Precedence: junk" \
-A "X-Loop: zb(_at_)ispid(_dot_)com(_dot_)pl"; \
echo "Mail received.") | $SENDMAIL -t
...
The permissions seem fine. Let's simply the recipe to something
like this:
:0
|(/usr/local/bin/formail -r -A "Precedence: junk" \
- -A "X-Loop: zb(_at_)ispid(_dot_)com(_dot_)pl"; \
echo "Mail received.") >>$HOME/test.mailfolder
...
Following your tip I made sure, that 'vacation' script, which you can see
at the very beginning will work, when I comment out the '* ! ^FROM_DAEMON'
line. When I left this line uncommented, I've got in 'from':
[munch]
....so, it looks pretty good. But pay attention, that all the time I was
using example from man page (man procmailex). I think, we are at the end
of the puzzle, but the final question: what's wrong in '* ! ^FROM_DAEMON'
line ? How to replace it, to prevent mail-loops between daemons ? Simply
with '* ! ^daemon' (it seems so to me) ?
And why in man-page there is obviously broken example ? :(
This is my personal experience...
I *never* use the ^FROM_DAEMON, ^FROM_MAILER, ^TO_ or ^TO regular
expression macros - they have never worked for me like the procmailrc
man page claims they do. They tend to mismatch on what they are
supposed to catch, or catch things that they are not meant to. PITA.
IMHO, they are broken.
I've defined my own regular expression variables for things like this,
and they work just fine.
This confirms that I'm not the only one to experience this.
BTW...
% procmail -v
procmail v3.11pre4 1995/10/29 written and created by Stephen R. van den Berg
Cheers
Tony