Jim Reisert <jjr(_at_)mintcc(_dot_)external(_dot_)hp(_dot_)com> writes:
More on this problem:
What's really happening is that the mail is being appended to the SENDERS
mail spool when it originates on the system.
For example, a user 'w4an' sends mail to 'ad1c' and the message lands in
'w4an's mail spool.
What is causing this, and how can I get it to stop?
1) Are you sure you're running procmail 3.11pre3 or later? The
following appears in the HISTORY file and it appears it was added no
later than 3.11pre3:
Changes to procmail:
...
- If called with -d option and not running with enough
privileges, procmail will bounce the mail (instead of
delivering to the invoker, as it used to)
If this is the problem, then you know that procmail has insufficient
privileges and either needs to be made setuid root, or the local
mailer definition needs to be fixed. Or both. And you should
upgrade to 3.11pre7 as well.
2) Have you tried running sendmail with debugging flags to see how it
is calling procmail? Try running the following as root on the mail
server:
sendmail -odi -d11.2 -f root your(_at_)address(_dot_)here < /dev/null
For me, here, that prints out the following:
solen# sendmail -f root -odi -d11.2 guenther < /dev/null
openmailer: procmail -f root(_at_)solen(_dot_)gac(_dot_)edu -Y -a -d
guenther
openmailer: running as r/euid=0/0
openmailer: MCI(_at_)b8460: flags=2<TEMP>,
errno=0, herrno=0, exitstat=0, state=2, pid=2903,
maxsize=0, phase=NULL, mailer=local,
status=NULL, rstatus=NULL,
host=NULL, lastuse=Wed Dec 31 19:00:00 1969
giveresponse: stat=0, e->e_message=<NULL>
solen#
What does that generate on your system?
Philip Guenther