On Mon, 30 Nov 2009, patrick keshishian wrote:
> On Mon, Nov 30, 2009 at 4:29 PM, Philip Guenther <[email protected]>
> wrote:
...
> > (So that's another possible workaround: change the group of the spool
> > to something that no one is a member of.)
>
> I believe, that would cause security to complain about group ownership
> of the spool directory; which is the original reason OP started this
> thread.
Yes. On the other hand:
1) unlike the original problem, it's not actually a security issue, and
2) it can be fixed with one-line changes to
/etc/mtree/{4.4BSD.dist,special}
I get your point that altering the base to make a port happier when it's
not a good idea in its own right seems wrong. Thus my labeling it a
workaround and not a fix.
IMO, the Right Thing is to have the port excise a chunk of the logic in
procmail's screenmailbox() function. Simply changing GROUPW_UMASK seems
wrong, as procmail will continue to give the new mailbox the group of the
directory instead of behaving like mail.local by giving it the user's
default group.
Philip
