Thanks Ruud.
I've commented out DROPPRIVS in $HOME/.procmailrc
and found the system log in ~/Mail/ ... unfortunately it goes even
further back - to 2003 (?) .. see below ..
procmail: Skipped "+?(critical|security)? ?(pack|patch|update|upgrade)"
procmail: Skipped "* 1^0 ^subject: (abort|bug|error|failure)?"
procmail: Skipped "+?(advice|announcement|letter|message|notice|report)"
procmail: Skipped "swen"
procmail: Skipped "-junk"
procmail: No match on "> 140000"
procmail: Skipped "swen"
procmail: Skipped "-junk"
procmail: Extraneous locallockfile ignored
procmail: Assigning "PATH=/root/bin:/usr/local/bin:/usr/bin:/bin"
procmail: Locking "/root/Mail/INBOX.lock"
procmail: Assigning "LASTFOLDER=/root/Mail/INBOX"
procmail: Opening "/root/Mail/INBOX"
procmail: Acquiring kernel-lock
procmail: Unlocking "/root/Mail/INBOX.lock"
procmail: Notified comsat: "root(_at_)37:/root/Mail/INBOX"
From root Fri Nov 28 21:29:09 2003
Folder: /root/Mail/INBOX
.. the 'swen' thing was when my recent problems started. I was experimenting
with various things to stop an overwhelming DOS attack and may have done
some damage. I switched to Thunderbird for a while but have recently
rediscovered mutt again.
The user log is the one you are familiar with, containing ..
procmail: Assigning "LASTFOLDER=bounced"
procmail: Opening "bounced"
procmail: Acquiring kernel-lock
procmail: Unlocking "bounced.lock"
procmail: Notified comsat: "adam(_at_)241260:/home/adam/Maildir/bounced"
From root(_at_)paradise(_dot_)net(_dot_)nz Sat Dec 11 14:57:42 2004
Subject: Anacron job 'cron.daily' on Tux
Folder: bounced
.. I've inserted
LOG = "$_ u:$LOGNAME h:$HOME m:$MAILDIR$NL"
after the LOGFILE entry in both user & system rc files,
and attach ./procdiag.sh run as user adam (below).
Cheers,
Adam.
adam(_at_)Tux:~08:51:10$ ./procdiag.sh
# procdiag v20031105.1723
# procdiag run at Wed Dec 22 20:51:16 EST 2004
# general account information:
USER: adam (adam)
GROUPS: adam audio src scanner
SHELL: /bin/bash
MAIL:
hostname: tux (Tux)
FQDN: tux.paradise.net.nz
HOME: /home/adam
# user info from /etc/passwd (password is masked):
adam:x:1000:1000:Adam Bogacki,,,:/home/adam:/bin/bash
# system identifiers (if discernible):
OSTYPE: linux-gnu
MACHTYPE: i386-pc-linux-gnu
UNAME: Linux Tux 2.6.5-1-686 #5 Fri Apr 30 20:26:13 EST 2004 i686
GNU/Linux
# The current shell path is (not to be confused with the MTA-defined
# path):
PATH: /usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games
# formail and procmail information (as per versions in the current
# path):
0755 1 root root 26260 Fri Dec 3 05:51:27 2004
/usr/bin/formail
formail v3.22 2001/09/10
6755 1 root mail 67496 Fri Dec 3 05:51:27 2004
/usr/bin/procmail
procmail v3.22 2001/09/10
Default rcfile: $HOME/.procmailrc
It may be writable by your primary group
Your system mailbox: /var/mail/adam
# various procmail configuration elements:
ORGMAIL="/var/mail/adam"
SENDMAIL="/usr/sbin/sendmail"
SENDMAILFLAGS="-oi"
HOST="Tux"
PROCMAIL_VERSION="3.22"
LINEBUF="2048"
PATH="/home/adam/bin:/usr/local/bin:/usr/bin:/bin"
SHELL="/bin/bash"
SHELLMETAS="&|<>~;?*["
# usage banner from grep
Usage: grep [OPTION]... PATTERN [FILE]...
Try `grep --help' for more information.
# sed version or other identifier
0755 1 root root 41048 Wed Dec 1 11:28:55 2004
/bin/sed
GNU sed version 4.1.2
Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE,
to the extent permitted by law.
# sh info (intended to show whether sh is sh or a symlink to
# another shell)
lrwxrwxrwx 1 root root 4 Dec 20 13:42 /bin/sh -> bash
# sendmail program information (from procmail's $SENDMAIL):
4755 1 root root 644472 Wed Dec 8 00:01:21 2004
/usr/sbin/sendmail
exim: malformed debug_selector setting: + or - expected but
found "0"
# Determining Mlocal via sendmail diagnostic invocation
exim: malformed debug_selector setting: + or - expected but
found "0.15"
NOTE: procmail doesn't appear to be the LDA
# contents of /home/adam/.forward (if it exists)
"|IFS=' ' && exec /usr/bin/procmail -f- || exit 75 #adam"
# |sh -c "IFS=' ' && exec /usr/bin/procmail -f-||exit 75 #adam"
# An alternative .forward, not checked against the above, but
# merely
# offered here, is:
"|IFS=' ' && exec /usr/bin/procmail -f- || exit 75 #adam"
# file permissions and ownership:
0644 1 adam adam 4699 Wed Dec 22 20:47:39 2004
/home/adam/.procmailr c
0704 1 root root 125 Wed Dec 15 21:51:11 2004
/home/adam/.forward
0755 174 adam adam 12288 Wed Dec 22 20:47:39 2004
/home/adam/
0644 1 root root 2031 Wed Dec 22 20:47:12 2004
/etc/procmailrc
NOTE: There is no /etc/procmailrcs file.
0700 3 adam adam 4096 Mon Dec 20 21:00:28 2004
/home/adam/Mail/
0755 2 adam adam 4096 Mon Jan 19 21:11:19 2004
/home/adam/mail/
NOTE: There is no /home/adam/.procmail file.
0660 1 adam mail 0 Fri Jul 11 19:23:00 2003
/var/mail/adam
CAUTION: /var/mail/adam perms exceed 7755: curb back to 0640
2775 2 root mail 4096 Tue Dec 21 15:48:04 2004
/var/mail/
# procdiag report end
adam(_at_)Tux:~08:51:20$
On 21 Dec 2004 or thereabouts, Ruud wrote ..
Date: Tue, 21 Dec 2004 07:17:12 +0100
From: "Ruud H.G. van Tol" <rvtol(_at_)isolution(_dot_)nl>
Subject: Re: 'Folder: bounced '
To: "[procmail]" <procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE>
Message-ID: <049b01c4e724$bbc89460$0a01a8c0(_at_)isolution(_dot_)nl>
Content-Type: text/plain; charset=iso-8859-1
Toen wij Adam Bogacki kietelden, kwam er dit uit:
I've put DROPPRIVS at the top of both
/etc/procmailrc and $HOME/.procmailrc and
tried both
DROPPRIVS is only useful in /etc/procmailrc,
because in the user's .procmailrc only the
user's rights count (special circumstances
ignored).
When you set an environnment variable in the
/etc/procmailrc, you don't need to set it again
in the user's .procmailrc, but sometimes you
still want to do that, to be (as a user) immune
for changes at the /etc/procmailrc-level.
LOGFILE=$MAILDIR/.procmaillog
LOGFILE=$HOME/procmail.log
These are different. The first (starting with a dot,
so don't forget to use -a with ls when you look
for it) is in ~/Mail/, the second in ~/.
You could put a
LOG = "$_ u:$LOGNAME h:$HOME m:$MAILDIR$NL"
early (but after setting LOGFILE) in both .etc/procmailrc
and ~/.procmailrc, to create some log-output.
Tux:/home/adam# ./procdiag.sh
# procdiag v20031105.1723
# procdiag run at Tue Dec 21 16:20:38 EST 2004
# general account information:
USER: root (root)
Also run it as adam.
--
Grtz, Ruud
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail