Hi all,
I have still been unable to resolve this anomalie, although this is the
last try because there is an easy workaround.
For me, procmail insists on delivering to the system mailbox, ignoring
the settings of $DEFAULT and $ORGMAIL.
Is it possible that your .procmailrc is actually an INCLUDERC
from /etc/procmailrc, which is doing something else with
your fall-offs?
There is no /etc/procmailrc. I am the only user of procmail on the system.
Thanks to the 2 people who have replied before - here is my setup:
mail is delivered on a sunos 4.1.3 machine, and my .forward takes it to
a solaris machine (andromeda) first:
cat .forward
"|rsh andromeda ~kuhlmav/bin/procmail"
(The login shell is tcsh)
uname -a
SunOS andromeda 5.5 Generic sun4d sparc SUNW,SPARCserver-1000
~/bin/procmail -v
procmail v3.11pre7 1997/04/28 written and created by Stephen R. van den Berg
Locking strategies: dotlocking, fcntl(), lockf()
Default rcfile: $HOME/.procmailrc
Your system mailbox: /var/mail/kuhlmav
When compiling, I only made these 2 patches (abbreviated):
--- procmail-3.11pre7/Makefile.orig Mon Apr 28 12:27:40 1997
+++ procmail-3.11pre7/Makefile Thu Aug 13 12:23:11 1998
-BASENAME = /usr
+BASENAME = $(HOME)
+LOCKINGTEST=/var/mail $(HOME) /tmp /var/tmp
--- procmail-3.11pre7/src/authenticate.c.orig Mon Apr 28 12:27:45 1997
+++ procmail-3.11pre7/src/authenticate.c Thu Aug 13 12:22:09 1998
-#define MAILSPOOLDIR "/var/spool/mail/" /* watch the trailing / */
+#define MAILSPOOLDIR "/var/mail/" /* watch the trailing / */
With the following .procmailrc:
-----
VERBOSE=yes
PATH=/bin:/usr/bin:/usr/local/bin
MAILDIR=$HOME/Mail
MAILETCDIR=$MAILDIR/etc
DEFAULT=$MAILDIR/inbox
LOGFILE=$MAILETCDIR/procmail.log
UMASK=076
# Store a safety copy of each incoming mail
:0 c:
$MAILETCDIR/procmail.backup
:0 c
|echo $DEFAULT $ORGMAIL $LOGFILE $PATH >>$HOME/pmtest
#:0:
#$DEFAULT
------
which produces this log:
procmail: Assigning "UMASK=076"
procmail: Locking "/home/users/pg/kuhlmav/Mail/etc/procmail.backup.lock"
procmail: Assigning "LASTFOLDER=/home/users/pg/kuhlmav/Mail/etc/procmail.backup"
procmail: Opening "/home/users/pg/kuhlmav/Mail/etc/procmail.backup"
procmail: Acquiring kernel-lock
procmail: Unlocking "/home/users/pg/kuhlmav/Mail/etc/procmail.backup.lock"
procmail: Executing "echo $DEFAULT $ORGMAIL $LOGFILE $PATH >>$HOME/pmtest"
procmail: Assigning "LASTFOLDER=echo $DEFAULT $ORGMAIL $LOGFILE $PATH
$HOME/pmtest"
procmail: Locking "/var/mail/kuhlmav.lock"
procmail: [9474] Fri Aug 14 17:09:32 1998
procmail: Assigning "LASTFOLDER=/var/mail/kuhlmav"
procmail: Opening "/var/mail/kuhlmav"
procmail: Acquiring kernel-lock
procmail: Unlocking "/var/mail/kuhlmav.lock"
From
vku10(_at_)cantua(_dot_)canterbury(_dot_)ac(_dot_)nz@elec.canterbury.ac.nz
Fri Aug 14 17:09:34 1998
Subject: ttt5
Folder: /var/mail/kuhlmav 824
procmail: Notified comsat: "kuhlmav(_at_)9245:/var/mail/kuhlmav"
procmail delivers to /var/mail/kuhlmav instead of to $DEFAULT (as the docs and
other people say).
If I do not uncomment the last recipe (explicit delivery to $DEFAULT)
mail gets delivered to $DEFAULT.
$HOME/pmtest has this content:
/home/users/pg/kuhlmav/Mail/inbox
/var/mail/kuhlmav
/home/users/pg/kuhlmav/Mail/etc/procmail.log
[and here goes my usual shell path - why??????]
The setting of $DEFAULT is therefore correct, but the setting of $PATH
is completely ignored.
I have run out of ideas a while ago - has anyone any more? I don't like
this kind of discrepency in sensitive software because it might mean
that there is some other problem I don't know about.
Thanks for any help.
Volker