----- Original Message -----
From: "Bill Shupp" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, September 03, 2001 10:52 PM
Subject: Re: finished vaddaliasdomain() patch
> on 9/3/01 3:32 PM, Einar Bordewich at
[EMAIL PROTECTED]
> spake:
>
> > I don't understand what you are saying here? Which user?
> >
> > [EMAIL PROTECTED] is an existing user, [EMAIL PROTECTED] is not. You will find
> > vuserinfo [EMAIL PROTECTED], but not vuserinfo [EMAIL PROTECTED]? Is this your
> > issue?
> >
> > If so, this is correct. [EMAIL PROTECTED] has never been a user under
vpopmail,
> > and in my opinion he should not be.
> >
> > If I'm on the wrong track here, please enlighten me.
>
> Nah, I see your point. It just seems simpler to me to be able to use
> vpopmail's tools on either user@realdomain or user@aliasdomain. If
> `vuserinfo user@aliasdomain` returns "no such user", that seems needlessly
> confusing, IMO. Call me lazy, but if one extra line in
> /var/qmail/users/assign will save me the time of looking up the real
domain
> in /var/qmail/control/virtualdomains, I'll take it. ; )
>
> I don't feel that strongly either way, though. I'll defer to whatever Ken
> thinks is the right design.
I'll of course accept Ken's decision.
Before he makes one, I like to look at it this way:
user@aliasdomain is not and never has been a valid user together with
users@realdomain's password. Why should tools like vmoduser and vuserinfo
hit on non existing users, when vchkpw does not?
Better of with writing a tool, or add an option to vuserinfo that these
aliasdomains covers this user also.
--
--------------------------------------------
IDG New Media Einar Bordewich
Development Manager Phone: +47 2336 1420
E-Mail: eibo(at)newmedia.no
Lat: 59.91144 N Lon: 10.76097 E
--------------------------------------------
