On Wed, Aug 30, 2006 at 08:34:03PM +0200, Micha Lenk wrote:
> >Ah, there's the catch - the -d option. It makes maildrop switch to the
> >specified user's home directory. The user isn't actually specified, but I'm
> >assuming that since Exim sets $USER to the value of $local_part, this makes
> >maildrop deliver to the user the mail is being delivered to.
> >
> >However, I'm not actually sure that the maildrop process is executed *as*
> >the said user, but instead it runs as the Exim user ("Debian-exim"), but
> >writes files under the specified user. (This default is documented under
> >"Generic options for transports" in the exim4 info manual.)
>
> I verified your statements about Exim4 and I can confirm that the target
> program of pipe deliveries is executed as the (implicit, if
> check_local_user is used) specified user and that environment variables
> like USER are set accordingly.
That's not actually "confirming", you know :) One of Greg's original mails
states that the router calling the transport has check_local_user, so
the execution happens as the user (rather than as Debian-exim), and that's
all right.
Except that it's still unclear what the original problem could have been
*shrug*
The only remaining difference that I can think of is that the -d option is
doing something screwy with those 30% users that makes them work properly
under courier-maildrop, and that it is failing to do that with normal
maildrop. Greg? Are all your users alike, or are some configured with
something extra in relation to Courier or other authentication databases?
--
2. That which causes joy or happiness.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
