iredmail-doc/upgrade/upgrade.iredmail.0.8.7-0.9....

9.4 KiB

Upgrade iRedMail from 0.8.7 to 0.9.0

[TOC]

STILL WORKING IN PROGRESS, DO NOT APPLY IT.

ChangeLog

  • 2014-11-13: [All backends] Add index for SQL column msgs.spam_level in amavisd database.
  • 2014-11-06: [All backends] Fix improper SQL query command in domain transport query file.
  • 2014-09-09: [All backends] Fix incorrect setting to enable daily cron job to update SpamAssassin rules.
  • 2014-09-09: [All backends] Fix improper permission of Amavisd config file.
  • 2014-07-15: [All backends] Fix improper Postfix setting in both main.cf and master.cf.
  • 2014-06-19: [All backends] Add index for SQL column policy.policy_name in amavisd database.
  • 2014-06-07:
    • [OpenLDAP] Add new value for existing mail users: enabledService=indexer-worker.
    • [MySQL/PostgreSQL] New SQL column in vmail database: mailbox.enableindexer-worker.

General (All backends should apply these steps)

Update /etc/iredmail-release with iRedMail version number

iRedMail stores the release version in /etc/iredmail-release after installation, it's recommended to update this file after you upgraded iRedMail, so that you can know which version of iRedMail you're running. For example:

# File: /etc/iredmail-release
0.9.0

Upgrade Roundcube webmail to the latest stable release

Please follow Roundcube official tutorial to upgrade Roundcube webmail to the latest stable release immediately: How to upgrade Roundcube

Fix improper Postfix setting in both main.cf and master.cf

Currently, we don't have Postfix parameter receive_override_options= set in /etc/postfix/main.cf, instead, we have it in transport 127.0.0.1:10025 (Amavisd) like this:

# Part of file: /etc/postfix/master.cf

127.0.0.1:10025 inet n  -   -   -   -  smtpd
    ...
    -o receive_override_options=no_header_body_checks,no_unknown_recipient_checks,no_address_mappings

Without receive_override_options=no_address_mappings in main.cf:

  • Postfix will enable canonical address mapping, virtual alias map expansion, address masquerading, and automatic BCC (blind carbon-copy) recipients BEFORE injecting emails to content filter (Amavisd, in our case). For example, if you forward email to 3 email addresses, Postfix will expand the original recipient to 3 recipients, then Amavisd will get 3 emails for scanning. But with receive_override_options=no_address_mappings, Postfix won't expand original recipient to 3 addresses, and Amavisd gets only 1 email for scanning. It slightly improves mail server performance.

  • If a blacklisted sender (stored in Amavisd SQL database, not in Policyd/Cluebringer) sends email to user who forwards email to other addresses, Amavisd will quarantine the one sent to original recipient, but bypass emails sent to forwarded addresses.

Please apply below steps to fix above issues:

  • Add receive_override_options in Postfix with below shell command:
# postconf -e receive_override_options='no_address_mappings'
  • Open file /etc/postfix/master.cf (On Linux/OpenBSD) or /usr/local/etc/postfix/master.cf (on FreeBSD), find setting for transport 127.0.0.1:10025, remove no_address_mappings for its receive_override_options option:
# Part of file: /etc/postfix/master.cf

# ORIGINAL setting
#    -o receive_override_options=no_header_body_checks,no_unknown_recipient_checks,no_address_mappings

# MODIFIED setting
    -o receive_override_options=no_header_body_checks,no_unknown_recipient_checks
  • Restart Postfix service.

IMPORTANT NOTE: If you want to disable content_filter= in Postfix, please comment out receive_override_options= in Postfix config file main.cf too, otherwise canonical address mapping, virtual alias map expansion, address masquerading, and automatic BCC (blind carbon-copy) recipients will not work.

Fix improper file permission of Amavisd config file

NOTE: This step is applicable to only Red Hat/CentOS 6.

Amavisd config file /etc/amavisd/amavisd.conf must be owned by group amavis, otherwise after you upgraded to Red Hat/CentOS 7, Amavisd service cannot start.

# chgrp amavis /etc/amavisd/amavisd.conf

Fix incorrect setting to enable daily cron job to update SpamAssassin rules

NOTE: This step is applicable to only Debian and Ubuntu.

Please update file /etc/default/spamassassin to set CRON=1, so that SpamAssassin daily cron job will update SpamAssassin rules automatically.

# Part of file: /etc/default/spamassassin

CRON=1

OpenLDAP backend special

Fix improper LDAP query command in domain transport query file

Please open file /etc/postfix/ldap/transport_maps_domain.cf (on Linux/OpenBSD) or /usr/local/etc/postfix/ldap/transport_maps_domain.cf (on FreeBSD), add addition LDAP filter (!(domainBackupMX=yes)) in query = parameter:

# Part of file: /etc/postfix/ldap/transport_maps_domain.cf

# OLD setting
#query_filter    = (&(objectClass=mailDomain)(accountStatus=active)(enabledService=mail)(|(domainName=%s)(domainAliasName=%s)))

# NEW setting
query_filter    = (&(objectClass=mailDomain)(accountStatus=active)(enabledService=mail)(|(domainName=%s)(domainAliasName=%s))(!(domainBackupMX=yes)))

Restarting Postfix service is required.

Add new LDAP values for existing mail users

We will add new LDAP attribute/value pair for existing mail users: enabledService=indexer-worker. It's used by Dovecot.

  • Download below python script to adding new values for existing mail users.
# cd /root/
# wget https://bitbucket.org/zhb/iredmail/raw/default/extra/update/updateLDAPValues_087_to_090.py
  • Open downloaded file updateLDAPValues_087_to_090.py, set LDAP server related settings in this file. For example:
# Part of file: updateLDAPValues_087_to_090.py

uri = 'ldap://127.0.0.1:389'
basedn = 'o=domains,dc=example,dc=com'
bind_dn = 'cn=vmailadmin,dc=example,dc=com'
bind_pw = 'passwd'

You can find required LDAP credential in iRedAdmin config file or iRedMail.tips file under your iRedMail installation directory. Using either cn=Manager,dc=xx,dc=xx or cn=vmailadmin,dc=xx,dc=xx as bind dn is ok.

  • Execute this script, it will fix incorrect values and add correct ones:
# python updateLDAPValues_087_to_090.py

That's all.

Add index for SQL column in amavisd database

We need indexes for some SQL columns in amavisd database: policy.policy_name, msgs.spam_level. Both are used by iRedAdmin-Pro.

Now connect to SQL server as MySQL root user, create new columns, add required INDEX:

$ mysql -uroot -p
mysql> USE amavisd;
mysql> CREATE UNIQUE INDEX policy_idx_policy_name ON policy (policy_name);
mysql> CREATE INDEX msgs_idx_spam_level ON msgs (spam_level);

MySQL backend special

Fix improper SQL query command in domain transport query file

Please open file /etc/postfix/mysql/transport_maps_domain.cf (on Linux/OpenBSD) or /usr/local/etc/postfix/mysql/transport_maps_domain.cf (on FreeBSD), add addition SQL statement AND backupmx=0 in query = parameter:

# Part of file: /etc/postfix/mysql/transport_maps_domain.cf

# OLD setting
#query       = SELECT transport FROM domain WHERE domain='%s' AND active=1

# NEW setting
query       = SELECT transport FROM domain WHERE domain='%s' AND active=1 AND backupmx=0

Restarting Postfix service is required.

Add and remove SQL columns in vmail and amavisd databases

  • We need new SQL columns in vmail database: mailbox.enableindexer-worker, it's used by Dovecot.

  • We need new indexes for some 2 columns in amavisd database: policy.policy_name, msgs.spam_level. Both are used by iRedAdmin-Pro.

Now connect to SQL server as MySQL root user, create new columns, add required indexes:

$ mysql -uroot -p
mysql> USE vmail;
mysql> ALTER TABLE mailbox ADD COLUMN `enableindexer-worker` TINYINT(1) NOT NULL DEFAULT 1;
mysql> ALTER TABLE mailbox ADD INDEX (`enableindexer-worker`);

mysql> USE amavisd;
mysql> CREATE UNIQUE INDEX policy_idx_policy_name ON policy (policy_name);
mysql> CREATE INDEX msgs_idx_spam_level ON msgs (spam_level);

PostgreSQL backend special

Fix improper SQL query command in domain transport query file

Please open file /etc/postfix/pgsql/transport_maps_domain.cf (on Linux/OpenBSD) or /usr/local/etc/postfix/pgsql/transport_maps_domain.cf (on FreeBSD), add addition SQL statement AND backupmx=0 in query = parameter:

# Part of file: /etc/postfix/pgsql/transport_maps_domain.cf

# OLD setting
#query       = SELECT transport FROM domain WHERE domain='%s' AND active=1

# NEW setting
query       = SELECT transport FROM domain WHERE domain='%s' AND active=1 AND backupmx=0

Restarting Postfix service is required.

Add and remove SQL columns in vmail and amavisd databases

  • We need new SQL columns in vmail database: mailbox.enableindexer-worker, it's used by Dovecot.

  • We need new indexes for some 2 columns in amavisd database: policy.policy_name, msgs.spam_level. Both are used by iRedAdmin-Pro.

Now connect to SQL server as PostgreSQL admin user, create new columns, add required indexes:

# su - postgres
$ psql -d vmail
sql> ALTER TABLE mailbox ADD COLUMN enableindexer-worker INT2 NOT NULL DEFAULT 1;
sql> CREATE INDEX idx_mailbox_enableindexer_worker ON mailbox (enableindexer-worker);

sql> \c amavisd;
sql> CREATE UNIQUE INDEX policy_idx_policy_name ON policy (policy_name);
sql> CREATE INDEX msgs_idx_spam_level ON msgs (spam_level);