On Tue, 2009-01-27 at 12:05 -0800, Tim Traver wrote: > Timo or anyone, > > any insight into this???
Not really. There is currently no parameter to set home directory, maybe
v1.3's config rewrite could help in future.
> I really just want to tell dovecot's deliver where the home directory is
> without having to fork another process to do it.
>
> I may be able to create a shell script that set the env variable and
> then launched deliver, but that's another fork that I'd rather not have,
> and since I already know the home dir when I set up the .qmail-user
> file, I'd rather just set it...
A shell script doesn't have to fork deliver, just exec it.
> help...
>
> Tim.
>
>
>
> Tim Traver wrote:
> > Hi all,
> >
> > ok, after looking at all of the posts that I've found, and trying
> > numerous settings, I am a little stumped as to how to set up the deliver
> > program with qmail to get everything correct.
> >
> > Ultimately, I really don't want to do a lookup of the home dir if I
> > don't have to. I'd rather specify the stuff in the .qmail-user file for
> > that particular user to avoid the extra step.
> >
> > In looking in the wiki, it says for users without a lookup to use
> >
> > HOME=/path/to/user/homedir deliver -f $FROM_ENVELOPE
> >
> > but I can't do that in the .qmail file, which would normally look something
> > like this :
> >
> >
> > |/var/qmail/bin/preline -f /usr/local/libexec/dovecot/deliver -f
> > ${SENDER:-<>}
> >
> > I would rather not do the master authentication socket as described for
> > obvious reasons.
> >
> > is there a format in the .qmail file that I can use with deliver to achieve
> > what I want???
> >
> > Thanks,
> >
> > Tim.
> >
> >
> >
> >
> >
signature.asc
Description: This is a digitally signed message part
