Upgrade/iRedAdmin-Pro/LDAP/1.1.x-1.2.0

From iRedMail

(Difference between revisions)
Jump to: navigation, search
(Update iRedMail to 0.6.0)
(Update iRedMail to 0.6.0)
 
(19 intermediate revisions not shown)
Line 1: Line 1:
__TOC__
__TOC__
-
iRedAdmin-Pro-1.2.0 is NOT RELEASED YET, DON'T APPLY THIS.
+
= We want to hear from you =
-
= TODO =
+
Please tell us what you expect in next release:  [http://www.iredmail.org/forum/topic997-wishlist-for-iredadminpro130.html Wishlist for iRedAdmin-Pro-1.3.0]
-
* Add 'enabledService: internal'
+
 
 +
Note: [http://www.iredmail.org/forum/topic1238-iredadminpro130-is-available-for-upgrading-and-purchasing.html iRedAdmin-Pro-1.3.0 released].
= Update iRedMail to 0.6.0 =
= Update iRedMail to 0.6.0 =
 +
 +
You have to update your exist iRedMail to 0.6.0, here is upgrade tutorial:
 +
* [[Upgrade/iRedMail/0.5.1-0.6.0|Upgrade iRedMail from 0.5.1 to 0.6.0]]
iRedAdmin-Pro-1.2.0 needs below features which implemented in iRedMail-0.6.0:
iRedAdmin-Pro-1.2.0 needs below features which implemented in iRedMail-0.6.0:
-
* [http://iredmail.googlecode.com/hg/tags/0.6.0/samples/iredmail.schema New LDAP scheme file for iRedMail]. We added some new LDAP attributes in this new schema file. If you don't want to upgrade iRedMail to 0.6.0, you can download it and replace the old one by copying it to '''/etc/openldap/schema/''' (RHEL/CentOS) or '''/etc/ldap/schema/''' (Debian/Ubuntu), restarting openldap service is required.
+
* [http://iredmail.org/wiki/index.php?title=Upgrade/iRedMail/0.5.1-0.6.0#Use_newest_schema_file New LDAP scheme file for iRedMail]. We added some new LDAP attributes in this new schema file.
-
* [http://www.iredmail.org/forum/topic839-whats-new-in-iredadminpro-catchall-address-management.html Catch-all account support]. If you don't want to upgrade iRedMail to 0.6.0 (not recommended), you can implement this feature yourself: [http://www.iredmail.org/wiki/index.php?title=Addition/OpenLDAP/Catch-all Setup Catch-all Email Accounts in iRedMail-0.5.1 and earlier versions]
+
** '''Note''': If you don't want to upgrade iRedMail to 0.6.0, you can download it and replace the old one by copying it to '''/etc/openldap/schema/''' (RHEL/CentOS) or '''/etc/ldap/schema/''' (Debian/Ubuntu), restarting openldap service is required.
 +
* [http://iredmail.org/wiki/index.php?title=Upgrade/iRedMail/0.5.1-0.6.0#Add_Catch-all_Email_Accounts_support Add catch-all account support].
 +
** '''Note''': If you don't want to upgrade iRedMail to 0.6.0 (not recommended), you can implement this feature yourself: [http://www.iredmail.org/wiki/index.php?title=Addition/OpenLDAP/Catch-all Setup Catch-all Email Accounts in iRedMail-0.5.1 and earlier versions]
 +
* [http://iredmail.org/wiki/index.php?title=Upgrade/iRedMail/0.5.1-0.6.0#Add_missing_MySQL_table:_postfixpolicyd.blacklist_dnsname_on_Debian.2FUbuntu Add missing MySQL table: postfixpolicyd.blacklist_dnsname on Debian/Ubuntu]
 +
** '''Note''': It will create a new table postfixpolicyd.blacklist_dnsname. Used to block emails sent from blacklist_dnsname in Policyd,
iRedAdmin-Pro-1.2.0 needs below features which implemented in iRedAPD-1.3.0:
iRedAdmin-Pro-1.2.0 needs below features which implemented in iRedAPD-1.3.0:
* [http://www.iredmail.org/forum/topic852-whats-new-in-iredadminpro-bypass-or-block-certain-domainsusers.html Bypass or block certain domains/users]
* [http://www.iredmail.org/forum/topic852-whats-new-in-iredadminpro-bypass-or-block-certain-domainsusers.html Bypass or block certain domains/users]
-
So we recommend you to update your exist iRedMail installation to 0.6.0:
+
= Enable Whitelisting in Policyd =
-
* [[Upgrade/iRedMail/0.5.1-0.6.0|Upgrade iRedMail from 0.5.1 to 0.6.0]]
+
 
 +
Set '''WHITELISTSENDER=1''' in your policyd config file:
 +
* On RHEL/CentOS, it's set in /etc/policyd.conf.
 +
* On Debian/Ubuntu, it's set in /etc/postfix-policyd.conf.
 +
* On FreeBSD, it's set in /usr/local/etc/postfix-policyd-sf.conf.
= Alter MySQL Database =
= Alter MySQL Database =
-
* Update SQL database to add new table: '''iredadmin.updatelog'''. This table is used to store iRedAdmin-Pro update log, so that you don't want to check new version every time you log in as domain global admin.
+
* Update SQL database to add new table: '''iredadmin.updatelog'''.
 +
** Note: This table is used to store iRedAdmin-Pro update log, so that you don't need to check new version every time you log in as domain global admin.
 +
* Empty session table to force re-login.
{{cmd|<pre>
{{cmd|<pre>
-
$ mysql -uroot -p iredadmin
+
$ mysql -uroot -p
-
mysql> SOURCE /path/to/iredadmin-pro-1.2.0/docs/upgrade_v1.1.x_v1.2.0/upgrade_110_120.sql;
+
mysql> USE iredadmin;
 +
mysql> SOURCE /path/to/iredadmin-pro-1.2.0/docs/upgrade/1.1.x-1.2.0/upgrade.sql;
mysql> quit;
mysql> quit;
</pre>}}
</pre>}}
Line 72: Line 87:
# cp /usr/share/apache2/iRedAdmin-Pro-1.1.0/tools/dump_disclaimer.py /usr/share/apache2/iredadmin/tools/
# cp /usr/share/apache2/iRedAdmin-Pro-1.1.0/tools/dump_disclaimer.py /usr/share/apache2/iredadmin/tools/
</pre>}}
</pre>}}
 +
 +
[[Category: iRedAdmin-Pro]]
 +
[[Category: Upgrade]]
 +
[[Category: LDAP]]

Current revision as of 04:34, 30 October 2010

Contents


We want to hear from you

Please tell us what you expect in next release: Wishlist for iRedAdmin-Pro-1.3.0

Note: iRedAdmin-Pro-1.3.0 released.

Update iRedMail to 0.6.0

You have to update your exist iRedMail to 0.6.0, here is upgrade tutorial:

iRedAdmin-Pro-1.2.0 needs below features which implemented in iRedMail-0.6.0:

iRedAdmin-Pro-1.2.0 needs below features which implemented in iRedAPD-1.3.0:

Enable Whitelisting in Policyd

Set WHITELISTSENDER=1 in your policyd config file:

  • On RHEL/CentOS, it's set in /etc/policyd.conf.
  • On Debian/Ubuntu, it's set in /etc/postfix-policyd.conf.
  • On FreeBSD, it's set in /usr/local/etc/postfix-policyd-sf.conf.

Alter MySQL Database

  • Update SQL database to add new table: iredadmin.updatelog.
    • Note: This table is used to store iRedAdmin-Pro update log, so that you don't need to check new version every time you log in as domain global admin.
  • Empty session table to force re-login.
Terminal:
$ mysql -uroot -p
mysql> USE iredadmin;
mysql> SOURCE /path/to/iredadmin-pro-1.2.0/docs/upgrade/1.1.x-1.2.0/upgrade.sql;
mysql> quit;

Enable new version

To active new version of iRedAdmin-Pro, we need to:

  • Uncompress iRedAdmin-Pro-1.2.0.tar.bz2
  • Copy it to correct directory
  • Replace old symbol link
  • Copy old config file
  • Restart Apache web server

Here we go:

  • For RHEL/CentOS users:
Terminal:
# tar xjf iRedAdmin-Pro-1.2.0.tar.bz2
# cp -rf iRedAdmin-Pro-1.2.0 /var/www/
# cd /var/www/
# rm iredadmin      # This is old symbol link.
# ln -s iRedAdmin-Pro-1.2.0 iredadmin
# cp iRedAdmin-Pro-1.1.0/settings.ini iredadmin/
# /etc/init.d/httpd restart
  • For Debian/Ubuntu users:
Terminal:
# tar xjf iRedAdmin-Pro-1.2.0.tar.bz2
# cp -rf iRedAdmin-Pro-1.2.0 /usr/share/apache2/
# cd /usr/share/apache2/
# rm iredadmin      # This is old symbol link.
# ln -s iRedAdmin-Pro-1.2.0 iredadmin
# cp iRedAdmin-Pro-1.1.0/settings.ini iredadmin/
# /etc/init.d/apache2 restart

Update other tools

If you are using dump_disclaimer.py file to dump disclaimer content from LDAP automaticly, you can simpliy copy old version to iRedAdmin-Pro-1.2.0/tools/ directory.

  • For RHEL/CentOS users:
Terminal:
# cp /var/www/iRedAdmin-Pro-1.1.0/tools/dump_disclaimer.py /var/www/iredadmin/tools/
  • For Debian/Ubuntu users:
Terminal:
# cp /usr/share/apache2/iRedAdmin-Pro-1.1.0/tools/dump_disclaimer.py /usr/share/apache2/iredadmin/tools/
Personal tools