Re: [qmailtoaster] vpopmail --disable-many-domains opti

2011-05-29 Thread Carlos Herrera Polo
vpopmail with one table for domain is not easy when I have to
integrate with jabber (openfire) auth / mysql.


2011/5/29, Martin Waschbüsch IT-Dienstleistungen :
> Hi Jake,
>
> Am 28.05.2011 um 17:19 schrieb Jake Vickers:
>>
>> So I'm still curious as to what you think the benefits are. Segregating
>> your data into multiple tables was always the way I learned to obtain
>> performance. The nature of the requests from QMT are probably not those
>> that would require any performance tuning - the only one I've ever run
>> into is the default number of connections.  So I'm willing to table that
>> point if there are other mitigating factors.
>>
>> So what are the advantages/benefits you are thinking will be gained from a
>> single table?
>
>
> I agree with Eric that it probably will not make much of a difference with
> regards to performance.
> However, a lot of applications that might want to have access to the email
> user database are not all that flexible and do not support having different
> domains in different tables.
> E.g. using courier-auth with mysql or SOGo with mysql-backend, etc. There
> are other examples.
> For my own use, I have written an accounting backend that also cycles
> through domains and users, etc. to produce detail-information to be attached
> to invoices and that, too, is just way easier when having all in one table.
>
> Granted, that may be simplistic design on the parts of those programs, but
> hey, it works and it is way easier to recompile vpopmail to achieve
> compatibility than patch those programs.
> Also, whenever there is any database schema change in order for vpopmail to
> be upgraded, it is much easier to upgrade that one table than to find all
> the tables that hold domains and path those.
>
> Last but not least, mysql (and other databases) have length-limitations for
> domain names. I always wondered, but never tried, what would happen if I
> added a domain with a name longer than 'max-table-name-length' to the
> database?
> I think the current limit for mysql is 32 chars and domain names can be
> longer.
>
> Best,
>
> Martin
>
> --
> Martin Waschbüsch
> IT-Dienstleistungen
> Lautensackstr. 16
> 80687 München
>
> Telefon: +49 89 57005708
> Fax: +49 89 57868023
> Mobil: +49 170 2189794
> serv...@waschbuesch.it
> http://www.waschbuesch.it
> -
> Qmailtoaster is sponsored by Vickers Consulting Group
> (www.vickersconsulting.com)
> Vickers Consulting Group offers Qmailtoaster support and installations.
>   If you need professional help with your setup, contact them today!
> -
>  Please visit qmailtoaster.com for the latest news, updates, and
> packages.
>
>   To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
>  For additional commands, e-mail:
> qmailtoaster-list-h...@qmailtoaster.com
>
>
>

-- 
Enviado desde mi dispositivo móvil

-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
  If you need professional help with your setup, contact them today!
-
 Please visit qmailtoaster.com for the latest news, updates, and packages.

  To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
 For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com




Re: [qmailtoaster] vpopmail --disable-many-domains option

2011-05-29 Thread Martin Waschbüsch IT-Dienstleistungen
Hi Jake,

Am 28.05.2011 um 17:19 schrieb Jake Vickers:
> 
> So I'm still curious as to what you think the benefits are. Segregating your 
> data into multiple tables was always the way I learned to obtain performance. 
> The nature of the requests from QMT are probably not those that would require 
> any performance tuning - the only one I've ever run into is the default 
> number of connections.  So I'm willing to table that point if there are other 
> mitigating factors.
> 
> So what are the advantages/benefits you are thinking will be gained from a 
> single table?


I agree with Eric that it probably will not make much of a difference with 
regards to performance.
However, a lot of applications that might want to have access to the email user 
database are not all that flexible and do not support having different domains 
in different tables.
E.g. using courier-auth with mysql or SOGo with mysql-backend, etc. There are 
other examples.
For my own use, I have written an accounting backend that also cycles through 
domains and users, etc. to produce detail-information to be attached to 
invoices and that, too, is just way easier when having all in one table.

Granted, that may be simplistic design on the parts of those programs, but hey, 
it works and it is way easier to recompile vpopmail to achieve compatibility 
than patch those programs.
Also, whenever there is any database schema change in order for vpopmail to be 
upgraded, it is much easier to upgrade that one table than to find all the 
tables that hold domains and path those.

Last but not least, mysql (and other databases) have length-limitations for 
domain names. I always wondered, but never tried, what would happen if I added 
a domain with a name longer than 'max-table-name-length' to the database?
I think the current limit for mysql is 32 chars and domain names can be longer.

Best,

Martin

--
Martin Waschbüsch
IT-Dienstleistungen
Lautensackstr. 16
80687 München

Telefon: +49 89 57005708
Fax: +49 89 57868023
Mobil: +49 170 2189794
serv...@waschbuesch.it
http://www.waschbuesch.it
-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
  If you need professional help with your setup, contact them today!
-
 Please visit qmailtoaster.com for the latest news, updates, and packages.

  To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
 For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com