Mark Irvine <mirvine(_at_)compsoc(_dot_)com> writes:
...
The following mail is quite long, and rather newbieish is content. My
appologies for sendind such a long mail, but I have been stuck on this
problem for several weeks now.
I'm trying to get procmail working on my home PC running Linux(2.2)(RedHat6.0).
I am having some strange problems getting it to actually do ANYTHING.
When I say it won't do anything, it won't do any basic filtering, or even
generate a log file!
...
The problem is almost certainly one of permissions. If you were to examine
the maillog file in /var/log you should find bunches of messages saying
Suspicious rcfile "/home/mark/.procmailrc"
If you then look up "Suspicious rcfile" in the procmail(1) manpage you'll
see a blurb about procmail not trusting the default rcfile if it's either
a) world writable
b) in a world writable directory
c) group writable, or
d) in a group writable directory
The default Redhat installation puts each user in their own group and sets
their default permissions to include group-write, such that conditions
(c) and (d) are both met. There are two solutions:
1) The prefered solution is to install a version of procmail compiled with
the GROUP_PER_USER define set in the config.h file at compile time.
At one time there was an RPM of procmail version 3.13.1 that had this
set, but I don't know what happened to it. If you can't find such
a beast you can always download the source from:
ftp://ftp.procmail.org/pub/procmail/
and compile it yourself.
2) chmod g-w ~ ~/.procmailrc
This is quick, but fragile: don't forget to do this for all the other
users on the system and the new user template...
BTW: your message came across as a MIME multipart message, the first
part containing only the command
Always reply to mirvine(_at_)compsoc(_dot_)com
while the second part had the actual text of your question, encoded for
some reason in base64! That just leaves me asking "why????" Was this
intentional?
Philip Guenther