On Sun, 2006-12-17 at 18:06 +0100, Michael Monnerie wrote:
> On Sonntag, 17. Dezember 2006 00:42 Michael Monnerie wrote:
> > Advantage:
> 
> Seems nobody wants to discuss this here.

Patience, patience. Nobody's in a rush to overhaul the way we resolve
deliveries. Even if it's only a couple hours of coding, it's tens or
hundreds of hours of thinking it through.

> If the extra "dbmail_domains" table would be included, there's another 
> simplification that would be nice:
> 
> - in dbmail_users.userid you only need to store the user name without 
> domain extension
> - dbmail could automatically append all possible alias domains for that 
> user
> - that would need another field "domain_idnr" or so, because one client 
> (customer) could have several domains like this:
> domA
> domB (alias of domA)
> domC
> domD (alias of domC)
> with my current model, you can't know from a user if he should be in 
> domA+B or domC+D, because only the client_idnr exists
> 
> The advantage:
> - store only userpart of login (e.g. user1, user2, user3)
> - auto-append alias and root domains ([EMAIL PROTECTED], [EMAIL PROTECTED], 
> etc)
> - so the user can login as both domains, without any difference
> - the difference is just for logging purposes, e.g. user1 has a PC and a 
> Notebook. The admin sets as username on the PC [EMAIL PROTECTED], and on the 
> Notebook [EMAIL PROTECTED], to easily find out which PC/notebook connected 
> when

I generally like this idea, a lot, and I like how it can leverage
client_id to separate users with the same names in different domains.
Unless we added another few flags or abstractions, though, it would
require that users have unique names within an *organization* even if
that org had many different *domains*. Something to think about.

> One other feature request: I'd like to have more stats.
> - For every hour a user logs in via imap/pop, log number of queries and 
> bytes transferred. Like this, you can find your heavy users, which is 
> good for optimizing the database (balance over multiple servers)

Some of this data could be collected as the daemons run and reported via
the /var/run/dbmail-<foo>.state file.

> - How many e-mails and bytes per hour does a user receive

You could mine this data with appropriate queries.

Aaron

_______________________________________________
DBmail mailing list
DBmail@dbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail

Reply via email to