Feargal Reilly wrote:
... it's then up to the end-user as to how they use it ...
Since the exact format and treatment of a 'gecos' field would be defined by the application, I think it's best to use the client_idnr field in the user table as a pointer to any application-specific data in another table or database. We use the client_idnr to tie a DBMail user to a virtual host account on our system, for example. (Although I think for 2.0 it would be a good idea to rename this field to 'userdata' or something else more generic; the time to do that is in a new major release number.)
But if there's an RFC or something that clearly defines how such data is to be used, then even if DBMail doesn't actually use it there should be no problem defining it in the tables.
-- Will Berry Co-founder, Second Brain website hosting http://www.secondbrainhosting.com/
