Yodel! You know, the bts has a Version: header ;-)
I guess you're using the sarge version? The bug probably still persists, but postgrey now uses its own group instead of 'nogroup'. I'm not entirely sure how I can easily fix this bug (while avoiding hacking postgrey code, that is) without having postgrey running as group postfix (this would be a possibility, but I'm not thrilled at using some other package's group and having to create it myself just in case postfix won't - and then having to care about how postfix creates its group wrt homedir etc.) I'm thinking about having postgrey use sockets by default in post etch timeframe anyway, so I'll have to fix this sooner or later. For now, I guess you already found out that you can start postfix with --group=postfix? cheers -- vbi -- The content of this message may or may not reflect the opinion of me, my employer, my girlfriend, my cat or anybody else, regardless of the fact whether such an employer, girlfriend, cat, or anybody else exists. I (or my employer, girlfriend, cat or whoever) disclaim any legal obligations resulting from the above message. You, as the reader of this message, may or may not have the permission to redistribute this message as a whole or in parts, verbatim or in modified form, or to distribute any message at all.
pgp79hC3f75YQ.pgp
Description: PGP signature
