Viktor, Thanks for the answers. I thing I have what I need for now; I'll give it a try in a but.
Thanks! On Sat, Apr 6, 2013, at 10:58 AM, Viktor Dukhovni wrote: > On Sat, Apr 06, 2013 at 10:53:54AM -0700, ixlo...@sent.at wrote: > > > > I am attaching a patch for "MacOSX", where a bare-metal "make > > > upgrade" with no main.cf fails, because Apple defines "postfix" as > > > a nickname for "_postfix" and "postdrop" as a nickname for "_postdrop", > > > so with default compile-time settings the Postfix installer aborts > > > because its uid appears to be shared. > > > > I'm building on Linux. Do I need to apply that patch to my source, even > > though it's for MacOSX? > > Oddly enough perhaps yes, since though the patch is mostly for > MacOSX, it provides additional compile-time tuning on other platforms. > > > What I get now is: > > > > make upgrade > > ... > > make: Nothing to be done for `update'. > > /bin/sh postfix-install -non-interactive > > postfix-install: Error: "postdrop" needs an entry in the group > > file. > > Remember, "postdrop" needs a dedicated group id. > > make: *** [upgrade] Error 1 > > Your system does not have a "postdrop" group. > > > Since the distro already installed its version of postfix -- both > > version and config are not what I want/need, so that's why I'm building > > my own -- there exist users/groups for postfix > > > > grep post /etc/group > > mail:x:12:postfix > > maildrop:!:59:postfix > > postfix:!:51: > > Well, "maildrop" is not "postdrop". > > > Is it the patch I need here, or do I still need to create a user/group > > above & beyond what the distro had previously installed? > > You can either create a "postdrop" group, or with the patch re-use the > existing "maildrop" group, which makes it easier to transition between > the system and your custom Postfix, since file permissions will be the > same. I recommend the latter: > > CCARGS='... -DDEF_SGID_GROUP=\"maildrop\"' > > -- > Viktor.
