On Sun, Jun 24, 2007 at 01:48:23AM -0700, SM <[EMAIL PROTECTED]> wrote: > Hi Mike, > At 17:14 23-06-2007, Mike Markley wrote: > >Is there a Good Way to force ownership (both user and group) on a milter > >socket? I see that smfi_opensocket() honors umask, but that doesn't help > >with the GID, and dkim-filter doesn't seem to be picking up the primary > >GID of its -u argument: > > Try the attached patch. dkim-filter will pick the primary GID of its > -u argument with it.
Very nice! Thanks. My other question: chmod vs. umask? My primary concern with using umask to force the socket to be group-writable is that it (should) impact any other file the filter creates, including stats and debug files, but that sounds like a pretty low risk to me. Having never run a Milter under Postfix, I have no idea what best practice is (although I did note at least one vote in favor of chmod). Just seeking opinions and any pros or cons I may have missed. -- Mike Markley <[EMAIL PROTECTED]> Is truth not truth for all? - Natira, "For the World is Hollow and I have Touched the Sky", stardate 5476.4. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ dkim-milter-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss
