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)
