Well, this isn't actually for me. I'm trying to create a workaround to allow
an upgrade to qmail 1.03 for a client who is currently using a heavily modded
qmail 1.01. (the person who made the modifications is gone, and the current
source doesn't compile. nice, huh?)
Basically, they don't want to store the .qmail files in the home directory,
they want to store them in a directory under the home directory.. So,
instead of /home/customer/.qmail-info, they want to do
/home/customer/customer/.qmail-info.. (And they have software that is
writing the .qmail files to /home/customer/customer instead of
/home/customer, and I don't have the source to those either.)
So it occured to me that they really didn't need a .qmail file for every
user, since the directory names they are delvering to are just $EXT. I
figured I could just deliver to /home/customer/$EXT/Maildir/.
So, any ideas how I can write a .qmail-default to deliver based on the info
in the .qmail files in /home/customer/customer/?
--Adam
On Wed, Apr 19, 2000 at 07:37:21AM +0200, Peter van Dijk wrote:
> On Wed, Apr 19, 2000 at 01:22:05AM -0400, Adam McKenna wrote:
> > in .qmail-default:
> >
> > /home/user/$EXT/Maildir/
>
> This is assuming this .qmail-default file is in user's homedir.
>
> I don't think qmail does variable expansion.
>
> I also think you are trusting information from outside users too much.
>
> Greetz, Peter.
> --
> Peter van Dijk - student/sysadmin/ircoper/madly in love/pretending coder
> |
> | 'C makes it easy to shoot yourself in the foot;
> | C++ makes it harder, but when you do it blows your whole leg off.'
> | Bjarne Stroustrup, Inventor of C++
>
