On Freitag, 1. Juni 2007 Blake Mitchell wrote: > It always seemed to me that the dbmail_aliases table should have a > user_idnr column along with the deliver_to column. This way if > deliver_to was null, go to the user's inbox. This would allow > constraints to prevent dangling aliases on user delete, and aliases > to user_idnrs that don't exist. > > It would require a user for every alias, but there's no harm in > creating administrative users that don't actually receive mail.
We've extended the dbmail_aliases with a domain_idnr, and of course we have a zmi_domains table, where all local domains are defined. It has lots of advantages, and anyway we need it for billing. We do not have the billing part, ATM we concentrate on the web interface. user/alias administration is finished, and as we created a zmi_cronjobs table, we even did a vacation where users can define start/end dates, that's pretty nice and people love it already. mfg zmi -- // Michael Monnerie, Ing.BSc ----- http://it-management.at // Tel: 0676/846 914 666 .network.your.ideas. // PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import" // Fingerprint: EA39 8918 EDFF 0A68 ACFB 11B7 BA2D 060F 1C6F E6B0 // Keyserver: www.keyserver.net Key-ID: 1C6FE6B0
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
