That's a really good point. Refencing my posts about a clients table, we could
also hardwire clientid 1 as the "internal client" and have only internal users
part of that client group. This makes me happier than a boolean column, which
I don't really like because we'd have to change every auth query to add "...
where users.system = 0" at the end.

But there's also the interaction with LDAP and the proposals for configurable
SQL authentication queries (see pam_mysql / nss_mysql as an example of this
idea) and how we're going to ensure that the internal user account is properly
represented by the authentication provider.

In any event, we need to come up with something good during the 2.1 series.
Clearly IC&S wants to get 2.0 out the door, and Ilja's solution to my hack
should work well enough despite the potential side effects like running a
per-user billing script and trying to send bill's to dbmail_internal -- which
might be a good thing, really. Just put IC&S' address in and hope that their
billing department doesn't pay close attention to invoices... :-P

Aaron


Thomas Mueller <[EMAIL PROTECTED]> said:

> Hi Aaron,
> 
> > Sure, that works. It's probably the easiest way to retrofit onto an
> > existing system, too. Should also work fine with LDAP, just as long
> > as we mention that an LDAP account needs to be created with this name.
> > Reserved numbers would have been an LDAP nightmare, now that I think
> > about it.
> > 
> > In the future we can have things like... 
> > 
> > #define DBMAIL_LOST_MAILBOX_USERNAME "[EMAIL PROTECTED]@__"
> > #define DBMAIL_LOST_MESSAGE_USERNAME "[EMAIL PROTECTED]@__"
> > 
> > And we'll only need to insert those accounts as the code is written.
> > 
> > Now, we just need make sure that these users cannot log in...
> 
> Ilja's idea of adding an additional boolean column if it is a system
> account would make everything much cleaner though.
> 
> External programs could select all non-system users much easier than
> with names (ignore all [EMAIL PROTECTED]@__ user?).
> 
> So I'd propose to keep the [EMAIL PROTECTED]@__ user but add
> an additional column too. What do you think?
> 
> MfG Thomas Mueller - http://www.tmueller.com for pgp key (95702B3B)
-- 

Reply via email to