I'm going to look into it and set up a test account and get back, but my
preliminary tests indicate that the gid in the authentication db is being
ignored, although the delivery directory is being honored.  I have 

DEFAULTDELIVERY="| /usr/bin/maildrop"

set in /etc/courier/courierd, so it may be a maildrop issue.  Gotta run out
for a while, but I'll get back with something more definitive later.

I'm not sure where I can find the version information, but I believe I'm
running courier-0.42.2.  It's been a while since I've rebuilt it, and I have
a number of versions in my source directory.


Thus spake Sam Varshavchik on Thu, Jul 01, 2004 at 06:45:39PM CDT
> Lindsay Haisley writes:
> 
> >Outside of changing the spec'd gid of the mailman user in /etc/passwd, is
> >there any way to instruct courier to use an alternate gid when delivering
> >mail to a specific account?  I would think that the gid spec'd in the
> >authentication database should do this, but apparently it doesn't, even
> >though the proper delivery directory is pulled from this database.
> 
> It should.  The uid and gid of the local mail delivery process is set from 
> the authentication database.  There is no other place it could possibly 
> come from.
> 
> 



-- 
Lindsay Haisley       | "Everything works    |     PGP public key
FMP Computer Services |       if you let it" |      available at
512-259-1190          |    (The Roadie)      | <http://www.fmp.com/pubkeys>
http://www.fmp.com    |                      |


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to