Strange. It worked correctly when I ran the command on the mailhost, as both
myself and root, but not when I ran it from another machine.
jlloyd(_at_)suw3svr01:{~}:==> /admin/procmail/bin/procmail -f root -d root <
/etc/motd
procmail: [11202] Sat Apr 3 10:59:26 1999
procmail: Assigning "SHELL=/bin/sh"
procmail: Assigning "PATH=/admin/procmail/bin:/bin:/usr/ucb"
procmail: Assigning "ORGMAIL=/var/mail/root"
procmail: Assigning "MAILDIR=/"
procmail: Assigning "LOGFILE=/.procmail-log"
procmail: Opening "/.procmail-log"
I'm going to do some more testing, but let me know if this has helped.
Thanks!
jcl
"pg" == Philip Guenther <guenther(_at_)gac(_dot_)edu> writes:
pg> "Justin C. Lloyd" <jcl(_at_)biogate(_dot_)com> writes:
I have a .procmailrc file set up for root on our mail server, and everything
seemed to be working fine with it until I upgraded to procmail 3.12. I've
also just upgraded to sendmail 8.9.3, but that was from 8.9.1, so I don't
think my problem is a result of sendmail paranoia.
My problem is this: Now, procmail is not writing to $LOGFILE, which is set
to
/.procmail-log. It's reporting to syslog
Mar 31 09:59:55 suw3svr01 procmail[23778]: Error while writing to
"/.procmail-log"
pg> What happens if you put VERBOSE=on at the top of the /.procmailrc file
pg> and then run procmail as root with the command
pg> procmail -f root -d root < file_containing_an_email_message
pg> Philip Guenther
--
Justin C. Lloyd Harris Corporation, ISD Voice 407/984-5558
jlloyd(_at_)harris(_dot_)com 505 John Rodes Blvd. Fax
407/984-6323
Unix System Administrator Melbourne, FL 32935 Office W3/1807
"A standard doesn't have to be good, it just has to be good enough. The fact
that it is a standard more than makes up the difference." -- jwz