-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
* On 09-01-02 at 15:09
* Martin McCarthy said....
This is one of the things that Sean's script would have spotted for you,
I believe. Presumably the permissions on /home/nick/.procmailrc and/or
/home/nick are also 777. Procmail recognises that as a security problem
and refuses to use an unsafe .procmailrc. If you take a look at 'man
procmail' you'll find:
Suspicious rcfile "x" The owner of the rcfile was not the
recipient or root, the file was
world writable, or the directory
that contained it was world
writable, or this was the default
rcfile ($HOME/.procmailrc) and ei-
ther it was group writable or the
directory that contained it was
group writable (the rcfile was not
used).
Set the permissions on .procmailrc to, say, 640 and on /home/nick to,
say, 755 and try again.
Well that must be it! Out of pure exasperation I just re-wrote it and
didn't touch the permissions. Now it's all working very smoothly!
Now the real learning can start.
Much thanks for your help Martin
- --
Nick Wilson
Tel: +45 3325 0688
Fax: +45 3325 0677
Web: www.explodingnet.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE8PE/aHpvrrTa6L5oRAoA4AJ9vzhpSbUDoHPmyphaMS0vOkis+RgCfa82B
Uk2PnaF9cqyCQjJbbrf5bZ0=
=vpIh
-----END PGP SIGNATURE-----
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail