1 (edited by Rashef 2009-11-02 22:58:06)

Topic: Doubts about 0.5.0 > 0.5.1 upgrade...

Section "MySQL backend only."/"Use proxymap to improve performance and reliability under high load."
Why does virtual_alias_maps become virtual_alias_domains in your example?

Section "MySQL backend only."/"Add more columns."
Who/what does manage the new settings? Should I eventually change these options through phpMyAdmin?

Thx

2

Re: Doubts about 0.5.0 > 0.5.1 upgrade...

Rashef wrote:

Why does virtual_alias_maps become virtual_alias_domains in your example?

It's an typo error. Fixed moment ago. Thanks for your report. smile

Rashef wrote:

Section "MySQL backend only."/"Add more columns."
Who/what does manage the new settings? Should I eventually change these options through phpMyAdmin?

Oops, forget to explain why we need these columns. I will improve this section tomorrow.

Just a quick explain:

  • enableimapsecured, enablepop3secured, enablemanagesievesecured (in vmail.mailbox table) are used to restrict per-user POP3, IMAP and managesieve services over TLS/SSL. Used in Dovecot.

  • defaultuserquota (in vmail.domain table) are used to store default user quota size. Will be used in iRedAdmin - yes, iRedAdmin will support MySQL backend in the future.

  • minpasswordlength, maxpasswordlength (in vmail.domain table) are used to store default minimal and maximum password length while create new users. Will be used in iRedAdmin.

Am i miss something? Please let me know. smile

3

Re: Doubts about 0.5.0 > 0.5.1 upgrade...

ZhangHuangbin wrote:

yes, iRedAdmin will support MySQL backend in the future.

This is the greatest news you could give me! wink

4

Re: Doubts about 0.5.0 > 0.5.1 upgrade...

hi, Rashef.

I already fixed upgrade tutorial. Thanks for your help. smile
http://www.iredmail.org/upgrade_050_051.html