In message <016a01ca309d$32892d50$979b87f0$(_at_)com>,
on Tuesday, 8 September, 2009 at 11:58:24 Rob Henry
(rob(_at_)sharpbus(_dot_)com) wrote:
Well it made a difference but not the one we are looking for.
Log file:
procmail: [1257] Tue Sep 8 11:50:22 2009
procmail: No match on "^X-Spam-Status: Yes"
procmail: Assigning
"PATH=/home/rjh/bin:/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin"
procmail: Suspicious rcfile "/home/rjh/.procmailrc"
procmail: Couldn't read "/home/rjh/.procmailrc"
procmail: Locking "/var/spool/mail/rjh.lock"
procmail: Assigning "LASTFOLDER=/var/spool/mail/rjh"
procmail: Opening "/var/spool/mail/rjh"
procmail: Acquiring kernel-lock
procmail: Unlocking "/var/spool/mail/rjh.lock"
procmail: Notified comsat: "rjh(_at_)556:/var/spool/mail/rjh"
From rjh(_at_)mail(_dot_)sharpbus(_dot_)com Tue Sep 8 11:50:21 2009
Subject: sharp567 vacation on
Folder: /var/spool/mail/rjh
8331
procmail: Unlocking "/home/rjh/mail/.Pm/lockmail"
drwxrwxr-x 6 rjh rjh 4096 Sep 8 11:22 /home/rjh
drwxrwxr-x 7 rjh rjh 4096 Sep 8 10:04 /home/rjh/mail
From man procmail:
Suspicious rcfile "x" The owner of the rcfile was not the recipient or
root, the file was world writable, or the direc-
tory that contained it was world writable, or
this was the default rcfile ($HOME/.procmailrc)
and either it was group writable or the directo-
ry that contained it was group writable (the rc-
file was not used).
Did you make /home/rjh world writable or was it already so? I was
expecting you to make it drwxr-xr-x. I know I did not say that exactly,
I just assumed you could read my mind. :-)
So, while we try to get to the bottom of your problem please make files
644 and directories 755. Sorry for not being explicit before.
Cheers,
Nick.
--
____________________________________________________________
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