On Fri, 19 Feb 1999, Paul Gregg wrote:
> In article <[EMAIL PROTECTED]> you wrote:
> > On Wed, 20 Jan 1999, Robert Adams wrote:
>
> >> user on the system. Anyone know of a way to get around this? Say, to tell
> >> qmail to drop all mail to something like /mail/u/s/username?
>
>
> I don't believe qmail can deliver to hashed spools like this by default.
>
> I've just written a delivery script to deliver to hashed spools because I
> needed it (gonna be *many* users).
>
> I nearly got it working with virtualdomains and users/assign with 26*26
> entries, but it ment that I needed a virtualhosts entry for every
> virtuall domain and each user was going to have one so it was not
> practical and thus I wrote my own script as ~alias/.qmail-default.
I think it can if you use the qmail-users mechanism
NAME
qmail-users - assign mail addresses to users
OVERVIEW
The file /var/qmail/users/assign assigns addresses to
users. For example,
=joe.shmoe:joe:503:78:/home/joe:::
says that mail for joe.shmoe should be delivered to user
joe, with uid 503 and gid 78, as specified by
/home/joe/.qmail.
Assignments fed to qmail-newu will be used by qmail-lspawn
to control qmail-local's deliveries. See qmail-newu(8).
A change to /var/qmail/users/assign will have no effect
until qmail-newu is run.
..snip...
=local:user:uid:gid:homedir:dash:ext:
Here local is an address; user, uid, and gid are the
account name, uid, and gid of the user in charge of local;
and messages to local will be controlled by home-
dir/.qmaildashext.
...snip...
so i would expect running the file though a little perl script which
replaces homedir with the hased spool directory will work (assuming the
user has permissions to their hashed spool directory.)
or have I missed the point of the question?
Richard
