First, sorry that I didn't see that your build the directory before.
On Wed, 22 Oct 2003, Adrian Simmons wrote:
Adrian Simmons wrote:
[...]
On a hunch I changed the parent directory name, it was, with full path:
/Users/adrian/Library/Mail_Spool/backup
its now:
/Users/adrian/Library/Mailspool/backup
and *ta-da!* the error is gone, for 3 fetchmail collections at least.
I can imagine a scenario, when one time you be rooted by "su - root"
and other time by just "su". For this reason you got different
umask(1) in different sessions - when you build the new dir. Maybe
I guess (again) something that you have already checked but I try to
help. Maybe you invoke somewhere in the script something that change
the permission of the directory (it happened to me and I remember it
very very good...)
Also I remember similar question when one of the members had no exec
permissions on the directory. The permission for directory must be
read AND exec.
Bye,
Udi
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail