Perhaps someone knows if this is a bug that has been fixed in newer
procmail (I have 2.92pre4) or something wrong here at my host.
I run procmail from my personal directory (not superuser). To make a
long story short, when the .procmailrc has done its thing, and the
remaining mail goes into the default mailbox, which is
/var/spool/mail/ , the mailbox is chgrp'd to *my* GID (user) instead
of "mail". The perms on those spools are 664, so anyone in
my group could read or write to my mailbox. I took the .forward out,
and sent myself mail. The GID/perms are now OK again since it is the
system not procmail, that is delivering the mail. When procmail
delivers, the GID goes back to 'public'.
Is there a way around this? Is this fixed in later versions?
Are you _sure_ you mean 664? That would include readable by world.
I'm guessing you mean 660.
The quick fix is to simply place "UMASK=077" at the top of your .procmailrc.
On the otherhand, if you originally configured procmail on a BSDish OS,
and it's now running under a sysVish version (e.g., SunOS 4.x -> Solaris 2.x)
then you should reconfigure and recompile, if just to avoid the cost and
bugginess of compatibility libraries. However, if you "make recommend"
you may find that it suggests that you install setgid "mail". If you
can't do that (or can't convince your sysadmin to install it for real),
then you should just go with the UMASK setting.
Philip Guenther
----------------------------------------------------------------
Philip Guenther UNIX Systems and Network Administrator
Internet: guenther(_at_)gac(_dot_)edu Phonenet: (507) 933-7596
Gustavus Adolphus College St. Peter, MN 56082-1498
I am _not_ a representative sample of the Gustavus Community. Yeah, right...
Source code never lies (it just misleads). (Programming by Purloined Letter?)