I put all of this in the front-end management system. The dbmail tables
are part of that as are the powerdns tables and virtual webserver
information.
Curtis
--
Curtis Maurand
mailto:[EMAIL PROTECTED]
http://www.maurand.com
On Thu, 13 May 2004, Feargal Reilly wrote:
On Thu, 13 May 2004 09:49:18 +0200
Ilja Booij <[EMAIL PROTECTED]> wrote:
I don't know if this should be a part of DBMail itself. I can see it how
it would be useful, but I don't think it should be a part of dbmail proper.
Actually, when you consider dbmail is replacing the need for system users, some
sort of GECOS information should be there for those who are in the custom of
using it. All that would really be required from your end would be a single
text column called gecos added to the user table.
The format of GECOS (GCOS) fields vary from system to system, the only
agreement seems to be that it's a comma seperated list, and the name is the
first element in that list. Thus it probably wouldn't be worthwhile devoting
another table to it
If others then want to come up with dbmail specific versions of finger and
suchlike, then at least the schema is there.
With regard to tracking the relationship between users, it is a good solution
to the problem of sending over-quota mails to over-quota users.
Like you I'm not convinced as to whether it belongs in dbmail itself, but if it
did, the cleanest solution would be a single 'class' field in the user table.
However, I'm divided over whether it should be there by default, when dbmail
itself doesn't use it. I guess it's the same debate about caching the message
headers to make life easier for web clients.
-fr.
Ilja
Jacques Beaudoin wrote:
Hi all
Some time i wish i could have some fields in dbmail
where i could input users specific data like
- is supervisor or secretary email address
- location
- etc
I run a script 3 time a week to analyse my users mail quotas
so if there over quota i send them a "over quota email".
I'm sending a "over quota email" to a user thats not reading is email !!!!!
So also sending the "over quota email" to is supervisor mite be a option.
My question is ?
Could a "user description table" with 4 or 5 fields
be useful in a future release of dbmail.
Bien ? vous
Jacques Beaudoin
Agent d'administration
Les services des technologies
de l'information et des communications
Commission scolaire de la Pointe de l'?le
Montr?al, Qu?bec, Canada
_______________________________________________
Dbmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
_______________________________________________
Dbmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
--
Feargal Reilly,
Codeshifter,
Chrysalink Systems.