iRedMail - User contributions [en]

IRedMail/FAQ/Enable.Greylist.Opt.In

ZhangHuangbin — Sun, 19 May 2013 02:25:13 GMT

ZhangHuangbin:

__TOC__

----
NOTE: This tutorial is applicable to Policyd-1.8, not Cluebringer (a.k.a. Policyd v2). If you're running Cluebringer, please login to https://your_server/cluebringer/ instead.
----

== Enable greylist opt in and opt out in Policyd ==

Some people are fairly irate when it comes to mail and
refuse wanting to have any type of delay. this feature
enables each and every person the ability to not subject
themselves to greylisting. this feature is also VERY
usefull when you dont want to subject EVERY person to
greylisting at once but instead allows you to enable
it in batches/groups of users so you get a feel on the
type of complaints or praise from your users.

Please update Policyd setting '''OPTINOUT''' to 1 to enable greylist opt in / opt out:
* On RHEL/CentOS/Scientific Linux, it's set in file '''/etc/policyd.conf'''.
* On Debian/Ubuntu, it's set in file '''/etc/postfix-policyd.conf'''.
* On openSUSE, it's set in file '''/etc/policyd.conf'''.
* On FreeBSD, it's set in file '''/usr/local/etc/postfix-policyd-sf.conf'''.
{{cfg|policyd.conf|<pre>
OPTINOUT=1
OPTINOUTALL=1
</pre>}}

Restarting Policyd service is required to make it work.

Notes:
* iRedAdmin-Pro customers can manage greylist opt-in with one lick with the latest iRedAdmin-Pro releases, in domain profile page or user profile page, under tab '''Advanced'''.
* For more details about how to set greylist opt-in manually with MySQL command line or phpMyAdmin, please refer to Policyd official document: http://policyd.sourceforge.net/readme.html (Section "Greylist Opt-in / Opt-out")

Upgrade/iRedMail/0.8.4-0.8.5

ZhangHuangbin — Fri, 17 May 2013 05:17:35 GMT

ZhangHuangbin: /* ChangeLog */

__TOC__

= ChangeLog =
* 2013-05-17: [ldap] Support assigning mail list/alias as member of another mailing list.
* 2013-05-12: [all backends] Fix incorrect Amavisd SQL column name: policy.unchecked_lovers_maps (incorrect one) -> policy.unchecked_lover.
* 2013-04-26: [ldap] Fix incorrect ACL for attribute "memberOfGroup".
* 2013-04-03: [ldap] Use the latest iRedMail LDAP schema file.
* 2013-04-03: [MySQL/PostgreSQL] Add one new column used for store preferred language for newly created mail users

= General (All backends should apply these steps) =
No upgrade available yet.

= OpenLDAP backend special =
== Use the latest LDAP schema file provided by iRedMail ==
With the latest LDAP schema file, we can:
* use attribute '''preferredLanguage''' for mail domain object, it's used to storage short language code (e.g. de_DE, en_US) for newly created mail users.
* Assign mail list/alias as member of another mailing list.

Steps to use the latest LDAP schema file are:

* Download the newest iRedMail ldap schema file
* Copy old ldap schema file as a backup copy
* Replace the old one
* Restart OpenLDAP service.

Here we go:

* On RHEL/CentOS/Scientific Linux (both release 5.x and 6.x), openSUSE, Gentoo, OpenBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/openldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/openldap/schema/
# /etc/init.d/slapd restart # <-- Or: /etc/init.d/ldap restart
</pre>}}

* On Debian/Ubuntu:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/ldap/schema/
# /etc/init.d/slapd restart
</pre>}}

* On FreeBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /usr/local/etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /usr/local/etc/openldap/schema/
# /etc/init.d/slapd restart
</pre>}}

== Fix incorrect ACL for attribute "memberOfGroup" ==
Permission for attribute '''memberOfGroup''' is not set correctly, it causes normal user can add himself to any mail list in LDAP. Default permission is writeable by self, it should be "read" by "self" instead.

* Open OpenLDAP config file '''slapd.conf''', find below lines:
** On RHEL/CentOS, openSUSE, Gentoo, OpenBSD, it's '''/etc/openldap/slapd.conf'''.
** On Debian/Ubuntu, it's '''/etc/ldap/slapd.conf'''.
** On FreeBSD, it's '''/usr/local/etc/openldap/slapd.conf'''.
{{cfg|slapd.conf|<pre>
# User attrs.
access to attrs="employeeNumber, ..."
</pre>}}

* Prepend attribute name "memberOfGroup" before "employeeNumber". The final result looks like below:
{{cfg|slapd.conf|<pre>
# User attrs.
access to attrs="memberOfGroup, employeeNumber, ..."
</pre>}}

* Save the config file, then restart OpenLDAP service to make it use new ACL.
** On RHEL/CentOS 5, openSUSE, please restart it with command <pre># /etc/init.d/ldap restart</pre>
** On RHEL/CentOS 6 and other Linux distribution, please restart it with command: <pre># /etc/init.d/slapd restart</pre>
** On FreeBSD, please restart it with command: <pre># /usr/local/etc/rc.d/slapd restart</pre>
** On OpenBSD, please restart it with command: <pre># /etc/rc.d/slapd restart</pre>

== Support assigning mail list/alias as member of another mailing list ==
* Open Postfix ldap lookup file '''/etc/postfix/ldap/virtual_group_maps.cf''', update the value of '''query_filter''' parameter to add addition LDAP objectclasses:
** On FreeBSD, it's '''/usr/local/etc/postfix/ldap/virtual_group_maps.cf'''.
{{cfg|/etc/postfix/ldap/virtual_group_maps.cf|<pre>
# OLD SETTING
#query_filter = (&(accountStatus=active)(enabledService=mail)(enabledService=deliver)(|(memberOfGroup=%s)(shadowAddress=%s))(|(objectClass=mailUser)(objectClass=mailExternalUser)))

# NEW SETTING
query_filter = (&(accountStatus=active)(enabledService=mail)(enabledService=deliver)(|(memberOfGroup=%s)(shadowAddress=%s))(|(objectClass=mailUser)(objectClass=mailExternalUser)(objectClass=mailList)(objectClass=mailAlias)))
</pre>}}

* Restart Postfix service to use our new setting.
** On Linux: {{cmd|<pre># /etc/init.d/postfix restart</pre>}}
** On FreeBSD: {{cmd|<pre># /usr/local/etc/rc.d/postfix restart</pre>}}
** On OpenBSD: {{cmd|<pre># /etc/rc.d/postfix restart</pre>}}

== Fix incorrect SQL column name in Amavisd database ==

Amavisd-new-2.7.1 fixes a SQL column name "policy.unchecked_lover", previously incorrectly specified as "policy.unchecked_lovers_maps";

Please login to MySQL server as root user, execute SQL commands to fix incorrect column name:
{{cmd|<pre>
# mysql -uroot -p
mysql> USE amavisd;
mysql> ALTER TABLE policy CHANGE unchecked_lovers_maps unchecked_lover CHAR(1) DEFAULT NULL;
</pre>}}

= MySQL backend special =
== Add one new column used for store preferred language for newly created mail users ==
We now storage short language code (e.g. de_DE, en_US) for newly created mail users, it requires a new SQL column '''defaultlanguage''' for this.

Please login to MySQL server as root user, execute SQL commands to add required columns and indexes.
{{cmd|<pre>
# mysql -uroot -p
mysql> USE vmail;
mysql> ALTER TABLE domain ADD COLUMN defaultlanguage VARCHAR(5) NOT NULL DEFAULT 'en_US';
</pre>}}
== Fix incorrect SQL column name in Amavisd database ==

Amavisd-new-2.7.1 fixes a SQL column name "policy.unchecked_lover", previously incorrectly specified as "policy.unchecked_lovers_maps";

Please login to MySQL server as root user, execute SQL commands to fix incorrect column name:
{{cmd|<pre>
# mysql -uroot -p
mysql> USE amavisd;
mysql> ALTER TABLE policy CHANGE unchecked_lovers_maps unchecked_lover CHAR(1) DEFAULT NULL;
</pre>}}
= PostgreSQL backend special =
== Add one new column used for store preferred language for newly created mail users ==

We now storage short language code (e.g. de_DE, en_US) for newly created mail users, it requires a new SQL column '''defaultlanguage''' for this.

Please switch to PostgreSQL daemon user, then execute SQL commands to add required columns and indexes:
* On Linux, PostgreSQL daemon user is postgres.
* On FreeBSD, PostgreSQL daemon user is pgsql.
* On OpenBSD, PostgreSQL daemon user is """_postgresql".
{{cmd|<pre>
# su - postgres
$ psql -d vmail
sql> ALTER TABLE domain ADD COLUMN defaultlanguage VARCHAR(5) NOT NULL DEFAULT 'en_US';
</pre>}}
== Fix incorrect SQL column name in Amavisd database ==

Amavisd-new-2.7.1 fixes a SQL column name "policy.unchecked_lover", previously incorrectly specified as "policy.unchecked_lovers_maps";

Please switch to PostgreSQL daemon user, then execute SQL commands to fix incorrect column name:
* On Linux, PostgreSQL daemon user is postgres.
* On FreeBSD, PostgreSQL daemon user is pgsql.
* On OpenBSD, PostgreSQL daemon user is """_postgresql".
{{cmd|<pre>
# su - postgres
$ psql -d amavisd
sql> ALTER TABLE policy RENAME unchecked_lovers_maps TO unchecked_lover;
</pre>}}

Upgrade/iRedMail/0.8.4-0.8.5

ZhangHuangbin — Fri, 17 May 2013 05:14:01 GMT

ZhangHuangbin: /* Fix incorrect ACL for attribute "memberOfGroup" */

__TOC__

= ChangeLog =
* 2013-05-12: [all backends] Fix incorrect Amavisd SQL column name: policy.unchecked_lovers_maps (incorrect one) -> policy.unchecked_lover.
* 2013-04-26: [ldap] Fix incorrect ACL for attribute "memberOfGroup".
* 2013-04-03: [ldap] Use the latest iRedMail LDAP schema file.
* 2013-04-03: [MySQL/PostgreSQL] Add one new column used for store preferred language for newly created mail users

= General (All backends should apply these steps) =
No upgrade available yet.

= OpenLDAP backend special =
== Use the latest LDAP schema file provided by iRedMail ==
With the latest LDAP schema file, we can:
* use attribute '''preferredLanguage''' for mail domain object, it's used to storage short language code (e.g. de_DE, en_US) for newly created mail users.
* Assign mail list/alias as member of another mailing list.

Steps to use the latest LDAP schema file are:

* Download the newest iRedMail ldap schema file
* Copy old ldap schema file as a backup copy
* Replace the old one
* Restart OpenLDAP service.

Here we go:

* On RHEL/CentOS/Scientific Linux (both release 5.x and 6.x), openSUSE, Gentoo, OpenBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/openldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/openldap/schema/
# /etc/init.d/slapd restart # <-- Or: /etc/init.d/ldap restart
</pre>}}

* On Debian/Ubuntu:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/ldap/schema/
# /etc/init.d/slapd restart
</pre>}}

* On FreeBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /usr/local/etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /usr/local/etc/openldap/schema/
# /etc/init.d/slapd restart
</pre>}}

== Fix incorrect ACL for attribute "memberOfGroup" ==
Permission for attribute '''memberOfGroup''' is not set correctly, it causes normal user can add himself to any mail list in LDAP. Default permission is writeable by self, it should be "read" by "self" instead.

* Open OpenLDAP config file '''slapd.conf''', find below lines:
** On RHEL/CentOS, openSUSE, Gentoo, OpenBSD, it's '''/etc/openldap/slapd.conf'''.
** On Debian/Ubuntu, it's '''/etc/ldap/slapd.conf'''.
** On FreeBSD, it's '''/usr/local/etc/openldap/slapd.conf'''.
{{cfg|slapd.conf|<pre>
# User attrs.
access to attrs="employeeNumber, ..."
</pre>}}

* Prepend attribute name "memberOfGroup" before "employeeNumber". The final result looks like below:
{{cfg|slapd.conf|<pre>
# User attrs.
access to attrs="memberOfGroup, employeeNumber, ..."
</pre>}}

* Save the config file, then restart OpenLDAP service to make it use new ACL.
** On RHEL/CentOS 5, openSUSE, please restart it with command <pre># /etc/init.d/ldap restart</pre>
** On RHEL/CentOS 6 and other Linux distribution, please restart it with command: <pre># /etc/init.d/slapd restart</pre>
** On FreeBSD, please restart it with command: <pre># /usr/local/etc/rc.d/slapd restart</pre>
** On OpenBSD, please restart it with command: <pre># /etc/rc.d/slapd restart</pre>

== Support assigning mail list/alias as member of another mailing list ==
* Open Postfix ldap lookup file '''/etc/postfix/ldap/virtual_group_maps.cf''', update the value of '''query_filter''' parameter to add addition LDAP objectclasses:
** On FreeBSD, it's '''/usr/local/etc/postfix/ldap/virtual_group_maps.cf'''.
{{cfg|/etc/postfix/ldap/virtual_group_maps.cf|<pre>
# OLD SETTING
#query_filter = (&(accountStatus=active)(enabledService=mail)(enabledService=deliver)(|(memberOfGroup=%s)(shadowAddress=%s))(|(objectClass=mailUser)(objectClass=mailExternalUser)))

# NEW SETTING
query_filter = (&(accountStatus=active)(enabledService=mail)(enabledService=deliver)(|(memberOfGroup=%s)(shadowAddress=%s))(|(objectClass=mailUser)(objectClass=mailExternalUser)(objectClass=mailList)(objectClass=mailAlias)))
</pre>}}

* Restart Postfix service to use our new setting.
** On Linux: {{cmd|<pre># /etc/init.d/postfix restart</pre>}}
** On FreeBSD: {{cmd|<pre># /usr/local/etc/rc.d/postfix restart</pre>}}
** On OpenBSD: {{cmd|<pre># /etc/rc.d/postfix restart</pre>}}

== Fix incorrect SQL column name in Amavisd database ==

Amavisd-new-2.7.1 fixes a SQL column name "policy.unchecked_lover", previously incorrectly specified as "policy.unchecked_lovers_maps";

Please login to MySQL server as root user, execute SQL commands to fix incorrect column name:
{{cmd|<pre>
# mysql -uroot -p
mysql> USE amavisd;
mysql> ALTER TABLE policy CHANGE unchecked_lovers_maps unchecked_lover CHAR(1) DEFAULT NULL;
</pre>}}

= MySQL backend special =
== Add one new column used for store preferred language for newly created mail users ==
We now storage short language code (e.g. de_DE, en_US) for newly created mail users, it requires a new SQL column '''defaultlanguage''' for this.

Please login to MySQL server as root user, execute SQL commands to add required columns and indexes.
{{cmd|<pre>
# mysql -uroot -p
mysql> USE vmail;
mysql> ALTER TABLE domain ADD COLUMN defaultlanguage VARCHAR(5) NOT NULL DEFAULT 'en_US';
</pre>}}
== Fix incorrect SQL column name in Amavisd database ==

Amavisd-new-2.7.1 fixes a SQL column name "policy.unchecked_lover", previously incorrectly specified as "policy.unchecked_lovers_maps";

Please login to MySQL server as root user, execute SQL commands to fix incorrect column name:
{{cmd|<pre>
# mysql -uroot -p
mysql> USE amavisd;
mysql> ALTER TABLE policy CHANGE unchecked_lovers_maps unchecked_lover CHAR(1) DEFAULT NULL;
</pre>}}
= PostgreSQL backend special =
== Add one new column used for store preferred language for newly created mail users ==

We now storage short language code (e.g. de_DE, en_US) for newly created mail users, it requires a new SQL column '''defaultlanguage''' for this.

Please switch to PostgreSQL daemon user, then execute SQL commands to add required columns and indexes:
* On Linux, PostgreSQL daemon user is postgres.
* On FreeBSD, PostgreSQL daemon user is pgsql.
* On OpenBSD, PostgreSQL daemon user is """_postgresql".
{{cmd|<pre>
# su - postgres
$ psql -d vmail
sql> ALTER TABLE domain ADD COLUMN defaultlanguage VARCHAR(5) NOT NULL DEFAULT 'en_US';
</pre>}}
== Fix incorrect SQL column name in Amavisd database ==

Amavisd-new-2.7.1 fixes a SQL column name "policy.unchecked_lover", previously incorrectly specified as "policy.unchecked_lovers_maps";

Please switch to PostgreSQL daemon user, then execute SQL commands to fix incorrect column name:
* On Linux, PostgreSQL daemon user is postgres.
* On FreeBSD, PostgreSQL daemon user is pgsql.
* On OpenBSD, PostgreSQL daemon user is """_postgresql".
{{cmd|<pre>
# su - postgres
$ psql -d amavisd
sql> ALTER TABLE policy RENAME unchecked_lovers_maps TO unchecked_lover;
</pre>}}

Upgrade/iRedMail/0.8.4-0.8.5

ZhangHuangbin — Fri, 17 May 2013 05:09:14 GMT

ZhangHuangbin: /* Use the latest LDAP schema file provided by iRedMail */

__TOC__

= ChangeLog =
* 2013-05-12: [all backends] Fix incorrect Amavisd SQL column name: policy.unchecked_lovers_maps (incorrect one) -> policy.unchecked_lover.
* 2013-04-26: [ldap] Fix incorrect ACL for attribute "memberOfGroup".
* 2013-04-03: [ldap] Use the latest iRedMail LDAP schema file.
* 2013-04-03: [MySQL/PostgreSQL] Add one new column used for store preferred language for newly created mail users

= General (All backends should apply these steps) =
No upgrade available yet.

= OpenLDAP backend special =
== Use the latest LDAP schema file provided by iRedMail ==
With the latest LDAP schema file, we can:
* use attribute '''preferredLanguage''' for mail domain object, it's used to storage short language code (e.g. de_DE, en_US) for newly created mail users.
* Assign mail list/alias as member of another mailing list.

Steps to use the latest LDAP schema file are:

* Download the newest iRedMail ldap schema file
* Copy old ldap schema file as a backup copy
* Replace the old one
* Restart OpenLDAP service.

Here we go:

* On RHEL/CentOS/Scientific Linux (both release 5.x and 6.x), openSUSE, Gentoo, OpenBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/openldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/openldap/schema/
# /etc/init.d/slapd restart # <-- Or: /etc/init.d/ldap restart
</pre>}}

* On Debian/Ubuntu:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/ldap/schema/
# /etc/init.d/slapd restart
</pre>}}

* On FreeBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /usr/local/etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /usr/local/etc/openldap/schema/
# /etc/init.d/slapd restart
</pre>}}

== Fix incorrect ACL for attribute "memberOfGroup" ==
Permission for attribute '''memberOfGroup''' is not set correctly, it causes normal user can add himself to any mail list in LDAP. Default permission is writeable by self, it should be "read" by "self" instead.

* Open OpenLDAP config file '''slapd.conf''', find below lines:
** On RHEL/CentOS, openSUSE, Gentoo, OpenBSD, it's '''/etc/openldap/slapd.conf'''.
** On Debian/Ubuntu, it's '''/etc/ldap/slapd.conf'''.
** On FreeBSD, it's '''/usr/local/etc/openldap/slapd.conf'''.
{{cfg|slapd.conf|<pre>
# User attrs.
access to attrs="employeeNumber, ..."
</pre>}}

* Prepend attribute name "memberOfGroup" before "employeeNumber". The final result looks like below:
{{cfg|slapd.conf|<pre>
# User attrs.
access to attrs="memberOfGroup, employeeNumber, ..."
</pre>}}

* Save the config file, then restart OpenLDAP service to make it use new ACL.
** On RHEL/CentOS 5, openSUSE, please restart it with command <pre># /etc/init.d/ldap restart</pre>
** On RHEL/CentOS 6 and other Linux distribution, please restart it with command: <pre># /etc/init.d/slapd restart</pre>
** On FreeBSD, please restart it with command: <pre># /usr/local/etc/rc.d/slapd restart</pre>
** On OpenBSD, please restart it with command: <pre># /etc/rc.d/slapd restart</pre>

== Fix incorrect SQL column name in Amavisd database ==

Amavisd-new-2.7.1 fixes a SQL column name "policy.unchecked_lover", previously incorrectly specified as "policy.unchecked_lovers_maps";

Please login to MySQL server as root user, execute SQL commands to fix incorrect column name:
{{cmd|<pre>
# mysql -uroot -p
mysql> USE amavisd;
mysql> ALTER TABLE policy CHANGE unchecked_lovers_maps unchecked_lover CHAR(1) DEFAULT NULL;
</pre>}}

= MySQL backend special =
== Add one new column used for store preferred language for newly created mail users ==
We now storage short language code (e.g. de_DE, en_US) for newly created mail users, it requires a new SQL column '''defaultlanguage''' for this.

Please login to MySQL server as root user, execute SQL commands to add required columns and indexes.
{{cmd|<pre>
# mysql -uroot -p
mysql> USE vmail;
mysql> ALTER TABLE domain ADD COLUMN defaultlanguage VARCHAR(5) NOT NULL DEFAULT 'en_US';
</pre>}}
== Fix incorrect SQL column name in Amavisd database ==

Amavisd-new-2.7.1 fixes a SQL column name "policy.unchecked_lover", previously incorrectly specified as "policy.unchecked_lovers_maps";

Please login to MySQL server as root user, execute SQL commands to fix incorrect column name:
{{cmd|<pre>
# mysql -uroot -p
mysql> USE amavisd;
mysql> ALTER TABLE policy CHANGE unchecked_lovers_maps unchecked_lover CHAR(1) DEFAULT NULL;
</pre>}}
= PostgreSQL backend special =
== Add one new column used for store preferred language for newly created mail users ==

We now storage short language code (e.g. de_DE, en_US) for newly created mail users, it requires a new SQL column '''defaultlanguage''' for this.

Please switch to PostgreSQL daemon user, then execute SQL commands to add required columns and indexes:
* On Linux, PostgreSQL daemon user is postgres.
* On FreeBSD, PostgreSQL daemon user is pgsql.
* On OpenBSD, PostgreSQL daemon user is """_postgresql".
{{cmd|<pre>
# su - postgres
$ psql -d vmail
sql> ALTER TABLE domain ADD COLUMN defaultlanguage VARCHAR(5) NOT NULL DEFAULT 'en_US';
</pre>}}
== Fix incorrect SQL column name in Amavisd database ==

Amavisd-new-2.7.1 fixes a SQL column name "policy.unchecked_lover", previously incorrectly specified as "policy.unchecked_lovers_maps";

Please switch to PostgreSQL daemon user, then execute SQL commands to fix incorrect column name:
* On Linux, PostgreSQL daemon user is postgres.
* On FreeBSD, PostgreSQL daemon user is pgsql.
* On OpenBSD, PostgreSQL daemon user is """_postgresql".
{{cmd|<pre>
# su - postgres
$ psql -d amavisd
sql> ALTER TABLE policy RENAME unchecked_lovers_maps TO unchecked_lover;
</pre>}}

Upgrade/iRedMail/0.8.4-0.8.5

ZhangHuangbin — Sun, 12 May 2013 13:50:59 GMT

ZhangHuangbin:

__TOC__

= ChangeLog =
* 2013-05-12: [all backends] Fix incorrect Amavisd SQL column name: policy.unchecked_lovers_maps (incorrect one) -> policy.unchecked_lover.
* 2013-04-26: [ldap] Fix incorrect ACL for attribute "memberOfGroup".
* 2013-04-03: [ldap] Use the latest iRedMail LDAP schema file.
* 2013-04-03: [MySQL/PostgreSQL] Add one new column used for store preferred language for newly created mail users

= General (All backends should apply these steps) =
No upgrade available yet.

= OpenLDAP backend special =
== Use the latest LDAP schema file provided by iRedMail ==
With the latest LDAP schema file, we can use attribute '''preferredLanguage''' for mail domain object, it's used to storage short language code (e.g. de_DE, en_US) for newly created mail users. Steps to use the latest LDAP schema file are:

* Download the newest iRedMail ldap schema file
* Copy old ldap schema file as a backup copy
* Replace the old one
* Restart OpenLDAP service.

Here we go:

* On RHEL/CentOS/Scientific Linux (both release 5.x and 6.x), openSUSE, Gentoo, OpenBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/openldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/openldap/schema/
# /etc/init.d/slapd restart # <-- Or: /etc/init.d/ldap restart
</pre>}}

* On Debian/Ubuntu:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/ldap/schema/
# /etc/init.d/slapd restart
</pre>}}

* On FreeBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /usr/local/etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /usr/local/etc/openldap/schema/
# /etc/init.d/slapd restart
</pre>}}

== Fix incorrect ACL for attribute "memberOfGroup" ==
Permission for attribute '''memberOfGroup''' is not set correctly, it causes normal user can add himself to any mail list in LDAP. Default permission is writeable by self, it should be "read" by "self" instead.

* Open OpenLDAP config file '''slapd.conf''', find below lines:
** On RHEL/CentOS, openSUSE, Gentoo, OpenBSD, it's '''/etc/openldap/slapd.conf'''.
** On Debian/Ubuntu, it's '''/etc/ldap/slapd.conf'''.
** On FreeBSD, it's '''/usr/local/etc/openldap/slapd.conf'''.
{{cfg|slapd.conf|<pre>
# User attrs.
access to attrs="employeeNumber, ..."
</pre>}}

* Prepend attribute name "memberOfGroup" before "employeeNumber". The final result looks like below:
{{cfg|slapd.conf|<pre>
# User attrs.
access to attrs="memberOfGroup, employeeNumber, ..."
</pre>}}

* Save the config file, then restart OpenLDAP service to make it use new ACL.
** On RHEL/CentOS 5, openSUSE, please restart it with command <pre># /etc/init.d/ldap restart</pre>
** On RHEL/CentOS 6 and other Linux distribution, please restart it with command: <pre># /etc/init.d/slapd restart</pre>
** On FreeBSD, please restart it with command: <pre># /usr/local/etc/rc.d/slapd restart</pre>
** On OpenBSD, please restart it with command: <pre># /etc/rc.d/slapd restart</pre>

== Fix incorrect SQL column name in Amavisd database ==

Amavisd-new-2.7.1 fixes a SQL column name "policy.unchecked_lover", previously incorrectly specified as "policy.unchecked_lovers_maps";

Please login to MySQL server as root user, execute SQL commands to fix incorrect column name:
{{cmd|<pre>
# mysql -uroot -p
mysql> USE amavisd;
mysql> ALTER TABLE policy CHANGE unchecked_lovers_maps unchecked_lover CHAR(1) DEFAULT NULL;
</pre>}}

= MySQL backend special =
== Add one new column used for store preferred language for newly created mail users ==
We now storage short language code (e.g. de_DE, en_US) for newly created mail users, it requires a new SQL column '''defaultlanguage''' for this.

Please login to MySQL server as root user, execute SQL commands to add required columns and indexes.
{{cmd|<pre>
# mysql -uroot -p
mysql> USE vmail;
mysql> ALTER TABLE domain ADD COLUMN defaultlanguage VARCHAR(5) NOT NULL DEFAULT 'en_US';
</pre>}}
== Fix incorrect SQL column name in Amavisd database ==

Amavisd-new-2.7.1 fixes a SQL column name "policy.unchecked_lover", previously incorrectly specified as "policy.unchecked_lovers_maps";

Please login to MySQL server as root user, execute SQL commands to fix incorrect column name:
{{cmd|<pre>
# mysql -uroot -p
mysql> USE amavisd;
mysql> ALTER TABLE policy CHANGE unchecked_lovers_maps unchecked_lover CHAR(1) DEFAULT NULL;
</pre>}}
= PostgreSQL backend special =
== Add one new column used for store preferred language for newly created mail users ==

We now storage short language code (e.g. de_DE, en_US) for newly created mail users, it requires a new SQL column '''defaultlanguage''' for this.

Please switch to PostgreSQL daemon user, then execute SQL commands to add required columns and indexes:
* On Linux, PostgreSQL daemon user is postgres.
* On FreeBSD, PostgreSQL daemon user is pgsql.
* On OpenBSD, PostgreSQL daemon user is """_postgresql".
{{cmd|<pre>
# su - postgres
$ psql -d vmail
sql> ALTER TABLE domain ADD COLUMN defaultlanguage VARCHAR(5) NOT NULL DEFAULT 'en_US';
</pre>}}
== Fix incorrect SQL column name in Amavisd database ==

Amavisd-new-2.7.1 fixes a SQL column name "policy.unchecked_lover", previously incorrectly specified as "policy.unchecked_lovers_maps";

Please switch to PostgreSQL daemon user, then execute SQL commands to fix incorrect column name:
* On Linux, PostgreSQL daemon user is postgres.
* On FreeBSD, PostgreSQL daemon user is pgsql.
* On OpenBSD, PostgreSQL daemon user is """_postgresql".
{{cmd|<pre>
# su - postgres
$ psql -d amavisd
sql> ALTER TABLE policy RENAME unchecked_lovers_maps TO unchecked_lover;
</pre>}}

Upgrade/iRedMail/0.8.4-0.8.5

ZhangHuangbin — Sun, 12 May 2013 13:47:42 GMT

ZhangHuangbin: /* Fix incorrect SQL column name in Amavisd database */

__TOC__

= ChangeLog =
* 2013-05-12: [all backends] Fix incorrect Amavisd SQL column name: policy.unchecked_lovers_maps (incorrect one) -> policy.unchecked_lover.
* 2013-04-26: [ldap] Fix incorrect ACL for attribute "memberOfGroup".
* 2013-04-03: [ldap] Use the latest iRedMail LDAP schema file.
* 2013-04-03: [MySQL/PostgreSQL] Add one new column used for store preferred language for newly created mail users

= General (All backends should apply these steps) =
No upgrade available yet.

= OpenLDAP backend special =
== Use the latest LDAP schema file provided by iRedMail ==
With the latest LDAP schema file, we can use attribute '''preferredLanguage''' for mail domain object, it's used to storage short language code (e.g. de_DE, en_US) for newly created mail users. Steps to use the latest LDAP schema file are:

* Download the newest iRedMail ldap schema file
* Copy old ldap schema file as a backup copy
* Replace the old one
* Restart OpenLDAP service.

Here we go:

* On RHEL/CentOS/Scientific Linux (both release 5.x and 6.x), openSUSE, Gentoo, OpenBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/openldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/openldap/schema/
# /etc/init.d/slapd restart # <-- Or: /etc/init.d/ldap restart
</pre>}}

* On Debian/Ubuntu:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/ldap/schema/
# /etc/init.d/slapd restart
</pre>}}

* On FreeBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /usr/local/etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /usr/local/etc/openldap/schema/
# /etc/init.d/slapd restart
</pre>}}

== Fix incorrect ACL for attribute "memberOfGroup" ==
Permission for attribute '''memberOfGroup''' is not set correctly, it causes normal user can add himself to any mail list in LDAP. Default permission is writeable by self, it should be "read" by "self" instead.

* Open OpenLDAP config file '''slapd.conf''', find below lines:
** On RHEL/CentOS, openSUSE, Gentoo, OpenBSD, it's '''/etc/openldap/slapd.conf'''.
** On Debian/Ubuntu, it's '''/etc/ldap/slapd.conf'''.
** On FreeBSD, it's '''/usr/local/etc/openldap/slapd.conf'''.
{{cfg|slapd.conf|<pre>
# User attrs.
access to attrs="employeeNumber, ..."
</pre>}}

* Prepend attribute name "memberOfGroup" before "employeeNumber". The final result looks like below:
{{cfg|slapd.conf|<pre>
# User attrs.
access to attrs="memberOfGroup, employeeNumber, ..."
</pre>}}

* Save the config file, then restart OpenLDAP service to make it use new ACL.
** On RHEL/CentOS 5, openSUSE, please restart it with command <pre># /etc/init.d/ldap restart</pre>
** On RHEL/CentOS 6 and other Linux distribution, please restart it with command: <pre># /etc/init.d/slapd restart</pre>
** On FreeBSD, please restart it with command: <pre># /usr/local/etc/rc.d/slapd restart</pre>
** On OpenBSD, please restart it with command: <pre># /etc/rc.d/slapd restart</pre>

== Fix incorrect SQL column name in Amavisd database ==

Amavisd-new-2.7.1 fixes a SQL column name "policy.unchecked_lover", previously incorrectly specified as "policy.unchecked_lovers_maps";

Please login to MySQL server as root user, execute SQL commands to fix incorrect column name:
{{cmd|<pre>
# mysql -uroot -p
mysql> USE amavisd;
mysql> ALTER TABLE policy CHANGE unchecked_lovers_maps unchecked_lover CHAR(1) DEFAULT NULL;
</pre>

= MySQL backend special =
== Add one new column used for store preferred language for newly created mail users ==
We now storage short language code (e.g. de_DE, en_US) for newly created mail users, it requires a new SQL column '''defaultlanguage''' for this.

Please login to MySQL server as root user, execute SQL commands to add required columns and indexes.
{{cmd|<pre>
# mysql -uroot -p
mysql> USE vmail;
mysql> ALTER TABLE domain ADD COLUMN defaultlanguage VARCHAR(5) NOT NULL DEFAULT 'en_US';
</pre>}}
== Fix incorrect SQL column name in Amavisd database ==

Amavisd-new-2.7.1 fixes a SQL column name "policy.unchecked_lover", previously incorrectly specified as "policy.unchecked_lovers_maps";

Please login to MySQL server as root user, execute SQL commands to fix incorrect column name:
{{cmd|<pre>
# mysql -uroot -p
mysql> USE amavisd;
mysql> ALTER TABLE policy CHANGE unchecked_lovers_maps unchecked_lover CHAR(1) DEFAULT NULL;
</pre>
= PostgreSQL backend special =
== Add one new column used for store preferred language for newly created mail users ==

We now storage short language code (e.g. de_DE, en_US) for newly created mail users, it requires a new SQL column '''defaultlanguage''' for this.

Please switch to PostgreSQL daemon user, then execute SQL commands to add required columns and indexes:
* On Linux, PostgreSQL daemon user is postgres.
* On FreeBSD, PostgreSQL daemon user is pgsql.
* On OpenBSD, PostgreSQL daemon user is """_postgresql".
{{cmd|<pre>
# su - postgres
$ psql -d vmail
sql> ALTER TABLE domain ADD COLUMN defaultlanguage VARCHAR(5) NOT NULL DEFAULT 'en_US';
</pre>}}
== Fix incorrect SQL column name in Amavisd database ==

Amavisd-new-2.7.1 fixes a SQL column name "policy.unchecked_lover", previously incorrectly specified as "policy.unchecked_lovers_maps";

Please switch to PostgreSQL daemon user, then execute SQL commands to fix incorrect column name:
* On Linux, PostgreSQL daemon user is postgres.
* On FreeBSD, PostgreSQL daemon user is pgsql.
* On OpenBSD, PostgreSQL daemon user is """_postgresql".
{{cmd|<pre>
# su - postgres
$ psql -d amavisd
sql> ALTER TABLE policy RENAME unchecked_lovers_maps TO unchecked_lover;
</pre>}}

Upgrade/iRedMail/0.8.4-0.8.5

ZhangHuangbin — Sun, 12 May 2013 13:45:20 GMT

ZhangHuangbin:

__TOC__

= ChangeLog =
* 2013-05-12: [all backends] Fix incorrect Amavisd SQL column name: policy.unchecked_lovers_maps (incorrect one) -> policy.unchecked_lover.
* 2013-04-26: [ldap] Fix incorrect ACL for attribute "memberOfGroup".
* 2013-04-03: [ldap] Use the latest iRedMail LDAP schema file.
* 2013-04-03: [MySQL/PostgreSQL] Add one new column used for store preferred language for newly created mail users

= General (All backends should apply these steps) =
No upgrade available yet.

= OpenLDAP backend special =
== Use the latest LDAP schema file provided by iRedMail ==
With the latest LDAP schema file, we can use attribute '''preferredLanguage''' for mail domain object, it's used to storage short language code (e.g. de_DE, en_US) for newly created mail users. Steps to use the latest LDAP schema file are:

* Download the newest iRedMail ldap schema file
* Copy old ldap schema file as a backup copy
* Replace the old one
* Restart OpenLDAP service.

Here we go:

* On RHEL/CentOS/Scientific Linux (both release 5.x and 6.x), openSUSE, Gentoo, OpenBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/openldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/openldap/schema/
# /etc/init.d/slapd restart # <-- Or: /etc/init.d/ldap restart
</pre>}}

* On Debian/Ubuntu:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/ldap/schema/
# /etc/init.d/slapd restart
</pre>}}

* On FreeBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /usr/local/etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /usr/local/etc/openldap/schema/
# /etc/init.d/slapd restart
</pre>}}

== Fix incorrect ACL for attribute "memberOfGroup" ==
Permission for attribute '''memberOfGroup''' is not set correctly, it causes normal user can add himself to any mail list in LDAP. Default permission is writeable by self, it should be "read" by "self" instead.

* Open OpenLDAP config file '''slapd.conf''', find below lines:
** On RHEL/CentOS, openSUSE, Gentoo, OpenBSD, it's '''/etc/openldap/slapd.conf'''.
** On Debian/Ubuntu, it's '''/etc/ldap/slapd.conf'''.
** On FreeBSD, it's '''/usr/local/etc/openldap/slapd.conf'''.
{{cfg|slapd.conf|<pre>
# User attrs.
access to attrs="employeeNumber, ..."
</pre>}}

* Prepend attribute name "memberOfGroup" before "employeeNumber". The final result looks like below:
{{cfg|slapd.conf|<pre>
# User attrs.
access to attrs="memberOfGroup, employeeNumber, ..."
</pre>}}

* Save the config file, then restart OpenLDAP service to make it use new ACL.
** On RHEL/CentOS 5, openSUSE, please restart it with command <pre># /etc/init.d/ldap restart</pre>
** On RHEL/CentOS 6 and other Linux distribution, please restart it with command: <pre># /etc/init.d/slapd restart</pre>
** On FreeBSD, please restart it with command: <pre># /usr/local/etc/rc.d/slapd restart</pre>
** On OpenBSD, please restart it with command: <pre># /etc/rc.d/slapd restart</pre>

== Fix incorrect SQL column name in Amavisd database ==

Amavisd-new-2.7.1 fixes a SQL column name "policy.unchecked_lover", previously incorrectly specified as "policy.unchecked_lovers_maps";

Please login to MySQL server as root user, execute SQL commands to fix incorrect column name:
{{cmd|<pre>
# mysql -uroot -p
mysql> USE amavisd;
mysql> ALTER TABLE policy CHANGE unchecked_lovers_maps unchecked_lover CHAR(1) DEFAULT NULL;
</pre>

= MySQL backend special =
== Add one new column used for store preferred language for newly created mail users ==
We now storage short language code (e.g. de_DE, en_US) for newly created mail users, it requires a new SQL column '''defaultlanguage''' for this.

Please login to MySQL server as root user, execute SQL commands to add required columns and indexes.
{{cmd|<pre>
# mysql -uroot -p
mysql> USE vmail;
mysql> ALTER TABLE domain ADD COLUMN defaultlanguage VARCHAR(5) NOT NULL DEFAULT 'en_US';
</pre>}}
== Fix incorrect SQL column name in Amavisd database ==

Amavisd-new-2.7.1 fixes a SQL column name "policy.unchecked_lover", previously incorrectly specified as "policy.unchecked_lovers_maps";

Please login to MySQL server as root user, execute SQL commands to fix incorrect column name:
{{cmd|<pre>
# mysql -uroot -p
mysql> USE amavisd;
mysql> ALTER TABLE policy CHANGE unchecked_lovers_maps unchecked_lover CHAR(1) DEFAULT NULL;
</pre>
= PostgreSQL backend special =
== Add one new column used for store preferred language for newly created mail users ==

We now storage short language code (e.g. de_DE, en_US) for newly created mail users, it requires a new SQL column '''defaultlanguage''' for this.

Please switch to PostgreSQL daemon user, then execute SQL commands to add required columns and indexes:
* On Linux, PostgreSQL daemon user is postgres.
* On FreeBSD, PostgreSQL daemon user is pgsql.
* On OpenBSD, PostgreSQL daemon user is """_postgresql".
{{cmd|<pre>
# su - postgres
$ psql -d vmail
sql> ALTER TABLE domain ADD COLUMN defaultlanguage VARCHAR(5) NOT NULL DEFAULT 'en_US';
</pre>}}
== Fix incorrect SQL column name in Amavisd database ==

Amavisd-new-2.7.1 fixes a SQL column name "policy.unchecked_lover", previously incorrectly specified as "policy.unchecked_lovers_maps";

Please switch to PostgreSQL daemon user, then execute SQL commands to fix incorrect column name:
* On Linux, PostgreSQL daemon user is postgres.
* On FreeBSD, PostgreSQL daemon user is pgsql.
* On OpenBSD, PostgreSQL daemon user is """_postgresql".
{{cmd|<pre>
# su - postgres
$ psql -d amavisd
sql> ALTER TABLE domain RENAME unchecked_lovers_maps TO unchecked_lover;
</pre>}}

IRedMail/FAQ/Completely.Disable.Amavisd.ClamAV.SpamAssassin

ZhangHuangbin — Sat, 11 May 2013 13:10:45 GMT

ZhangHuangbin: /* Stop virus/spam scanning, keep DKIM signing/verification and Disclaimer */

__TOC__

In iRedMail, Amavisd provides below features:

* content-based spam scanning (invoke SpamAssassin)
* Virus scanning (invoke ClamAV)
* DKIM singing
* DKIM verification (through SpamAssassin + Perl module)
* SPF verification (through SpamAssassin + Perl module)
* Disclaimer (throught AlterMIME)

= Stop virus/spam scanning, keep DKIM signing/verification and Disclaimer =

If you want to disable virus and spam scanning, but keep DKIM signing and disclaimer, please try this:

* Keep "content_filter =" setting in Postfix main.cf.
{{cfg|main.cf|<pre>
content_filter = smtp-amavis:[127.0.0.1]:10024
</pre>}}

* Find below lines in /etc/amavisd/amavisd.conf:

{{cfg|amavisd.conf|<pre>
# @bypass_virus_checks_maps = (1); # controls running of anti-virus code
# @bypass_spam_checks_maps = (1); # controls running of anti-spam code
</pre>}}

Uncomment above lines (removing "# " at the beginning of each line), and restart Amavisd service.

= Completely disable all features =

If you want to completely disable spam and virus scanning services, steps:

# Comment out 'content_filter = smtp-amavis:[127.0.0.1]:10024' in Postfix config file main.cf, and restart Postfix service.
# Disable network services: Amavisd, ClamAV.

Notes:

* ClamAV and SpamAssassin will be invoked by Amavisd, so if you disable Amavisd, those two are disabled too.
* SpamAssassin doesn't have daemon service running in iRedMail solution, so there's no need to stop SpamAssassin service.

[[Category: FAQ]]
[[Category: iRedMail/FAQ]]

IRedMail/FAQ/Upgrade.iRedAPD

ZhangHuangbin — Tue, 07 May 2013 12:28:58 GMT

ZhangHuangbin:

----
This tutorial describes how to upgrade iRedAPD to the latest stable release, iRedAPD-1.4.0. It's applicable on all Linux/BSD distributions supported by iRedMail.

Important notes:
* Since iRedAPD-1.4.0, we use Python source file as config file, not '.ini' format anymore.
* We don't need second instance, '''iredapd-rr''', anymore.
----

* Download the latest stable release here: http://iredmail.org/yum/misc/ For example, iRedAPD-1.4.0.tar.bz2.
* Upload it to your iRedMail server. Assume it's '''/root/iRedAPD-1.4.0.tar.bz2''' on the server.
* Extract downloaded package and move to /opt/.
{{cmd|<pre>
# tar xjf /root/iRedAPD-1.4.0.tar.bz2 -C /opt/
</pre>}}
You get a new directory: /opt/iRedAPD-1.4.0/.

* Set correct owner and permission:
{{cmd|<pre>
# chown -R iredapd:iredapd /opt/iRedAPD-1.4.0
# chmod -R 0700 /opt/iRedAPD-1.4.0
</pre>}}

* Generate new config file from sample file, and set correct file owner and permission.
{{cmd|<pre>
# cd /opt/iRedAPD-1.4.0/
# cp settings.py.sample settings.py
# chown -R iredapd:iredapd settings.py
# chmod -R 0600 settings.py
</pre>}}
WARNING: Config file '''/opt/iredapd/settings.py''' contains sensitive infomation (username, password), please don't make it world-readable. Permission 0600 is the best.

* Please open '''/opt/iredapd/settings.py''', and sync settings with old iRedAPD config file '''/opt/iRedAPD-[OLD-VERSION]/etc/iredapd.ini'''.
** In old version of iRedAPD, all parameters under "[ldap]" section are now new parameters start with '''ldap_'''.
** In old version of iRedAPD, all parameters under "[sql]" (or "[mysql]") section are now new parameters start with '''sql_'''.

* Remove symbol link of old release:
{{cmd|<pre>
# rm -i /opt/iredapd # <- Don't not end with '/'.
</pre>}}

* Create symbol link to the latest release:
{{cmd|<pre>
# cd /opt/
# ln -s iRedAPD-1.4.0 iredapd
</pre>}}
* Copy new RC script for your server. We have scripts for different Linux/BSD distributions. Please copy the proper one for your server. For example:
** /opt/iredapd/rc_scripts/iredapd.debian: For Debian and Ubuntu.
** /opt/iredapd/rc_scripts/iredapd.freebsd: For FreeBSD. Please copy to /usr/local/etc/rc.d/.
** /opt/iredapd/rc_scripts/iredapd.gentoo: For Gentoo Linux.
** /opt/iredapd/rc_scripts/iredapd.openbsd: For OpenBSD. Please copy to /etc/rc.d/.
** /opt/iredapd/rc_scripts/iredapd.opensuse: For openSUSE.
** /opt/iredapd/rc_scripts/iredapd.rhel: For Red Hat, CentOS, Scientific Linux.
{{cmd|<pre>
# cp /opt/iredapd/rc_scripts/iredapd.rhel /etc/init.d/iredapd
# chmod +x /etc/init.d/iredapd
</pre>}}

* Restart iRedAPD service:
{{cmd|<pre>
#
# ---- On Linux ----
#
# /etc/init.d/iredapd restart

#
# ---- On FreeBSD ----
#
# /usr/local/etc/rc.d/iredapd restart

#
# ---- On OpenBSD ----
#
# /etc/rc.d/iredapd restart
</pre>}}

* If you don't have file '''/etc/init.d/iredapd-rr''' on Linux, or '''/etc/rc.d/iredapd-rr''' on OpenBSD, or '''/usr/local/etc/rc.d/iredapd-rr''' on FreeBSD, it's safe to ignore below steps. But if you have it, please stop service '''iredapd-rr''', then move all enabled plugin names listed in '''/opt/iRedAPD-[OLD_VERSION]/etc/iredapd-rr.ini''' to our new config file '''/opt/iredapd/settings.py''', in parameter '''plugins = '''.
{{cmd|<pre>
# /etc/init.d/iredapd-rr stop
# rm /etc/init.d/iredapd-rr
</pre>}}

Check whether you have '''check_policy_service inet:127.0.0.1:7778''' in Postfix config file '''/etc/postfix/main.cf''' (Linux/OpenBSD) or '''/usr/local/etc/postfix/main.cf''', if you have it, please remove '''check_policy_service inet:127.0.0.1:7778''', then restart Postfix service.

That's all.

[[Category: FAQ]]
[[Category: iRedMail/FAQ]]

Upgrade/iRedMail/0.8.4-0.8.5

ZhangHuangbin — Fri, 26 Apr 2013 03:26:57 GMT

ZhangHuangbin: /* ChangeLog */

__TOC__

= ChangeLog =
* 2013-04-26: [ldap] Fix incorrect ACL for attribute "memberOfGroup".
* 2013-04-03: [ldap] Use the latest iRedMail LDAP schema file.
* 2013-04-03: [MySQL/PostgreSQL] Add one new column used for store preferred language for newly created mail users

= General (All backends should apply these steps) =
= OpenLDAP backend special =
== Use the latest LDAP schema file provided by iRedMail ==
With the latest LDAP schema file, we can use attribute '''preferredLanguage''' for mail domain object, it's used to storage short language code (e.g. de_DE, en_US) for newly created mail users. Steps to use the latest LDAP schema file are:

* Download the newest iRedMail ldap schema file
* Copy old ldap schema file as a backup copy
* Replace the old one
* Restart OpenLDAP service.

Here we go:

* On RHEL/CentOS/Scientific Linux (both release 5.x and 6.x), openSUSE, Gentoo, OpenBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/openldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/openldap/schema/
# /etc/init.d/slapd restart # <-- Or: /etc/init.d/ldap restart
</pre>}}

* On Debian/Ubuntu:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/ldap/schema/
# /etc/init.d/slapd restart
</pre>}}

* On FreeBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /usr/local/etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /usr/local/etc/openldap/schema/
# /etc/init.d/slapd restart
</pre>}}

== Fix incorrect ACL for attribute "memberOfGroup" ==
Permission for attribute '''memberOfGroup''' is not set correctly, it causes normal user can add himself to any mail list in LDAP. Default permission is writeable by self, it should be "read" by "self" instead.

* Open OpenLDAP config file '''slapd.conf''', find below lines:
** On RHEL/CentOS, openSUSE, Gentoo, OpenBSD, it's '''/etc/openldap/slapd.conf'''.
** On Debian/Ubuntu, it's '''/etc/ldap/slapd.conf'''.
** On FreeBSD, it's '''/usr/local/etc/openldap/slapd.conf'''.
{{cfg|slapd.conf|<pre>
# User attrs.
access to attrs="employeeNumber, ..."
</pre>}}

* Prepend attribute name "memberOfGroup" before "employeeNumber". The final result looks like below:
{{cfg|slapd.conf|<pre>
# User attrs.
access to attrs="memberOfGroup, employeeNumber, ..."
</pre>}}

* Save the config file, then restart OpenLDAP service to make it use new ACL.
** On RHEL/CentOS 5, openSUSE, please restart it with command <pre># /etc/init.d/ldap restart</pre>
** On RHEL/CentOS 6 and other Linux distribution, please restart it with command: <pre># /etc/init.d/slapd restart</pre>
** On FreeBSD, please restart it with command: <pre># /usr/local/etc/rc.d/slapd restart</pre>
** On OpenBSD, please restart it with command: <pre># /etc/rc.d/slapd restart</pre>

= MySQL backend special =
== Add one new column used for store preferred language for newly created mail users ==
We now storage short language code (e.g. de_DE, en_US) for newly created mail users, it requires a new SQL column '''defaultlanguage''' for this.

Please login to MySQL server as root user, execute SQL commands to add required columns and indexes.
{{cmd|<pre>
# mysql -uroot -p
mysql> USE vmail;
mysql> ALTER TABLE domain ADD COLUMN defaultlanguage VARCHAR(5) NOT NULL DEFAULT 'en_US';
</pre>}}

= PostgreSQL backend special =
== Add one new column used for store preferred language for newly created mail users ==

We now storage short language code (e.g. de_DE, en_US) for newly created mail users, it requires a new SQL column '''defaultlanguage''' for this.

Please switch to PostgreSQL daemon user, then execute SQL commands to add required columns and indexes:
On Linux, PostgreSQL daemon user is postgres.
On FreeBSD, PostgreSQL daemon user is pgsql.
On OpenBSD, PostgreSQL daemon user is """_postgresql".
{{cmd|<pre>
# su - postgres
$ psql -d vmail
sql> ALTER TABLE domain ADD COLUMN defaultlanguage VARCHAR(5) NOT NULL DEFAULT 'en_US';
</pre>}}

Upgrade/iRedMail/0.8.4-0.8.5

ZhangHuangbin — Fri, 26 Apr 2013 03:25:27 GMT

ZhangHuangbin: /* Use the latest LDAP schema file provided by iRedMail */

__TOC__

= ChangeLog =
* 2013-04-03:
** [ldap] Use the latest iRedMail LDAP schema file.
** [MySQL/PostgreSQL] Add one new column used for store preferred language for newly created mail users

= General (All backends should apply these steps) =
= OpenLDAP backend special =
== Use the latest LDAP schema file provided by iRedMail ==
With the latest LDAP schema file, we can use attribute '''preferredLanguage''' for mail domain object, it's used to storage short language code (e.g. de_DE, en_US) for newly created mail users. Steps to use the latest LDAP schema file are:

* Download the newest iRedMail ldap schema file
* Copy old ldap schema file as a backup copy
* Replace the old one
* Restart OpenLDAP service.

Here we go:

* On RHEL/CentOS/Scientific Linux (both release 5.x and 6.x), openSUSE, Gentoo, OpenBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/openldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/openldap/schema/
# /etc/init.d/slapd restart # <-- Or: /etc/init.d/ldap restart
</pre>}}

* On Debian/Ubuntu:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/ldap/schema/
# /etc/init.d/slapd restart
</pre>}}

* On FreeBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /usr/local/etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /usr/local/etc/openldap/schema/
# /etc/init.d/slapd restart
</pre>}}

== Fix incorrect ACL for attribute "memberOfGroup" ==
Permission for attribute '''memberOfGroup''' is not set correctly, it causes normal user can add himself to any mail list in LDAP. Default permission is writeable by self, it should be "read" by "self" instead.

* Open OpenLDAP config file '''slapd.conf''', find below lines:
** On RHEL/CentOS, openSUSE, Gentoo, OpenBSD, it's '''/etc/openldap/slapd.conf'''.
** On Debian/Ubuntu, it's '''/etc/ldap/slapd.conf'''.
** On FreeBSD, it's '''/usr/local/etc/openldap/slapd.conf'''.
{{cfg|slapd.conf|<pre>
# User attrs.
access to attrs="employeeNumber, ..."
</pre>}}

* Prepend attribute name "memberOfGroup" before "employeeNumber". The final result looks like below:
{{cfg|slapd.conf|<pre>
# User attrs.
access to attrs="memberOfGroup, employeeNumber, ..."
</pre>}}

* Save the config file, then restart OpenLDAP service to make it use new ACL.
** On RHEL/CentOS 5, openSUSE, please restart it with command <pre># /etc/init.d/ldap restart</pre>
** On RHEL/CentOS 6 and other Linux distribution, please restart it with command: <pre># /etc/init.d/slapd restart</pre>
** On FreeBSD, please restart it with command: <pre># /usr/local/etc/rc.d/slapd restart</pre>
** On OpenBSD, please restart it with command: <pre># /etc/rc.d/slapd restart</pre>

= MySQL backend special =
== Add one new column used for store preferred language for newly created mail users ==
We now storage short language code (e.g. de_DE, en_US) for newly created mail users, it requires a new SQL column '''defaultlanguage''' for this.

Please login to MySQL server as root user, execute SQL commands to add required columns and indexes.
{{cmd|<pre>
# mysql -uroot -p
mysql> USE vmail;
mysql> ALTER TABLE domain ADD COLUMN defaultlanguage VARCHAR(5) NOT NULL DEFAULT 'en_US';
</pre>}}

= PostgreSQL backend special =
== Add one new column used for store preferred language for newly created mail users ==

We now storage short language code (e.g. de_DE, en_US) for newly created mail users, it requires a new SQL column '''defaultlanguage''' for this.

Please switch to PostgreSQL daemon user, then execute SQL commands to add required columns and indexes:
On Linux, PostgreSQL daemon user is postgres.
On FreeBSD, PostgreSQL daemon user is pgsql.
On OpenBSD, PostgreSQL daemon user is """_postgresql".
{{cmd|<pre>
# su - postgres
$ psql -d vmail
sql> ALTER TABLE domain ADD COLUMN defaultlanguage VARCHAR(5) NOT NULL DEFAULT 'en_US';
</pre>}}

Upgrade/iRedMail/0.8.3-0.8.4

ZhangHuangbin — Thu, 25 Apr 2013 14:13:11 GMT

ZhangHuangbin: /* Update /etc/iredmail-release with iRedMail version number */

__TOC__

= ChangeLog =
* 2013-03-28: Update /etc/iredmail-release with iRedMail version number.
* 2013-03-28: Upgrade Roundcube webmail to the latest 0.8.6.
* 2013-03-25: [ldap] Fix incorrect LDAP query filter in Postfix.
* 2013-01-08: [sql] Add 4 new columns in table '''vmail.mailbox''' for MySQL/PostgreSQL backends.
* 2012-10-24: [ldap] Supports alias domains in Postfix per-user bcc lookup files.

= General (All backends should apply these steps) =

== Update /etc/iredmail-release with iRedMail version number ==
iRedMail stores the initial version number in /etc/iredmail-release after installation completed, 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:
{{cfg|/etc/iredmail-release|<pre>
0.8.4
</pre>}}

== Add new alias 'virusalert' in Postfix for Amavisd ==
Amavisd will send an email notification to address "virusalert@[YOUR_HOSTNAME]" by default, but we don't have this user in Postfix alias file (/etc/postfix/aliases on Linux/OpenBSD, or /usr/local/etc/postfix/aliases on FreeBSD) or SQL/LDAP database, so emails are not delivered. Below steps add a alias in Postfix alias file, and it will be forwarded to root user by default.

Add new alias (Note, use '/usr/local/etc/postfix/aliases' on FreeBSD instead), and update the database:
{{cmd|<pre>
# echo 'virusalert: root' >> /etc/postfix/aliases
# postalias /etc/postfix/aliases
</pre>}}

== Upgrade Roundcube webmail to the latest 0.8.6 ==
There's zero day vulnerability in Roundcubemail-0.8.5 and older releases, please follow this tutorial to upgrade Roundcube webmail to the latest 0.8.6 immediately: [[IRedMail/FAQ/Upgrade.Roundcube.Webmail |Upgrade Roundcube webmail]]

About the zero day vulnerability, please refer to this thread: http://lists.roundcube.net/pipermail/dev/2013-March/022328.html

== Upgrade iRedAPD (Postfix policy server) to the latest 1.4.0 ==
Please follow this tutorial to upgrade iRedAPD to the latest stable release: [[IRedMail/FAQ/Upgrade.iRedAPD |How to upgrade iRedAPD]]

== Upgrade iRedAdmin (open source edition) to the latest 0.2.1 ==
Please follow this tutorial to upgrade iRedAdmin open source edition to the latest stable release: [[IRedMail/FAQ/Upgrade.iRedAdmin.Open.Source.Edition |How to upgrade iRedAdmin (open source edition) to the latest stable release]]

= OpenLDAP backend special =
== Fix incorrect LDAP query filter in Postfix ==
If you add external email addresses as mail list members, iRedAdmin-Pro will store them in attribute '''memberOfGroup''', this will cause exported LDIF data cannot be restored. Below are steps to fix this issue.
=== Use the latest LDAP schema file provided by iRedMail ===
To fix this issue, we need the latest LDAP schema file provided by iRedMail. Steps are:
* Download the newest iRedMail ldap schema file
* Copy old ldap schema file as a backup copy
* Replace the old one
* Restart OpenLDAP service.

Here we go:

* On RHEL/CentOS/Scientific Linux (both release 5.x and 6.x), openSUSE, Gentoo, OpenBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/openldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/openldap/schema/
# /etc/init.d/slapd restart # <-- Or: /etc/init.d/ldap restart
</pre>}}

* On Debian/Ubuntu:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/ldap/schema/
# /etc/init.d/slapd restart
</pre>}}

* On FreeBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /usr/local/etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /usr/local/etc/openldap/schema/
# /usr/local/etc/rc.d/slapd restart
</pre>}}

=== Update existing accounts ===
* Download python script used to adding missing values.
{{cmd|<pre>
# cd /root/
# wget https://bitbucket.org/zhb/iredmail/raw/default/extra/update/updateLDAPValues_083_to_084.py
</pre>}}
Open updateLDAPValues_083_to_084.py, config LDAP server related settings in file head. e.g.
File: updateLDAPValues_083_to_084.py
{{cfg|updateLDAPValues_083_to_084.py|<pre>
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'
</pre>}}
Tip:
* You can find them in iRedAdmin config file or iRedMail.tips file under your iRedMail installation directory.
* Use 'cn=Manager' instead of 'cn=vmailadmin' here is ok too.

Execute this script, it will fix incorrect values and add correct ones:
{{cmd|<pre>
# python updateLDAPValues_083_to_084.py
</pre>}}

=== Fix incorrect LDAP query filter in Postfix ===
* On Linux/OpenBSD, please update '''/etc/postfix/ldap/virtual_group_maps.cf'''. On FreeBSD, update '''/usr/local/etc/postfix/ldap/virtual_group_maps.cf''' instead.
{{cfg|virtual_group_maps.cf|<pre>
# OLD setting
#query_filter = (&(memberOfGroup=%s)(accountStatus=active)(enabledService=mail)(enabledService=deliver)(|(objectClass=mailUser)(objectClass=mailExternalUser)))

# New setting
query_filter = (&(accountStatus=active)(enabledService=mail)(enabledService=deliver)(|(memberOfGroup=%s)(shadowAddress=%s))(|(objectClass=mailUser)(objectClass=mailExternalUser)))
</pre>}}

== Supports alias domains in Postfix per-user bcc lookup files ==
* In /etc/postfix/ldap/sender_bcc_maps_user.cf, replace "(mail=%s)" by "(|(mail=%s)(&(enabledService=shadowaddress)(shadowAddress=%s)))" in parameter "query_filter =". The final LDAP filter looks like below:
{{cfg|ldap/sender_bcc_maps_user.cf|<pre>
query_filter = (&(|(mail=%s)(&(enabledService=shadowaddress)(shadowAddress=%s)))(objectClass=mailUser)(accountStatus=active)(enabledService=mail)(enabledService=senderbcc))
</pre>}}

* Perform the same modification in file /etc/postfix/ldap/recipient_bcc_maps_user.cf, the final LDAP filter looks like below:
{{cfg|ldap/recipient_bcc_maps_user.cf|<pre>
query_filter = (&(|(mail=%s)(&(enabledService=shadowaddress)(shadowAddress=%s)))(objectClass=mailUser)(accountStatus=active)(enabledService=mail)(enabledService=recipientbcc))
</pre>}}

* Restarting Postfix service is required.

== Create addition SQL index for Amavisd database ==
We need one more SQL index for Amavisd database, it's used to speed up performance of viewing quarantined mails.
* Important Note: It will take a long time if you have many records in table '''msgs'''.
{{cmd|<pre>
$ mysql -uroot -p
mysql> USE amavisd;
mysql> ALTER TABLE msgs ADD INDEX (quar_type);
</pre>}}

= MySQL backend special =
== Add 4 new columns used for per-user restriction ==
New version of iRedAPD (Postfix policy daemon) requires 4 new columns in table '''vmail.mailbox''': allowedsenders, rejectedsenders, allowedrecipients, rejectedrecipients. They're used for per-user restriction. For example, you can now define who can send email to your local user, or your user can send email to which external domains or users.

Please login to MySQL server as root user, execute SQL commands to add required columns and indexes.
{{cmd|<pre>
# mysql -uroot -p
mysql> USE vmail;
mysql> ALTER TABLE mailbox ADD COLUMN allowedsenders TEXT NOT NULL DEFAULT '';
mysql> ALTER TABLE mailbox ADD COLUMN rejectedsenders TEXT NOT NULL DEFAULT '';
mysql> ALTER TABLE mailbox ADD COLUMN allowedrecipients TEXT NOT NULL DEFAULT '';
mysql> ALTER TABLE mailbox ADD COLUMN rejectedrecipients TEXT NOT NULL DEFAULT '';
</pre>}}

Supported formats of sender/recipients are:
* user@example.com: single user
* @example.com: single domain
* @'''.'''example.com: domain and its sub domain
* '''@.''': any users.

Multiple senders/recipients must be separated by comma, for example:
{{cmd|<pre>
sql> INSERT INTO mailbox SET allowedsenders='@gmail.com,user@example.com';
</pre>}}
== Create addition SQL index for Amavisd database ==
We need one more SQL index for Amavisd database, it's used to speed up performance of viewing quarantined mails.
* Important Note: It will take a long time if you have many records in table '''msgs'''.
{{cmd|<pre>
$ mysql -uroot -p
mysql> USE amavisd;
mysql> ALTER TABLE msgs ADD INDEX (quar_type);
</pre>}}

= PostgreSQL backend special =
== Add 4 new columns used for per-user restriction ==
New version of iRedAPD (Postfix policy daemon) requires 4 new columns in table '''vmail.mailbox''': allowedsenders, rejectedsenders, allowedrecipients, rejectedrecipients. They're used for per-user restriction. For example, you can now define who can send email to your local user, or your user can send email to which external domains or users.

Please switch to PostgreSQL daemon user, then execute SQL commands to add required columns and indexes:
On Linux, PostgreSQL daemon user is postgres.
On FreeBSD, PostgreSQL daemon user is pgsql.
On OpenBSD, PostgreSQL daemon user is """_postgresql".
{{cmd|<pre>
# su - postgres
$ psql -d vmail
sql> ALTER TABLE mailbox ADD COLUMN allowedsenders TEXT NOT NULL DEFAULT '';
sql> ALTER TABLE mailbox ADD COLUMN rejectedsenders TEXT NOT NULL DEFAULT '';
sql> ALTER TABLE mailbox ADD COLUMN allowedrecipients TEXT NOT NULL DEFAULT '';
sql> ALTER TABLE mailbox ADD COLUMN rejectedrecipients TEXT NOT NULL DEFAULT '';
</pre>}}

Supported formats of sender/recipients are:
* user@example.com: single user
* @example.com: single domain
* @'''.'''example.com: domain and its sub domain
* '''@.''': any users.

Multiple senders/recipients must be separated by comma, for example:
{{cmd|<pre>
sql> INSERT INTO mailbox SET allowedsenders='@gmail.com,user@example.com';
</pre>}}

== Create addition SQL index for Amavisd database ==
We need one more SQL index for Amavisd database, it's used to speed up performance of viewing quarantined mails.
* Important Note: It will take a long time if you have many records in table '''msgs'''.

Please switch to PostgreSQL daemon user, then execute SQL commands to add required columns and indexes:
* On Linux, PostgreSQL daemon user is postgres.
* On FreeBSD, PostgreSQL daemon user is pgsql.
* On OpenBSD, PostgreSQL daemon user is """_postgresql".
{{cmd|<pre>
# su - postgres
$ psql -d amavisd
sql> CREATE INDEX idx_msgs_quar_type ON msgs (quar_type);
</pre>}}

Postfix SPF check

ZhangHuangbin — Tue, 23 Apr 2013 14:32:05 GMT

ZhangHuangbin:

__TOC__

----
'''NOTE''':
* This tutorial is contributed by iRedMail user, please use it on your own.
* iRedMail has SPF check enabled with Amavisd-new and perl module '''perl-Mail-SPF''' after queue, so you don't need this if after-queue SPF verification is ok for you.
----

= Summary =

Using the Python version of SPF Policy Server for Postfix it is possible to implement checking of SPF of incoming messages in Postfix, with immediate reject or pass (if desired).
This article will describe how to achieve this feature.

== Notes ==
* There is also a Perl version of the software, but it is not recommended because it does not scale well and should only be used for small scale servers.
* This tutorial was written for a CentOS-based system. Please adapt it to fit your distro and configuration.
* It is assumed that the user has good knowledge of the technologies used therein.

= Installation =
* Download the latest version of pypolicyd-spf from [https://launchpad.net/pypolicyd-spf/ the project's home page].
* Unpack it and install it by using the instructions in the ''README'' file.

= Configuration =
Set-up your '''''/etc/python-policyd-spf/policyd-spf.conf''''' to fit your needs.

At the beginning, make sure you set:
{{cfg|/etc/python-policyd-spf/policyd-spf.conf|<pre>
defaultSeedOnly = 0
</pre>}} so no messages are actually rejected by policyd-SPF. You will thus be able to check the effect of your config without losing important messages.

For example, a quite good configuration for fighting spam (but not losing legitimate messages) would contain
{{cfg|/etc/python-policyd-spf/policyd-spf.conf|<pre>
HELO_reject = Fail
Mail_From_reject = Fail
PermError_reject = False
TempError_Defer = False
skip_addresses = 127.0.0.0/8,::ffff:127.0.0.0//104,::1//128
</pre>}}
The meaning of each parameter is explained in the ''README'' file and in the man page ('''''man 5 policyd-spf.conf''''').

= Enable SPF check in Postfix =
Edit your '''''master.cf''''' file and add at the end:
{{cfg|/etc/postfix/master.cf|<pre>
# SPF check
spfpolicy unix - n n - - spawn
user=nobody argv=/usr/bin/python /usr/bin/policyd-spf
</pre>}}

Edit your '''''main.cf''''' file and add the following line in ''smtpd_recipient_restrictions'', towards the end, but before the main policyd service (usually running on port 10031):
{{cfg|/etc/postfix/main.cf|<pre>
smtpd_recipient_restrictions =
...
check_policy_service unix:private/spfpolicy,
...
</pre>}}

Restart postfix:
{{cmd|<pre>
/etc/init.d/postfix restart
</pre>}}

== Final notes ==
* Verify the effect of your changes by checking the maillog.
* When you are happy with a set of config parameters for pypolicyd-spf, be sure to enable actual SPF enforcing:
{{cfg|/etc/python-policyd-spf/policyd-spf.conf|<pre>
defaultSeedOnly = 1
</pre>}}

--[[User:Maxie ro|Maxie ro]] 20:13, 15 February 2011 (UTC)

[[Category: iRedMail/FAQ]]
[[Category: FAQ]]

IRedMail/FAQ/Enable.Throttling/FreeBSD

ZhangHuangbin — Mon, 22 Apr 2013 16:54:31 GMT

ZhangHuangbin:

iRedMail implements sender & recipient throttling via policyd-1.8.x, but it's disabled by default. You can enable it by follow below steps on FreeBSD:

We choose to run two Policyd instances/daemons:
* one listens on port 10031, used for greylisting, white/blacklisting and recipient throttling.
* another one listens on port 10032, used for sender throttling.
----

Here we go:

* Disable sender throttling in ''''/usr/local/etc/postfix-policyd-sf.conf''', but enable recipient throttling:
{{cfg|/usr/local/etc/postfix-policyd-sf.conf|<pre>
SENDERTHROTTLE=0
SENDER_THROTTLE_SASL=0
SENDER_THROTTLE_HOST=0

# Enable recipient throttling in this instance, will be invoked in Postfix
# smtpd_recipient_restrictions.
RECIPIENTTHROTTLE=1
</pre>}}

* Enable throttling in '''/usr/local/etc/policyd_sender_throttle.conf''':
{{cfg|/usr/local/etc/policyd_sender_throttle.conf|<pre>
SENDERTHROTTLE=1
SENDER_THROTTLE_SASL=1
SENDER_THROTTLE_HOST=0

# Disable recipient throttling in this instance.
# Recipient Throttling can not work at smtpd_end_of_data_restrictions. Policyd v2 (a.k.a. Cluebringer)
# overcomes this and tracks the recipients for each smtpd instance. To track quotas
# precisely v2 can be used in smtpd_recipient_restrictions and smtpd_end_of_data_restrictions.
# v2 knows about the various restrictions.
# Reference: http://comments.gmane.org/gmane.mail.postfix.policyd/826
RECIPIENTTHROTTLE=0
</pre>}}

* Create another policyd rc script:
{{cmd|<pre>
# cd /usr/local/etc/rc.d/
# cp policyd policyd_sender_throttle
# perl -pi -e 's#postfix-policyd-sf#policyd_sender_throttle#g' policyd_sender_throttle
# perl -pi -e 's#^(command=).*#${1}/usr/local/sbin/postfix-policyd-sf#' policyd_sender_throttle
</pre>}}

* Append below line to '''/etc/rc.conf''':
{{cfg|/etc/rc.conf|<pre>
policyd_sender_throttle_enable='YES'
</pre>}}

* Restart policyd service now:
{{cmd|<pre>
# /usr/local/etc/rc.d/policyd restart
# /usr/local/etc/rc.d/policyd_sender_throttle restart
</pre>}}

It will listen on two ports: 10031, 10032. You can verify it via command '''sockstat''':
{{cmd|<pre>
# sockstat -4 | grep -i 1003
policyd postfix-po 1193 6 tcp4 127.0.0.1:10032 *:*
policyd postfix-po 911 6 tcp4 127.0.0.1:10031 *:*
</pre>}}

* Enable throttling in Postfix '''/usr/local/etc/postfix/main.cf''':
{{cfg|/usr/local/etc/postfix/main.cf|<pre>
smtpd_end_of_data_restrictions = check_policy_service inet:127.0.0.1:10032
</pre>}}

Restart postfix:
{{cmd|<pre>
# /usr/local/etc/rc.d/postfix restart
</pre>}}

That's all.

Refer to Policyd official documentation to set throttling: http://policyd.sourceforge.net/readme.html

[[Category: iRedMail]]
[[Category: iRedMail/FAQ]]
[[Category: FAQ]]
[[Category: Policyd]]
[[Category: Throttling]]

IRedMail/FAQ/Enable.Throttling/Debian.Ubuntu

ZhangHuangbin — Mon, 22 Apr 2013 16:54:06 GMT

ZhangHuangbin:

iRedMail ships Policyd-1.8.x for sender & recipient throttling, but it's disabled by default. You can enable it by follow below steps on Debian:

We choose to run two Policyd instances/daemons:
* one listens on port 10031, used for greylisting, white/blacklisting and recipient throttling.
* another one listens on port 10032, used for sender throttling.
----

Here we go:

* Disable sender throttling in '''/etc/postfix-policyd.conf''', but enable recipient throttling. Warning: This is '''NOT''' the complete file.
{{cfg|/etc/postfix-policyd.conf|<pre>
SENDERTHROTTLE=0
SENDER_THROTTLE_SASL=0
SENDER_THROTTLE_HOST=0

# Enable recipient throttling in this instance, will be invoked in Postfix
# smtpd_recipient_restrictions.
RECIPIENTTHROTTLE=1
</pre>}}

* Enable throttling in '''/etc/postfix-policyd_throttle.conf'''. Warning: This is '''NOT''' the complete file.
{{cfg|/etc/postfix-policyd_throttle.conf|<pre>
SENDERTHROTTLE=1
SENDER_THROTTLE_SASL=1
SENDER_THROTTLE_HOST=0

# Disable recipient throttling in this instance.
# Recipient Throttling can not work at smtpd_end_of_data_restrictions. Policyd v2 (a.k.a. Cluebringer)
# overcomes this and tracks the recipients for each smtpd instance. To track quotas
# precisely v2 can be used in smtpd_recipient_restrictions and smtpd_end_of_data_restrictions.
# v2 knows about the various restrictions.
# Reference: http://comments.gmane.org/gmane.mail.postfix.policyd/826
RECIPIENTTHROTTLE=0

WHITELISTING=0 # <-- If set to 1, throttling won't work!
BLACKLISTING=0
BLACKLIST_HELO=0
BLACKLISTSENDER=0
HELO_CHECK=0
SPAMTRAPPING=0
GREYLISTING=0
</pre>}}

* Save below content as file '''/etc/init.d/postfix-policyd_sender_throttle'''. This is the complete file.
<pre>
#! /bin/sh
### BEGIN INIT INFO
# Provides: postfix-policyd_throttle
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
### END INIT INFO

PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/usr/sbin/postfix-policyd
CONFIG=/etc/postfix-policyd_throttle.conf
PIDFILE='/var/run/policyd_throttle.pid'
NAME=postfix-policyd_throttle
DESC="Postfix throttling policy daemon"

test -x $DAEMON || exit 0

# Include policyd defaults if available
#if [ -f /etc/default/postfix-policyd ] ; then
# . /etc/default/postfix-policyd
#fi

set -e

PIDFILE=`grep "PIDFILE" $CONFIG | awk -F "=" '{print $2}' | awk '{print $1}'`

case "$1" in
start)
echo -n "Starting $DESC: "
start-stop-daemon --start --quiet --background --pidfile $PIDFILE --exec $DAEMON -- -c $CONFIG
echo "$NAME."
;;
stop)
echo -n "Stopping $DESC: "
start-stop-daemon --stop --quiet --pidfile $PIDFILE --exec $DAEMON
echo "$NAME."
;;
reload|force-reload)
echo -n "Reloading $DESC configuration: "
start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --exec $DAEMON
echo "$NAME."
;;
restart)
echo -n "Restarting $DESC: "
start-stop-daemon --stop --quiet --pidfile $PIDFILE --exec $DAEMON
sleep 1
start-stop-daemon --start --quiet --background --pidfile $PIDFILE --exec $DAEMON -- -c $CONFIG
echo "$NAME."
;;
*)
N=/etc/init.d/$NAME
echo "Usage: $N {start|stop|restart|reload|force-reload}" >&2
exit 1
;;
esac

exit 0
</pre>

* Start policyd via '''/etc/init.d/postfix-policyd_sender_throttle''':
{{cmd|<pre>
# chmod 0755 /etc/init.d/postfix-policyd_sender_throttle
# update-rc.d postfix-policyd_sender_throttle defaults
# /etc/init.d/postfix-policyd_sender_throttle restart
# /etc/init.d/postfix-policyd restart
</pre>}}

Now run command '''netstat''' to see if everything is working right. You should get two lines of output like below:
{{cmd|<pre>
# netstat -ntlp | grep -i 1003
tcp 0 0 127.0.0.1:10031 0.0.0.0:* LISTEN 3454/policyd
tcp 0 0 127.0.0.1:10032 0.0.0.0:* LISTEN 3459/policyd
</pre>}}

The most important info is port numbers: 10031, 10032.

* Enable throttling in Postfix '''/etc/postfix/main.cf'''. The following line should already be there, but commented out by default. Uncomment it. If it's not there, add it.
{{cfg|/etc/postfix/main.cf|<pre>
smtpd_end_of_data_restrictions = check_policy_service inet:127.0.0.1:10032
</pre>}}

* Restart postfix to re-read new configuration.
{{cmd|<pre>
# /etc/init.d/postfix restart
</pre>}}

That's all.

If it works, you'll find lines similar to the following in /var/log/mail.log.
<pre>
postfix-policyd: rcpt=81, throttle=update(a), host=127.0.0.1,
from=robert@example.com, to=someone@spamtrap.net, size=1749/10240000,
quota=30611/250000000, count=9/50(9), rcpt=9/3600(9), threshold=0%|16%|0%
</pre>

Refer to Policyd official documentation to set throttling: http://policyd.sourceforge.net/readme.html

[[Category: iRedMail]]
[[Category: iRedMail/FAQ]]
[[Category: FAQ]]
[[Category: Policyd]]
[[Category: Throttling]]

IRedMail/FAQ/Enable.Throttling/RHEL.CentOS

ZhangHuangbin — Mon, 22 Apr 2013 16:53:45 GMT

ZhangHuangbin:

iRedMail ships Policyd-1.8.x for sender & recipient throttling, but it's disabled by default. You can enable it by follow below steps on RHEL/CentOS:

We choose to run two Policyd instances/daemons:
* one listens on port 10031, used for greylisting, white/blacklisting and recipient throttling.
* another one listens on port 10032, used for sender throttling.
----

Here we go:
* Disable sender throttling in '''/etc/postfix-policyd.conf''', but enable recipient throttling:
{{cfg|/etc/policyd.conf|<pre>
SENDERTHROTTLE=0
SENDER_THROTTLE_SASL=0
SENDER_THROTTLE_HOST=0

# Enable recipient throttling in this instance, will be invoked in Postfix
# smtpd_recipient_restrictions.
RECIPIENTTHROTTLE=1
</pre>}}

* Enable throttling in '''/etc/policyd_sender_throttle.conf''':
{{cfg|/etc/policyd_sender_throttle.conf|<pre>
SENDERTHROTTLE=1
SENDER_THROTTLE_SASL=1
SENDER_THROTTLE_HOST=0

# Disable recipient throttling in this instance.
# Recipient Throttling can not work at smtpd_end_of_data_restrictions. Policyd v2 (a.k.a. Cluebringer)
# overcomes this and tracks the recipients for each smtpd instance. To track quotas
# precisely v2 can be used in smtpd_recipient_restrictions and smtpd_end_of_data_restrictions.
# v2 knows about the various restrictions.
# Reference: http://comments.gmane.org/gmane.mail.postfix.policyd/826
RECIPIENTTHROTTLE=0
</pre>}}

Note: You may only enable '''SENDER_THROTTLE_SASL''' or '''SENDER_THROTTLE_HOST''' but '''NOT''' both.

* Edit '''/etc/init.d/policyd''', set '''ENABLE_SENDER_THROTTLE='YES'''' to start another policyd instance for throttling:
{{cfg|/etc/init.d/policyd|<pre>
ENABLE_SENDER_THROTTLE="YES"
</pre>}}

* Restart policyd service:
{{cmd|<pre>
# /etc/init.d/policyd restart
</pre>}}

It will listen on two ports: 10031, 10032. You can verify it via command '''netstat''':
{{cmd|<pre>
# netstat -ntlp | grep -i 1003
tcp 0 0 127.0.0.1:10031 0.0.0.0:* LISTEN 3454/policyd
tcp 0 0 127.0.0.1:10032 0.0.0.0:* LISTEN 3459/policyd
</pre>}}

* Enable throttling in Postfix '''/etc/postfix/main.cf''':
{{cfg|/etc/postfix/main.cf|<pre>
smtpd_end_of_data_restrictions = check_policy_service inet:127.0.0.1:10032
</pre>}}

Restart postfix:
{{cmd|<pre>
# /etc/init.d/postfix restart
</pre>}}

That's all.

Refer to Policyd official documentation to set throttling: http://policyd.sourceforge.net/readme.html

[[Category: iRedMail]]
[[Category: iRedMail/FAQ]]
[[Category: FAQ]]
[[Category: Policyd]]
[[Category: Throttling]]

IRedMail/FAQ/Enable.Throttling/RHEL.CentOS

ZhangHuangbin — Mon, 22 Apr 2013 16:53:20 GMT

ZhangHuangbin:

iRedMail ships Policyd-1.8.x for sender & recipient throttling, but it's disabled by default. You can enable it by follow below steps on RHEL/CentOS:

We choose to run two Policyd instances/daemons:
* one listens on port 10031, used for greylisting, white/blacklisting and recipient throttling.
* another one listens on port 10032, used for sender throttling.

* Disable sender throttling in '''/etc/postfix-policyd.conf''', but enable recipient throttling:
{{cfg|/etc/policyd.conf|<pre>
SENDERTHROTTLE=0
SENDER_THROTTLE_SASL=0
SENDER_THROTTLE_HOST=0

# Enable recipient throttling in this instance, will be invoked in Postfix
# smtpd_recipient_restrictions.
RECIPIENTTHROTTLE=1
</pre>}}

* Enable throttling in '''/etc/policyd_sender_throttle.conf''':
{{cfg|/etc/policyd_sender_throttle.conf|<pre>
SENDERTHROTTLE=1
SENDER_THROTTLE_SASL=1
SENDER_THROTTLE_HOST=0

# Disable recipient throttling in this instance.
# Recipient Throttling can not work at smtpd_end_of_data_restrictions. Policyd v2 (a.k.a. Cluebringer)
# overcomes this and tracks the recipients for each smtpd instance. To track quotas
# precisely v2 can be used in smtpd_recipient_restrictions and smtpd_end_of_data_restrictions.
# v2 knows about the various restrictions.
# Reference: http://comments.gmane.org/gmane.mail.postfix.policyd/826
RECIPIENTTHROTTLE=0
</pre>}}

Note: You may only enable '''SENDER_THROTTLE_SASL''' or '''SENDER_THROTTLE_HOST''' but '''NOT''' both.

* Edit '''/etc/init.d/policyd''', set '''ENABLE_SENDER_THROTTLE='YES'''' to start another policyd instance for throttling:
{{cfg|/etc/init.d/policyd|<pre>
ENABLE_SENDER_THROTTLE="YES"
</pre>}}

* Restart policyd service:
{{cmd|<pre>
# /etc/init.d/policyd restart
</pre>}}

It will listen on two ports: 10031, 10032. You can verify it via command '''netstat''':
{{cmd|<pre>
# netstat -ntlp | grep -i 1003
tcp 0 0 127.0.0.1:10031 0.0.0.0:* LISTEN 3454/policyd
tcp 0 0 127.0.0.1:10032 0.0.0.0:* LISTEN 3459/policyd
</pre>}}

* Enable throttling in Postfix '''/etc/postfix/main.cf''':
{{cfg|/etc/postfix/main.cf|<pre>
smtpd_end_of_data_restrictions = check_policy_service inet:127.0.0.1:10032
</pre>}}

Restart postfix:
{{cmd|<pre>
# /etc/init.d/postfix restart
</pre>}}

That's all.

Refer to Policyd official documentation to set throttling: http://policyd.sourceforge.net/readme.html

[[Category: iRedMail]]
[[Category: iRedMail/FAQ]]
[[Category: FAQ]]
[[Category: Policyd]]
[[Category: Throttling]]

IRedMail/FAQ/Enable.Throttling/FreeBSD

ZhangHuangbin — Mon, 22 Apr 2013 16:43:12 GMT

ZhangHuangbin:

iRedMail implements sender & recipient throttling via policyd-1.8.x, but it's disabled by default. You can enable it by follow below steps on FreeBSD:

* Disable sender throttling in ''''/usr/local/etc/postfix-policyd-sf.conf''', but enable recipient throttling:
{{cfg|/usr/local/etc/postfix-policyd-sf.conf|<pre>
SENDERTHROTTLE=0
SENDER_THROTTLE_SASL=0
SENDER_THROTTLE_HOST=0

# Enable recipient throttling in this instance, will be invoked in Postfix
# smtpd_recipient_restrictions.
RECIPIENTTHROTTLE=1
</pre>}}

* Enable throttling in '''/usr/local/etc/policyd_sender_throttle.conf''':
{{cfg|/usr/local/etc/policyd_sender_throttle.conf|<pre>
SENDERTHROTTLE=1
SENDER_THROTTLE_SASL=1
SENDER_THROTTLE_HOST=0

# Disable recipient throttling in this instance.
# Recipient Throttling can not work at smtpd_end_of_data_restrictions. Policyd v2 (a.k.a. Cluebringer)
# overcomes this and tracks the recipients for each smtpd instance. To track quotas
# precisely v2 can be used in smtpd_recipient_restrictions and smtpd_end_of_data_restrictions.
# v2 knows about the various restrictions.
# Reference: http://comments.gmane.org/gmane.mail.postfix.policyd/826
RECIPIENTTHROTTLE=0
</pre>}}

* Create another policyd rc script:
{{cmd|<pre>
# cd /usr/local/etc/rc.d/
# cp policyd policyd_sender_throttle
# perl -pi -e 's#postfix-policyd-sf#policyd_sender_throttle#g' policyd_sender_throttle
# perl -pi -e 's#^(command=).*#${1}/usr/local/sbin/postfix-policyd-sf#' policyd_sender_throttle
</pre>}}

* Append below line to '''/etc/rc.conf''':
{{cfg|/etc/rc.conf|<pre>
policyd_sender_throttle_enable='YES'
</pre>}}

* Restart policyd service now:
{{cmd|<pre>
# /usr/local/etc/rc.d/policyd restart
# /usr/local/etc/rc.d/policyd_sender_throttle restart
</pre>}}

It will listen on two ports: 10031, 10032. You can verify it via command '''sockstat''':
{{cmd|<pre>
# sockstat -4 | grep -i 1003
policyd postfix-po 1193 6 tcp4 127.0.0.1:10032 *:*
policyd postfix-po 911 6 tcp4 127.0.0.1:10031 *:*
</pre>}}

* Enable throttling in Postfix '''/usr/local/etc/postfix/main.cf''':
{{cfg|/usr/local/etc/postfix/main.cf|<pre>
smtpd_end_of_data_restrictions = check_policy_service inet:127.0.0.1:10032
</pre>}}

Restart postfix:
{{cmd|<pre>
# /usr/local/etc/rc.d/postfix restart
</pre>}}

That's all.

Refer to Policyd official documentation to set throttling: http://policyd.sourceforge.net/readme.html

[[Category: iRedMail]]
[[Category: iRedMail/FAQ]]
[[Category: FAQ]]
[[Category: Policyd]]
[[Category: Throttling]]

IRedMail/FAQ/Enable.Throttling/Debian.Ubuntu

ZhangHuangbin — Mon, 22 Apr 2013 16:43:06 GMT

ZhangHuangbin:

iRedMail ships Policyd-1.8.x for sender & recipient throttling, but it's disabled by default. You can enable it by follow below steps on Debian:

* Disable sender throttling in '''/etc/postfix-policyd.conf''', but enable recipient throttling. Warning: This is '''NOT''' the complete file.
{{cfg|/etc/postfix-policyd.conf|<pre>
SENDERTHROTTLE=0
SENDER_THROTTLE_SASL=0
SENDER_THROTTLE_HOST=0

# Enable recipient throttling in this instance, will be invoked in Postfix
# smtpd_recipient_restrictions.
RECIPIENTTHROTTLE=1
</pre>}}

* Enable throttling in '''/etc/postfix-policyd_throttle.conf'''. Warning: This is '''NOT''' the complete file.
{{cfg|/etc/postfix-policyd_throttle.conf|<pre>
SENDERTHROTTLE=1
SENDER_THROTTLE_SASL=1
SENDER_THROTTLE_HOST=0

# Disable recipient throttling in this instance.
# Recipient Throttling can not work at smtpd_end_of_data_restrictions. Policyd v2 (a.k.a. Cluebringer)
# overcomes this and tracks the recipients for each smtpd instance. To track quotas
# precisely v2 can be used in smtpd_recipient_restrictions and smtpd_end_of_data_restrictions.
# v2 knows about the various restrictions.
# Reference: http://comments.gmane.org/gmane.mail.postfix.policyd/826
RECIPIENTTHROTTLE=0

WHITELISTING=0 # <-- If set to 1, throttling won't work!
BLACKLISTING=0
BLACKLIST_HELO=0
BLACKLISTSENDER=0
HELO_CHECK=0
SPAMTRAPPING=0
GREYLISTING=0
</pre>}}

* Save below content as file '''/etc/init.d/postfix-policyd_sender_throttle'''. This is the complete file.
<pre>
#! /bin/sh
### BEGIN INIT INFO
# Provides: postfix-policyd_throttle
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
### END INIT INFO

PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/usr/sbin/postfix-policyd
CONFIG=/etc/postfix-policyd_throttle.conf
PIDFILE='/var/run/policyd_throttle.pid'
NAME=postfix-policyd_throttle
DESC="Postfix throttling policy daemon"

test -x $DAEMON || exit 0

# Include policyd defaults if available
#if [ -f /etc/default/postfix-policyd ] ; then
# . /etc/default/postfix-policyd
#fi

set -e

PIDFILE=`grep "PIDFILE" $CONFIG | awk -F "=" '{print $2}' | awk '{print $1}'`

case "$1" in
start)
echo -n "Starting $DESC: "
start-stop-daemon --start --quiet --background --pidfile $PIDFILE --exec $DAEMON -- -c $CONFIG
echo "$NAME."
;;
stop)
echo -n "Stopping $DESC: "
start-stop-daemon --stop --quiet --pidfile $PIDFILE --exec $DAEMON
echo "$NAME."
;;
reload|force-reload)
echo -n "Reloading $DESC configuration: "
start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --exec $DAEMON
echo "$NAME."
;;
restart)
echo -n "Restarting $DESC: "
start-stop-daemon --stop --quiet --pidfile $PIDFILE --exec $DAEMON
sleep 1
start-stop-daemon --start --quiet --background --pidfile $PIDFILE --exec $DAEMON -- -c $CONFIG
echo "$NAME."
;;
*)
N=/etc/init.d/$NAME
echo "Usage: $N {start|stop|restart|reload|force-reload}" >&2
exit 1
;;
esac

exit 0
</pre>

* Start policyd via '''/etc/init.d/postfix-policyd_sender_throttle''':
{{cmd|<pre>
# chmod 0755 /etc/init.d/postfix-policyd_sender_throttle
# update-rc.d postfix-policyd_sender_throttle defaults
# /etc/init.d/postfix-policyd_sender_throttle restart
# /etc/init.d/postfix-policyd restart
</pre>}}

Now run command '''netstat''' to see if everything is working right. You should get two lines of output like below:
{{cmd|<pre>
# netstat -ntlp | grep -i 1003
tcp 0 0 127.0.0.1:10031 0.0.0.0:* LISTEN 3454/policyd
tcp 0 0 127.0.0.1:10032 0.0.0.0:* LISTEN 3459/policyd
</pre>}}

The most important info is port numbers: 10031, 10032.

* Enable throttling in Postfix '''/etc/postfix/main.cf'''. The following line should already be there, but commented out by default. Uncomment it. If it's not there, add it.
{{cfg|/etc/postfix/main.cf|<pre>
smtpd_end_of_data_restrictions = check_policy_service inet:127.0.0.1:10032
</pre>}}

* Restart postfix to re-read new configuration.
{{cmd|<pre>
# /etc/init.d/postfix restart
</pre>}}

That's all.

If it works, you'll find lines similar to the following in /var/log/mail.log.
<pre>
postfix-policyd: rcpt=81, throttle=update(a), host=127.0.0.1,
from=robert@example.com, to=someone@spamtrap.net, size=1749/10240000,
quota=30611/250000000, count=9/50(9), rcpt=9/3600(9), threshold=0%|16%|0%
</pre>

Refer to Policyd official documentation to set throttling: http://policyd.sourceforge.net/readme.html

[[Category: iRedMail]]
[[Category: iRedMail/FAQ]]
[[Category: FAQ]]
[[Category: Policyd]]
[[Category: Throttling]]

IRedMail/FAQ/Enable.Throttling/RHEL.CentOS

ZhangHuangbin — Mon, 22 Apr 2013 16:43:03 GMT

ZhangHuangbin:

iRedMail ships Policyd-1.8.x for sender & recipient throttling, but it's disabled by default. You can enable it by follow below steps on RHEL/CentOS:

* Disable sender throttling in '''/etc/postfix-policyd.conf''', but enable recipient throttling:
{{cfg|/etc/policyd.conf|<pre>
SENDERTHROTTLE=0
SENDER_THROTTLE_SASL=0
SENDER_THROTTLE_HOST=0

# Enable recipient throttling in this instance, will be invoked in Postfix
# smtpd_recipient_restrictions.
RECIPIENTTHROTTLE=1
</pre>}}

* Enable throttling in '''/etc/policyd_sender_throttle.conf''':
{{cfg|/etc/policyd_sender_throttle.conf|<pre>
SENDERTHROTTLE=1
SENDER_THROTTLE_SASL=1
SENDER_THROTTLE_HOST=0

# Disable recipient throttling in this instance.
# Recipient Throttling can not work at smtpd_end_of_data_restrictions. Policyd v2 (a.k.a. Cluebringer)
# overcomes this and tracks the recipients for each smtpd instance. To track quotas
# precisely v2 can be used in smtpd_recipient_restrictions and smtpd_end_of_data_restrictions.
# v2 knows about the various restrictions.
# Reference: http://comments.gmane.org/gmane.mail.postfix.policyd/826
RECIPIENTTHROTTLE=0
</pre>}}

Note: You may only enable '''SENDER_THROTTLE_SASL''' or '''SENDER_THROTTLE_HOST''' but '''NOT''' both.

* Edit '''/etc/init.d/policyd''', set '''ENABLE_SENDER_THROTTLE='YES'''' to start another policyd instance for throttling:
{{cfg|/etc/init.d/policyd|<pre>
ENABLE_SENDER_THROTTLE="YES"
</pre>}}

* Restart policyd service:
{{cmd|<pre>
# /etc/init.d/policyd restart
</pre>}}

It will listen on two ports: 10031, 10032. You can verify it via command '''netstat''':
{{cmd|<pre>
# netstat -ntlp | grep -i 1003
tcp 0 0 127.0.0.1:10031 0.0.0.0:* LISTEN 3454/policyd
tcp 0 0 127.0.0.1:10032 0.0.0.0:* LISTEN 3459/policyd
</pre>}}

* Enable throttling in Postfix '''/etc/postfix/main.cf''':
{{cfg|/etc/postfix/main.cf|<pre>
smtpd_end_of_data_restrictions = check_policy_service inet:127.0.0.1:10032
</pre>}}

Restart postfix:
{{cmd|<pre>
# /etc/init.d/postfix restart
</pre>}}

That's all.

Refer to Policyd official documentation to set throttling: http://policyd.sourceforge.net/readme.html

[[Category: iRedMail]]
[[Category: iRedMail/FAQ]]
[[Category: FAQ]]
[[Category: Policyd]]
[[Category: Throttling]]

IRedMail/FAQ/Enable.Throttling/RHEL.CentOS

ZhangHuangbin — Mon, 22 Apr 2013 16:32:46 GMT

ZhangHuangbin:

iRedMail ships Policyd-1.8.x for sender & recipient throttling, but it's disabled by default. You can enable it by follow below steps on RHEL/CentOS:

* Disable sender throttling in '''/etc/postfix-policyd.conf''', but enable recipient throttling:
{{cfg|/etc/policyd.conf|<pre>
SENDERTHROTTLE=0
SENDER_THROTTLE_SASL=0
SENDER_THROTTLE_HOST=0

RECIPIENTTHROTTLE=1
</pre>}}

* Enable throttling in '''/etc/policyd_sender_throttle.conf''':
{{cfg|/etc/policyd_sender_throttle.conf|<pre>
SENDERTHROTTLE=1
SENDER_THROTTLE_SASL=1
SENDER_THROTTLE_HOST=0

# Disable recipient throttling in this instance.
# Recipient Throttling can not work at smtpd_end_of_data_restrictions. Policyd v2 (a.k.a. Cluebringer)
# overcomes this and tracks the recipients for each smtpd instance. To track quotas
# precisely v2 can be used in smtpd_recipient_restrictions and smtpd_end_of_data_restrictions.
# v2 knows about the various restrictions.
# Reference: http://comments.gmane.org/gmane.mail.postfix.policyd/826
RECIPIENTTHROTTLE=0
</pre>}}

Note: You may only enable '''SENDER_THROTTLE_SASL''' or '''SENDER_THROTTLE_HOST''' but '''NOT''' both.

* Edit '''/etc/init.d/policyd''', set '''ENABLE_SENDER_THROTTLE='YES'''' to start another policyd instance for throttling:
{{cfg|/etc/init.d/policyd|<pre>
ENABLE_SENDER_THROTTLE="YES"
</pre>}}

* Restart policyd service:
{{cmd|<pre>
# /etc/init.d/policyd restart
</pre>}}

It will listen on two ports: 10031, 10032. You can verify it via command '''netstat''':
{{cmd|<pre>
# netstat -ntlp | grep -i 1003
tcp 0 0 127.0.0.1:10031 0.0.0.0:* LISTEN 3454/policyd
tcp 0 0 127.0.0.1:10032 0.0.0.0:* LISTEN 3459/policyd
</pre>}}

* Enable throttling in Postfix '''/etc/postfix/main.cf''':
{{cfg|/etc/postfix/main.cf|<pre>
smtpd_end_of_data_restrictions = check_policy_service inet:127.0.0.1:10032
</pre>}}

Restart postfix:
{{cmd|<pre>
# /etc/init.d/postfix restart
</pre>}}

That's all.

Refer to Policyd official documentation to set throttling: http://policyd.sourceforge.net/readme.html

[[Category: iRedMail]]
[[Category: iRedMail/FAQ]]
[[Category: FAQ]]
[[Category: Policyd]]
[[Category: Throttling]]

IRedMail/FAQ/Enable.Throttling/RHEL.CentOS

ZhangHuangbin — Mon, 22 Apr 2013 16:31:46 GMT

ZhangHuangbin:

iRedMail ships Policyd-1.8.x for sender & recipient throttling, but it's disabled by default. You can enable it by follow below steps on RHEL/CentOS:

* Disable sender throttling in '''/etc/postfix-policyd.conf''', but enable recipient throttling:
{{cfg|/etc/policyd.conf|<pre>
SENDERTHROTTLE=0
SENDER_THROTTLE_SASL=0
SENDER_THROTTLE_HOST=0

RECIPIENTTHROTTLE=0
</pre>}}

* Enable throttling in '''/etc/policyd_sender_throttle.conf''':
{{cfg|/etc/policyd_sender_throttle.conf|<pre>
SENDERTHROTTLE=1
SENDER_THROTTLE_SASL=1
SENDER_THROTTLE_HOST=0

# Disable recipient throttling in this instance.
# Recipient Throttling can not work at smtpd_end_of_data_restrictions. Policyd v2 (a.k.a. Cluebringer)
# overcomes this and tracks the recipients for each smtpd instance. To track quotas
# precisely v2 can be used in smtpd_recipient_restrictions and smtpd_end_of_data_restrictions.
# v2 knows about the various restrictions.
# Reference: http://comments.gmane.org/gmane.mail.postfix.policyd/826
RECIPIENTTHROTTLE=0
</pre>}}

Note: You may only enable '''SENDER_THROTTLE_SASL''' or '''SENDER_THROTTLE_HOST''' but '''NOT''' both.

* Edit '''/etc/init.d/policyd''', set '''ENABLE_SENDER_THROTTLE='YES'''' to start another policyd instance for throttling:
{{cfg|/etc/init.d/policyd|<pre>
ENABLE_SENDER_THROTTLE="YES"
</pre>}}

* Restart policyd service:
{{cmd|<pre>
# /etc/init.d/policyd restart
</pre>}}

It will listen on two ports: 10031, 10032. You can verify it via command '''netstat''':
{{cmd|<pre>
# netstat -ntlp | grep -i 1003
tcp 0 0 127.0.0.1:10031 0.0.0.0:* LISTEN 3454/policyd
tcp 0 0 127.0.0.1:10032 0.0.0.0:* LISTEN 3459/policyd
</pre>}}

* Enable throttling in Postfix '''/etc/postfix/main.cf''':
{{cfg|/etc/postfix/main.cf|<pre>
smtpd_end_of_data_restrictions = check_policy_service inet:127.0.0.1:10032
</pre>}}

Restart postfix:
{{cmd|<pre>
# /etc/init.d/postfix restart
</pre>}}

That's all.

Refer to Policyd official documentation to set throttling: http://policyd.sourceforge.net/readme.html

[[Category: iRedMail]]
[[Category: iRedMail/FAQ]]
[[Category: FAQ]]
[[Category: Policyd]]
[[Category: Throttling]]

IRedMail/FAQ/Enable.Throttling/RHEL.CentOS

ZhangHuangbin — Mon, 22 Apr 2013 16:29:39 GMT

ZhangHuangbin:

iRedMail ships Policyd-1.8.x for sender & recipient throttling, but it's disabled by default. You can enable it by follow below steps on RHEL/CentOS:

* Disable sender throttling in '''/etc/postfix-policyd.conf''', but enable recipient throttling:
{{cfg|/etc/policyd.conf|<pre>
SENDERTHROTTLE=0
SENDER_THROTTLE_SASL=0
SENDER_THROTTLE_HOST=0

RECIPIENTTHROTTLE=0
</pre>}}

* Enable throttling in '''/etc/policyd_sender_throttle.conf''':
{{cfg|/etc/policyd_sender_throttle.conf|<pre>
SENDERTHROTTLE=1
SENDER_THROTTLE_SASL=1
SENDER_THROTTLE_HOST=0

# Disable recipient throttling in this instance.
# Recipient Throttling can not work at smtpd_end_of_data_restrictions. Policyd v2 (a.k.a. Cluebringer)
# overcomes this and tracks the recipients for each smtpd instance. To track quotas
# precisely v2 can be used in smtpd_recipient_restrictions and smtpd_end_of_data_restrictions.
# v2 knows about the various restrictions.
RECIPIENTTHROTTLE=0
</pre>}}

Note: You may only enable '''SENDER_THROTTLE_SASL''' or '''SENDER_THROTTLE_HOST''' but '''NOT''' both.

* Edit '''/etc/init.d/policyd''', set '''ENABLE_SENDER_THROTTLE='YES'''' to start another policyd instance for throttling:
{{cfg|/etc/init.d/policyd|<pre>
ENABLE_SENDER_THROTTLE="YES"
</pre>}}

* Restart policyd service:
{{cmd|<pre>
# /etc/init.d/policyd restart
</pre>}}

It will listen on two ports: 10031, 10032. You can verify it via command '''netstat''':
{{cmd|<pre>
# netstat -ntlp | grep -i 1003
tcp 0 0 127.0.0.1:10031 0.0.0.0:* LISTEN 3454/policyd
tcp 0 0 127.0.0.1:10032 0.0.0.0:* LISTEN 3459/policyd
</pre>}}

* Enable throttling in Postfix '''/etc/postfix/main.cf''':
{{cfg|/etc/postfix/main.cf|<pre>
smtpd_end_of_data_restrictions = check_policy_service inet:127.0.0.1:10032
</pre>}}

Restart postfix:
{{cmd|<pre>
# /etc/init.d/postfix restart
</pre>}}

That's all.

Refer to Policyd official documentation to set throttling: http://policyd.sourceforge.net/readme.html

[[Category: iRedMail]]
[[Category: iRedMail/FAQ]]
[[Category: FAQ]]
[[Category: Policyd]]
[[Category: Throttling]]

IRedMail/FAQ/Enable.Throttling/RHEL.CentOS

ZhangHuangbin — Mon, 22 Apr 2013 16:28:16 GMT

ZhangHuangbin:

iRedMail ships Policyd-1.8.x for sender & recipient throttling, but it's disabled by default. You can enable it by follow below steps on RHEL/CentOS:

* Disable sender throttling in '''/etc/postfix-policyd.conf''', but enable recipient throttling:
{{cfg|/etc/policyd.conf|<pre>
SENDERTHROTTLE=0
SENDER_THROTTLE_SASL=0
SENDER_THROTTLE_HOST=0

RECIPIENTTHROTTLE=0
</pre>}}

* Enable throttling in '''/etc/policyd_sender_throttle.conf''':
{{cfg|/etc/policyd_sender_throttle.conf|<pre>
SENDERTHROTTLE=1
SENDER_THROTTLE_SASL=1
SENDER_THROTTLE_HOST=0

# Disable recipient throttling in this instance.
# Recipient Throttling can not work at smtpd_end_of_data_restrictions. This has nothing to do
# with Policyd but an is Postfix limitation.
RECIPIENTTHROTTLE=0
</pre>}}

Note: You may only enable '''SENDER_THROTTLE_SASL''' or '''SENDER_THROTTLE_HOST''' but '''NOT''' both.

* Edit '''/etc/init.d/policyd''', set '''ENABLE_SENDER_THROTTLE='YES'''' to start another policyd instance for throttling:
{{cfg|/etc/init.d/policyd|<pre>
ENABLE_SENDER_THROTTLE="YES"
</pre>}}

* Restart policyd service:
{{cmd|<pre>
# /etc/init.d/policyd restart
</pre>}}

It will listen on two ports: 10031, 10032. You can verify it via command '''netstat''':
{{cmd|<pre>
# netstat -ntlp | grep -i 1003
tcp 0 0 127.0.0.1:10031 0.0.0.0:* LISTEN 3454/policyd
tcp 0 0 127.0.0.1:10032 0.0.0.0:* LISTEN 3459/policyd
</pre>}}

* Enable throttling in Postfix '''/etc/postfix/main.cf''':
{{cfg|/etc/postfix/main.cf|<pre>
smtpd_end_of_data_restrictions = check_policy_service inet:127.0.0.1:10032
</pre>}}

Restart postfix:
{{cmd|<pre>
# /etc/init.d/postfix restart
</pre>}}

That's all.

Refer to Policyd official documentation to set throttling: http://policyd.sourceforge.net/readme.html

[[Category: iRedMail]]
[[Category: iRedMail/FAQ]]
[[Category: FAQ]]
[[Category: Policyd]]
[[Category: Throttling]]

IRedMail/FAQ/Enable.Throttling/RHEL.CentOS

ZhangHuangbin — Mon, 22 Apr 2013 16:26:57 GMT

ZhangHuangbin:

iRedMail ships Policyd-1.8.x for sender & recipient throttling, but it's disabled by default. You can enable it by follow below steps on RHEL/CentOS:

* Disable sender throttling in '''/etc/postfix-policyd.conf''', but enable recipient throttling:
{{cfg|/etc/policyd.conf|<pre>
SENDERTHROTTLE=0
SENDER_THROTTLE_SASL=0
SENDER_THROTTLE_HOST=0

RECIPIENTTHROTTLE=0
</pre>}}

* Enable throttling in '''/etc/policyd_sender_throttle.conf''':
{{cfg|/etc/policyd_sender_throttle.conf|<pre>
SENDERTHROTTLE=1
SENDER_THROTTLE_SASL=1
SENDER_THROTTLE_HOST=0

# Disable recipient throttling in this instance.
# Recipient Throttling can not work at smtpd_end_of_data_restrictions.
RECIPIENTTHROTTLE=0
</pre>}}

Note: You may only enable '''SENDER_THROTTLE_SASL''' or '''SENDER_THROTTLE_HOST''' but '''NOT''' both.

* Edit '''/etc/init.d/policyd''', set '''ENABLE_SENDER_THROTTLE='YES'''' to start another policyd instance for throttling:
{{cfg|/etc/init.d/policyd|<pre>
ENABLE_SENDER_THROTTLE="YES"
</pre>}}

* Restart policyd service:
{{cmd|<pre>
# /etc/init.d/policyd restart
</pre>}}

It will listen on two ports: 10031, 10032. You can verify it via command '''netstat''':
{{cmd|<pre>
# netstat -ntlp | grep -i 1003
tcp 0 0 127.0.0.1:10031 0.0.0.0:* LISTEN 3454/policyd
tcp 0 0 127.0.0.1:10032 0.0.0.0:* LISTEN 3459/policyd
</pre>}}

* Enable throttling in Postfix '''/etc/postfix/main.cf''':
{{cfg|/etc/postfix/main.cf|<pre>
smtpd_end_of_data_restrictions = check_policy_service inet:127.0.0.1:10032
</pre>}}

Restart postfix:
{{cmd|<pre>
# /etc/init.d/postfix restart
</pre>}}

That's all.

Refer to Policyd official documentation to set throttling: http://policyd.sourceforge.net/readme.html

[[Category: iRedMail]]
[[Category: iRedMail/FAQ]]
[[Category: FAQ]]
[[Category: Policyd]]
[[Category: Throttling]]

Integration/Active.Directory.iRedMail

ZhangHuangbin — Fri, 19 Apr 2013 02:26:48 GMT

ZhangHuangbin: /* Enable LDAP query with AD in Postfix */

__TOC__

= Summary =

'''NOTE''': We just tested this tutorial on Windows 2000, 2003, 2008 R2 server, if you tested it on other versions and works well, please let us know. [http://iredmail.org/contact.html Contact us].

With AD + iRedMail integration, you can get below features:

* User authentication against Windows Active Directory. You can now manage mail domains, users, mail lists with AD.
* Mail list support with group in AD.
* Global LDAP Address Book with AD in Roundcube Webmail.
* Account status support. Disable user in Active Directory will cause this account disabled in iRedMail.

Since AD uses different LDAP schema, you will lose some iRedMail special features. e.g.

* Per-user, per-domain service control with LDAP (e.g. enable/disable POP3/IMAP/SMTP services). You should use hash file instead.
* [TO BE CONTINUED]

= Requirements =

To integrate Microsoft Active Directory with iRedMail, you should have:

* A working Linux/BSD server with iRedMail+OpenLDAP installed.
* A working Microsoft Windows (2000/2003) server, with Active Directory installed and working properly, listen on port 389 (ldap://) or 636 (ldaps://), and allow LDAP connections from iRedMail server.

= Install iRedMail =

Please install iRedMail on Linux/BSD with OpenLDAP backend first, we will achieve this AD integration by simply modify some configure files.

Here is [http://iredmail.org/doc.html#installation_guide iRedMail installaion guides].

= Integrate Microsoft Active Directory =

We assume:
* Hostname of your AD server is 'ad.example.com', listen on port 389.
** We will use this hostname below, you can replace it by IP address of this AD server if you want.
** If you want to force LDAP connection with LDAPS, use port 636 instead.
* Base dn in AD is "dc=example,dc=com", email addresses of all users are ends with '@example.com' (Your mail domain is 'example.com').
* All user accounts and mail list accounts are placed under dn "cn=Users,dc=example,dc=com". '''Note:''' dn is case-insensitive.
* For ldap connection, protocol version '3' is recommended. All pupular LDAP servers support LDAP protocol version 3.
* Store all mails on Linux/BSD servers, not on AD server.
** Storage directory is '''/var/vmail/vmail1''', same as default in iRedMail.
** Mailbox of user "support@example.com" will be '''/var/vmail/vmail1/example.com/support/Maildir/''', maildir format.

== Create user account in AD, used for LDAP query ==

With iRedMail + OpenLDAP, we have a low-privileged account "cn=vmail,dc=xxx,dc=xxx" for query only. So we suggest you create a same account '''vmail''' in AD, with complex password.

'''NOTE''':
* [http://www.iredmail.org/forum/post8630.html#p8630 Dovecot will treat characters as comment after a inline '#', so please just don't use '#' in password]

=== Test AD query with ldap command line tool on iRedMail server===
We should make sure this newly created user is able to connect to AD server, so please verify it with below command on iRedMail server:

{{cmd|<pre>
# ldapsearch -x -h ad.example.com -D 'vmail' -W -b 'cn=users,dc=example,dc=com'
Enter password: password_of_vmail
</pre>}}
If it prints all users stored in AD server, then it's working as expected.

== Enable LDAP query with AD in Postfix ==

We will execute some commands to modify Postfix settings to:

* Disable unused iRedMail special settings.
* Authenticate against AD server instead of local OpenLDAP server.

'''Note''': we will create three AD query files later:
* /etc/postfix/ad_virtual_mailbox_maps.cf
* /etc/postfix/ad_virtual_group_maps.cf
* /etc/postfix/ad_sender_login_maps.cf

* Disable unused iRedMail special settings:
{{cmd|<pre>
# postconf -e virtual_alias_maps=''
# postconf -e sender_bcc_maps=''
# postconf -e recipient_bcc_maps=''
# postconf -e relay_domains=''
# postconf -e relay_recipient_maps=''
</pre>}}

* Add your mail domain in "smtpd_sasl_local_domain" and "virtual_mailbox_domains":
{{cmd|<pre>
# postconf -e smtpd_sasl_local_domain='example.com'
# postconf -e virtual_mailbox_domains='example.com'
</pre>}}

* Change transport maps setting:
{{cmd|<pre>
# postconf -e transport_maps='hash:/etc/postfix/transport'
</pre>}}

* Enable AD query. Note: We will create these 3 files later.
** Verify SMTP senders
{{cmd|<pre>
# postconf -e smtpd_sender_login_maps='proxy:ldap:/etc/postfix/ad_sender_login_maps.cf'
</pre>}}

** Used to verify local mail users
{{cmd|<pre>
# postconf -e virtual_mailbox_maps='proxy:ldap:/etc/postfix/ad_virtual_mailbox_maps.cf'
</pre>}}

** Used to verify local mail lists/groups.
{{cmd|<pre>
# postconf -e virtual_alias_maps='proxy:ldap:/etc/postfix/ad_virtual_group_maps.cf'
</pre>}}

* Create/Edit file: '''/etc/postfix/transport'''.
{{cfg|/etc/postfix/transport|<pre>
example.com dovecot
</pre>}}
Note: '''dovecot''' here is a Postfix transport defined in /etc/postfix/master.cf, used to deliver received emails to user mailboxes.

Run 'postmap' so that postfix can read it:
{{cmd|<pre>
# postmap hash:/etc/postfix/transport
</pre>}}

* Create/Edit file: '''/etc/postfix/ad_sender_login_maps.cf''':
{{cfg|/etc/postfix/ad_sender_login_maps.cf|<pre>
server_host = ad.example.com
server_port = 389
version = 3
bind = yes
start_tls = no
bind_dn = vmail
bind_pw = password_of_vmail
search_base = cn=users,dc=example,dc=com
scope = sub
query_filter = (&(userPrincipalName=%s)(objectClass=person)(!(userAccountControl:1.2.840.113556.1.4.803:=2)))
result_attribute= userPrincipalName
debuglevel = 0
</pre>}}

* Create/Edit file: '''/etc/postfix/ad_virtual_mailbox_maps.cf'''
{{cfg|/etc/postfix/ad_virtual_mailbox_maps.cf|<pre>
server_host = ad.example.com
server_port = 389
version = 3
bind = yes
start_tls = no
bind_dn = vmail
bind_pw = passwd_of_vmail
search_base = cn=users,dc=example,dc=com
scope = sub
query_filter = (&(objectclass=person)(userPrincipalName=%s))
result_attribute= userPrincipalName
result_format = %d/%u/Maildir/
debuglevel = 0
</pre>}}

'''Note:''' Here, we define users' mailboxes to be "example.com/username/Maildir/" in '''"result_format"''' setting.

Maildir of the first example user created during iRedMail installation, www@example.com, is 'example.com/w/w/w/www-[TIMESTAMP]/Maildir/', and this maildir path is stored in OpenLDAP (attribute '''"mailMessageStore"'''). But we don't store maildir path in Active Directory, so we hard-code maildir path here.

* Create/Edit file: '''/etc/postfix/ad_virtual_group_maps.cf'''
{{cfg|/etc/postfix/ad_virtual_group_maps.cf|<pre>
server_host = ad.example.com
server_port = 389
version = 3
bind = yes
start_tls = no
bind_dn = vmail
bind_pw = password_of_vmail
search_base = cn=users,dc=example,dc=com
scope = sub
query_filter = (&(objectClass=group)(mail=%s))
special_result_attribute = member
leaf_result_attribute = mail
result_attribute= userPrincipalName
debuglevel = 0
</pre>}}
'''Note''':
* If your user have email address in both "mail" and "userPrincipalName", you will get duplicate result. Comment 'leaf_result_attribute' can fix it.
* If your group account doesn't contains attribute 'mail' and 'userPrincipalName', please try 'query_filter = (&(objectClass=group)(sAMAccountName=%u))' instead.

Also, we need to remove iRedAPD related settings in Postfix:
* Open /etc/postfix/main.cf
* Remove this setting: '''check_policy_service inet:127.0.0.1:7777'''.

== Verify LDAP query with AD in Postfix ==

We can use command line tool '''postmap''' to verify AD query in postfix.

* Query mail user:
{{cmd|<pre>
# postmap -q user@example.com ldap:/etc/postfix/ad_virtual_mailbox_maps.cf
example.com/user/Maildir/
</pre>}}

* '''DEBUG''': If nothing returned by the command, it means LDAP query doesn't get expected result. Please set '''"debuglevel = 1"''' in file '''"ad_sender_login_maps.cf"''', then query again, it now will print more debug message, If you're not familiar with this kind of output message, please post the debug message in our [http://www.iredmail.org/forum/ forum] to ask help.

* Verify sender login check:
{{cmd|<pre>
# postmap -q user@example.com ldap:/etc/postfix/ad_sender_login_maps.cf
user@example.com
</pre>}}

* Verify mail list/group. Steps:
** Create a group in AD, e.g. testgroup@example.com.
** Assign at least one member to this group.
** Execute below command on iRedMail server to verify it can get members.
{{cmd|<pre>
# postmap -q testgroup@example.com ldap:/etc/postfix/ad_virtual_group_maps.cf
member01@example.com
member02@example.com
</pre>}}
'''postmap''' will return nothing if 1) mail group doesn't exist; 2) group doesn't have any members.

== Enable LDAP query with AD in Dovecot ==

We need to modify '''/etc/dovecot-ldap.conf''' (RHEL/CentOS) or '''/etc/dovecot/dovecot-ldap.conf''' (Debian/Ubuntu), let dovecot query AD instead of local OpenLDAP server.

{{cfg|dovecot-ldap.conf|<pre>
hosts = ad.example.com:389
ldap_version = 3
auth_bind = yes
dn = vmail
dnpass = passwd_of_vmail
base = cn=users,dc=example,dc=com
scope = subtree
deref = never
user_filter = (&(userPrincipalName=%u)(objectClass=person)(!(userAccountControl:1.2.840.113556.1.4.803:=2)))
pass_filter = (&(userPrincipalName=%u)(objectClass=person)(!(userAccountControl:1.2.840.113556.1.4.803:=2)))
pass_attrs = userPassword=password
default_pass_scheme = CRYPT
user_attrs = =home=/var/vmail/vmail1/%Ld/%Ln/Maildir/,=mail=maildir:/var/vmail/vmail1/%Ld/%Ln/Maildir/
</pre>}}

Now restart dovecot service to make it work immediately.

'''Note''': we don't have per-user quota limit here, you can set a hard-coded quota for all users in '''/etc/dovecot.conf''' (RHEL/CentOS) or '''/etc/dovecot/dovecot.conf''' (Debian/Ubuntu). Example:
{{cfg|dovecot.conf|<pre>
plugin {
# --- SKIP OTHER SETTINGS HERE ---
# Format: integer + M/G/T.
# M -> MB, G -> GB, T -> TB.
quota_rule = *:storage=1G
}
</pre>}}

== Verify LDAP query with AD in Dovecot ==
We can use command '''telnet''' to verify AD query in Dovecot.

'''Note''': Please do restart dovecot before testing.

{{cmd|<pre>
# telnet localhost 143 # <- Type this
* OK [...] Dovecot ready.

. login user@example.com password_of_user # <- Type this
. OK [...] Logged in
# <- Quit telnet with "Ctrl+]", then type 'quit'.
</pre>}}

Note: You just type '''. login user@example.com password''' (Do NOT miss the dot) in above testing, if it returns '''Logged in''', then dovecot + AD works as expected.

== Enable Global LDAP Address Book wih AD in Roundcube webmail ==

Edit roundcube config file: /var/www/roundcubemail/config/main.inc.php (RHEL/CentOS) or /usr/share/apache2/roundcubemail/config/main.inc.php (Debian/Ubuntu).

You can remove exist LDAP address book which stored in OpenLDAP, and add a new one with AD.

{{cfg|main.inc.php|<pre>

#
# "sql" is personal address book stored in roundcube database.
# "example.com" is new LDAP address book with AD, we will create it below.
#
$rcmail_config['autocomplete_addressbooks'] = array("sql", "example.com");

#
# Global LDAP Address Book with AD.
#
$rcmail_config['ldap_public']["example.com"] = array(
'name' => 'Global Address Book',
'hosts' => array("ad.example.com"), // <- Set AD hostname or IP address here.
'port' => 389,
'use_tls' => false, // <- Set to true if you want to use LDAPS. Change port to 636 on above line too.

// ---- Used to search accounts only in the same domain. ----
'user_specific' => false,
'base_dn' => "cn=users,dc=example,dc=com", // <- Set base dn in AD
'bind_dn' => "vmail", # <- bind dn
'bind_pass' => "password_of_vmail", // <- bind password
'writable' => false, # <- Do not allow mail user write data back to AD.
'ldap_version' => "3",

// ---- Search ----
//'search_fields' => array('displayname', 'userprincipalname', 'sn', 'givenname',), // <- fields to search in
'search_fields' => array('mail', 'cn', 'sAMAccountName', 'displayname', 'sn', 'givenName'),
//'name_field' => 'displayname',
'name_field' => 'cn',
//'email_field' => 'userprincipalname',
'email_field' => 'mail',
'surname_field' => 'sn',
//'firstname_field' => 'givenname',
'firstname_field' => 'givenName',
//'sort' => 'displayname',
'sort' => 'cn',
'scope' => 'sub',
//'filter' => "(&(objectclass=person)(!(userAccountControl:1.2.840.113556.1.4.803:=2)))",
'filter' => "(mail=*@*)",
'fuzzy_search' => true
);
</pre>}}

= Additions =

* If your mail domain name is different than Windows Active Directory domain: http://www.iredmail.org/forum/topic3165-integration-with-windows-domain.html

= ChangeLog =
* 2011-10-22: Use 'postconf -e' to set Postfix settings instead of edit main.cf directly.
* 2011-07-15: Replace 'userAccountControl=514' with 'userAccountControl:1.2.840.113556.1.4.803:=2'. This will still work if the user has additional attributes like password expired or never changes. Thanks Rick Culler <rculler@caresouth>.

Upgrade/iRedMail/0.8.3-0.8.4

ZhangHuangbin — Fri, 05 Apr 2013 09:09:55 GMT

ZhangHuangbin: /* Use the latest LDAP schema file provided by iRedMail */

__TOC__

= ChangeLog =
* 2013-03-28: Update /etc/iredmail-release with iRedMail version number.
* 2013-03-28: Upgrade Roundcube webmail to the latest 0.8.6.
* 2013-03-25: [ldap] Fix incorrect LDAP query filter in Postfix.
* 2013-01-08: [sql] Add 4 new columns in table '''vmail.mailbox''' for MySQL/PostgreSQL backends.
* 2012-10-24: [ldap] Supports alias domains in Postfix per-user bcc lookup files.

= General (All backends should apply these steps) =

== Update /etc/iredmail-release with iRedMail version number ==
iRedMail stores the initial version number in /etc/iredmail-release after installation completed, 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:
{{cfg|/etc/iredmail-release|<pre>
0.8.6
</pre>}}

== Add new alias 'virusalert' in Postfix for Amavisd ==
Amavisd will send an email notification to address "virusalert@[YOUR_HOSTNAME]" by default, but we don't have this user in Postfix alias file (/etc/postfix/aliases on Linux/OpenBSD, or /usr/local/etc/postfix/aliases on FreeBSD) or SQL/LDAP database, so emails are not delivered. Below steps add a alias in Postfix alias file, and it will be forwarded to root user by default.

Add new alias (Note, use '/usr/local/etc/postfix/aliases' on FreeBSD instead), and update the database:
{{cmd|<pre>
# echo 'virusalert: root' >> /etc/postfix/aliases
# postalias /etc/postfix/aliases
</pre>}}

== Upgrade Roundcube webmail to the latest 0.8.6 ==
There's zero day vulnerability in Roundcubemail-0.8.5 and older releases, please follow this tutorial to upgrade Roundcube webmail to the latest 0.8.6 immediately: [[IRedMail/FAQ/Upgrade.Roundcube.Webmail |Upgrade Roundcube webmail]]

About the zero day vulnerability, please refer to this thread: http://lists.roundcube.net/pipermail/dev/2013-March/022328.html

== Upgrade iRedAPD (Postfix policy server) to the latest 1.4.0 ==
Please follow this tutorial to upgrade iRedAPD to the latest stable release: [[IRedMail/FAQ/Upgrade.iRedAPD |How to upgrade iRedAPD]]

== Upgrade iRedAdmin (open source edition) to the latest 0.2.1 ==
Please follow this tutorial to upgrade iRedAdmin open source edition to the latest stable release: [[IRedMail/FAQ/Upgrade.iRedAdmin.Open.Source.Edition |How to upgrade iRedAdmin (open source edition) to the latest stable release]]

= OpenLDAP backend special =
== Fix incorrect LDAP query filter in Postfix ==
If you add external email addresses as mail list members, iRedAdmin-Pro will store them in attribute '''memberOfGroup''', this will cause exported LDIF data cannot be restored. Below are steps to fix this issue.
=== Use the latest LDAP schema file provided by iRedMail ===
To fix this issue, we need the latest LDAP schema file provided by iRedMail. Steps are:
* Download the newest iRedMail ldap schema file
* Copy old ldap schema file as a backup copy
* Replace the old one
* Restart OpenLDAP service.

Here we go:

* On RHEL/CentOS/Scientific Linux (both release 5.x and 6.x), openSUSE, Gentoo, OpenBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/openldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/openldap/schema/
# /etc/init.d/slapd restart # <-- Or: /etc/init.d/ldap restart
</pre>}}

* On Debian/Ubuntu:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/ldap/schema/
# /etc/init.d/slapd restart
</pre>}}

* On FreeBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /usr/local/etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /usr/local/etc/openldap/schema/
# /usr/local/etc/rc.d/slapd restart
</pre>}}

=== Update existing accounts ===
* Download python script used to adding missing values.
{{cmd|<pre>
# cd /root/
# wget https://bitbucket.org/zhb/iredmail/raw/default/extra/update/updateLDAPValues_083_to_084.py
</pre>}}
Open updateLDAPValues_083_to_084.py, config LDAP server related settings in file head. e.g.
File: updateLDAPValues_083_to_084.py
{{cfg|updateLDAPValues_083_to_084.py|<pre>
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'
</pre>}}
Tip:
* You can find them in iRedAdmin config file or iRedMail.tips file under your iRedMail installation directory.
* Use 'cn=Manager' instead of 'cn=vmailadmin' here is ok too.

Execute this script, it will fix incorrect values and add correct ones:
{{cmd|<pre>
# python updateLDAPValues_083_to_084.py
</pre>}}

=== Fix incorrect LDAP query filter in Postfix ===
* On Linux/OpenBSD, please update '''/etc/postfix/ldap/virtual_group_maps.cf'''. On FreeBSD, update '''/usr/local/etc/postfix/ldap/virtual_group_maps.cf''' instead.
{{cfg|virtual_group_maps.cf|<pre>
# OLD setting
#query_filter = (&(memberOfGroup=%s)(accountStatus=active)(enabledService=mail)(enabledService=deliver)(|(objectClass=mailUser)(objectClass=mailExternalUser)))

# New setting
query_filter = (&(accountStatus=active)(enabledService=mail)(enabledService=deliver)(|(memberOfGroup=%s)(shadowAddress=%s))(|(objectClass=mailUser)(objectClass=mailExternalUser)))
</pre>}}

== Supports alias domains in Postfix per-user bcc lookup files ==
* In /etc/postfix/ldap/sender_bcc_maps_user.cf, replace "(mail=%s)" by "(|(mail=%s)(&(enabledService=shadowaddress)(shadowAddress=%s)))" in parameter "query_filter =". The final LDAP filter looks like below:
{{cfg|ldap/sender_bcc_maps_user.cf|<pre>
query_filter = (&(|(mail=%s)(&(enabledService=shadowaddress)(shadowAddress=%s)))(objectClass=mailUser)(accountStatus=active)(enabledService=mail)(enabledService=senderbcc))
</pre>}}

* Perform the same modification in file /etc/postfix/ldap/recipient_bcc_maps_user.cf, the final LDAP filter looks like below:
{{cfg|ldap/recipient_bcc_maps_user.cf|<pre>
query_filter = (&(|(mail=%s)(&(enabledService=shadowaddress)(shadowAddress=%s)))(objectClass=mailUser)(accountStatus=active)(enabledService=mail)(enabledService=recipientbcc))
</pre>}}

* Restarting Postfix service is required.

== Create addition SQL index for Amavisd database ==
We need one more SQL index for Amavisd database, it's used to speed up performance of viewing quarantined mails.
* Important Note: It will take a long time if you have many records in table '''msgs'''.
{{cmd|<pre>
$ mysql -uroot -p
mysql> USE amavisd;
mysql> ALTER TABLE msgs ADD INDEX (quar_type);
</pre>}}

= MySQL backend special =
== Add 4 new columns used for per-user restriction ==
New version of iRedAPD (Postfix policy daemon) requires 4 new columns in table '''vmail.mailbox''': allowedsenders, rejectedsenders, allowedrecipients, rejectedrecipients. They're used for per-user restriction. For example, you can now define who can send email to your local user, or your user can send email to which external domains or users.

Please login to MySQL server as root user, execute SQL commands to add required columns and indexes.
{{cmd|<pre>
# mysql -uroot -p
mysql> USE vmail;
mysql> ALTER TABLE mailbox ADD COLUMN allowedsenders TEXT NOT NULL DEFAULT '';
mysql> ALTER TABLE mailbox ADD COLUMN rejectedsenders TEXT NOT NULL DEFAULT '';
mysql> ALTER TABLE mailbox ADD COLUMN allowedrecipients TEXT NOT NULL DEFAULT '';
mysql> ALTER TABLE mailbox ADD COLUMN rejectedrecipients TEXT NOT NULL DEFAULT '';
</pre>}}

Supported formats of sender/recipients are:
* user@example.com: single user
* @example.com: single domain
* @'''.'''example.com: domain and its sub domain
* '''@.''': any users.

Multiple senders/recipients must be separated by comma, for example:
{{cmd|<pre>
sql> INSERT INTO mailbox SET allowedsenders='@gmail.com,user@example.com';
</pre>}}
== Create addition SQL index for Amavisd database ==
We need one more SQL index for Amavisd database, it's used to speed up performance of viewing quarantined mails.
* Important Note: It will take a long time if you have many records in table '''msgs'''.
{{cmd|<pre>
$ mysql -uroot -p
mysql> USE amavisd;
mysql> ALTER TABLE msgs ADD INDEX (quar_type);
</pre>}}

= PostgreSQL backend special =
== Add 4 new columns used for per-user restriction ==
New version of iRedAPD (Postfix policy daemon) requires 4 new columns in table '''vmail.mailbox''': allowedsenders, rejectedsenders, allowedrecipients, rejectedrecipients. They're used for per-user restriction. For example, you can now define who can send email to your local user, or your user can send email to which external domains or users.

Please switch to PostgreSQL daemon user, then execute SQL commands to add required columns and indexes:
On Linux, PostgreSQL daemon user is postgres.
On FreeBSD, PostgreSQL daemon user is pgsql.
On OpenBSD, PostgreSQL daemon user is """_postgresql".
{{cmd|<pre>
# su - postgres
$ psql -d vmail
sql> ALTER TABLE mailbox ADD COLUMN allowedsenders TEXT NOT NULL DEFAULT '';
sql> ALTER TABLE mailbox ADD COLUMN rejectedsenders TEXT NOT NULL DEFAULT '';
sql> ALTER TABLE mailbox ADD COLUMN allowedrecipients TEXT NOT NULL DEFAULT '';
sql> ALTER TABLE mailbox ADD COLUMN rejectedrecipients TEXT NOT NULL DEFAULT '';
</pre>}}

Supported formats of sender/recipients are:
* user@example.com: single user
* @example.com: single domain
* @'''.'''example.com: domain and its sub domain
* '''@.''': any users.

Multiple senders/recipients must be separated by comma, for example:
{{cmd|<pre>
sql> INSERT INTO mailbox SET allowedsenders='@gmail.com,user@example.com';
</pre>}}

== Create addition SQL index for Amavisd database ==
We need one more SQL index for Amavisd database, it's used to speed up performance of viewing quarantined mails.
* Important Note: It will take a long time if you have many records in table '''msgs'''.

Please switch to PostgreSQL daemon user, then execute SQL commands to add required columns and indexes:
* On Linux, PostgreSQL daemon user is postgres.
* On FreeBSD, PostgreSQL daemon user is pgsql.
* On OpenBSD, PostgreSQL daemon user is """_postgresql".
{{cmd|<pre>
# su - postgres
$ psql -d amavisd
sql> CREATE INDEX idx_msgs_quar_type ON msgs (quar_type);
</pre>}}

Upgrade/iRedMail/0.8.4-0.8.5

ZhangHuangbin — Wed, 03 Apr 2013 16:01:35 GMT

ZhangHuangbin: /* ChangeLog */

Upgrade/iRedMail/0.8.4-0.8.5

ZhangHuangbin — Wed, 03 Apr 2013 16:00:42 GMT

ZhangHuangbin:

__TOC__

= ChangeLog =
= General (All backends should apply these steps) =
= OpenLDAP backend special =
== Use the latest LDAP schema file provided by iRedMail ==
With the latest LDAP schema file, we can use attribute '''preferredLanguage''' for mail domain object, it's used to storage short language code (e.g. de_DE, en_US) for newly created mail users. Steps to use the latest LDAP schema file are:

* Download the newest iRedMail ldap schema file
* Copy old ldap schema file as a backup copy
* Replace the old one
* Restart OpenLDAP service.

Here we go:

* On RHEL/CentOS/Scientific Linux (both release 5.x and 6.x), openSUSE, Gentoo, OpenBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/openldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/openldap/schema/
# /etc/init.d/slapd restart # <-- Or: /etc/init.d/ldap restart
</pre>}}

* On Debian/Ubuntu:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/ldap/schema/
# /etc/init.d/slapd restart
</pre>}}

* On FreeBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /usr/local/etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /usr/local/etc/openldap/schema/
# /etc/init.d/slapd restart
</pre>}}

= MySQL backend special =
== Add one new column used for store preferred language for newly created mail users ==
We now storage short language code (e.g. de_DE, en_US) for newly created mail users, it requires a new SQL column '''defaultlanguage''' for this.

Please login to MySQL server as root user, execute SQL commands to add required columns and indexes.
{{cmd|<pre>
# mysql -uroot -p
mysql> USE vmail;
mysql> ALTER TABLE domain ADD COLUMN defaultlanguage VARCHAR(5) NOT NULL DEFAULT 'en_US';
</pre>}}

= PostgreSQL backend special =
== Add one new column used for store preferred language for newly created mail users ==

We now storage short language code (e.g. de_DE, en_US) for newly created mail users, it requires a new SQL column '''defaultlanguage''' for this.

Please switch to PostgreSQL daemon user, then execute SQL commands to add required columns and indexes:
On Linux, PostgreSQL daemon user is postgres.
On FreeBSD, PostgreSQL daemon user is pgsql.
On OpenBSD, PostgreSQL daemon user is """_postgresql".
{{cmd|<pre>
# su - postgres
$ psql -d vmail
sql> ALTER TABLE domain ADD COLUMN defaultlanguage VARCHAR(5) NOT NULL DEFAULT 'en_US';
</pre>}}

Upgrade/iRedMail/0.8.4-0.8.5

ZhangHuangbin — Wed, 03 Apr 2013 15:57:51 GMT

ZhangHuangbin: /* Use the latest LDAP schema file provided by iRedMail */

Upgrade/iRedMail/0.8.4-0.8.5

ZhangHuangbin — Wed, 03 Apr 2013 15:55:35 GMT

ZhangHuangbin: Created page with '__TOC__ = ChangeLog = = General (All backends should apply these steps) = = OpenLDAP backend special = == Use the latest LDAP schema file provided by iRedMail == = MySQL backend…'

__TOC__

= ChangeLog =
= General (All backends should apply these steps) =
= OpenLDAP backend special =
== Use the latest LDAP schema file provided by iRedMail ==
= MySQL backend special =
== Add one new column used for store preferred language for newly created mail users ==
= PostgreSQL backend special =
== Add one new column used for store preferred language for newly created mail users ==

Install/iRedMail/FreeBSD.Jail

ZhangHuangbin — Wed, 03 Apr 2013 15:04:19 GMT

ZhangHuangbin: /* Summary */

__TOC__

= Summary =

* This tutorial describes how to create a FreeBSD Jail with ezjail, and install the latest iRedMail in Jail.
* We use hostname '''mx.example.com''' and IP address '''172.16.122.244''' for our Jail server.

Notes:

* This tutorial was tested with FreeBSD 9 and the latest ports tree, but it should work on FreeBSD 8 and 10 too.
* All backends available in iRedMail (OpenLDAP, MySQL, PostgreSQL) were tested, work like a charm. :)

= Requirements =

* The latest stable release of iRedMail. You can download it here: http://www.iredmail.org/download.html
* Port '''sysutils/ezjail''' for FreeBSD.

= Preparation =

== Set a proper hostname and IP address for Jail server ==
We use hostname '''mx.example.com''' and internal IP address '''172.16.122.244''' for example. We created an alias IP address on network interface '''em0''', so we have below setting in '''/etc/rc.conf''' for this IP address:
{{cfg|/etc/rc.conf|<pre>
ifconfig_em0_alias0="inet 172.16.122.244 netmask 255.255.255.0"

# Settings for our Jail: mx.example.com.
jail_mx_example_com_hostname="mx.example.com"
jail_mx_example_com_ip="172.16.122.244"
</pre>}}

== Install sysutils/ezjail and add required settings ==
* Install ezjail with ports tree:
{{cmd|<pre>
# cd /usr/ports/sysutils/ezjail/
# make install clean
</pre>}}

* Enable Jail by adding below setting in '''/etc/rc.conf''':
{{cfg|/etc/rc.conf|<pre>
# Start ezjail while system start up
ezjail_enable="YES"

# Required by PostgreSQL, otherwise initializing database will fail.
jail_sysvipc_allow="YES"
</pre>}}

* [OPTIONAL] Allow to use '''ping''' command inside Jail by adding below line in '''/etc/sysctl.conf''':
{{cfg|/etc/sysctl.conf|<pre>
security.jail.allow_raw_sockets=1
</pre>}}

* Rebooting system is required after changing '''/etc/rc.conf'''.
{{cmd|<pre># reboot</pre>}}

= Create Jail =

* After system start up, create the base jail that all jails we created later will use:
{{cmd|<pre>
# ezjail-admin install -p
</pre>}}

* create Jail for domain name '''mx.example.com''', bound to internal IP address 172.16.122.244. All files are placed under '''/jails/mx.example.com''':
{{cmd|<pre>
# ezjail-admin create -r /jails/mx.example.com mx.example.com 172.16.122.244
</pre>}}

* Set hostname of Jail in '''/jails/mx.example.com/etc/rc.conf''':
{{cfg|/jails/mx.example.com/etc/rc.conf|<pre>
hostname="mx.example.com"
</pre>}}

* [OPTIONAL] Share /usr/ports/distfiles/ with Jail by adding below line in '''/etc/fstab.mx_example_com''':
** NOTE: Jail will set ports tree to '''/var/ports''' instead of '''/usr/ports''' in /jails/mx.example.com/etc/make.conf, you can either use it or change it to '''/usr/ports'''.
{{cfg|/etc/fstab.mx_example.com|<pre>
/usr/ports/distfiles /jails/mx.example.com/basejail/usr/ports/distfiles nullfs rw 0 0
</pre>}}

* Start Jail.
{{cmd|<pre>
# /usr/local/etc/rc.d/ezjail restart
</pre>}}

* List all Jails:
{{cmd|<pre>
# ezjail-admin list
STA JID IP Hostname Root Directory
--- ---- ---------------- --------------------------------- ------------------------
DS 1 172.16.122.244 mx.example.com /jails/mx.example.com
</pre>}}

= Install iRedMail =

We can now enter this Jail:
{{cmd|<pre>
# ezjail-admin console mx.example.com
</pre>}}

* In Jail, update '''/etc/resolv.conf''' with valid DNS server address(es). For example:
{{cfg|Jail: /etc/resolv.conf|<pre>
nameserver 172.16.122.2
</pre>}}

* In Jail, install binary package '''bash'''. Required by iRedMail.
{{cmd|<pre>
Jail # pkg_add -r bash-static
</pre>}}

* In Jail, Start iRedMail installer with your Jail ip address:
{{cmd|<pre>
Jail # bash
bash # cd /root/iRedMail/
bash # LOCAL_ADDRESS='172.16.122.244' bash iRedMail.sh
</pre>}}

That's all.

Install/iRedMail/FreeBSD.Jail

ZhangHuangbin — Wed, 03 Apr 2013 14:38:38 GMT

ZhangHuangbin: /* Requirements */

__TOC__

= Summary =

This tutorial describes how to create a FreeBSD Jail with ezjail, and install the latest iRedMail in Jail.

We use hostname '''mx.example.com''' and IP address '''172.16.122.244''' for our Jail server.

Notes:

* This tutorial was tested with FreeBSD 9 and the latest ports tree, but it should work on FreeBSD 8 and 10 too.
* All backends available in iRedMail (OpenLDAP, MySQL, PostgreSQL) were tested, work like a charm. :)

= Requirements =

* The latest stable release of iRedMail. You can download it here: http://www.iredmail.org/download.html
* Port '''sysutils/ezjail''' for FreeBSD.

= Preparation =

== Set a proper hostname and IP address for Jail server ==
We use hostname '''mx.example.com''' and internal IP address '''172.16.122.244''' for example. We created an alias IP address on network interface '''em0''', so we have below setting in '''/etc/rc.conf''' for this IP address:
{{cfg|/etc/rc.conf|<pre>
ifconfig_em0_alias0="inet 172.16.122.244 netmask 255.255.255.0"

# Settings for our Jail: mx.example.com.
jail_mx_example_com_hostname="mx.example.com"
jail_mx_example_com_ip="172.16.122.244"
</pre>}}

== Install sysutils/ezjail and add required settings ==
* Install ezjail with ports tree:
{{cmd|<pre>
# cd /usr/ports/sysutils/ezjail/
# make install clean
</pre>}}

* Enable Jail by adding below setting in '''/etc/rc.conf''':
{{cfg|/etc/rc.conf|<pre>
# Start ezjail while system start up
ezjail_enable="YES"

# Required by PostgreSQL, otherwise initializing database will fail.
jail_sysvipc_allow="YES"
</pre>}}

* [OPTIONAL] Allow to use '''ping''' command inside Jail by adding below line in '''/etc/sysctl.conf''':
{{cfg|/etc/sysctl.conf|<pre>
security.jail.allow_raw_sockets=1
</pre>}}

* Rebooting system is required after changing '''/etc/rc.conf'''.
{{cmd|<pre># reboot</pre>}}

= Create Jail =

* After system start up, create the base jail that all jails we created later will use:
{{cmd|<pre>
# ezjail-admin install -p
</pre>}}

* create Jail for domain name '''mx.example.com''', bound to internal IP address 172.16.122.244. All files are placed under '''/jails/mx.example.com''':
{{cmd|<pre>
# ezjail-admin create -r /jails/mx.example.com mx.example.com 172.16.122.244
</pre>}}

* Set hostname of Jail in '''/jails/mx.example.com/etc/rc.conf''':
{{cfg|/jails/mx.example.com/etc/rc.conf|<pre>
hostname="mx.example.com"
</pre>}}

* [OPTIONAL] Share /usr/ports/distfiles/ with Jail by adding below line in '''/etc/fstab.mx_example_com''':
** NOTE: Jail will set ports tree to '''/var/ports''' instead of '''/usr/ports''' in /jails/mx.example.com/etc/make.conf, you can either use it or change it to '''/usr/ports'''.
{{cfg|/etc/fstab.mx_example.com|<pre>
/usr/ports/distfiles /jails/mx.example.com/basejail/usr/ports/distfiles nullfs rw 0 0
</pre>}}

* Start Jail.
{{cmd|<pre>
# /usr/local/etc/rc.d/ezjail restart
</pre>}}

* List all Jails:
{{cmd|<pre>
# ezjail-admin list
STA JID IP Hostname Root Directory
--- ---- ---------------- --------------------------------- ------------------------
DS 1 172.16.122.244 mx.example.com /jails/mx.example.com
</pre>}}

= Install iRedMail =

We can now enter this Jail:
{{cmd|<pre>
# ezjail-admin console mx.example.com
</pre>}}

* In Jail, update '''/etc/resolv.conf''' with valid DNS server address(es). For example:
{{cfg|Jail: /etc/resolv.conf|<pre>
nameserver 172.16.122.2
</pre>}}

* In Jail, install binary package '''bash'''. Required by iRedMail.
{{cmd|<pre>
Jail # pkg_add -r bash-static
</pre>}}

* In Jail, Start iRedMail installer with your Jail ip address:
{{cmd|<pre>
Jail # bash
bash # cd /root/iRedMail/
bash # LOCAL_ADDRESS='172.16.122.244' bash iRedMail.sh
</pre>}}

That's all.

IRedMail/FAQ/Upgrade.iRedAPD

ZhangHuangbin — Mon, 01 Apr 2013 14:24:13 GMT

ZhangHuangbin:

----
This tutorial describes how to upgrade iRedAPD to the latest stable release, iRedAPD-1.4.0. It's applicable on all Linux/BSD distributions supported by iRedMail.

Important notes:
* Since iRedAPD-1.4.0, we use Python source file as config file, not '.ini' format anymore.
* We don't need second instance, '''iredapd-rr''', anymore.
----

* Download the latest stable release here: http://iredmail.org/yum/misc/ For example, iRedAPD-1.4.0.tar.bz2.
* Upload it to your iRedMail server. Assume it's '''/root/iRedAPD-1.4.0.tar.bz2''' on the server.
* Extract downloaded package and move to /opt/.
{{cmd|<pre>
# tar xjf /root/iRedAPD-1.4.0.tar.bz2 -C /opt/
</pre>}}
You get a new directory: /opt/iRedAPD-1.4.0/.

* Set correct owner and permission:
{{cmd|<pre>
# chown -R iredapd:iredapd /opt/iRedAPD-1.4.0
# chmod -R 0700 /opt/iRedAPD-1.4.0
</pre>}}

* Generate new config file from sample file, and set correct file owner and permission.
{{cmd|<pre>
# cd /opt/iRedAPD-1.4.0/
# cp settings.py.sample settings.py
# chown -R iredapd:iredapd settings.py
# chmod -R 0600 settings.py
</pre>}}
WARNING: Config file '''/opt/iredapd/settings.py''' contains sensitive infomation (username, password), please don't make it world-readable. Permission 0600 is the best.

* Please open '''/opt/iredapd/settings.py''', and sync settings with old iRedAPD config file '''/opt/iRedAPD-[OLD-VERSION]/etc/iredapd.ini'''.
** In old version of iRedAPD, all parameters under "[ldap]" section are now new parameters start with '''ldap_'''.
** In old version of iRedAPD, all parameters under "[sql]" (or "[mysql]") section are now new parameters start with '''sql_'''.

* After sync settings, please copy new RC script for your server. We have scripts for different Linux/BSD distributions. Please copy the proper one for your server. For example:
** /opt/iredapd/rc_scripts/iredapd.debian: For Debian and Ubuntu.
** /opt/iredapd/rc_scripts/iredapd.freebsd: For FreeBSD. Please copy to /usr/local/etc/rc.d/.
** /opt/iredapd/rc_scripts/iredapd.gentoo: For Gentoo Linux.
** /opt/iredapd/rc_scripts/iredapd.openbsd: For OpenBSD. Please copy to /etc/rc.d/.
** /opt/iredapd/rc_scripts/iredapd.opensuse: For openSUSE.
** /opt/iredapd/rc_scripts/iredapd.rhel: For Red Hat, CentOS, Scientific Linux.
{{cmd|<pre>
# cp /opt/iredapd/rc_scripts/iredapd.rhel /etc/init.d/iredapd
# chmod +x /etc/init.d/iredapd
</pre>}}
* Remove symbol link of old release:
{{cmd|<pre>
# rm -i /opt/iredapd # <- Don't not end with '/'.
</pre>}}

* Create symbol link to the latest release:
{{cmd|<pre>
# cd /opt/
# ln -s iRedAPD-1.4.0 iredapd
</pre>}}

* Restart iRedAPD service:
{{cmd|<pre>
#
# ---- On Linux ----
#
# /etc/init.d/iredapd restart

#
# ---- On FreeBSD ----
#
# /usr/local/etc/rc.d/iredapd restart

#
# ---- On OpenBSD ----
#
# /etc/rc.d/iredapd restart
</pre>}}

* If you don't have file '''/etc/init.d/iredapd-rr''' on Linux, or '''/etc/rc.d/iredapd-rr''' on OpenBSD, or '''/usr/local/etc/rc.d/iredapd-rr''' on FreeBSD, it's safe to ignore below steps. But if you have it, please stop service '''iredapd-rr''', then move all enabled plugin names listed in '''/opt/iRedAPD-[OLD_VERSION]/etc/iredapd-rr.ini''' to our new config file '''/opt/iredapd/settings.py''', in parameter '''plugins = '''.
{{cmd|<pre>
# /etc/init.d/iredapd-rr stop
# rm /etc/init.d/iredapd-rr
</pre>}}

Check whether you have '''check_policy_service inet:127.0.0.1:7778''' in Postfix config file '''/etc/postfix/main.cf''' (Linux/OpenBSD) or '''/usr/local/etc/postfix/main.cf''', if you have it, please remove '''check_policy_service inet:127.0.0.1:7778''', then restart Postfix service.

That's all.

[[Category: FAQ]]
[[Category: iRedMail/FAQ]]

IRedMail/FAQ/Upgrade.iRedAPD

ZhangHuangbin — Mon, 01 Apr 2013 14:23:45 GMT

ZhangHuangbin:

----
This tutorial describes how to upgrade iRedAPD to the latest stable release, iRedAPD-1.4.0. It's applicable on all Linux/BSD distributions supported by iRedMail.

Important notes:
* Since iRedAPD-1.4.0, we use Python source file as config file, not '.ini' format anymore.
* We don't need second instance, '''iredapd-rr''', anymore.
----

* Download the latest stable release here: http://iredmail.org/yum/misc/ For example, iRedAPD-1.4.0.tar.bz2.
* Upload it to your iRedMail server. Assume it's '''/root/iRedAPD-1.4.0.tar.bz2''' on the server.
* Extract downloaded package and move to /opt/.
{{cmd|<pre>
# tar xjf /root/iRedAPD-1.4.0.tar.bz2 -C /opt/
</pre>}}
You get a new directory: /opt/iRedAPD-1.4.0/.

* Set correct owner and permission:
{{cmd|<pre>
# chown -R iredapd:iredapd /opt/iRedAPD-1.4.0
# chmod -R 0700 /opt/iRedAPD-1.4.0
</pre>}}

* Generate new config file from sample file, and set correct file owner and permission.
{{cmd|<pre>
# cd /opt/iRedAPD-1.4.0/
# cp settings.py.sample settings.py
# chown -R iredapd:iredapd settings.py
# chmod -R 0600 settings.py
</pre>}}
WARNING: Config file '''/opt/iredapd/settings.py''' contains sensitive infomation (username, password), please don't make it world-readable. Permission 0600 is the best.

* Please open '''/opt/iredapd/settings.py''', and sync settings with old iRedAPD config file '''/opt/iRedAPD-[OLD-VERSION]/etc/iredapd.ini'''.
** In old version of iRedAPD, all parameters under "[ldap]" section are now new parameters start with '''ldap_'''.
** In old version of iRedAPD, all parameters under "[sql]" (or "[mysql]") section are now new parameters start with '''sql_'''.

* After sync settings, please copy new RC script for your server. We have scripts for different Linux/BSD distributions. Please copy the proper one for your server. For example:
** iredapd.debian: For Debian and Ubuntu.
** iredapd.freebsd: For FreeBSD. Please copy to /usr/local/etc/rc.d/.
** iredapd.gentoo: For Gentoo Linux.
** iredapd.openbsd: For OpenBSD. Please copy to /etc/rc.d/.
** iredapd.opensuse: For openSUSE.
** iredapd.rhel: For Red Hat, CentOS, Scientific Linux.
{{cmd|<pre>
# cp /opt/iredapd/rc_scripts/iredapd.rhel /etc/init.d/iredapd
# chmod +x /etc/init.d/iredapd
</pre>}}
* Remove symbol link of old release:
{{cmd|<pre>
# rm -i /opt/iredapd # <- Don't not end with '/'.
</pre>}}

* Create symbol link to the latest release:
{{cmd|<pre>
# cd /opt/
# ln -s iRedAPD-1.4.0 iredapd
</pre>}}

* Restart iRedAPD service:
{{cmd|<pre>
#
# ---- On Linux ----
#
# /etc/init.d/iredapd restart

#
# ---- On FreeBSD ----
#
# /usr/local/etc/rc.d/iredapd restart

#
# ---- On OpenBSD ----
#
# /etc/rc.d/iredapd restart
</pre>}}

* If you don't have file '''/etc/init.d/iredapd-rr''' on Linux, or '''/etc/rc.d/iredapd-rr''' on OpenBSD, or '''/usr/local/etc/rc.d/iredapd-rr''' on FreeBSD, it's safe to ignore below steps. But if you have it, please stop service '''iredapd-rr''', then move all enabled plugin names listed in '''/opt/iRedAPD-[OLD_VERSION]/etc/iredapd-rr.ini''' to our new config file '''/opt/iredapd/settings.py''', in parameter '''plugins = '''.
{{cmd|<pre>
# /etc/init.d/iredapd-rr stop
# rm /etc/init.d/iredapd-rr
</pre>}}

Check whether you have '''check_policy_service inet:127.0.0.1:7778''' in Postfix config file '''/etc/postfix/main.cf''' (Linux/OpenBSD) or '''/usr/local/etc/postfix/main.cf''', if you have it, please remove '''check_policy_service inet:127.0.0.1:7778''', then restart Postfix service.

That's all.

[[Category: FAQ]]
[[Category: iRedMail/FAQ]]

Upgrade/iRedMail/0.8.3-0.8.4

ZhangHuangbin — Thu, 28 Mar 2013 16:07:53 GMT

ZhangHuangbin: /* Create addition SQL index for Amavisd database */

__TOC__

= ChangeLog =
* 2013-03-28: Update /etc/iredmail-release with iRedMail version number.
* 2013-03-28: Upgrade Roundcube webmail to the latest 0.8.6.
* 2013-03-25: [ldap] Fix incorrect LDAP query filter in Postfix.
* 2013-01-08: [sql] Add 4 new columns in table '''vmail.mailbox''' for MySQL/PostgreSQL backends.
* 2012-10-24: [ldap] Supports alias domains in Postfix per-user bcc lookup files.

= General (All backends should apply these steps) =

== Update /etc/iredmail-release with iRedMail version number ==
iRedMail stores the initial version number in /etc/iredmail-release after installation completed, 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:
{{cfg|/etc/iredmail-release|<pre>
0.8.6
</pre>}}

== Add new alias 'virusalert' in Postfix for Amavisd ==
Amavisd will send an email notification to address "virusalert@[YOUR_HOSTNAME]" by default, but we don't have this user in Postfix alias file (/etc/postfix/aliases on Linux/OpenBSD, or /usr/local/etc/postfix/aliases on FreeBSD) or SQL/LDAP database, so emails are not delivered. Below steps add a alias in Postfix alias file, and it will be forwarded to root user by default.

Add new alias (Note, use '/usr/local/etc/postfix/aliases' on FreeBSD instead), and update the database:
{{cmd|<pre>
# echo 'virusalert: root' >> /etc/postfix/aliases
# postalias /etc/postfix/aliases
</pre>}}

== Upgrade Roundcube webmail to the latest 0.8.6 ==
There's zero day vulnerability in Roundcubemail-0.8.5 and older releases, please follow this tutorial to upgrade Roundcube webmail to the latest 0.8.6 immediately: [[IRedMail/FAQ/Upgrade.Roundcube.Webmail |Upgrade Roundcube webmail]]

About the zero day vulnerability, please refer to this thread: http://lists.roundcube.net/pipermail/dev/2013-March/022328.html

== Upgrade iRedAPD (Postfix policy server) to the latest 1.4.0 ==
Please follow this tutorial to upgrade iRedAPD to the latest stable release: [[IRedMail/FAQ/Upgrade.iRedAPD |How to upgrade iRedAPD]]

== Upgrade iRedAdmin (open source edition) to the latest 0.2.1 ==
Please follow this tutorial to upgrade iRedAdmin open source edition to the latest stable release: [[IRedMail/FAQ/Upgrade.iRedAdmin.Open.Source.Edition |How to upgrade iRedAdmin (open source edition) to the latest stable release]]

= OpenLDAP backend special =
== Fix incorrect LDAP query filter in Postfix ==
If you add external email addresses as mail list members, iRedAdmin-Pro will store them in attribute '''memberOfGroup''', this will cause exported LDIF data cannot be restored. Below are steps to fix this issue.
=== Use the latest LDAP schema file provided by iRedMail ===
To fix this issue, we need the latest LDAP schema file provided by iRedMail. Steps are:
* Download the newest iRedMail ldap schema file
* Copy old ldap schema file as a backup copy
* Replace the old one
* Restart OpenLDAP service.

Here we go:

* On RHEL/CentOS/Scientific Linux (both release 5.x and 6.x), openSUSE, Gentoo, OpenBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/openldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/openldap/schema/
# /etc/init.d/slapd restart # <-- Or: /etc/init.d/ldap restart
</pre>}}

* On Debian/Ubuntu:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/ldap/schema/
# /etc/init.d/slapd restart
</pre>}}

* On FreeBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /usr/local/etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /usr/local/etc/openldap/schema/
# /etc/init.d/slapd restart
</pre>}}

=== Update existing accounts ===
* Download python script used to adding missing values.
{{cmd|<pre>
# cd /root/
# wget https://bitbucket.org/zhb/iredmail/raw/default/extra/update/updateLDAPValues_083_to_084.py
</pre>}}
Open updateLDAPValues_083_to_084.py, config LDAP server related settings in file head. e.g.
File: updateLDAPValues_083_to_084.py
{{cfg|updateLDAPValues_083_to_084.py|<pre>
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'
</pre>}}
Tip:
* You can find them in iRedAdmin config file or iRedMail.tips file under your iRedMail installation directory.
* Use 'cn=Manager' instead of 'cn=vmailadmin' here is ok too.

Execute this script, it will fix incorrect values and add correct ones:
{{cmd|<pre>
# python updateLDAPValues_083_to_084.py
</pre>}}

=== Fix incorrect LDAP query filter in Postfix ===
* On Linux/OpenBSD, please update '''/etc/postfix/ldap/virtual_group_maps.cf'''. On FreeBSD, update '''/usr/local/etc/postfix/ldap/virtual_group_maps.cf''' instead.
{{cfg|virtual_group_maps.cf|<pre>
# OLD setting
#query_filter = (&(memberOfGroup=%s)(accountStatus=active)(enabledService=mail)(enabledService=deliver)(|(objectClass=mailUser)(objectClass=mailExternalUser)))

# New setting
query_filter = (&(accountStatus=active)(enabledService=mail)(enabledService=deliver)(|(memberOfGroup=%s)(shadowAddress=%s))(|(objectClass=mailUser)(objectClass=mailExternalUser)))
</pre>}}

== Supports alias domains in Postfix per-user bcc lookup files ==
* In /etc/postfix/ldap/sender_bcc_maps_user.cf, replace "(mail=%s)" by "(|(mail=%s)(&(enabledService=shadowaddress)(shadowAddress=%s)))" in parameter "query_filter =". The final LDAP filter looks like below:
{{cfg|ldap/sender_bcc_maps_user.cf|<pre>
query_filter = (&(|(mail=%s)(&(enabledService=shadowaddress)(shadowAddress=%s)))(objectClass=mailUser)(accountStatus=active)(enabledService=mail)(enabledService=senderbcc))
</pre>}}

* Perform the same modification in file /etc/postfix/ldap/recipient_bcc_maps_user.cf, the final LDAP filter looks like below:
{{cfg|ldap/recipient_bcc_maps_user.cf|<pre>
query_filter = (&(|(mail=%s)(&(enabledService=shadowaddress)(shadowAddress=%s)))(objectClass=mailUser)(accountStatus=active)(enabledService=mail)(enabledService=recipientbcc))
</pre>}}

* Restarting Postfix service is required.

== Create addition SQL index for Amavisd database ==
We need one more SQL index for Amavisd database, it's used to speed up performance of viewing quarantined mails.
* Important Note: It will take a long time if you have many records in table '''msgs'''.
{{cmd|<pre>
$ mysql -uroot -p
mysql> USE amavisd;
mysql> ALTER TABLE msgs ADD INDEX (quar_type);
</pre>}}

= MySQL backend special =
== Add 4 new columns used for per-user restriction ==
New version of iRedAPD (Postfix policy daemon) requires 4 new columns in table '''vmail.mailbox''': allowedsenders, rejectedsenders, allowedrecipients, rejectedrecipients. They're used for per-user restriction. For example, you can now define who can send email to your local user, or your user can send email to which external domains or users.

Please login to MySQL server as root user, execute SQL commands to add required columns and indexes.
{{cmd|<pre>
# mysql -uroot -p
mysql> USE vmail;
mysql> ALTER TABLE mailbox ADD COLUMN allowedsenders TEXT NOT NULL DEFAULT '';
mysql> ALTER TABLE mailbox ADD COLUMN rejectedsenders TEXT NOT NULL DEFAULT '';
mysql> ALTER TABLE mailbox ADD COLUMN allowedrecipients TEXT NOT NULL DEFAULT '';
mysql> ALTER TABLE mailbox ADD COLUMN rejectedrecipients TEXT NOT NULL DEFAULT '';
</pre>}}

Supported formats of sender/recipients are:
* user@example.com: single user
* @example.com: single domain
* @'''.'''example.com: domain and its sub domain
* '''@.''': any users.

Multiple senders/recipients must be separated by comma, for example:
{{cmd|<pre>
sql> INSERT INTO mailbox SET allowedsenders='@gmail.com,user@example.com';
</pre>}}
== Create addition SQL index for Amavisd database ==
We need one more SQL index for Amavisd database, it's used to speed up performance of viewing quarantined mails.
* Important Note: It will take a long time if you have many records in table '''msgs'''.
{{cmd|<pre>
$ mysql -uroot -p
mysql> USE amavisd;
mysql> ALTER TABLE msgs ADD INDEX (quar_type);
</pre>}}

= PostgreSQL backend special =
== Add 4 new columns used for per-user restriction ==
New version of iRedAPD (Postfix policy daemon) requires 4 new columns in table '''vmail.mailbox''': allowedsenders, rejectedsenders, allowedrecipients, rejectedrecipients. They're used for per-user restriction. For example, you can now define who can send email to your local user, or your user can send email to which external domains or users.

Please switch to PostgreSQL daemon user, then execute SQL commands to add required columns and indexes:
On Linux, PostgreSQL daemon user is postgres.
On FreeBSD, PostgreSQL daemon user is pgsql.
On OpenBSD, PostgreSQL daemon user is """_postgresql".
{{cmd|<pre>
# su - postgres
$ psql -d vmail
sql> ALTER TABLE mailbox ADD COLUMN allowedsenders TEXT NOT NULL DEFAULT '';
sql> ALTER TABLE mailbox ADD COLUMN rejectedsenders TEXT NOT NULL DEFAULT '';
sql> ALTER TABLE mailbox ADD COLUMN allowedrecipients TEXT NOT NULL DEFAULT '';
sql> ALTER TABLE mailbox ADD COLUMN rejectedrecipients TEXT NOT NULL DEFAULT '';
</pre>}}

Supported formats of sender/recipients are:
* user@example.com: single user
* @example.com: single domain
* @'''.'''example.com: domain and its sub domain
* '''@.''': any users.

Multiple senders/recipients must be separated by comma, for example:
{{cmd|<pre>
sql> INSERT INTO mailbox SET allowedsenders='@gmail.com,user@example.com';
</pre>}}

== Create addition SQL index for Amavisd database ==
We need one more SQL index for Amavisd database, it's used to speed up performance of viewing quarantined mails.
* Important Note: It will take a long time if you have many records in table '''msgs'''.

Please switch to PostgreSQL daemon user, then execute SQL commands to add required columns and indexes:
* On Linux, PostgreSQL daemon user is postgres.
* On FreeBSD, PostgreSQL daemon user is pgsql.
* On OpenBSD, PostgreSQL daemon user is """_postgresql".
{{cmd|<pre>
# su - postgres
$ psql -d amavisd
sql> CREATE INDEX idx_msgs_quar_type ON msgs (quar_type);
</pre>}}

Upgrade/iRedMail/0.8.3-0.8.4

ZhangHuangbin — Thu, 28 Mar 2013 15:56:19 GMT

ZhangHuangbin: /* ChangeLog */

__TOC__

= ChangeLog =
* 2013-03-28: Update /etc/iredmail-release with iRedMail version number.
* 2013-03-28: Upgrade Roundcube webmail to the latest 0.8.6.
* 2013-03-25: [ldap] Fix incorrect LDAP query filter in Postfix.
* 2013-01-08: [sql] Add 4 new columns in table '''vmail.mailbox''' for MySQL/PostgreSQL backends.
* 2012-10-24: [ldap] Supports alias domains in Postfix per-user bcc lookup files.

= General (All backends should apply these steps) =

== Update /etc/iredmail-release with iRedMail version number ==
iRedMail stores the initial version number in /etc/iredmail-release after installation completed, 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:
{{cfg|/etc/iredmail-release|<pre>
0.8.6
</pre>}}

== Add new alias 'virusalert' in Postfix for Amavisd ==
Amavisd will send an email notification to address "virusalert@[YOUR_HOSTNAME]" by default, but we don't have this user in Postfix alias file (/etc/postfix/aliases on Linux/OpenBSD, or /usr/local/etc/postfix/aliases on FreeBSD) or SQL/LDAP database, so emails are not delivered. Below steps add a alias in Postfix alias file, and it will be forwarded to root user by default.

Add new alias (Note, use '/usr/local/etc/postfix/aliases' on FreeBSD instead), and update the database:
{{cmd|<pre>
# echo 'virusalert: root' >> /etc/postfix/aliases
# postalias /etc/postfix/aliases
</pre>}}

== Upgrade Roundcube webmail to the latest 0.8.6 ==
There's zero day vulnerability in Roundcubemail-0.8.5 and older releases, please follow this tutorial to upgrade Roundcube webmail to the latest 0.8.6 immediately: [[IRedMail/FAQ/Upgrade.Roundcube.Webmail |Upgrade Roundcube webmail]]

About the zero day vulnerability, please refer to this thread: http://lists.roundcube.net/pipermail/dev/2013-March/022328.html

== Upgrade iRedAPD (Postfix policy server) to the latest 1.4.0 ==
Please follow this tutorial to upgrade iRedAPD to the latest stable release: [[IRedMail/FAQ/Upgrade.iRedAPD |How to upgrade iRedAPD]]

== Upgrade iRedAdmin (open source edition) to the latest 0.2.1 ==
Please follow this tutorial to upgrade iRedAdmin open source edition to the latest stable release: [[IRedMail/FAQ/Upgrade.iRedAdmin.Open.Source.Edition |How to upgrade iRedAdmin (open source edition) to the latest stable release]]

= OpenLDAP backend special =
== Fix incorrect LDAP query filter in Postfix ==
If you add external email addresses as mail list members, iRedAdmin-Pro will store them in attribute '''memberOfGroup''', this will cause exported LDIF data cannot be restored. Below are steps to fix this issue.
=== Use the latest LDAP schema file provided by iRedMail ===
To fix this issue, we need the latest LDAP schema file provided by iRedMail. Steps are:
* Download the newest iRedMail ldap schema file
* Copy old ldap schema file as a backup copy
* Replace the old one
* Restart OpenLDAP service.

Here we go:

* On RHEL/CentOS/Scientific Linux (both release 5.x and 6.x), openSUSE, Gentoo, OpenBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/openldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/openldap/schema/
# /etc/init.d/slapd restart # <-- Or: /etc/init.d/ldap restart
</pre>}}

* On Debian/Ubuntu:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/ldap/schema/
# /etc/init.d/slapd restart
</pre>}}

* On FreeBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /usr/local/etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /usr/local/etc/openldap/schema/
# /etc/init.d/slapd restart
</pre>}}

=== Update existing accounts ===
* Download python script used to adding missing values.
{{cmd|<pre>
# cd /root/
# wget https://bitbucket.org/zhb/iredmail/raw/default/extra/update/updateLDAPValues_083_to_084.py
</pre>}}
Open updateLDAPValues_083_to_084.py, config LDAP server related settings in file head. e.g.
File: updateLDAPValues_083_to_084.py
{{cfg|updateLDAPValues_083_to_084.py|<pre>
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'
</pre>}}
Tip:
* You can find them in iRedAdmin config file or iRedMail.tips file under your iRedMail installation directory.
* Use 'cn=Manager' instead of 'cn=vmailadmin' here is ok too.

Execute this script, it will fix incorrect values and add correct ones:
{{cmd|<pre>
# python updateLDAPValues_083_to_084.py
</pre>}}

=== Fix incorrect LDAP query filter in Postfix ===
* On Linux/OpenBSD, please update '''/etc/postfix/ldap/virtual_group_maps.cf'''. On FreeBSD, update '''/usr/local/etc/postfix/ldap/virtual_group_maps.cf''' instead.
{{cfg|virtual_group_maps.cf|<pre>
# OLD setting
#query_filter = (&(memberOfGroup=%s)(accountStatus=active)(enabledService=mail)(enabledService=deliver)(|(objectClass=mailUser)(objectClass=mailExternalUser)))

# New setting
query_filter = (&(accountStatus=active)(enabledService=mail)(enabledService=deliver)(|(memberOfGroup=%s)(shadowAddress=%s))(|(objectClass=mailUser)(objectClass=mailExternalUser)))
</pre>}}

== Supports alias domains in Postfix per-user bcc lookup files ==
* In /etc/postfix/ldap/sender_bcc_maps_user.cf, replace "(mail=%s)" by "(|(mail=%s)(&(enabledService=shadowaddress)(shadowAddress=%s)))" in parameter "query_filter =". The final LDAP filter looks like below:
{{cfg|ldap/sender_bcc_maps_user.cf|<pre>
query_filter = (&(|(mail=%s)(&(enabledService=shadowaddress)(shadowAddress=%s)))(objectClass=mailUser)(accountStatus=active)(enabledService=mail)(enabledService=senderbcc))
</pre>}}

* Perform the same modification in file /etc/postfix/ldap/recipient_bcc_maps_user.cf, the final LDAP filter looks like below:
{{cfg|ldap/recipient_bcc_maps_user.cf|<pre>
query_filter = (&(|(mail=%s)(&(enabledService=shadowaddress)(shadowAddress=%s)))(objectClass=mailUser)(accountStatus=active)(enabledService=mail)(enabledService=recipientbcc))
</pre>}}

* Restarting Postfix service is required.

== Create addition SQL index for Amavisd database ==
We need one more SQL index for Amavisd database, it's used to speed up performance of viewing quarantined mails.
* Important Note: It will take a long time if you have many records in table '''msgs'''.
{{cmd|<pre>
$ mysql -uroot -p
mysql> USE amavisd;
mysql> ALTER TABLE msgs ADD INDEX (quar_type);
</pre>}}

= MySQL backend special =
== Add 4 new columns used for per-user restriction ==
New version of iRedAPD (Postfix policy daemon) requires 4 new columns in table '''vmail.mailbox''': allowedsenders, rejectedsenders, allowedrecipients, rejectedrecipients. They're used for per-user restriction. For example, you can now define who can send email to your local user, or your user can send email to which external domains or users.

Please login to MySQL server as root user, execute SQL commands to add required columns and indexes.
{{cmd|<pre>
# mysql -uroot -p
mysql> USE vmail;
mysql> ALTER TABLE mailbox ADD COLUMN allowedsenders TEXT NOT NULL DEFAULT '';
mysql> ALTER TABLE mailbox ADD COLUMN rejectedsenders TEXT NOT NULL DEFAULT '';
mysql> ALTER TABLE mailbox ADD COLUMN allowedrecipients TEXT NOT NULL DEFAULT '';
mysql> ALTER TABLE mailbox ADD COLUMN rejectedrecipients TEXT NOT NULL DEFAULT '';
</pre>}}

Supported formats of sender/recipients are:
* user@example.com: single user
* @example.com: single domain
* @'''.'''example.com: domain and its sub domain
* '''@.''': any users.

Multiple senders/recipients must be separated by comma, for example:
{{cmd|<pre>
sql> INSERT INTO mailbox SET allowedsenders='@gmail.com,user@example.com';
</pre>}}
== Create addition SQL index for Amavisd database ==
We need one more SQL index for Amavisd database, it's used to speed up performance of viewing quarantined mails.
* Important Note: It will take a long time if you have many records in table '''msgs'''.
{{cmd|<pre>
$ mysql -uroot -p
mysql> USE amavisd;
mysql> ALTER TABLE msgs ADD INDEX (quar_type);
</pre>}}

= PostgreSQL backend special =
== Add 4 new columns used for per-user restriction ==
New version of iRedAPD (Postfix policy daemon) requires 4 new columns in table '''vmail.mailbox''': allowedsenders, rejectedsenders, allowedrecipients, rejectedrecipients. They're used for per-user restriction. For example, you can now define who can send email to your local user, or your user can send email to which external domains or users.

Please switch to PostgreSQL daemon user, then execute SQL commands to add required columns and indexes:
On Linux, PostgreSQL daemon user is postgres.
On FreeBSD, PostgreSQL daemon user is pgsql.
On OpenBSD, PostgreSQL daemon user is """_postgresql".
{{cmd|<pre>
# su - postgres
$ psql -d vmail
sql> ALTER TABLE mailbox ADD COLUMN allowedsenders TEXT NOT NULL DEFAULT '';
sql> ALTER TABLE mailbox ADD COLUMN rejectedsenders TEXT NOT NULL DEFAULT '';
sql> ALTER TABLE mailbox ADD COLUMN allowedrecipients TEXT NOT NULL DEFAULT '';
sql> ALTER TABLE mailbox ADD COLUMN rejectedrecipients TEXT NOT NULL DEFAULT '';
</pre>}}

Supported formats of sender/recipients are:
* user@example.com: single user
* @example.com: single domain
* @'''.'''example.com: domain and its sub domain
* '''@.''': any users.

Multiple senders/recipients must be separated by comma, for example:
{{cmd|<pre>
sql> INSERT INTO mailbox SET allowedsenders='@gmail.com,user@example.com';
</pre>}}

== Create addition SQL index for Amavisd database ==
We need one more SQL index for Amavisd database, it's used to speed up performance of viewing quarantined mails.
* Important Note: It will take a long time if you have many records in table '''msgs'''.

Please switch to PostgreSQL daemon user, then execute SQL commands to add required columns and indexes:
* On Linux, PostgreSQL daemon user is postgres.
* On FreeBSD, PostgreSQL daemon user is pgsql.
* On OpenBSD, PostgreSQL daemon user is """_postgresql".
{{cmd|<pre>
# su - postgres
$ psql -d vmail
sql> CREATE INDEX idx_msgs_quar_type ON msgs (quar_type);
</pre>}}

Upgrade/iRedMail/0.8.3-0.8.4

ZhangHuangbin — Thu, 28 Mar 2013 15:56:00 GMT

ZhangHuangbin: /* General (All backends should apply these steps) */

__TOC__

= ChangeLog =
* 2013-03-28: Upgrade Roundcube webmail to the latest 0.8.6.
* 2013-03-25: [ldap] Fix incorrect LDAP query filter in Postfix.
* 2013-01-08: [sql] Add 4 new columns in table '''vmail.mailbox''' for MySQL/PostgreSQL backends.
* 2012-10-24: [ldap] Supports alias domains in Postfix per-user bcc lookup files.

= General (All backends should apply these steps) =

== Update /etc/iredmail-release with iRedMail version number ==
iRedMail stores the initial version number in /etc/iredmail-release after installation completed, 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:
{{cfg|/etc/iredmail-release|<pre>
0.8.6
</pre>}}

== Add new alias 'virusalert' in Postfix for Amavisd ==
Amavisd will send an email notification to address "virusalert@[YOUR_HOSTNAME]" by default, but we don't have this user in Postfix alias file (/etc/postfix/aliases on Linux/OpenBSD, or /usr/local/etc/postfix/aliases on FreeBSD) or SQL/LDAP database, so emails are not delivered. Below steps add a alias in Postfix alias file, and it will be forwarded to root user by default.

Add new alias (Note, use '/usr/local/etc/postfix/aliases' on FreeBSD instead), and update the database:
{{cmd|<pre>
# echo 'virusalert: root' >> /etc/postfix/aliases
# postalias /etc/postfix/aliases
</pre>}}

== Upgrade Roundcube webmail to the latest 0.8.6 ==
There's zero day vulnerability in Roundcubemail-0.8.5 and older releases, please follow this tutorial to upgrade Roundcube webmail to the latest 0.8.6 immediately: [[IRedMail/FAQ/Upgrade.Roundcube.Webmail |Upgrade Roundcube webmail]]

About the zero day vulnerability, please refer to this thread: http://lists.roundcube.net/pipermail/dev/2013-March/022328.html

== Upgrade iRedAPD (Postfix policy server) to the latest 1.4.0 ==
Please follow this tutorial to upgrade iRedAPD to the latest stable release: [[IRedMail/FAQ/Upgrade.iRedAPD |How to upgrade iRedAPD]]

== Upgrade iRedAdmin (open source edition) to the latest 0.2.1 ==
Please follow this tutorial to upgrade iRedAdmin open source edition to the latest stable release: [[IRedMail/FAQ/Upgrade.iRedAdmin.Open.Source.Edition |How to upgrade iRedAdmin (open source edition) to the latest stable release]]

= OpenLDAP backend special =
== Fix incorrect LDAP query filter in Postfix ==
If you add external email addresses as mail list members, iRedAdmin-Pro will store them in attribute '''memberOfGroup''', this will cause exported LDIF data cannot be restored. Below are steps to fix this issue.
=== Use the latest LDAP schema file provided by iRedMail ===
To fix this issue, we need the latest LDAP schema file provided by iRedMail. Steps are:
* Download the newest iRedMail ldap schema file
* Copy old ldap schema file as a backup copy
* Replace the old one
* Restart OpenLDAP service.

Here we go:

* On RHEL/CentOS/Scientific Linux (both release 5.x and 6.x), openSUSE, Gentoo, OpenBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/openldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/openldap/schema/
# /etc/init.d/slapd restart # <-- Or: /etc/init.d/ldap restart
</pre>}}

* On Debian/Ubuntu:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/ldap/schema/
# /etc/init.d/slapd restart
</pre>}}

* On FreeBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /usr/local/etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /usr/local/etc/openldap/schema/
# /etc/init.d/slapd restart
</pre>}}

=== Update existing accounts ===
* Download python script used to adding missing values.
{{cmd|<pre>
# cd /root/
# wget https://bitbucket.org/zhb/iredmail/raw/default/extra/update/updateLDAPValues_083_to_084.py
</pre>}}
Open updateLDAPValues_083_to_084.py, config LDAP server related settings in file head. e.g.
File: updateLDAPValues_083_to_084.py
{{cfg|updateLDAPValues_083_to_084.py|<pre>
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'
</pre>}}
Tip:
* You can find them in iRedAdmin config file or iRedMail.tips file under your iRedMail installation directory.
* Use 'cn=Manager' instead of 'cn=vmailadmin' here is ok too.

Execute this script, it will fix incorrect values and add correct ones:
{{cmd|<pre>
# python updateLDAPValues_083_to_084.py
</pre>}}

=== Fix incorrect LDAP query filter in Postfix ===
* On Linux/OpenBSD, please update '''/etc/postfix/ldap/virtual_group_maps.cf'''. On FreeBSD, update '''/usr/local/etc/postfix/ldap/virtual_group_maps.cf''' instead.
{{cfg|virtual_group_maps.cf|<pre>
# OLD setting
#query_filter = (&(memberOfGroup=%s)(accountStatus=active)(enabledService=mail)(enabledService=deliver)(|(objectClass=mailUser)(objectClass=mailExternalUser)))

# New setting
query_filter = (&(accountStatus=active)(enabledService=mail)(enabledService=deliver)(|(memberOfGroup=%s)(shadowAddress=%s))(|(objectClass=mailUser)(objectClass=mailExternalUser)))
</pre>}}

== Supports alias domains in Postfix per-user bcc lookup files ==
* In /etc/postfix/ldap/sender_bcc_maps_user.cf, replace "(mail=%s)" by "(|(mail=%s)(&(enabledService=shadowaddress)(shadowAddress=%s)))" in parameter "query_filter =". The final LDAP filter looks like below:
{{cfg|ldap/sender_bcc_maps_user.cf|<pre>
query_filter = (&(|(mail=%s)(&(enabledService=shadowaddress)(shadowAddress=%s)))(objectClass=mailUser)(accountStatus=active)(enabledService=mail)(enabledService=senderbcc))
</pre>}}

* Perform the same modification in file /etc/postfix/ldap/recipient_bcc_maps_user.cf, the final LDAP filter looks like below:
{{cfg|ldap/recipient_bcc_maps_user.cf|<pre>
query_filter = (&(|(mail=%s)(&(enabledService=shadowaddress)(shadowAddress=%s)))(objectClass=mailUser)(accountStatus=active)(enabledService=mail)(enabledService=recipientbcc))
</pre>}}

* Restarting Postfix service is required.

== Create addition SQL index for Amavisd database ==
We need one more SQL index for Amavisd database, it's used to speed up performance of viewing quarantined mails.
* Important Note: It will take a long time if you have many records in table '''msgs'''.
{{cmd|<pre>
$ mysql -uroot -p
mysql> USE amavisd;
mysql> ALTER TABLE msgs ADD INDEX (quar_type);
</pre>}}

= MySQL backend special =
== Add 4 new columns used for per-user restriction ==
New version of iRedAPD (Postfix policy daemon) requires 4 new columns in table '''vmail.mailbox''': allowedsenders, rejectedsenders, allowedrecipients, rejectedrecipients. They're used for per-user restriction. For example, you can now define who can send email to your local user, or your user can send email to which external domains or users.

Please login to MySQL server as root user, execute SQL commands to add required columns and indexes.
{{cmd|<pre>
# mysql -uroot -p
mysql> USE vmail;
mysql> ALTER TABLE mailbox ADD COLUMN allowedsenders TEXT NOT NULL DEFAULT '';
mysql> ALTER TABLE mailbox ADD COLUMN rejectedsenders TEXT NOT NULL DEFAULT '';
mysql> ALTER TABLE mailbox ADD COLUMN allowedrecipients TEXT NOT NULL DEFAULT '';
mysql> ALTER TABLE mailbox ADD COLUMN rejectedrecipients TEXT NOT NULL DEFAULT '';
</pre>}}

Supported formats of sender/recipients are:
* user@example.com: single user
* @example.com: single domain
* @'''.'''example.com: domain and its sub domain
* '''@.''': any users.

Multiple senders/recipients must be separated by comma, for example:
{{cmd|<pre>
sql> INSERT INTO mailbox SET allowedsenders='@gmail.com,user@example.com';
</pre>}}
== Create addition SQL index for Amavisd database ==
We need one more SQL index for Amavisd database, it's used to speed up performance of viewing quarantined mails.
* Important Note: It will take a long time if you have many records in table '''msgs'''.
{{cmd|<pre>
$ mysql -uroot -p
mysql> USE amavisd;
mysql> ALTER TABLE msgs ADD INDEX (quar_type);
</pre>}}

= PostgreSQL backend special =
== Add 4 new columns used for per-user restriction ==
New version of iRedAPD (Postfix policy daemon) requires 4 new columns in table '''vmail.mailbox''': allowedsenders, rejectedsenders, allowedrecipients, rejectedrecipients. They're used for per-user restriction. For example, you can now define who can send email to your local user, or your user can send email to which external domains or users.

Please switch to PostgreSQL daemon user, then execute SQL commands to add required columns and indexes:
On Linux, PostgreSQL daemon user is postgres.
On FreeBSD, PostgreSQL daemon user is pgsql.
On OpenBSD, PostgreSQL daemon user is """_postgresql".
{{cmd|<pre>
# su - postgres
$ psql -d vmail
sql> ALTER TABLE mailbox ADD COLUMN allowedsenders TEXT NOT NULL DEFAULT '';
sql> ALTER TABLE mailbox ADD COLUMN rejectedsenders TEXT NOT NULL DEFAULT '';
sql> ALTER TABLE mailbox ADD COLUMN allowedrecipients TEXT NOT NULL DEFAULT '';
sql> ALTER TABLE mailbox ADD COLUMN rejectedrecipients TEXT NOT NULL DEFAULT '';
</pre>}}

Supported formats of sender/recipients are:
* user@example.com: single user
* @example.com: single domain
* @'''.'''example.com: domain and its sub domain
* '''@.''': any users.

Multiple senders/recipients must be separated by comma, for example:
{{cmd|<pre>
sql> INSERT INTO mailbox SET allowedsenders='@gmail.com,user@example.com';
</pre>}}

== Create addition SQL index for Amavisd database ==
We need one more SQL index for Amavisd database, it's used to speed up performance of viewing quarantined mails.
* Important Note: It will take a long time if you have many records in table '''msgs'''.

Please switch to PostgreSQL daemon user, then execute SQL commands to add required columns and indexes:
* On Linux, PostgreSQL daemon user is postgres.
* On FreeBSD, PostgreSQL daemon user is pgsql.
* On OpenBSD, PostgreSQL daemon user is """_postgresql".
{{cmd|<pre>
# su - postgres
$ psql -d vmail
sql> CREATE INDEX idx_msgs_quar_type ON msgs (quar_type);
</pre>}}

Main Page

ZhangHuangbin — Thu, 28 Mar 2013 15:52:54 GMT

ZhangHuangbin: /* Upgrade Tutorials */

= iRedMail =
== Release Notes ==
* [http://www.iredmail.org/forum/topic4646-news-announcements-bug-fixes-iredmail084-has-been-released.html 0.8.4], 2013-03-26
* [http://www.iredmail.org/forum/topic4016-news-announcements-bug-fixes-iredmail083-has-been-released.html 0.8.3], 2012-10-13
* [http://www.iredmail.org/forum/topic3913-news-announcements-bug-fixes-iredmail082-has-been-released.html 0.8.2], 2012-09-19
* [http://www.iredmail.org/forum/topic3499-news-announcements-bug-fixes-iredmail081-has-been-released.html 0.8.1], 2012-06-08
* [http://www.iredmail.org/forum/topic3345.html 0.8.0], 2012-05-10
* [http://www.iredmail.org/forum/topic2816-iredmail074-has-been-released.html 0.7.4], 2012-01-09
* [[Release.Notes/iRedMail/0.7.3|0.7.3]], 2011-08-17
* [[Release.Notes/iRedMail/0.7.2|0.7.2]], 2011-06-10
* [[Release.Notes/iRedMail/0.7.1|0.7.1]], 2011-05-01
* [[Release.Notes/iRedMail/0.7.0|0.7.0]], 2011-04-01
* [[Release.Notes/iRedMail/0.6.1|0.6.1]]
* [[Release.Notes/iRedMail/0.6.0|0.6.0]]

== Installation Guide ==
* Install iRedMail on:
** [http://www.iredmail.org/install_iredmail_on_rhel.html Red Hat Enterprise Linux, CentOS, Scientific Linux]. Works on both version 5.x and 6.x.
** [http://www.iredmail.org/install_iredmail_on_debian.html Debian]
** [http://www.iredmail.org/install_iredmail_on_ubuntu.html Ubuntu, Mint]
** [http://www.iredmail.org/install_iredmail_on_opensuse.html openSuSE]
** [http://www.iredmail.org/install_iredmail_on_gentoo.html Gentoo]
** [http://www.iredmail.org/install_iredmail_on_freebsd.html FreeBSD (without Jail)], or [[Install/iRedMail/FreeBSD.Jail |inside Jail]].
** [http://www.iredmail.org/install_iredmail_on_openbsd.html OpenBSD].

* [https://bitbucket.org/zhb/iredapd/src/default/README.md?at=default Install iRedAPD], a postfix policy daemon:

== Upgrade Tutorials ==
* [[Upgrade/iRedMail/0.8.3-0.8.4|0.8.3 -> 0.8.4]]. 2013-03-26. LDAP schema update, SQL (MySQL/PostgreSQL) structure update.
* [[Upgrade/iRedMail/0.8.2-0.8.3|0.8.2 -> 0.8.3]]. 2012-09-13.
* [[Upgrade/iRedMail/0.8.1-0.8.2|0.8.1 -> 0.8.2]]. 2012-09-19. LDAP schema update, SQL (MySQL/PostgreSQL) structure update.
* [[Upgrade/iRedMail/0.8.0-0.8.1|0.8.0 -> 0.8.1]]. 2012-06-08. LDAP schema update, SQL (MySQL/PostgreSQL) structure update.
* [[Upgrade/iRedMail/0.7.4-0.8.0|0.7.4 -> 0.8.0]]. 2012-05-10. New LDAP attribute/value, SQL (MySQL) structure update.
* [[Upgrade/iRedMail/0.7.3-0.7.4|0.7.3 -> 0.7.4]]. 2012-01-09. SQL (MySQL) structure update.
* [[Upgrade/iRedMail/0.7.4-rc3-0.7.4|0.7.4-rc3 -> 0.7.4]]
* [[Upgrade/iRedMail/0.7.2-0.7.3|0.7.2 -> 0.7.3]]. 2011-08-17.
* [[Upgrade/iRedMail/0.7.1-0.7.2|0.7.1 -> 0.7.2]]. 2011-06-10.
* [[Upgrade/iRedMail/0.7.0-0.7.1|0.7.0 -> 0.7.1]]. 2011-05-01.
* [[Upgrade/iRedMail/0.6.1-0.7.0|0.6.1 -> 0.7.0]]. 2011-03-31.
* [[Upgrade/iRedMail/0.6.0-0.6.1|0.6.0 -> 0.6.1]]
* [[Upgrade/iRedMail/0.5.1-0.6.0|0.5.1 -> 0.6.0]]
* [http://www.iredmail.org/upgrade_050_051.html 0.5.0 -> 0.5.1]
* [http://code.google.com/p/iredmail/wiki/Upgrade_040_050 0.4.0 -> 0.5.0]
* [http://code.google.com/p/iredmail/wiki/Upgrade_032_040 0.3.2 -> 0.4.0]

== FAQ ==
* [[iRedMail/FAQ|iRedMail FAQ]]

== Integrations ==

* [[Integration/Active.Directory.iRedMail|Microsoft Active Directory + iRedMail]]
* [[Integration/PureFTPd.iRedMail.with.OpenLDAP |PureFTPd + iRedMail (OpenLDAP)]]
* [[Integration/Ejabberd.iRedMail.with.OpenLDAP |Ejabberd + iRedMail (OpenLDAP)]]
* [[Integration/OpenVPN.iRedMail.with.OpenLDAP |OpenVPN + iRedMail (OpenLDAP)]]
* [[Integration/SOGo.iRedMail.with.OpenLDAP |SOGo + iRedMail (OpenLDAP)]]
* [[Integration/DBMail.iRedMail.with.MySQL.backend |Integrate DBMail in iRedMail (MySQL backend)]], stores mail messages in MySQL.
* [http://www.howtoforge.com/installing-iredmail-and-mailman-on-debian-squeeze Installing iRedMail And Mailman On Debian Squeeze]

= iRedAdmin-Pro =
== Installation Guide ==

You can install iRedAdmin from scratch with below installation guides, they work for both iRedAdmin-Pro and iRedAdmin open source edition.

Note: If you already have iRedAdmin open source edition installed, you can [[Migrate/iRedAdmin-Pro/OSE-Pro |migrate from iRedAdmin open source edition to iRedAdmin-Pro]] easily.

<table border="1">
<tr>
<th>Install iRedAdmin-Pro for '''OpenLDAP''' backend</th>
<th>Install iRedAdmin-Pro for '''MySQL''' backend</th>
<th>Install iRedAdmin-Pro for '''PostgreSQL''' backend</th>
</tr>

<tr>
<td>[http://www.iredmail.org/admin_installation_rhel.html Red Hat Enterprise Linux, CentOS, Scientific Linux]</td>
<td>[[Install/iRedAdmin-Pro/MySQL/RHEL |Red Hat Enterprise Linux, CentOS, Scientific Linux]]</td>
<td>[[Install/iRedAdmin-Pro/PGSQL/RHEL |Red Hat Enterprise Linux, CentOS, Scientific Linux]]</td>
</tr>

<tr>
<td>[http://www.iredmail.org/admin_installation_debian.html Debian, Ubuntu, Mint]</td>
<td>[[Install/iRedAdmin-Pro/MySQL/Debian |Debian, Ubuntu, Mint]]</td>
<td>[[Install/iRedAdmin-Pro/PGSQL/Debian |Debian, Ubuntu, Mint]]</td>
</tr>

<tr>
<td>[http://www.iredmail.org/admin_installation_opensuse.html openSuSE]</td>
<td>[[Install/iRedAdmin-Pro/MySQL/OpenSuSE |openSUSE]]</td>
<td>[[Install/iRedAdmin-Pro/PGSQL/openSuSE |openSUSE]]</td>
</tr>

<tr>
<td>[http://www.iredmail.org/admin_installation_gentoo.html Gentoo]</td>
<td>[[Install/iRedAdmin-Pro/MySQL/Gentoo |Gentoo]]</td>
<td>[[Install/iRedAdmin-Pro/PGSQL/Gentoo |Gentoo]]</td>
</tr>

<tr>
<td>[http://www.iredmail.org/admin_installation_freebsd.html FreeBSD]</td>
<td>[[Install/iRedAdmin-Pro/MySQL/FreeBSD |FreeBSD]]</td>
<td>[[Install/iRedAdmin-Pro/PGSQL/FreeBSD |FreeBSD]]</td>
</tr>

<tr>
<td>[http://www.iredmail.org/admin_installation_openbsd.html OpenBSD]</td>
<td>[[Install/iRedAdmin-Pro/MySQL/OpenBSD |OpenBSD]]</td>
<td>[[Install/iRedAdmin-Pro/PGSQL/OpenBSD |OpenBSD]]</td>
</tr>
</table>

== Release Notes ==
<table border="1">
<tr>
<th>iRedAdmin-Pro-LDAP</th>
<th>iRedAdmin-Pro-MySQL</th>
<th>iRedAdmin-Pro-PGSQL</th>
</tr>

<tr>
<td>[http://www.iredmail.org/forum/topic4647-news-announcements-bug-fixes-iredadminproldap190-has-been-released.html 1.9.0], bugfix release. 2013-03-26</td>
<td>[http://www.iredmail.org/forum/topic4649-news-announcements-bug-fixes-iredadminpromysql160-has-been-released.html 1.6.0], bugfix release. 2013-03-26</td>
<td>[http://www.iredmail.org/forum/topic4650-news-announcements-bug-fixes-iredadminpropgsql120-has-been-released.html 1.2.0], bugfix release. 2013-03-26</td>
</tr>

<tr>
<td>[http://www.iredmail.org/forum/topic3919-news-announcements-bug-fixes-iredadminproldap180-has-been-released.html 1.8.0], bugfix release. 2012-09-19</td>
<td>[http://www.iredmail.org/forum/topic3920-news-announcements-bug-fixes-iredadminpromysql150-has-been-released.html 1.5.0], bugfix release. 2012-09-19</td>
<td>[http://www.iredmail.org/forum/topic3921-news-announcements-bug-fixes-iredadminpropgsql11-has-been-released.html 1.1], bugfix release. 2012-09-19</td>
</tr>

<tr>
<td>[http://www.iredmail.org/forum/topic3369-news-announcements-bug-fixes-iredadminproldap172-has-been-released.html 1.7.0], bugfix release. 2012-05-10</td>
<td>[http://www.iredmail.org/forum/topic3370-news-announcements-bug-fixes-iredadminpromysql140-has-been-released.html 1.4.0], bugfix release. 2012-05-10</td>
<td>[[Release.Notes/iRedAdmin-Pro/PGSQL/1.0|1.0]], initial release. 2012-05-10</td>
</tr>

<tr>
<td>[[Release.Notes/iRedAdmin-Pro/LDAP/1.6.3|1.6.3]], bugfix release. 2012-01-10</td>
<td>[[Release.Notes/iRedAdmin-Pro/MySQL/1.3.1|1.3.1]], bugfix release. 2012-01-10</td>
<td></td>
</tr>

<tr>
<td>[[Release.Notes/iRedAdmin-Pro/LDAP/1.6.2|1.6.2]], bugfix release. 2011-08-xx</td>
<td>[[Release.Notes/iRedAdmin-Pro/MySQL/1.3.0|1.3.0]]. 2011-08-xx</td>
<td></td>
</tr>

<tr>
<td>[[Release.Notes/iRedAdmin-Pro/LDAP/1.6.1|1.6.1]], bugfix release. 2011-06-26</td>
<td>[[Release.Notes/iRedAdmin-Pro/MySQL/1.2.1|1.2.1]], bugfix release. 2011-06-26</td>
<td></td>
</tr>

<tr>
<td>[[Release.Notes/iRedAdmin-Pro/LDAP/1.6.0|1.6.0]], security fix release. 2011-06-10</td>
<td>[[Release.Notes/iRedAdmin-Pro/MySQL/1.2.0|1.2.0]], security fix release. 2011-06-10</td>
<td></td>
</tr>

<tr>
<td>[[Release.Notes/iRedAdmin-Pro/LDAP/1.5.0|1.5.0]], 2011-05-03</td>
<td>[[Release.Notes/iRedAdmin-Pro/MySQL/1.1.0|1.1.0]], 2011-05-03</td>
<td></td>
</tr>

<tr>
<td>[[Release.Notes/iRedAdmin-Pro/LDAP/1.4.1|1.4.1]], 2011-03-03</td>
<td>[[Release.Notes/iRedAdmin-Pro/MySQL/1.0|1.0]], 2011-02-01</td>
<td></td>
</tr>

<tr>
<td>[[Release.Notes/iRedAdmin-Pro/LDAP/1.4.0|1.4.0]], 2011-02-01</td>
<td></td>
<td></td>
</tr>

<tr>
<td>[[Release.Notes/iRedAdmin-Pro/LDAP/1.3.0|1.3.0]], 2010-10-01</td>
<td></td>
<td></td>
</tr>

<tr>
<td>[[Release.Notes/iRedAdmin-Pro/LDAP/1.2.0|1.2.0]], 2010-06-18</td>
<td></td>
<td></td>
</tr>

</table>

== Upgrade Tutorials ==
Notes:
* iRedAdmin-Pro-LDAP:
** You can upgrade iRedAdmin-Pro-LDAP-1.4.0 or later versions to 1.9.0 directly by following upgrade tutorial for v1.5.0 or later versions.
** You can upgrade iRedAdmin-Pro-LDAP-1.3.0 to 1.6.2 directly with tutorial: [[Upgrade/iRedAdmin-Pro/LDAP/1.3.0-1.4.0 |Upgrade iRedAdmin-Pro-LDAP-1.3.0 to 1.4.0]]
* iRedAdmin-Pro-MySQL:
** You can upgrade iRedAdmin-Pro-MySQL-1.1.0 or later versions to 1.6.0 directly by following upgrade tutorial for v1.2.0 or later versions.
* iRedAdmin-Pro-PGSQL:
** You can upgrade iRedAdmin-Pro-PGSQL-1.0 or later releases to 1.2.0 directly.

<table border="1">
<tr>
<th>iRedAdmin-Pro-LDAP</th>
<th>iRedAdmin-Pro-MySQL</th>
<th>iRedAdmin-Pro-PGSQL</th>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.8-1.9.0|1.8.x -> 1.9.0]]. Security fix.2013-03-xx.</td>
<td>[[Upgrade/iRedAdmin-Pro/MySQL/1.5-1.6.0|1.5.x -> 1.6.0]]. Bugfix release. 2013-03-xx.</td>
<td>[[Upgrade/iRedAdmin-Pro/PGSQL/1.1-1.2.0|1.1.x -> 1.2.0]]. Bugfix release. 2013-03-xx.</td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.7.2-1.8.0|1.7.2 -> 1.8.0]]. Bugfix release. 2012-09-15.</td>
<td>[[Upgrade/iRedAdmin-Pro/MySQL/1.4.0-1.5.0|1.4.0 -> 1.5.0]]. Bugfix release. 2012-09-15.</td>
<td>[[Upgrade/iRedAdmin-Pro/PGSQL/1.0-1.1|1.0 -> 1.1]]. Bugfix release. 2012-09-15.</td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.6.3-1.7.0|1.6.3 -> 1.7.0]]. Bugfix release. 2012-05-10.</td>
<td>[[Upgrade/iRedAdmin-Pro/MySQL/1.3.1-1.4.0|1.3.1 -> 1.4.0]]. Bugfix release. 2012-05-10.</td>
<td></td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.6.2-1.6.3|1.6.2 -> 1.6.3]]. Bugfix release. 2012-01-10.</td>
<td>[[Upgrade/iRedAdmin-Pro/MySQL/1.3.0-1.3.1|1.3.0 -> 1.3.1]]. Bugfix release. 2012-01-10.</td>
<td></td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.6.1-1.6.2|1.6.1 -> 1.6.2]]. Bugfix release. 2011-08-17.</td>
<td>[[Upgrade/iRedAdmin-Pro/MySQL/1.2.1-1.3.0|1.2.1 -> 1.3.0]]. 2011-08-17.</td>
<td></td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.6.0-1.6.1|1.6.0 -> 1.6.1]]. Bugfix release. 2011-06-26</td>
<td>[[Upgrade/iRedAdmin-Pro/MySQL/1.2.0-1.2.1|1.2.0 -> 1.2.1]]. Bugfix release. 2011-06-26</td>
<td></td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.5.0-1.6.0|1.5.0 -> 1.6.0]]. Security fix release. 2011-06-10</td>
<td>[[Upgrade/iRedAdmin-Pro/MySQL/1.1.0-1.2.0|1.1.0 -> 1.2.0]]. Security fix release. 2011-06-10</td>
<td></td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.4.1-1.5.0|1.4.1 -> 1.5.0]]. 2011-05-03</td>
<td>[[Upgrade/iRedAdmin-Pro/MySQL/1.0-1.1.0|1.0 -> 1.1.0]]. 2011-05-03</td>
<td></td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.4.0-1.4.1|1.4.0 -> 1.4.1]]. bugfix release.</td>
<td></td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.3.0-1.4.0|1.3.0 -> 1.4.0]]</td>
<td></td>
<td></td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.2.0-1.3.0|1.2.0 -> 1.3.0]]</td>
<td></td>
<td></td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.1.x-1.2.0|1.1.x -> 1.2.0]]</td>
<td></td>
<td></td>
</tr>

<tr>
<td>[http://www.iredmail.org/forum/topic615-how-to-upgrade-iredadminpro10x-to-v110.html 1.0.x -> 1.1.0]</td>
<td></td>
<td></td>
</tr>

</table>

== FAQ ==
* [[iRedAdmin-Pro/FAQ |iRedAdmin-Pro FAQ]]

= Additions Articles/Tutorials =

== General ==
* [[IRedMail/FAQ/Backup |How to backup MySQL database and LDAP data]]
* [[Addition/Setup.Bind.As.Cache.DNS.Server |Setup Bind as cache DNS server on iRedMail to speed up DNS lookup.]] Contributed by Hoho.
* [[Addition/Always_accept_messages_for_special_aliases |Always accept messages for special aliases (postmaster@, abuse@, ...).]] Contributed by Maxie_ro.
* [[Addition/Configure_dk-filter_to_sign_emails_with_Domainkeys |Configure dk-filter to sign emails with Domainkeys.]] Contributed by Derchris.
* [[iRedMail/FAQ/Share.IMAP.Folder |Share IMAP folder with Dovecot 1.2 and Roundcube webmail 0.5]]
* [[Addition/Secure.Your.Exist.iRedAdmin |Secure your exist iRedAdmin]]
* [[Addition/Protect.Configure.Files|Protect configure files which contain username/password]]
* [[iRedMail/FAQ/Integrate.MySQL.in.Amavisd |Integrate MySQL in Amavisd]]
* [[IRedMail/FAQ/Quarantining.SPAM |Quarantining VIRUS and SPAM into MySQL with Amavisd]]. For iRedMail-0.7.0 and later versions.
* [[iRedMail/FAQ/Quarantining.Messages |Quarantining VIRUS and SPAM into MySQL with Amavisd]]. For iRedMail-0.6.1 and earlier versions.
* [[iRedMail/FAQ/Enable.Throttling |Enable sender & recipient throttling with Policyd]]
* [[iRedMail/FAQ/Store.Realtime.Quota.In.MySQL |Store Real-time Quota in MySQL with Dovecot 1.2]]
* [[iRedMail/FAQ/Upgrade.Dovecot.1.1.to.1.2 |Upgrade Dovecot 1.1.x to 1.2.x]]
* [[Postfix SPF check |Immediate SPF check in Postfix using pypolicyd-spf]] Contributed by Maxie_ro.
* [[Addition/Migrate.to.New.iRedMail.Server |Migrate to new iRedMail server]]
* [[Addition/Install.PostfixAdmin.For.MySQL.Backend |Install PostfixAdmin for MySQL backend]]
* [[Addition/Hardening.your.iRedMail.Server |Hardening your iRedMail Server]]
* [[Addition/Force.Users.to.Change.Password.in.90.Days |Force users to change password in 90 days]]
* [[Addition/Shared_folders_with_dovecot_1.2 |Shared folders with dovecot 1.2]] - '''WORK IN PROGRESS''' - Contributed by Maxie_ro.
* [[Addition/Harden.iRedMail.with.Fail2ban |Harden iRedMail with Fail2ban]]
* [[Addition/NTP |Keep your computer-time in sync]]
* [[Addition/Good.Practise |Good Practise]]
* [[Addition/Bad.Practise |Bad Practise - what NOT to do]]
* [[IRedMail/FAQ/Delete.Sent.Received.Mail.Log.Manually |How to delete log of Sent/Received mails manually]]
* [[iRedMail/FAQ/Delete.Quarantined.Mails.Manually |How to delete quarantined mails manually]]
* [[IRedMail/FAQ/Recalculate.Mailbox.Quota |How to force Dovecot to recalculate mailbox quota]]
* [[IRedMail/FAQ/Archive.Mails.with.Postfix.Bcc |How to archive mails with Postfix BCC]]
* [[IRedMail/FAQ/Enable.Disable.Greylisting |How to enable or disable greylisting with Policyd-1.8]]
* [[IRedMail/FAQ/Backup.iRedMail.Server |How to backup and restore iRedMail server]] - '''WORK IN PROGRESS'''
* [[iRedMail/FAQ/Ignore.Trash.Folder.in.Quota |How to ignore Trash folder in mailbox quota]]
* [[IRedMail/FAQ/EndUser/Howto.Configure.Thunderbird.for.iRedMail#Use_OpenLDAP_as_Global_LDAP_Address_Book |How to configure Thunderbird for iRedMail]], with global LDAP address book support.
* [[IRedMail/FAQ/Generate.New.SSL.Cert.Key |How to generate new SSL cert and key]]
* [[IRedMail/FAQ/Disable.Spam.Virus.Scanning.for.Outgoing.Mails |Disable spam and virus scanning for outgoing mails]]
* [[IRedMail/FAQ/Pipe.Incoming.Email.For.Certain.User.To.External.Script |Pipe incoming email for certain user to external script]]
* [[IRedMail/FAQ/Upgrade.Roundcube.Webmail |How to upgrade Roundcube webmail]]
* [[iRedMail/FAQ/Enable.Greylist.Opt.In |How to enable greylist opt in with Policyd (v1.8x)]]
* [[iRedMail/FAQ/Store.SpamAssassin.Bayes.In.SQL |How to configure iRedMail to store SpamAssassin Bayes data in SQL server]]
* [[iRedMail/FAQ/Completely.Disable.Amavisd.ClamAV.SpamAssassin |How to completely disable spam and virus scanning (Amavisd, ClamAV, SpamAssassin)]]
* [[iRedMail/FAQ/Upgrade.iRedAPD |How to upgrade iRedAPD (Postfix policy server)]]
* [[iRedMail/FAQ/Upgrade.iRedAdmin.Open.Source.Edition |How to upgrade iRedAdmin (open source edition)]]
* [[iRedMail/FAQ/Dovecot.Master.User |How to enable Dovecot Master User]]

== OpenLDAP backend only ==
* [[Addition/OpenLDAP/Catch-all|Setup Catch-all Email Accounts in iRedMail-0.5.1 and earlier versions]]
* [[Addition/OpenLDAP/Personal_LDAP_Address_Book|Setup per-user personal LDAP address book]]

== Clustering and storage ==
* [[Master-master_high-availability_failover_iRedMail_system_using_GlusterFS |How to setup master/master iRedMail replication using GlusterFS]]
* [[Cluster/General.Resource |General cluster related resource]]

Main Page

ZhangHuangbin — Thu, 28 Mar 2013 15:52:00 GMT

ZhangHuangbin: /* Release Notes */

= iRedMail =
== Release Notes ==
* [http://www.iredmail.org/forum/topic4646-news-announcements-bug-fixes-iredmail084-has-been-released.html 0.8.4], 2013-03-26
* [http://www.iredmail.org/forum/topic4016-news-announcements-bug-fixes-iredmail083-has-been-released.html 0.8.3], 2012-10-13
* [http://www.iredmail.org/forum/topic3913-news-announcements-bug-fixes-iredmail082-has-been-released.html 0.8.2], 2012-09-19
* [http://www.iredmail.org/forum/topic3499-news-announcements-bug-fixes-iredmail081-has-been-released.html 0.8.1], 2012-06-08
* [http://www.iredmail.org/forum/topic3345.html 0.8.0], 2012-05-10
* [http://www.iredmail.org/forum/topic2816-iredmail074-has-been-released.html 0.7.4], 2012-01-09
* [[Release.Notes/iRedMail/0.7.3|0.7.3]], 2011-08-17
* [[Release.Notes/iRedMail/0.7.2|0.7.2]], 2011-06-10
* [[Release.Notes/iRedMail/0.7.1|0.7.1]], 2011-05-01
* [[Release.Notes/iRedMail/0.7.0|0.7.0]], 2011-04-01
* [[Release.Notes/iRedMail/0.6.1|0.6.1]]
* [[Release.Notes/iRedMail/0.6.0|0.6.0]]

== Installation Guide ==
* Install iRedMail on:
** [http://www.iredmail.org/install_iredmail_on_rhel.html Red Hat Enterprise Linux, CentOS, Scientific Linux]. Works on both version 5.x and 6.x.
** [http://www.iredmail.org/install_iredmail_on_debian.html Debian]
** [http://www.iredmail.org/install_iredmail_on_ubuntu.html Ubuntu, Mint]
** [http://www.iredmail.org/install_iredmail_on_opensuse.html openSuSE]
** [http://www.iredmail.org/install_iredmail_on_gentoo.html Gentoo]
** [http://www.iredmail.org/install_iredmail_on_freebsd.html FreeBSD (without Jail)], or [[Install/iRedMail/FreeBSD.Jail |inside Jail]].
** [http://www.iredmail.org/install_iredmail_on_openbsd.html OpenBSD].

* [https://bitbucket.org/zhb/iredapd/src/default/README.md?at=default Install iRedAPD], a postfix policy daemon:

== Upgrade Tutorials ==
* [[Upgrade/iRedMail/0.8.3-0.8.4|0.8.3 -> 0.8.4]]. 2013-03-26. LDAP schema update, SQL (MySQL/PostgreSQL) structure update.
* [[Upgrade/iRedMail/0.8.2-0.8.3|0.8.2 -> 0.8.3]]. 2012-09-13.
* [[Upgrade/iRedMail/0.8.1-0.8.2|0.8.1 -> 0.8.2]]. 2012-09-19. LDAP schema update, SQL (MySQL/PostgreSQL) structure update.
* [[Upgrade/iRedMail/0.8.0-0.8.1|0.8.0 -> 0.8.1]]. 2012-06-08. LDAP schema update, SQL (MySQL/PostgreSQL) structure update.
* [[Upgrade/iRedMail/0.7.4-0.8.0|0.7.4 -> 0.8.0]]. 2012-05-10. New LDAP attribute/value, SQL (MySQL) structure update.
* [[Upgrade/iRedMail/0.7.3-0.7.4|0.7.3 -> 0.7.4]]. 2012-01-09. SQL (MySQL) structure update.
* [[Upgrade/iRedMail/0.7.4-rc3-0.7.4|0.7.4-rc3 -> 0.7.4]]
* [[Upgrade/iRedMail/0.7.2-0.7.3|0.7.2 -> 0.7.3]]. 2011-08-17.
* [[Upgrade/iRedMail/0.7.1-0.7.2|0.7.1 -> 0.7.2]]. 2011-06-10.
* [[Upgrade/iRedMail/0.7.0-0.7.1|0.7.0 -> 0.7.1]]. 2011-05-01.
* [[Upgrade/iRedMail/0.6.1-0.7.0|0.6.1 -> 0.7.0]]. 2011-03-31.
* [[Upgrade/iRedMail/0.6.0-0.6.1|0.6.0 -> 0.6.1]]
* [[Upgrade/iRedMail/0.5.1-0.6.0|0.5.1 -> 0.6.0]]
* [http://www.iredmail.org/upgrade_050_051.html 0.5.0 -> 0.5.1]
* [http://code.google.com/p/iredmail/wiki/Upgrade_040_050 0.4.0 -> 0.5.0]
* [http://code.google.com/p/iredmail/wiki/Upgrade_032_040 0.3.2 -> 0.4.0]

== FAQ ==
* [[iRedMail/FAQ|iRedMail FAQ]]

== Integrations ==

* [[Integration/Active.Directory.iRedMail|Microsoft Active Directory + iRedMail]]
* [[Integration/PureFTPd.iRedMail.with.OpenLDAP |PureFTPd + iRedMail (OpenLDAP)]]
* [[Integration/Ejabberd.iRedMail.with.OpenLDAP |Ejabberd + iRedMail (OpenLDAP)]]
* [[Integration/OpenVPN.iRedMail.with.OpenLDAP |OpenVPN + iRedMail (OpenLDAP)]]
* [[Integration/SOGo.iRedMail.with.OpenLDAP |SOGo + iRedMail (OpenLDAP)]]
* [[Integration/DBMail.iRedMail.with.MySQL.backend |Integrate DBMail in iRedMail (MySQL backend)]], stores mail messages in MySQL.
* [http://www.howtoforge.com/installing-iredmail-and-mailman-on-debian-squeeze Installing iRedMail And Mailman On Debian Squeeze]

= iRedAdmin-Pro =
== Installation Guide ==

You can install iRedAdmin from scratch with below installation guides, they work for both iRedAdmin-Pro and iRedAdmin open source edition.

Note: If you already have iRedAdmin open source edition installed, you can [[Migrate/iRedAdmin-Pro/OSE-Pro |migrate from iRedAdmin open source edition to iRedAdmin-Pro]] easily.

<table border="1">
<tr>
<th>Install iRedAdmin-Pro for '''OpenLDAP''' backend</th>
<th>Install iRedAdmin-Pro for '''MySQL''' backend</th>
<th>Install iRedAdmin-Pro for '''PostgreSQL''' backend</th>
</tr>

<tr>
<td>[http://www.iredmail.org/admin_installation_rhel.html Red Hat Enterprise Linux, CentOS, Scientific Linux]</td>
<td>[[Install/iRedAdmin-Pro/MySQL/RHEL |Red Hat Enterprise Linux, CentOS, Scientific Linux]]</td>
<td>[[Install/iRedAdmin-Pro/PGSQL/RHEL |Red Hat Enterprise Linux, CentOS, Scientific Linux]]</td>
</tr>

<tr>
<td>[http://www.iredmail.org/admin_installation_debian.html Debian, Ubuntu, Mint]</td>
<td>[[Install/iRedAdmin-Pro/MySQL/Debian |Debian, Ubuntu, Mint]]</td>
<td>[[Install/iRedAdmin-Pro/PGSQL/Debian |Debian, Ubuntu, Mint]]</td>
</tr>

<tr>
<td>[http://www.iredmail.org/admin_installation_opensuse.html openSuSE]</td>
<td>[[Install/iRedAdmin-Pro/MySQL/OpenSuSE |openSUSE]]</td>
<td>[[Install/iRedAdmin-Pro/PGSQL/openSuSE |openSUSE]]</td>
</tr>

<tr>
<td>[http://www.iredmail.org/admin_installation_gentoo.html Gentoo]</td>
<td>[[Install/iRedAdmin-Pro/MySQL/Gentoo |Gentoo]]</td>
<td>[[Install/iRedAdmin-Pro/PGSQL/Gentoo |Gentoo]]</td>
</tr>

<tr>
<td>[http://www.iredmail.org/admin_installation_freebsd.html FreeBSD]</td>
<td>[[Install/iRedAdmin-Pro/MySQL/FreeBSD |FreeBSD]]</td>
<td>[[Install/iRedAdmin-Pro/PGSQL/FreeBSD |FreeBSD]]</td>
</tr>

<tr>
<td>[http://www.iredmail.org/admin_installation_openbsd.html OpenBSD]</td>
<td>[[Install/iRedAdmin-Pro/MySQL/OpenBSD |OpenBSD]]</td>
<td>[[Install/iRedAdmin-Pro/PGSQL/OpenBSD |OpenBSD]]</td>
</tr>
</table>

== Release Notes ==
<table border="1">
<tr>
<th>iRedAdmin-Pro-LDAP</th>
<th>iRedAdmin-Pro-MySQL</th>
<th>iRedAdmin-Pro-PGSQL</th>
</tr>

<tr>
<td>[http://www.iredmail.org/forum/topic4647-news-announcements-bug-fixes-iredadminproldap190-has-been-released.html 1.9.0], bugfix release. 2013-03-26</td>
<td>[http://www.iredmail.org/forum/topic4649-news-announcements-bug-fixes-iredadminpromysql160-has-been-released.html 1.6.0], bugfix release. 2013-03-26</td>
<td>[http://www.iredmail.org/forum/topic4650-news-announcements-bug-fixes-iredadminpropgsql120-has-been-released.html 1.2.0], bugfix release. 2013-03-26</td>
</tr>

<tr>
<td>[http://www.iredmail.org/forum/topic3919-news-announcements-bug-fixes-iredadminproldap180-has-been-released.html 1.8.0], bugfix release. 2012-09-19</td>
<td>[http://www.iredmail.org/forum/topic3920-news-announcements-bug-fixes-iredadminpromysql150-has-been-released.html 1.5.0], bugfix release. 2012-09-19</td>
<td>[http://www.iredmail.org/forum/topic3921-news-announcements-bug-fixes-iredadminpropgsql11-has-been-released.html 1.1], bugfix release. 2012-09-19</td>
</tr>

<tr>
<td>[http://www.iredmail.org/forum/topic3369-news-announcements-bug-fixes-iredadminproldap172-has-been-released.html 1.7.0], bugfix release. 2012-05-10</td>
<td>[http://www.iredmail.org/forum/topic3370-news-announcements-bug-fixes-iredadminpromysql140-has-been-released.html 1.4.0], bugfix release. 2012-05-10</td>
<td>[[Release.Notes/iRedAdmin-Pro/PGSQL/1.0|1.0]], initial release. 2012-05-10</td>
</tr>

<tr>
<td>[[Release.Notes/iRedAdmin-Pro/LDAP/1.6.3|1.6.3]], bugfix release. 2012-01-10</td>
<td>[[Release.Notes/iRedAdmin-Pro/MySQL/1.3.1|1.3.1]], bugfix release. 2012-01-10</td>
<td></td>
</tr>

<tr>
<td>[[Release.Notes/iRedAdmin-Pro/LDAP/1.6.2|1.6.2]], bugfix release. 2011-08-xx</td>
<td>[[Release.Notes/iRedAdmin-Pro/MySQL/1.3.0|1.3.0]]. 2011-08-xx</td>
<td></td>
</tr>

<tr>
<td>[[Release.Notes/iRedAdmin-Pro/LDAP/1.6.1|1.6.1]], bugfix release. 2011-06-26</td>
<td>[[Release.Notes/iRedAdmin-Pro/MySQL/1.2.1|1.2.1]], bugfix release. 2011-06-26</td>
<td></td>
</tr>

<tr>
<td>[[Release.Notes/iRedAdmin-Pro/LDAP/1.6.0|1.6.0]], security fix release. 2011-06-10</td>
<td>[[Release.Notes/iRedAdmin-Pro/MySQL/1.2.0|1.2.0]], security fix release. 2011-06-10</td>
<td></td>
</tr>

<tr>
<td>[[Release.Notes/iRedAdmin-Pro/LDAP/1.5.0|1.5.0]], 2011-05-03</td>
<td>[[Release.Notes/iRedAdmin-Pro/MySQL/1.1.0|1.1.0]], 2011-05-03</td>
<td></td>
</tr>

<tr>
<td>[[Release.Notes/iRedAdmin-Pro/LDAP/1.4.1|1.4.1]], 2011-03-03</td>
<td>[[Release.Notes/iRedAdmin-Pro/MySQL/1.0|1.0]], 2011-02-01</td>
<td></td>
</tr>

<tr>
<td>[[Release.Notes/iRedAdmin-Pro/LDAP/1.4.0|1.4.0]], 2011-02-01</td>
<td></td>
<td></td>
</tr>

<tr>
<td>[[Release.Notes/iRedAdmin-Pro/LDAP/1.3.0|1.3.0]], 2010-10-01</td>
<td></td>
<td></td>
</tr>

<tr>
<td>[[Release.Notes/iRedAdmin-Pro/LDAP/1.2.0|1.2.0]], 2010-06-18</td>
<td></td>
<td></td>
</tr>

</table>

== Upgrade Tutorials ==
Notes:
* iRedAdmin-Pro-LDAP:
** You can upgrade iRedAdmin-Pro-LDAP-1.4.0 or later versions to 1.9.0 directly by following upgrade tutorial for v1.5.0 or later versions.
** You can upgrade iRedAdmin-Pro-LDAP-1.3.0 to 1.6.2 directly with tutorial: [[Upgrade/iRedAdmin-Pro/LDAP/1.3.0-1.4.0 |Upgrade iRedAdmin-Pro-LDAP-1.3.0 to 1.4.0]]
* iRedAdmin-Pro-MySQL:
** You can upgrade iRedAdmin-Pro-MySQL-1.1.0 or later versions to 1.5.1 directly by following upgrade tutorial for v1.2.0 or later versions.

<table border="1">
<tr>
<th>iRedAdmin-Pro-LDAP</th>
<th>iRedAdmin-Pro-MySQL</th>
<th>iRedAdmin-Pro-PGSQL</th>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.8-1.9.0|1.8.x -> 1.9.0]]. Security fix.2013-03-xx.</td>
<td>[[Upgrade/iRedAdmin-Pro/MySQL/1.5-1.6.0|1.5.x -> 1.6.0]]. Bugfix release. 2013-03-xx.</td>
<td>[[Upgrade/iRedAdmin-Pro/PGSQL/1.1-1.2.0|1.1.x -> 1.2.0]]. Bugfix release. 2013-03-xx.</td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.7.2-1.8.0|1.7.2 -> 1.8.0]]. Bugfix release. 2012-09-15.</td>
<td>[[Upgrade/iRedAdmin-Pro/MySQL/1.4.0-1.5.0|1.4.0 -> 1.5.0]]. Bugfix release. 2012-09-15.</td>
<td>[[Upgrade/iRedAdmin-Pro/PGSQL/1.0-1.1|1.0 -> 1.1]]. Bugfix release. 2012-09-15.</td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.6.3-1.7.0|1.6.3 -> 1.7.0]]. Bugfix release. 2012-05-10.</td>
<td>[[Upgrade/iRedAdmin-Pro/MySQL/1.3.1-1.4.0|1.3.1 -> 1.4.0]]. Bugfix release. 2012-05-10.</td>
<td></td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.6.2-1.6.3|1.6.2 -> 1.6.3]]. Bugfix release. 2012-01-10.</td>
<td>[[Upgrade/iRedAdmin-Pro/MySQL/1.3.0-1.3.1|1.3.0 -> 1.3.1]]. Bugfix release. 2012-01-10.</td>
<td></td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.6.1-1.6.2|1.6.1 -> 1.6.2]]. Bugfix release. 2011-08-17.</td>
<td>[[Upgrade/iRedAdmin-Pro/MySQL/1.2.1-1.3.0|1.2.1 -> 1.3.0]]. 2011-08-17.</td>
<td></td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.6.0-1.6.1|1.6.0 -> 1.6.1]]. Bugfix release. 2011-06-26</td>
<td>[[Upgrade/iRedAdmin-Pro/MySQL/1.2.0-1.2.1|1.2.0 -> 1.2.1]]. Bugfix release. 2011-06-26</td>
<td></td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.5.0-1.6.0|1.5.0 -> 1.6.0]]. Security fix release. 2011-06-10</td>
<td>[[Upgrade/iRedAdmin-Pro/MySQL/1.1.0-1.2.0|1.1.0 -> 1.2.0]]. Security fix release. 2011-06-10</td>
<td></td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.4.1-1.5.0|1.4.1 -> 1.5.0]]. 2011-05-03</td>
<td>[[Upgrade/iRedAdmin-Pro/MySQL/1.0-1.1.0|1.0 -> 1.1.0]]. 2011-05-03</td>
<td></td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.4.0-1.4.1|1.4.0 -> 1.4.1]]. bugfix release.</td>
<td></td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.3.0-1.4.0|1.3.0 -> 1.4.0]]</td>
<td></td>
<td></td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.2.0-1.3.0|1.2.0 -> 1.3.0]]</td>
<td></td>
<td></td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.1.x-1.2.0|1.1.x -> 1.2.0]]</td>
<td></td>
<td></td>
</tr>

<tr>
<td>[http://www.iredmail.org/forum/topic615-how-to-upgrade-iredadminpro10x-to-v110.html 1.0.x -> 1.1.0]</td>
<td></td>
<td></td>
</tr>

</table>

== FAQ ==
* [[iRedAdmin-Pro/FAQ |iRedAdmin-Pro FAQ]]

= Additions Articles/Tutorials =

== General ==
* [[IRedMail/FAQ/Backup |How to backup MySQL database and LDAP data]]
* [[Addition/Setup.Bind.As.Cache.DNS.Server |Setup Bind as cache DNS server on iRedMail to speed up DNS lookup.]] Contributed by Hoho.
* [[Addition/Always_accept_messages_for_special_aliases |Always accept messages for special aliases (postmaster@, abuse@, ...).]] Contributed by Maxie_ro.
* [[Addition/Configure_dk-filter_to_sign_emails_with_Domainkeys |Configure dk-filter to sign emails with Domainkeys.]] Contributed by Derchris.
* [[iRedMail/FAQ/Share.IMAP.Folder |Share IMAP folder with Dovecot 1.2 and Roundcube webmail 0.5]]
* [[Addition/Secure.Your.Exist.iRedAdmin |Secure your exist iRedAdmin]]
* [[Addition/Protect.Configure.Files|Protect configure files which contain username/password]]
* [[iRedMail/FAQ/Integrate.MySQL.in.Amavisd |Integrate MySQL in Amavisd]]
* [[IRedMail/FAQ/Quarantining.SPAM |Quarantining VIRUS and SPAM into MySQL with Amavisd]]. For iRedMail-0.7.0 and later versions.
* [[iRedMail/FAQ/Quarantining.Messages |Quarantining VIRUS and SPAM into MySQL with Amavisd]]. For iRedMail-0.6.1 and earlier versions.
* [[iRedMail/FAQ/Enable.Throttling |Enable sender & recipient throttling with Policyd]]
* [[iRedMail/FAQ/Store.Realtime.Quota.In.MySQL |Store Real-time Quota in MySQL with Dovecot 1.2]]
* [[iRedMail/FAQ/Upgrade.Dovecot.1.1.to.1.2 |Upgrade Dovecot 1.1.x to 1.2.x]]
* [[Postfix SPF check |Immediate SPF check in Postfix using pypolicyd-spf]] Contributed by Maxie_ro.
* [[Addition/Migrate.to.New.iRedMail.Server |Migrate to new iRedMail server]]
* [[Addition/Install.PostfixAdmin.For.MySQL.Backend |Install PostfixAdmin for MySQL backend]]
* [[Addition/Hardening.your.iRedMail.Server |Hardening your iRedMail Server]]
* [[Addition/Force.Users.to.Change.Password.in.90.Days |Force users to change password in 90 days]]
* [[Addition/Shared_folders_with_dovecot_1.2 |Shared folders with dovecot 1.2]] - '''WORK IN PROGRESS''' - Contributed by Maxie_ro.
* [[Addition/Harden.iRedMail.with.Fail2ban |Harden iRedMail with Fail2ban]]
* [[Addition/NTP |Keep your computer-time in sync]]
* [[Addition/Good.Practise |Good Practise]]
* [[Addition/Bad.Practise |Bad Practise - what NOT to do]]
* [[IRedMail/FAQ/Delete.Sent.Received.Mail.Log.Manually |How to delete log of Sent/Received mails manually]]
* [[iRedMail/FAQ/Delete.Quarantined.Mails.Manually |How to delete quarantined mails manually]]
* [[IRedMail/FAQ/Recalculate.Mailbox.Quota |How to force Dovecot to recalculate mailbox quota]]
* [[IRedMail/FAQ/Archive.Mails.with.Postfix.Bcc |How to archive mails with Postfix BCC]]
* [[IRedMail/FAQ/Enable.Disable.Greylisting |How to enable or disable greylisting with Policyd-1.8]]
* [[IRedMail/FAQ/Backup.iRedMail.Server |How to backup and restore iRedMail server]] - '''WORK IN PROGRESS'''
* [[iRedMail/FAQ/Ignore.Trash.Folder.in.Quota |How to ignore Trash folder in mailbox quota]]
* [[IRedMail/FAQ/EndUser/Howto.Configure.Thunderbird.for.iRedMail#Use_OpenLDAP_as_Global_LDAP_Address_Book |How to configure Thunderbird for iRedMail]], with global LDAP address book support.
* [[IRedMail/FAQ/Generate.New.SSL.Cert.Key |How to generate new SSL cert and key]]
* [[IRedMail/FAQ/Disable.Spam.Virus.Scanning.for.Outgoing.Mails |Disable spam and virus scanning for outgoing mails]]
* [[IRedMail/FAQ/Pipe.Incoming.Email.For.Certain.User.To.External.Script |Pipe incoming email for certain user to external script]]
* [[IRedMail/FAQ/Upgrade.Roundcube.Webmail |How to upgrade Roundcube webmail]]
* [[iRedMail/FAQ/Enable.Greylist.Opt.In |How to enable greylist opt in with Policyd (v1.8x)]]
* [[iRedMail/FAQ/Store.SpamAssassin.Bayes.In.SQL |How to configure iRedMail to store SpamAssassin Bayes data in SQL server]]
* [[iRedMail/FAQ/Completely.Disable.Amavisd.ClamAV.SpamAssassin |How to completely disable spam and virus scanning (Amavisd, ClamAV, SpamAssassin)]]
* [[iRedMail/FAQ/Upgrade.iRedAPD |How to upgrade iRedAPD (Postfix policy server)]]
* [[iRedMail/FAQ/Upgrade.iRedAdmin.Open.Source.Edition |How to upgrade iRedAdmin (open source edition)]]
* [[iRedMail/FAQ/Dovecot.Master.User |How to enable Dovecot Master User]]

== OpenLDAP backend only ==
* [[Addition/OpenLDAP/Catch-all|Setup Catch-all Email Accounts in iRedMail-0.5.1 and earlier versions]]
* [[Addition/OpenLDAP/Personal_LDAP_Address_Book|Setup per-user personal LDAP address book]]

== Clustering and storage ==
* [[Master-master_high-availability_failover_iRedMail_system_using_GlusterFS |How to setup master/master iRedMail replication using GlusterFS]]
* [[Cluster/General.Resource |General cluster related resource]]

Main Page

ZhangHuangbin — Thu, 28 Mar 2013 15:45:50 GMT

ZhangHuangbin: /* Release Notes */

= iRedMail =
== Release Notes ==
* [http://www.iredmail.org/forum/topic4646-news-announcements-bug-fixes-iredmail084-has-been-released.html 0.8.4], 2013-03-26
* [http://www.iredmail.org/forum/topic4016-news-announcements-bug-fixes-iredmail083-has-been-released.html 0.8.3], 2012-10-13
* [http://www.iredmail.org/forum/topic3913-news-announcements-bug-fixes-iredmail082-has-been-released.html 0.8.2], 2012-09-19
* [http://www.iredmail.org/forum/topic3499-news-announcements-bug-fixes-iredmail081-has-been-released.html 0.8.1], 2012-06-08
* [http://www.iredmail.org/forum/topic3345.html 0.8.0], 2012-05-10
* [http://www.iredmail.org/forum/topic2816-iredmail074-has-been-released.html 0.7.4], 2012-01-09
* [[Release.Notes/iRedMail/0.7.3|0.7.3]], 2011-08-17
* [[Release.Notes/iRedMail/0.7.2|0.7.2]], 2011-06-10
* [[Release.Notes/iRedMail/0.7.1|0.7.1]], 2011-05-01
* [[Release.Notes/iRedMail/0.7.0|0.7.0]], 2011-04-01
* [[Release.Notes/iRedMail/0.6.1|0.6.1]]
* [[Release.Notes/iRedMail/0.6.0|0.6.0]]

== Installation Guide ==
* Install iRedMail on:
** [http://www.iredmail.org/install_iredmail_on_rhel.html Red Hat Enterprise Linux, CentOS, Scientific Linux]. Works on both version 5.x and 6.x.
** [http://www.iredmail.org/install_iredmail_on_debian.html Debian]
** [http://www.iredmail.org/install_iredmail_on_ubuntu.html Ubuntu, Mint]
** [http://www.iredmail.org/install_iredmail_on_opensuse.html openSuSE]
** [http://www.iredmail.org/install_iredmail_on_gentoo.html Gentoo]
** [http://www.iredmail.org/install_iredmail_on_freebsd.html FreeBSD (without Jail)], or [[Install/iRedMail/FreeBSD.Jail |inside Jail]].
** [http://www.iredmail.org/install_iredmail_on_openbsd.html OpenBSD].

* [https://bitbucket.org/zhb/iredapd/src/default/README.md?at=default Install iRedAPD], a postfix policy daemon:

== Upgrade Tutorials ==
* [[Upgrade/iRedMail/0.8.3-0.8.4|0.8.3 -> 0.8.4]]. 2013-03-26. LDAP schema update, SQL (MySQL/PostgreSQL) structure update.
* [[Upgrade/iRedMail/0.8.2-0.8.3|0.8.2 -> 0.8.3]]. 2012-09-13.
* [[Upgrade/iRedMail/0.8.1-0.8.2|0.8.1 -> 0.8.2]]. 2012-09-19. LDAP schema update, SQL (MySQL/PostgreSQL) structure update.
* [[Upgrade/iRedMail/0.8.0-0.8.1|0.8.0 -> 0.8.1]]. 2012-06-08. LDAP schema update, SQL (MySQL/PostgreSQL) structure update.
* [[Upgrade/iRedMail/0.7.4-0.8.0|0.7.4 -> 0.8.0]]. 2012-05-10. New LDAP attribute/value, SQL (MySQL) structure update.
* [[Upgrade/iRedMail/0.7.3-0.7.4|0.7.3 -> 0.7.4]]. 2012-01-09. SQL (MySQL) structure update.
* [[Upgrade/iRedMail/0.7.4-rc3-0.7.4|0.7.4-rc3 -> 0.7.4]]
* [[Upgrade/iRedMail/0.7.2-0.7.3|0.7.2 -> 0.7.3]]. 2011-08-17.
* [[Upgrade/iRedMail/0.7.1-0.7.2|0.7.1 -> 0.7.2]]. 2011-06-10.
* [[Upgrade/iRedMail/0.7.0-0.7.1|0.7.0 -> 0.7.1]]. 2011-05-01.
* [[Upgrade/iRedMail/0.6.1-0.7.0|0.6.1 -> 0.7.0]]. 2011-03-31.
* [[Upgrade/iRedMail/0.6.0-0.6.1|0.6.0 -> 0.6.1]]
* [[Upgrade/iRedMail/0.5.1-0.6.0|0.5.1 -> 0.6.0]]
* [http://www.iredmail.org/upgrade_050_051.html 0.5.0 -> 0.5.1]
* [http://code.google.com/p/iredmail/wiki/Upgrade_040_050 0.4.0 -> 0.5.0]
* [http://code.google.com/p/iredmail/wiki/Upgrade_032_040 0.3.2 -> 0.4.0]

== FAQ ==
* [[iRedMail/FAQ|iRedMail FAQ]]

== Integrations ==

* [[Integration/Active.Directory.iRedMail|Microsoft Active Directory + iRedMail]]
* [[Integration/PureFTPd.iRedMail.with.OpenLDAP |PureFTPd + iRedMail (OpenLDAP)]]
* [[Integration/Ejabberd.iRedMail.with.OpenLDAP |Ejabberd + iRedMail (OpenLDAP)]]
* [[Integration/OpenVPN.iRedMail.with.OpenLDAP |OpenVPN + iRedMail (OpenLDAP)]]
* [[Integration/SOGo.iRedMail.with.OpenLDAP |SOGo + iRedMail (OpenLDAP)]]
* [[Integration/DBMail.iRedMail.with.MySQL.backend |Integrate DBMail in iRedMail (MySQL backend)]], stores mail messages in MySQL.
* [http://www.howtoforge.com/installing-iredmail-and-mailman-on-debian-squeeze Installing iRedMail And Mailman On Debian Squeeze]

= iRedAdmin-Pro =
== Installation Guide ==

You can install iRedAdmin from scratch with below installation guides, they work for both iRedAdmin-Pro and iRedAdmin open source edition.

Note: If you already have iRedAdmin open source edition installed, you can [[Migrate/iRedAdmin-Pro/OSE-Pro |migrate from iRedAdmin open source edition to iRedAdmin-Pro]] easily.

<table border="1">
<tr>
<th>Install iRedAdmin-Pro for '''OpenLDAP''' backend</th>
<th>Install iRedAdmin-Pro for '''MySQL''' backend</th>
<th>Install iRedAdmin-Pro for '''PostgreSQL''' backend</th>
</tr>

<tr>
<td>[http://www.iredmail.org/admin_installation_rhel.html Red Hat Enterprise Linux, CentOS, Scientific Linux]</td>
<td>[[Install/iRedAdmin-Pro/MySQL/RHEL |Red Hat Enterprise Linux, CentOS, Scientific Linux]]</td>
<td>[[Install/iRedAdmin-Pro/PGSQL/RHEL |Red Hat Enterprise Linux, CentOS, Scientific Linux]]</td>
</tr>

<tr>
<td>[http://www.iredmail.org/admin_installation_debian.html Debian, Ubuntu, Mint]</td>
<td>[[Install/iRedAdmin-Pro/MySQL/Debian |Debian, Ubuntu, Mint]]</td>
<td>[[Install/iRedAdmin-Pro/PGSQL/Debian |Debian, Ubuntu, Mint]]</td>
</tr>

<tr>
<td>[http://www.iredmail.org/admin_installation_opensuse.html openSuSE]</td>
<td>[[Install/iRedAdmin-Pro/MySQL/OpenSuSE |openSUSE]]</td>
<td>[[Install/iRedAdmin-Pro/PGSQL/openSuSE |openSUSE]]</td>
</tr>

<tr>
<td>[http://www.iredmail.org/admin_installation_gentoo.html Gentoo]</td>
<td>[[Install/iRedAdmin-Pro/MySQL/Gentoo |Gentoo]]</td>
<td>[[Install/iRedAdmin-Pro/PGSQL/Gentoo |Gentoo]]</td>
</tr>

<tr>
<td>[http://www.iredmail.org/admin_installation_freebsd.html FreeBSD]</td>
<td>[[Install/iRedAdmin-Pro/MySQL/FreeBSD |FreeBSD]]</td>
<td>[[Install/iRedAdmin-Pro/PGSQL/FreeBSD |FreeBSD]]</td>
</tr>

<tr>
<td>[http://www.iredmail.org/admin_installation_openbsd.html OpenBSD]</td>
<td>[[Install/iRedAdmin-Pro/MySQL/OpenBSD |OpenBSD]]</td>
<td>[[Install/iRedAdmin-Pro/PGSQL/OpenBSD |OpenBSD]]</td>
</tr>
</table>

== Release Notes ==
<table border="1">
<tr>
<th>iRedAdmin-Pro-LDAP</th>
<th>iRedAdmin-Pro-MySQL</th>
<th>iRedAdmin-Pro-PGSQL</th>
</tr>

<tr>
<td>[http://www.iredmail.org/forum/topic3919-news-announcements-bug-fixes-iredadminproldap180-has-been-released.html 1.8.0], bugfix release. 2012-09-19</td>
<td>[http://www.iredmail.org/forum/topic3920-news-announcements-bug-fixes-iredadminpromysql150-has-been-released.html 1.5.0], bugfix release. 2012-09-19</td>
<td>[http://www.iredmail.org/forum/topic3921-news-announcements-bug-fixes-iredadminpropgsql11-has-been-released.html 1.1], bugfix release. 2012-09-19</td>
</tr>

<tr>
<td>[http://www.iredmail.org/forum/topic3369-news-announcements-bug-fixes-iredadminproldap172-has-been-released.html 1.7.0], bugfix release. 2012-05-10</td>
<td>[http://www.iredmail.org/forum/topic3370-news-announcements-bug-fixes-iredadminpromysql140-has-been-released.html 1.4.0], bugfix release. 2012-05-10</td>
<td>[[Release.Notes/iRedAdmin-Pro/PGSQL/1.0|1.0]], initial release. 2012-05-10</td>
</tr>

<tr>
<td>[[Release.Notes/iRedAdmin-Pro/LDAP/1.6.3|1.6.3]], bugfix release. 2012-01-10</td>
<td>[[Release.Notes/iRedAdmin-Pro/MySQL/1.3.1|1.3.1]], bugfix release. 2012-01-10</td>
<td></td>
</tr>

<tr>
<td>[[Release.Notes/iRedAdmin-Pro/LDAP/1.6.2|1.6.2]], bugfix release. 2011-08-xx</td>
<td>[[Release.Notes/iRedAdmin-Pro/MySQL/1.3.0|1.3.0]]. 2011-08-xx</td>
<td></td>
</tr>

<tr>
<td>[[Release.Notes/iRedAdmin-Pro/LDAP/1.6.1|1.6.1]], bugfix release. 2011-06-26</td>
<td>[[Release.Notes/iRedAdmin-Pro/MySQL/1.2.1|1.2.1]], bugfix release. 2011-06-26</td>
<td></td>
</tr>

<tr>
<td>[[Release.Notes/iRedAdmin-Pro/LDAP/1.6.0|1.6.0]], security fix release. 2011-06-10</td>
<td>[[Release.Notes/iRedAdmin-Pro/MySQL/1.2.0|1.2.0]], security fix release. 2011-06-10</td>
<td></td>
</tr>

<tr>
<td>[[Release.Notes/iRedAdmin-Pro/LDAP/1.5.0|1.5.0]], 2011-05-03</td>
<td>[[Release.Notes/iRedAdmin-Pro/MySQL/1.1.0|1.1.0]], 2011-05-03</td>
<td></td>
</tr>

<tr>
<td>[[Release.Notes/iRedAdmin-Pro/LDAP/1.4.1|1.4.1]], 2011-03-03</td>
<td>[[Release.Notes/iRedAdmin-Pro/MySQL/1.0|1.0]], 2011-02-01</td>
<td></td>
</tr>

<tr>
<td>[[Release.Notes/iRedAdmin-Pro/LDAP/1.4.0|1.4.0]], 2011-02-01</td>
<td></td>
<td></td>
</tr>

<tr>
<td>[[Release.Notes/iRedAdmin-Pro/LDAP/1.3.0|1.3.0]], 2010-10-01</td>
<td></td>
<td></td>
</tr>

<tr>
<td>[[Release.Notes/iRedAdmin-Pro/LDAP/1.2.0|1.2.0]], 2010-06-18</td>
<td></td>
<td></td>
</tr>

</table>

== Upgrade Tutorials ==
Notes:
* iRedAdmin-Pro-LDAP:
** You can upgrade iRedAdmin-Pro-LDAP-1.4.0 or later versions to 1.9.0 directly by following upgrade tutorial for v1.5.0 or later versions.
** You can upgrade iRedAdmin-Pro-LDAP-1.3.0 to 1.6.2 directly with tutorial: [[Upgrade/iRedAdmin-Pro/LDAP/1.3.0-1.4.0 |Upgrade iRedAdmin-Pro-LDAP-1.3.0 to 1.4.0]]
* iRedAdmin-Pro-MySQL:
** You can upgrade iRedAdmin-Pro-MySQL-1.1.0 or later versions to 1.5.1 directly by following upgrade tutorial for v1.2.0 or later versions.

<table border="1">
<tr>
<th>iRedAdmin-Pro-LDAP</th>
<th>iRedAdmin-Pro-MySQL</th>
<th>iRedAdmin-Pro-PGSQL</th>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.8-1.9.0|1.8.x -> 1.9.0]]. Security fix.2013-03-xx.</td>
<td>[[Upgrade/iRedAdmin-Pro/MySQL/1.5-1.6.0|1.5.x -> 1.6.0]]. Bugfix release. 2013-03-xx.</td>
<td>[[Upgrade/iRedAdmin-Pro/PGSQL/1.1-1.2.0|1.1.x -> 1.2.0]]. Bugfix release. 2013-03-xx.</td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.7.2-1.8.0|1.7.2 -> 1.8.0]]. Bugfix release. 2012-09-15.</td>
<td>[[Upgrade/iRedAdmin-Pro/MySQL/1.4.0-1.5.0|1.4.0 -> 1.5.0]]. Bugfix release. 2012-09-15.</td>
<td>[[Upgrade/iRedAdmin-Pro/PGSQL/1.0-1.1|1.0 -> 1.1]]. Bugfix release. 2012-09-15.</td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.6.3-1.7.0|1.6.3 -> 1.7.0]]. Bugfix release. 2012-05-10.</td>
<td>[[Upgrade/iRedAdmin-Pro/MySQL/1.3.1-1.4.0|1.3.1 -> 1.4.0]]. Bugfix release. 2012-05-10.</td>
<td></td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.6.2-1.6.3|1.6.2 -> 1.6.3]]. Bugfix release. 2012-01-10.</td>
<td>[[Upgrade/iRedAdmin-Pro/MySQL/1.3.0-1.3.1|1.3.0 -> 1.3.1]]. Bugfix release. 2012-01-10.</td>
<td></td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.6.1-1.6.2|1.6.1 -> 1.6.2]]. Bugfix release. 2011-08-17.</td>
<td>[[Upgrade/iRedAdmin-Pro/MySQL/1.2.1-1.3.0|1.2.1 -> 1.3.0]]. 2011-08-17.</td>
<td></td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.6.0-1.6.1|1.6.0 -> 1.6.1]]. Bugfix release. 2011-06-26</td>
<td>[[Upgrade/iRedAdmin-Pro/MySQL/1.2.0-1.2.1|1.2.0 -> 1.2.1]]. Bugfix release. 2011-06-26</td>
<td></td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.5.0-1.6.0|1.5.0 -> 1.6.0]]. Security fix release. 2011-06-10</td>
<td>[[Upgrade/iRedAdmin-Pro/MySQL/1.1.0-1.2.0|1.1.0 -> 1.2.0]]. Security fix release. 2011-06-10</td>
<td></td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.4.1-1.5.0|1.4.1 -> 1.5.0]]. 2011-05-03</td>
<td>[[Upgrade/iRedAdmin-Pro/MySQL/1.0-1.1.0|1.0 -> 1.1.0]]. 2011-05-03</td>
<td></td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.4.0-1.4.1|1.4.0 -> 1.4.1]]. bugfix release.</td>
<td></td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.3.0-1.4.0|1.3.0 -> 1.4.0]]</td>
<td></td>
<td></td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.2.0-1.3.0|1.2.0 -> 1.3.0]]</td>
<td></td>
<td></td>
</tr>

<tr>
<td>[[Upgrade/iRedAdmin-Pro/LDAP/1.1.x-1.2.0|1.1.x -> 1.2.0]]</td>
<td></td>
<td></td>
</tr>

<tr>
<td>[http://www.iredmail.org/forum/topic615-how-to-upgrade-iredadminpro10x-to-v110.html 1.0.x -> 1.1.0]</td>
<td></td>
<td></td>
</tr>

</table>

== FAQ ==
* [[iRedAdmin-Pro/FAQ |iRedAdmin-Pro FAQ]]

= Additions Articles/Tutorials =

== General ==
* [[IRedMail/FAQ/Backup |How to backup MySQL database and LDAP data]]
* [[Addition/Setup.Bind.As.Cache.DNS.Server |Setup Bind as cache DNS server on iRedMail to speed up DNS lookup.]] Contributed by Hoho.
* [[Addition/Always_accept_messages_for_special_aliases |Always accept messages for special aliases (postmaster@, abuse@, ...).]] Contributed by Maxie_ro.
* [[Addition/Configure_dk-filter_to_sign_emails_with_Domainkeys |Configure dk-filter to sign emails with Domainkeys.]] Contributed by Derchris.
* [[iRedMail/FAQ/Share.IMAP.Folder |Share IMAP folder with Dovecot 1.2 and Roundcube webmail 0.5]]
* [[Addition/Secure.Your.Exist.iRedAdmin |Secure your exist iRedAdmin]]
* [[Addition/Protect.Configure.Files|Protect configure files which contain username/password]]
* [[iRedMail/FAQ/Integrate.MySQL.in.Amavisd |Integrate MySQL in Amavisd]]
* [[IRedMail/FAQ/Quarantining.SPAM |Quarantining VIRUS and SPAM into MySQL with Amavisd]]. For iRedMail-0.7.0 and later versions.
* [[iRedMail/FAQ/Quarantining.Messages |Quarantining VIRUS and SPAM into MySQL with Amavisd]]. For iRedMail-0.6.1 and earlier versions.
* [[iRedMail/FAQ/Enable.Throttling |Enable sender & recipient throttling with Policyd]]
* [[iRedMail/FAQ/Store.Realtime.Quota.In.MySQL |Store Real-time Quota in MySQL with Dovecot 1.2]]
* [[iRedMail/FAQ/Upgrade.Dovecot.1.1.to.1.2 |Upgrade Dovecot 1.1.x to 1.2.x]]
* [[Postfix SPF check |Immediate SPF check in Postfix using pypolicyd-spf]] Contributed by Maxie_ro.
* [[Addition/Migrate.to.New.iRedMail.Server |Migrate to new iRedMail server]]
* [[Addition/Install.PostfixAdmin.For.MySQL.Backend |Install PostfixAdmin for MySQL backend]]
* [[Addition/Hardening.your.iRedMail.Server |Hardening your iRedMail Server]]
* [[Addition/Force.Users.to.Change.Password.in.90.Days |Force users to change password in 90 days]]
* [[Addition/Shared_folders_with_dovecot_1.2 |Shared folders with dovecot 1.2]] - '''WORK IN PROGRESS''' - Contributed by Maxie_ro.
* [[Addition/Harden.iRedMail.with.Fail2ban |Harden iRedMail with Fail2ban]]
* [[Addition/NTP |Keep your computer-time in sync]]
* [[Addition/Good.Practise |Good Practise]]
* [[Addition/Bad.Practise |Bad Practise - what NOT to do]]
* [[IRedMail/FAQ/Delete.Sent.Received.Mail.Log.Manually |How to delete log of Sent/Received mails manually]]
* [[iRedMail/FAQ/Delete.Quarantined.Mails.Manually |How to delete quarantined mails manually]]
* [[IRedMail/FAQ/Recalculate.Mailbox.Quota |How to force Dovecot to recalculate mailbox quota]]
* [[IRedMail/FAQ/Archive.Mails.with.Postfix.Bcc |How to archive mails with Postfix BCC]]
* [[IRedMail/FAQ/Enable.Disable.Greylisting |How to enable or disable greylisting with Policyd-1.8]]
* [[IRedMail/FAQ/Backup.iRedMail.Server |How to backup and restore iRedMail server]] - '''WORK IN PROGRESS'''
* [[iRedMail/FAQ/Ignore.Trash.Folder.in.Quota |How to ignore Trash folder in mailbox quota]]
* [[IRedMail/FAQ/EndUser/Howto.Configure.Thunderbird.for.iRedMail#Use_OpenLDAP_as_Global_LDAP_Address_Book |How to configure Thunderbird for iRedMail]], with global LDAP address book support.
* [[IRedMail/FAQ/Generate.New.SSL.Cert.Key |How to generate new SSL cert and key]]
* [[IRedMail/FAQ/Disable.Spam.Virus.Scanning.for.Outgoing.Mails |Disable spam and virus scanning for outgoing mails]]
* [[IRedMail/FAQ/Pipe.Incoming.Email.For.Certain.User.To.External.Script |Pipe incoming email for certain user to external script]]
* [[IRedMail/FAQ/Upgrade.Roundcube.Webmail |How to upgrade Roundcube webmail]]
* [[iRedMail/FAQ/Enable.Greylist.Opt.In |How to enable greylist opt in with Policyd (v1.8x)]]
* [[iRedMail/FAQ/Store.SpamAssassin.Bayes.In.SQL |How to configure iRedMail to store SpamAssassin Bayes data in SQL server]]
* [[iRedMail/FAQ/Completely.Disable.Amavisd.ClamAV.SpamAssassin |How to completely disable spam and virus scanning (Amavisd, ClamAV, SpamAssassin)]]
* [[iRedMail/FAQ/Upgrade.iRedAPD |How to upgrade iRedAPD (Postfix policy server)]]
* [[iRedMail/FAQ/Upgrade.iRedAdmin.Open.Source.Edition |How to upgrade iRedAdmin (open source edition)]]
* [[iRedMail/FAQ/Dovecot.Master.User |How to enable Dovecot Master User]]

== OpenLDAP backend only ==
* [[Addition/OpenLDAP/Catch-all|Setup Catch-all Email Accounts in iRedMail-0.5.1 and earlier versions]]
* [[Addition/OpenLDAP/Personal_LDAP_Address_Book|Setup per-user personal LDAP address book]]

== Clustering and storage ==
* [[Master-master_high-availability_failover_iRedMail_system_using_GlusterFS |How to setup master/master iRedMail replication using GlusterFS]]
* [[Cluster/General.Resource |General cluster related resource]]

Upgrade/iRedMail/0.8.3-0.8.4

ZhangHuangbin — Thu, 28 Mar 2013 15:43:15 GMT

ZhangHuangbin: /* Supports alias domains in Postfix per-user bcc lookup files */

__TOC__

= ChangeLog =
* 2013-03-28: Upgrade Roundcube webmail to the latest 0.8.6.
* 2013-03-25: [ldap] Fix incorrect LDAP query filter in Postfix.
* 2013-01-08: [sql] Add 4 new columns in table '''vmail.mailbox''' for MySQL/PostgreSQL backends.
* 2012-10-24: [ldap] Supports alias domains in Postfix per-user bcc lookup files.

= General (All backends should apply these steps) =

== Add new alias 'virusalert' in Postfix for Amavisd ==
Amavisd will send an email notification to address "virusalert@[YOUR_HOSTNAME]" by default, but we don't have this user in Postfix alias file (/etc/postfix/aliases on Linux/OpenBSD, or /usr/local/etc/postfix/aliases on FreeBSD) or SQL/LDAP database, so emails are not delivered. Below steps add a alias in Postfix alias file, and it will be forwarded to root user by default.

Add new alias (Note, use '/usr/local/etc/postfix/aliases' on FreeBSD instead), and update the database:
{{cmd|<pre>
# echo 'virusalert: root' >> /etc/postfix/aliases
# postalias /etc/postfix/aliases
</pre>}}

== Upgrade Roundcube webmail to the latest 0.8.6 ==
There's zero day vulnerability in Roundcubemail-0.8.5 and older releases, please follow this tutorial to upgrade Roundcube webmail to the latest 0.8.6 immediately: [[IRedMail/FAQ/Upgrade.Roundcube.Webmail |Upgrade Roundcube webmail]]

About the zero day vulnerability, please refer to this thread: http://lists.roundcube.net/pipermail/dev/2013-March/022328.html

== Upgrade iRedAPD (Postfix policy server) to the latest 1.4.0 ==
Please follow this tutorial to upgrade iRedAPD to the latest stable release: [[IRedMail/FAQ/Upgrade.iRedAPD |How to upgrade iRedAPD]]

== Upgrade iRedAdmin (open source edition) to the latest 0.2.1 ==
Please follow this tutorial to upgrade iRedAdmin open source edition to the latest stable release: [[IRedMail/FAQ/Upgrade.iRedAdmin.Open.Source.Edition |How to upgrade iRedAdmin (open source edition) to the latest stable release]]

= OpenLDAP backend special =
== Fix incorrect LDAP query filter in Postfix ==
If you add external email addresses as mail list members, iRedAdmin-Pro will store them in attribute '''memberOfGroup''', this will cause exported LDIF data cannot be restored. Below are steps to fix this issue.
=== Use the latest LDAP schema file provided by iRedMail ===
To fix this issue, we need the latest LDAP schema file provided by iRedMail. Steps are:
* Download the newest iRedMail ldap schema file
* Copy old ldap schema file as a backup copy
* Replace the old one
* Restart OpenLDAP service.

Here we go:

* On RHEL/CentOS/Scientific Linux (both release 5.x and 6.x), openSUSE, Gentoo, OpenBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/openldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/openldap/schema/
# /etc/init.d/slapd restart # <-- Or: /etc/init.d/ldap restart
</pre>}}

* On Debian/Ubuntu:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /etc/ldap/schema/
# /etc/init.d/slapd restart
</pre>}}

* On FreeBSD:
{{cmd|<pre>
# cd /tmp
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/iredmail.schema

# cd /usr/local/etc/ldap/schema/
# cp iredmail.schema iredmail.schema.bak

# cp -f /tmp/iredmail.schema /usr/local/etc/openldap/schema/
# /etc/init.d/slapd restart
</pre>}}

=== Update existing accounts ===
* Download python script used to adding missing values.
{{cmd|<pre>
# cd /root/
# wget https://bitbucket.org/zhb/iredmail/raw/default/extra/update/updateLDAPValues_083_to_084.py
</pre>}}
Open updateLDAPValues_083_to_084.py, config LDAP server related settings in file head. e.g.
File: updateLDAPValues_083_to_084.py
{{cfg|updateLDAPValues_083_to_084.py|<pre>
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'
</pre>}}
Tip:
* You can find them in iRedAdmin config file or iRedMail.tips file under your iRedMail installation directory.
* Use 'cn=Manager' instead of 'cn=vmailadmin' here is ok too.

Execute this script, it will fix incorrect values and add correct ones:
{{cmd|<pre>
# python updateLDAPValues_083_to_084.py
</pre>}}

=== Fix incorrect LDAP query filter in Postfix ===
* On Linux/OpenBSD, please update '''/etc/postfix/ldap/virtual_group_maps.cf'''. On FreeBSD, update '''/usr/local/etc/postfix/ldap/virtual_group_maps.cf''' instead.
{{cfg|virtual_group_maps.cf|<pre>
# OLD setting
#query_filter = (&(memberOfGroup=%s)(accountStatus=active)(enabledService=mail)(enabledService=deliver)(|(objectClass=mailUser)(objectClass=mailExternalUser)))

# New setting
query_filter = (&(accountStatus=active)(enabledService=mail)(enabledService=deliver)(|(memberOfGroup=%s)(shadowAddress=%s))(|(objectClass=mailUser)(objectClass=mailExternalUser)))
</pre>}}

== Supports alias domains in Postfix per-user bcc lookup files ==
* In /etc/postfix/ldap/sender_bcc_maps_user.cf, replace "(mail=%s)" by "(|(mail=%s)(&(enabledService=shadowaddress)(shadowAddress=%s)))" in parameter "query_filter =". The final LDAP filter looks like below:
{{cfg|ldap/sender_bcc_maps_user.cf|<pre>
query_filter = (&(|(mail=%s)(&(enabledService=shadowaddress)(shadowAddress=%s)))(objectClass=mailUser)(accountStatus=active)(enabledService=mail)(enabledService=senderbcc))
</pre>}}

* Perform the same modification in file /etc/postfix/ldap/recipient_bcc_maps_user.cf, the final LDAP filter looks like below:
{{cfg|ldap/recipient_bcc_maps_user.cf|<pre>
query_filter = (&(|(mail=%s)(&(enabledService=shadowaddress)(shadowAddress=%s)))(objectClass=mailUser)(accountStatus=active)(enabledService=mail)(enabledService=recipientbcc))
</pre>}}

* Restarting Postfix service is required.

== Create addition SQL index for Amavisd database ==
We need one more SQL index for Amavisd database, it's used to speed up performance of viewing quarantined mails.
* Important Note: It will take a long time if you have many records in table '''msgs'''.
{{cmd|<pre>
$ mysql -uroot -p
mysql> USE amavisd;
mysql> ALTER TABLE msgs ADD INDEX (quar_type);
</pre>}}

= MySQL backend special =
== Add 4 new columns used for per-user restriction ==
New version of iRedAPD (Postfix policy daemon) requires 4 new columns in table '''vmail.mailbox''': allowedsenders, rejectedsenders, allowedrecipients, rejectedrecipients. They're used for per-user restriction. For example, you can now define who can send email to your local user, or your user can send email to which external domains or users.

Please login to MySQL server as root user, execute SQL commands to add required columns and indexes.
{{cmd|<pre>
# mysql -uroot -p
mysql> USE vmail;
mysql> ALTER TABLE mailbox ADD COLUMN allowedsenders TEXT NOT NULL DEFAULT '';
mysql> ALTER TABLE mailbox ADD COLUMN rejectedsenders TEXT NOT NULL DEFAULT '';
mysql> ALTER TABLE mailbox ADD COLUMN allowedrecipients TEXT NOT NULL DEFAULT '';
mysql> ALTER TABLE mailbox ADD COLUMN rejectedrecipients TEXT NOT NULL DEFAULT '';
</pre>}}

Supported formats of sender/recipients are:
* user@example.com: single user
* @example.com: single domain
* @'''.'''example.com: domain and its sub domain
* '''@.''': any users.

Multiple senders/recipients must be separated by comma, for example:
{{cmd|<pre>
sql> INSERT INTO mailbox SET allowedsenders='@gmail.com,user@example.com';
</pre>}}
== Create addition SQL index for Amavisd database ==
We need one more SQL index for Amavisd database, it's used to speed up performance of viewing quarantined mails.
* Important Note: It will take a long time if you have many records in table '''msgs'''.
{{cmd|<pre>
$ mysql -uroot -p
mysql> USE amavisd;
mysql> ALTER TABLE msgs ADD INDEX (quar_type);
</pre>}}

= PostgreSQL backend special =
== Add 4 new columns used for per-user restriction ==
New version of iRedAPD (Postfix policy daemon) requires 4 new columns in table '''vmail.mailbox''': allowedsenders, rejectedsenders, allowedrecipients, rejectedrecipients. They're used for per-user restriction. For example, you can now define who can send email to your local user, or your user can send email to which external domains or users.

Please switch to PostgreSQL daemon user, then execute SQL commands to add required columns and indexes:
On Linux, PostgreSQL daemon user is postgres.
On FreeBSD, PostgreSQL daemon user is pgsql.
On OpenBSD, PostgreSQL daemon user is """_postgresql".
{{cmd|<pre>
# su - postgres
$ psql -d vmail
sql> ALTER TABLE mailbox ADD COLUMN allowedsenders TEXT NOT NULL DEFAULT '';
sql> ALTER TABLE mailbox ADD COLUMN rejectedsenders TEXT NOT NULL DEFAULT '';
sql> ALTER TABLE mailbox ADD COLUMN allowedrecipients TEXT NOT NULL DEFAULT '';
sql> ALTER TABLE mailbox ADD COLUMN rejectedrecipients TEXT NOT NULL DEFAULT '';
</pre>}}

Supported formats of sender/recipients are:
* user@example.com: single user
* @example.com: single domain
* @'''.'''example.com: domain and its sub domain
* '''@.''': any users.

Multiple senders/recipients must be separated by comma, for example:
{{cmd|<pre>
sql> INSERT INTO mailbox SET allowedsenders='@gmail.com,user@example.com';
</pre>}}

== Create addition SQL index for Amavisd database ==
We need one more SQL index for Amavisd database, it's used to speed up performance of viewing quarantined mails.
* Important Note: It will take a long time if you have many records in table '''msgs'''.

Please switch to PostgreSQL daemon user, then execute SQL commands to add required columns and indexes:
* On Linux, PostgreSQL daemon user is postgres.
* On FreeBSD, PostgreSQL daemon user is pgsql.
* On OpenBSD, PostgreSQL daemon user is """_postgresql".
{{cmd|<pre>
# su - postgres
$ psql -d vmail
sql> CREATE INDEX idx_msgs_quar_type ON msgs (quar_type);
</pre>}}

IRedMail/FAQ/Upgrade.iRedAPD

ZhangHuangbin — Thu, 28 Mar 2013 15:38:24 GMT

ZhangHuangbin:

----
This tutorial describes how to upgrade iRedAPD to the latest stable release, iRedAPD-1.4.0. It's applicable on all Linux/BSD distributions supported by iRedMail.

Important notes:
* Since iRedAPD-1.4.0, we use Python source file as config file, not '.ini' format anymore.
* We don't need second instance, '''iredapd-rr''', anymore.
----

* Download the latest stable release here: http://iredmail.org/yum/misc/ For example, iRedAPD-1.4.0.tar.bz2.
* Upload it to your iRedMail server. Assume it's '''/root/iRedAPD-1.4.0.tar.bz2''' on the server.
* Extract downloaded package and move to /opt/.
{{cmd|<pre>
# tar xjf /root/iRedAPD-1.4.0.tar.bz2 -C /opt/
</pre>}}
You get a new directory: /opt/iRedAPD-1.4.0/.

* Set correct owner and permission:
{{cmd|<pre>
# chown -R iredapd:iredapd /opt/iRedAPD-1.4.0
# chmod -R 0700 /opt/iRedAPD-1.4.0
</pre>}}

* Generate new config file from sample file, and set correct file owner and permission.
{{cmd|<pre>
# cd /opt/iRedAPD-1.4.0/
# cp settings.py.sample settings.py
# chown -R iredapd:iredapd settings.py
# chmod -R 0600 settings.py
</pre>}}
WARNING: Config file '''/opt/iredapd/settings.py''' contains sensitive infomation (username, password), please don't make it world-readable. Permission 0600 is the best.

* Please open '''/opt/iredapd/settings.py''', and sync settings with old iRedAPD config file '''/opt/iRedAPD-[OLD-VERSION]/etc/iredapd.ini'''.
** In old version of iRedAPD, all parameters under "[ldap]" section are now new parameters start with '''ldap_'''.
** In old version of iRedAPD, all parameters under "[sql]" (or "[mysql]") section are now new parameters start with '''sql_'''.

* After sync settings, please copy new RC script for your server. We have scripts for different Please copy the proper one for your server. For example:
** iredapd.debian: For Debian and Ubuntu.
** iredapd.freebsd: For FreeBSD. Please copy to /usr/local/etc/rc.d/.
** iredapd.gentoo: For Gentoo Linux.
** iredapd.openbsd: For OpenBSD. Please copy to /etc/rc.d/.
** iredapd.opensuse: For openSUSE.
** iredapd.rhel: For Red Hat, CentOS, Scientific Linux.
{{cmd|<pre>
# cp /opt/iredapd/rc_scripts/iredapd.rhel /etc/init.d/iredapd
# chmod +x /etc/init.d/iredapd
</pre>}}
* Remove symbol link of old release:
{{cmd|<pre>
# rm -i /opt/iredapd # <- Don't not end with '/'.
</pre>}}

* Create symbol link to the latest release:
{{cmd|<pre>
# cd /opt/
# ln -s iRedAPD-1.4.0 iredapd
</pre>}}

* Restart iRedAPD service:
{{cmd|<pre>
#
# ---- On Linux ----
#
# /etc/init.d/iredapd restart

#
# ---- On FreeBSD ----
#
# /usr/local/etc/rc.d/iredapd restart

#
# ---- On OpenBSD ----
#
# /etc/rc.d/iredapd restart
</pre>}}

* If you don't have file '''/etc/init.d/iredapd-rr''' on Linux, or '''/etc/rc.d/iredapd-rr''' on OpenBSD, or '''/usr/local/etc/rc.d/iredapd-rr''' on FreeBSD, it's safe to ignore below steps. But if you have it, please stop service '''iredapd-rr''', then move all enabled plugin names listed in '''/opt/iRedAPD-[OLD_VERSION]/etc/iredapd-rr.ini''' to our new config file '''/opt/iredapd/settings.py''', in parameter '''plugins = '''.
{{cmd|<pre>
# /etc/init.d/iredapd-rr stop
# rm /etc/init.d/iredapd-rr
</pre>}}

Check whether you have '''check_policy_service inet:127.0.0.1:7778''' in Postfix config file '''/etc/postfix/main.cf''' (Linux/OpenBSD) or '''/usr/local/etc/postfix/main.cf''', if you have it, please remove '''check_policy_service inet:127.0.0.1:7778''', then restart Postfix service.

That's all.

[[Category: FAQ]]
[[Category: iRedMail/FAQ]]

IRedMail/FAQ/Upgrade.iRedAPD

ZhangHuangbin — Thu, 28 Mar 2013 15:36:44 GMT

ZhangHuangbin:

----
This tutorial describes how to upgrade iRedAPD to the latest stable release, iRedAPD-1.4.0. It's applicable on all Linux/BSD distributions supported by iRedMail.

Important notes:
* Since iRedAPD-1.4.0, we use Python source file as config file, not '.ini' format anymore.
* We don't need second instance, '''iredapd-rr''', anymore.
----

* Download the latest stable release here: http://iredmail.org/yum/misc/ For example, iRedAPD-1.4.0.tar.bz2.
* Upload it to your iRedMail server. Assume it's '''/root/iRedAPD-1.4.0.tar.bz2''' on the server.
* Extract downloaded package and move to /opt/.
{{cmd|<pre>
# tar xjf /root/iRedAPD-1.4.0.tar.bz2 -C /opt/
</pre>}}
You get a new directory: /opt/iRedAPD-1.4.0/.

* Set correct owner and permission:
{{cmd|<pre>
# chown -R iredapd:iredapd /opt/iRedAPD-1.4.0
# chmod -R 0700 /opt/iRedAPD-1.4.0
</pre>}}

* Generate new config file from sample file, and set correct file owner and permission.
{{cmd|<pre>
# cd /opt/iRedAPD-1.4.0/
# cp settings.py.sample settings.py
# chown -R iredapd:iredapd settings.py
# chmod -R 0600 settings.py
</pre>}}
WARNING: Config file '''/opt/iredapd/settings.py''' contains sensitive infomation (username, password), please don't make it world-readable. Permission 0600 is the best.

* Please open '''/opt/iredapd/settings.py''', and sync settings with old iRedAPD config file '''/opt/iRedAPD-[OLD-VERSION]/etc/iredapd.ini'''.
** In old version of iRedAPD, all parameters under "[ldap]" section are now new parameters start with '''ldap_'''.
** In old version of iRedAPD, all parameters under "[sql]" (or "[mysql]") section are now new parameters start with '''sql_'''.

* After sync settings, please copy new RC script for your server. We have scripts for different Please copy the proper one for your server. For example:
** iredapd.debian: For Debian and Ubuntu.
** iredapd.freebsd: For FreeBSD. Please copy to /usr/local/etc/rc.d/.
** iredapd.gentoo: For Gentoo Linux.
** iredapd.openbsd: For OpenBSD.
** iredapd.opensuse: For openSUSE.
** iredapd.rhel: For Red Hat, CentOS, Scientific Linux.
{{cmd|<pre>
# cp /opt/iredapd/rc_scripts/iredapd.rhel /etc/init.d/iredapd
# chmod +x /etc/init.d/iredapd
</pre>}}
* Remove symbol link of old release:
{{cmd|<pre>
# rm -i /opt/iredapd # <- Don't not end with '/'.
</pre>}}

* Create symbol link to the latest release:
{{cmd|<pre>
# cd /opt/
# ln -s iRedAPD-1.4.0 iredapd
</pre>}}

* Restart iRedAPD service:
{{cmd|<pre>
#
# ---- On Linux ----
#
# /etc/init.d/iredapd restart

#
# ---- On FreeBSD ----
#
# /usr/local/etc/rc.d/iredapd restart

#
# ---- On OpenBSD ----
#
# /etc/rc.d/iredapd restart
</pre>}}

* If you don't have file '''/etc/init.d/iredapd-rr''' on Linux, or '''/etc/rc.d/iredapd-rr''' on OpenBSD, or '''/usr/local/etc/rc.d/iredapd-rr''' on FreeBSD, it's safe to ignore below steps. But if you have it, please stop service '''iredapd-rr''', then move all enabled plugin names listed in '''/opt/iRedAPD-[OLD_VERSION]/etc/iredapd-rr.ini''' to our new config file '''/opt/iredapd/settings.py''', in parameter '''plugins = '''.
{{cmd|<pre>
# /etc/init.d/iredapd-rr stop
# rm /etc/init.d/iredapd-rr
</pre>}}

Check whether you have '''check_policy_service inet:127.0.0.1:7778''' in Postfix config file '''/etc/postfix/main.cf''' (Linux/OpenBSD) or '''/usr/local/etc/postfix/main.cf''', if you have it, please remove '''check_policy_service inet:127.0.0.1:7778''', then restart Postfix service.

That's all.

[[Category: FAQ]]
[[Category: iRedMail/FAQ]]

IRedMail/FAQ/Upgrade.iRedAPD

ZhangHuangbin — Thu, 28 Mar 2013 15:32:35 GMT

ZhangHuangbin:

----
This tutorial describes how to upgrade iRedAPD to the latest stable release, iRedAPD-1.4.0. It's applicable on all Linux/BSD distributions supported by iRedMail.

Important notes:
* Since iRedAPD-1.4.0, we use Python source file as config file, not '.ini' format anymore.
* We don't need second instance, '''iredapd-rr''', anymore.
----

* Download the latest stable release here: http://iredmail.org/yum/misc/ For example, iRedAPD-1.4.0.tar.bz2.
* Upload it to your iRedMail server. Assume it's '''/root/iRedAPD-1.4.0.tar.bz2''' on the server.
* Extract downloaded package and move to /opt/.
{{cmd|<pre>
# tar xjf /root/iRedAPD-1.4.0.tar.bz2 -C /opt/
</pre>}}
You get a new directory: /opt/iRedAPD-1.4.0/.

* Set correct owner and permission:
{{cmd|<pre>
# chown -R iredapd:iredapd /opt/iRedAPD-1.4.0
# chmod -R 0700 /opt/iRedAPD-1.4.0
</pre>}}

* Generate new config file from sample file, and set correct file owner and permission.
{{cmd|<pre>
# cd /opt/iRedAPD-1.4.0/
# cp settings.py.sample settings.py
# chown -R iredapd:iredapd settings.py
# chmod -R 0600 settings.py
</pre>}}
WARNING: Config file '''/opt/iredapd/settings.py''' contains sensitive infomation (username, password), please don't make it world-readable. Permission 0600 is the best.

* Please open '''/opt/iredapd/settings.py''', and sync settings with old iRedAPD config file '''/opt/iRedAPD-[OLD-VERSION]/etc/iredapd.ini'''.
** In old version of iRedAPD, all parameters under "[ldap]" section are now new parameters start with '''ldap_'''.
** In old version of iRedAPD, all parameters under "[sql]" (or "[mysql]") section are now new parameters start with '''sql_'''.

* After sync settings, please copy new RC script for your server. We have scripts for different Please copy the proper one for your server. For example:
** iredapd.debian: For Debian and Ubuntu.
** iredapd.freebsd: For FreeBSD. Please copy to /usr/local/etc/rc.d/.
** iredapd.gentoo: For Gentoo Linux.
** iredapd.openbsd: For OpenBSD.
** iredapd.opensuse: For openSUSE.
** iredapd.rhel: For Red Hat, CentOS, Scientific Linux.
{{cmd|<pre>
# cp /opt/iredapd/rc_scripts/iredapd.rhel /etc/init.d/iredapd
</pre>}}
* Remove symbol link of old release:
{{cmd|<pre>
# rm -i /opt/iredapd # <- Don't not end with '/'.
</pre>}}

* Create symbol link to the latest release:
{{cmd|<pre>
# cd /opt/
# ln -s iRedAPD-1.4.0 iredapd
</pre>}}

* Restart iRedAPD service:
{{cmd|<pre>
#
# ---- On Linux ----
#
# /etc/init.d/iredapd restart

#
# ---- On FreeBSD ----
#
# /usr/local/etc/rc.d/iredapd restart

#
# ---- On OpenBSD ----
#
# /etc/rc.d/iredapd restart
</pre>}}

* If you don't have file '''/etc/init.d/iredapd-rr''' on Linux, or '''/etc/rc.d/iredapd-rr''' on OpenBSD, or '''/usr/local/etc/rc.d/iredapd-rr''' on FreeBSD, it's safe to ignore below steps. But if you have it, please stop service '''iredapd-rr''', then move all enabled plugin names listed in '''/opt/iRedAPD-[OLD_VERSION]/etc/iredapd-rr.ini''' to our new config file '''/opt/iredapd/settings.py''', in parameter '''plugins = '''.
{{cmd|<pre>
# /etc/init.d/iredapd-rr stop
# rm /etc/init.d/iredapd-rr
</pre>}}

Check whether you have '''check_policy_service inet:127.0.0.1:7778''' in Postfix config file '''/etc/postfix/main.cf''' (Linux/OpenBSD) or '''/usr/local/etc/postfix/main.cf''', if you have it, please remove '''check_policy_service inet:127.0.0.1:7778''', then restart Postfix service.

That's all.

[[Category: FAQ]]
[[Category: iRedMail/FAQ]]

IRedMail/FAQ/Upgrade.Roundcube.Webmail

ZhangHuangbin — Thu, 28 Mar 2013 14:45:02 GMT

ZhangHuangbin:

__TOC__

----
WARNING: There's a zero day vulnerability found in Roundcubemail-0.8.5 and older releases, please upgrade your running Roundcube webmail to the latest roundcubemail-0.8.6 immediately.
----

This tutorial is used to upgrade Roundcube from old release to the latest release. Ideally, you can upgrade whichever old release to the latest Roundcube release with this tutorial. Post issues in our online support forum: http://www.iredmail.org/forum/

= Backup current Roundcube webmail database =

We must backup current Roundcube database before we go further.
{{cmd|<pre>
#
# ---- For MySQL backend
#
# mysqldump -u root -p roundcubemail > /root/mysql-db-roundcubemail.sql

#
# ---- For PostgreSQL backend
#
# su - postgres
# pg_dump roundcubemail > ~/db-roundcubemail.sql
</pre>}}

= Upgrade Roundcube webmail =
* Download the latest Roundcube webmail here: http://roundcube.net/. Here we take 0.8.6 for example: /root/roundcubemail-0.8.6.tar.gz

* Extract it in the right place.

{{cmd|<pre>
# ---- For RHEL/CentOS/Scientific Linux ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /var/www/
# cd /var/www/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown -R apache:apache roundcubemail-0.8.6

# ---- For Debian/Ubuntu ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /usr/share/apache2/
# cd /usr/share/apache2/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown -R www-data:www-data roundcubemail-0.8.6

# ---- For Gentoo Linux ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /var/www/
# cd /var/www/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown -R apache:apache roundcubemail-0.8.6

# ---- For openSUSE ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /srv/www/
# cd /srv/www/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown -R wwwrun:www roundcubemail-0.8.6

# ---- For FreeBSD ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /usr/local/www/
# cd /usr/local/www/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown -R www:www roundcubemail-0.8.6
</pre>}}

* Sync settings in config files '''roundcubemail-0.8.6/config/db.inc.php''' and '''roundcubemail-0.8.6/config/main.inc.php''' from old release.
** New version of Roundcube may add new config options, so it's not recommended to simply copy old config files.

* Set correct time zone in your PHP config file '''php.ini'''. For example:
** On RHEL/CentOS/Scientific Linux, it's '''/etc/php.ini'''
** On Debian/Ubuntu, it's '''/etc/php5/apache2/php.ini'''
** On Gentoo Linux, it's '''/etc/php/apache2-php5.3/php.ini'''
** On openSUSE, it's '''/etc/php5/apache2/php.ini'''
** on FreeBSD, it's '''/usr/local/etc/php.ini'''
{{cmd|<pre>
date.timezone = "Europe/Paris"
</pre>}}

* Upgrade Roundcube database structure by importing shipped SQL file. NOTE: It upgrades SQL structure from Roundcubemail-0.1, so it will report many error messages. but it's OK to ignore them all.
{{cmd|<pre>
#
# ---- For MySQL backend
#
# mysql -uroot -p
mysql> USE roundcubemail;
mysql> SOURCE roundcubemail-0.8.6/SQL/mysql.update.sql;

#
# ---- For PostgreSQL backend
#
# su - postgres
$ psql -d roundcubemail
sql> \i /var/www/roundcubemail-0.8.6/SQL/postgres.update.sql;
</pre>}}

* Now you need to sync config files for Roundcube plugins. iRedMail enables two plugins by default, you can check file '''roundcubemail-[OLD_VERSION]/config/main.inc.php''' to see whether you have addition plugins enabled. For example:
** roundcubemail-0.8.6/plugins/password/: Used to allow mail users to change their own passwords. Config file is roundcubemail-0.8.6/plugins/password/config.inc.php.
** roundcubemail-0.8.6/plugins/managesieve/: Used to allow mail users to manage their own mail filter rules. Config file is roundcubemail-0.8.6/plugins/managesieve/config.inc.php.
{{cfg|roundcubemail-[OLD_VERSION]/config/main.inc.php|<pre>
$rcmail_config['plugins'] = array("password", "managesieve");
</pre>}}

Please sync plugin settings between new Rondcubewebmail release and old one.

* Sync settings in roundcubemail-0.8.6/.htaccess with old version. Some php settings could become required.
* If you're using build-in addressbook, run indexing script roundcubemail-0.8.6/bin/indexcontacts.sh:
{{cmd|<pre>
# cd roundcubemail-0.8.6/
# chmod +x bin/indexcontacts.sh
# ./bin/indexcontacts.sh
</pre>}}

* Restrict accessing to sensitive files:
{{cmd|<pre>
# chmod 0000 roundcubemail-0.8.6/{CHANGELOG,INSTALL,LICENSE,README,UPGRADING,installer,SQL}
</pre>}}

* Remove symbol link and create a new one, link to new release:
{{cmd|<pre>
# rm roundcubemail
# ln -s roundcubemail-0.8.6 roundcubemail
</pre>}}

That's all, restarting Apache service is required.

Note: Please track Roundcube log file to see whether there's missing PHP modules, you should install missed ones manually.

= References =
* Roundcube official guide about upgrading: http://trac.roundcube.net/wiki/Howto_Upgrade

[[Category: FAQ]]
[[Category: iRedMail/FAQ]]

IRedMail/FAQ/Upgrade.Roundcube.Webmail

ZhangHuangbin — Thu, 28 Mar 2013 14:42:50 GMT

ZhangHuangbin:

__TOC__

----
WARNING: There's a zero day vulnerability found in Roundcubemail-0.8.5 and older releases, please upgrade your running Roundcube webmail to the latest roundcubemail-0.8.6 immediately.
----

This tutorial is used to upgrade Roundcube from old release to the latest release. Ideally, you can upgrade whichever old release to the latest Roundcube release with this tutorial. Post issues in our online support forum: http://www.iredmail.org/forum/

* Backup current Roundcube database first.

{{cmd|<pre>
#
# ---- For MySQL backend
#
# mysqldump -u root -p roundcubemail > /root/mysql-db-roundcubemail.sql

#
# ---- For PostgreSQL backend
#
# su - postgres
# pg_dump roundcubemail > ~/db-roundcubemail.sql
</pre>}}

* Download the latest Roundcube webmail here: http://roundcube.net/. Here we take 0.8.6 for example: /root/roundcubemail-0.8.6.tar.gz

* Extract it in the right place.

{{cmd|<pre>
# ---- For RHEL/CentOS/Scientific Linux ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /var/www/
# cd /var/www/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown -R apache:apache roundcubemail-0.8.6

# ---- For Debian/Ubuntu ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /usr/share/apache2/
# cd /usr/share/apache2/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown -R www-data:www-data roundcubemail-0.8.6

# ---- For Gentoo Linux ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /var/www/
# cd /var/www/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown -R apache:apache roundcubemail-0.8.6

# ---- For openSUSE ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /srv/www/
# cd /srv/www/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown -R wwwrun:www roundcubemail-0.8.6

# ---- For FreeBSD ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /usr/local/www/
# cd /usr/local/www/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown -R www:www roundcubemail-0.8.6
</pre>}}

* Sync settings in config files '''roundcubemail-0.8.6/config/db.inc.php''' and '''roundcubemail-0.8.6/config/main.inc.php''' from old release.
** New version of Roundcube may add new config options, so it's not recommended to simply copy old config files.

* Set correct time zone in your PHP config file '''php.ini'''. For example:
** On RHEL/CentOS/Scientific Linux, it's '''/etc/php.ini'''
** On Debian/Ubuntu, it's '''/etc/php5/apache2/php.ini'''
** On Gentoo Linux, it's '''/etc/php/apache2-php5.3/php.ini'''
** On openSUSE, it's '''/etc/php5/apache2/php.ini'''
** on FreeBSD, it's '''/usr/local/etc/php.ini'''
{{cmd|<pre>
date.timezone = "Europe/Paris"
</pre>}}

* Upgrade Roundcube database structure by importing shipped SQL file. NOTE: It upgrades SQL structure from Roundcubemail-0.1, so it will report many error messages. but it's OK to ignore them all.
{{cmd|<pre>
#
# ---- For MySQL backend
#
# mysql -uroot -p
mysql> USE roundcubemail;
mysql> SOURCE roundcubemail-0.8.6/SQL/mysql.update.sql;

#
# ---- For PostgreSQL backend
#
# su - postgres
$ psql -d roundcubemail
sql> \i /var/www/roundcubemail-0.8.6/SQL/postgres.update.sql;
</pre>}}

* Now you need to sync config files for Roundcube plugins. iRedMail enables two plugins by default, you can check file '''roundcubemail-[OLD_VERSION]/config/main.inc.php''' to see whether you have addition plugins enabled. For example:
** roundcubemail-0.8.6/plugins/password/: Used to allow mail users to change their own passwords. Config file is roundcubemail-0.8.6/plugins/password/config.inc.php.
** roundcubemail-0.8.6/plugins/managesieve/: Used to allow mail users to manage their own mail filter rules. Config file is roundcubemail-0.8.6/plugins/managesieve/config.inc.php.
{{cfg|roundcubemail-[OLD_VERSION]/config/main.inc.php|<pre>
$rcmail_config['plugins'] = array("password", "managesieve");
</pre>}}

Please sync plugin settings between new Rondcubewebmail release and old one.

* Sync settings in roundcubemail-0.8.6/.htaccess with old version. Some php settings could become required.
* If you're using build-in addressbook, run indexing script roundcubemail-0.8.6/bin/indexcontacts.sh:
{{cmd|<pre>
# cd roundcubemail-0.8.6/
# chmod +x bin/indexcontacts.sh
# ./bin/indexcontacts.sh
</pre>}}

* Restrict accessing to sensitive files:
{{cmd|<pre>
# chmod 0000 roundcubemail-0.8.6/{CHANGELOG,INSTALL,LICENSE,README,UPGRADING,installer,SQL}
</pre>}}

* Remove symbol link and create a new one, link to new release:
{{cmd|<pre>
# rm roundcubemail
# ln -s roundcubemail-0.8.6 roundcubemail
</pre>}}

That's all, restarting Apache service is required.

Note: Please track Roundcube log file to see whether there's missing PHP modules, you should install missed ones manually.

[[Category: FAQ]]
[[Category: iRedMail/FAQ]]

IRedMail/FAQ/Upgrade.Roundcube.Webmail

ZhangHuangbin — Thu, 28 Mar 2013 14:39:03 GMT

ZhangHuangbin:

__TOC__

----
WARNING: There's a zero day vulnerability found in Roundcubemail-0.8.5 and older releases, please upgrade your running Roundcube webmail to the latest roundcubemail-0.8.6 immediately.
----

This tutorial is used to upgrade Roundcube from old release to the latest release. Ideally, you can upgrade whichever old release to the latest Roundcube release with this tutorial. Post issues in our online support forum: http://www.iredmail.org/forum/

* Backup current Roundcube database first.

{{cmd|<pre>
#
# ---- For MySQL backend
#
# mysqldump -u root -p roundcubemail > /root/mysql-db-roundcubemail.sql

#
# ---- For PostgreSQL backend
#
# su - postgres
# pg_dump roundcubemail > ~/db-roundcubemail.sql
</pre>}}

* Download the latest Roundcube webmail here: http://roundcube.net/. Here we take 0.8.6 for example: /root/roundcubemail-0.8.6.tar.gz

* Extract it in the right place.

{{cmd|<pre>
# ---- For RHEL/CentOS/Scientific Linux ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /var/www/
# cd /var/www/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown -R apache:apache roundcubemail-0.8.6

# ---- For Debian/Ubuntu ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /usr/share/apache2/
# cd /usr/share/apache2/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown -R www-data:www-data roundcubemail-0.8.6

# ---- For Gentoo Linux ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /var/www/
# cd /var/www/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown -R apache:apache roundcubemail-0.8.6

# ---- For openSUSE ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /srv/www/
# cd /srv/www/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown -R wwwrun:www roundcubemail-0.8.6

# ---- For FreeBSD ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /usr/local/www/
# cd /usr/local/www/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown -R www:www roundcubemail-0.8.6
</pre>}}

* Sync settings in config files '''roundcubemail-0.8.6/config/db.inc.php''' and '''roundcubemail-0.8.6/config/main.inc.php''' from old release.
** New version of Roundcube may add new config options, so it's not recommended to simply copy old config files.

* Set correct time zone in your PHP config file '''php.ini'''. For example:
** On RHEL/CentOS/Scientific Linux, it's '''/etc/php.ini'''
** On Debian/Ubuntu, it's '''/etc/php5/apache2/php.ini'''
** On Gentoo Linux, it's '''/etc/php/apache2-php5.3/php.ini'''
** On openSUSE, it's '''/etc/php5/apache2/php.ini'''
** on FreeBSD, it's '''/usr/local/etc/php.ini'''
{{cmd|<pre>
date.timezone = "Europe/Paris"
</pre>}}

* Restart Apache web server if you have new required packages or PHP modules installed.

* Upgrade Roundcube database structure by importing shipped SQL file. NOTE: It upgrades SQL structure from Roundcubemail-0.1, so it will report many error messages. but it's OK to ignore them all.
{{cmd|<pre>
#
# ---- For MySQL backend
#
# mysql -uroot -p
mysql> USE roundcubemail;
mysql> SOURCE roundcubemail-0.8.6/SQL/mysql.update.sql;

#
# ---- For PostgreSQL backend
#
# su - postgres
$ psql -d roundcubemail
sql> \i /var/www/roundcubemail-0.8.6/SQL/postgres.update.sql;
</pre>}}

* Roundcube installer also gives the way to download main.inc.php and db.inc.php files, please download them and replace your old config files. Because old config files might miss some parameters. Don't forget to fix file permission after replaced:
{{cmd|<pre>
# ---- On RHEL/CentOS/Scientific Linux ----
# chown apache:apache roundcubemail-0.8.6/config/*

# ---- On Debian/Ubuntu ----
# chown www-data:www-data roundcubemail-0.8.6/config/*

# ---- On Gentoo Linux ----
# chown apache:apache roundcubemail-0.8.6/config/*

# ---- On openSUSE ----
# chown wwwrun:www roundcubemail-0.8.6/config/*

# ---- On FreeBSD ----
# chown www:www roundcubemail-0.8.6/config/*
</pre>}}

* After Roundcube installer finished upgrading process, disable installer in config file 'roundcubemail-0.8.6/config/main.inc.php' by updating below parameter:
{{cmd|<pre>
$rcmail_config['enable_installer'] = false;
</pre>}}

* Restrict accessing to sensitive files:
{{cmd|<pre>
# chmod 0000 roundcubemail-0.8.6/{CHANGELOG,INSTALL,LICENSE,README,UPGRADING,installer,SQL}
</pre>}}

* Now you need to sync config files for Roundcube plugins. iRedMail enables two plugins by default, you can check file '''roundcubemail-[OLD_VERSION]/config/main.inc.php''' to see whether you have addition plugins enabled. For example:
** roundcubemail-0.8.6/plugins/password/: Used to allow mail users to change their own passwords. Config file is roundcubemail-0.8.6/plugins/password/config.inc.php.
** roundcubemail-0.8.6/plugins/managesieve/: Used to allow mail users to manage their own mail filter rules. Config file is roundcubemail-0.8.6/plugins/managesieve/config.inc.php.
{{cfg|roundcubemail-[OLD_VERSION]/config/main.inc.php|<pre>
$rcmail_config['plugins'] = array("password", "managesieve");
</pre>}}

Please sync plugin settings between new Rondcubewebmail release and old one.

* Sync settings in roundcubemail-0.8.6/.htaccess with old version. Some php settings could become required.
* If you're using build-in addressbook, run indexing script roundcubemail-0.8.6/bin/indexcontacts.sh:
{{cmd|<pre>
# cd roundcubemail-0.8.6/
# chmod +x bin/indexcontacts.sh
# ./bin/indexcontacts.sh
</pre>}}

* Remove symbol link and create a new one, link to new release:
{{cmd|<pre>
# rm roundcubemail
# ln -s roundcubemail-0.8.6 roundcubemail
</pre>}}

That's all, restarting Apache service is required.

Note: Please track Roundcube log file to see whether there's missing PHP modules, you should install missed ones manually.

[[Category: FAQ]]
[[Category: iRedMail/FAQ]]

IRedMail/FAQ/Upgrade.Roundcube.Webmail

ZhangHuangbin — Thu, 28 Mar 2013 14:25:11 GMT

ZhangHuangbin:

__TOC__

----
WARNING: There's a zero day vulnerability found in Roundcubemail-0.8.5 and older releases, please upgrade your running Roundcube webmail to the latest roundcubemail-0.8.6 immediately.
----

This tutorial is used to upgrade Roundcube from old release to the latest release. Ideally, you can upgrade whichever old release to the latest Roundcube release with this tutorial. Post issues in our online support forum: http://www.iredmail.org/forum/

* Backup current Roundcube database first.

{{cmd|<pre>
#
# ---- For MySQL backend
#
# mysqldump -u root -p roundcubemail > /root/mysql-db-roundcubemail.sql

#
# ---- For PostgreSQL backend
#
# su - postgres
# pg_dump roundcubemail > ~/db-roundcubemail.sql
</pre>}}

* Download the latest Roundcube webmail here: http://roundcube.net/. Here we take 0.8.6 for example: /root/roundcubemail-0.8.6.tar.gz

* Extract it in the right place.

{{cmd|<pre>
# ---- For RHEL/CentOS/Scientific Linux ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /var/www/
# cd /var/www/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown -R apache:apache roundcubemail-0.8.6

# ---- For Debian/Ubuntu ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /usr/share/apache2/
# cd /usr/share/apache2/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown -R www-data:www-data roundcubemail-0.8.6

# ---- For Gentoo Linux ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /var/www/
# cd /var/www/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown -R apache:apache roundcubemail-0.8.6

# ---- For openSUSE ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /srv/www/
# cd /srv/www/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown -R wwwrun:www roundcubemail-0.8.6

# ---- For FreeBSD ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /usr/local/www/
# cd /usr/local/www/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown -R www:www roundcubemail-0.8.6
</pre>}}

* Sync settings in config files '''roundcubemail-0.8.6/config/db.inc.php''' and '''roundcubemail-0.8.6/config/main.inc.php''' from old release.
** New version of Roundcube may add new config options, so it's not recommended to simply copy old config files.

* Set correct time zone in your PHP config file '''php.ini'''. For example:
** On RHEL/CentOS/Scientific Linux, it's '''/etc/php.ini'''
** On Debian/Ubuntu, it's '''/etc/php5/apache2/php.ini'''
** On Gentoo Linux, it's '''/etc/php/apache2-php5.3/php.ini'''
** On openSUSE, it's '''/etc/php5/apache2/php.ini'''
** on FreeBSD, it's '''/usr/local/etc/php.ini'''
{{cmd|<pre>
date.timezone = "Europe/Paris"
</pre>}}

* Restart Apache web server if you have new required packages or PHP modules installed.

* Upgrade Roundcube database structure by importing shipped SQL file:
{{cmd|<pre>
# mysql -uroot -p
mysql> USE roundcubemail;
mysql> SOURCE roundcubemail-0.8.6/SQL/mysql.update.sql;
</pre>}}

* Roundcube installer also gives the way to download main.inc.php and db.inc.php files, please download them and replace your old config files. Because old config files might miss some parameters. Don't forget to fix file permission after replaced:
{{cmd|<pre>
# ---- On RHEL/CentOS/Scientific Linux ----
# chown apache:apache roundcubemail-0.8.6/config/*

# ---- On Debian/Ubuntu ----
# chown www-data:www-data roundcubemail-0.8.6/config/*

# ---- On Gentoo Linux ----
# chown apache:apache roundcubemail-0.8.6/config/*

# ---- On openSUSE ----
# chown wwwrun:www roundcubemail-0.8.6/config/*

# ---- On FreeBSD ----
# chown www:www roundcubemail-0.8.6/config/*
</pre>}}

* After Roundcube installer finished upgrading process, disable installer in config file 'roundcubemail-0.8.6/config/main.inc.php' by updating below parameter:
{{cmd|<pre>
$rcmail_config['enable_installer'] = false;
</pre>}}

* Restrict accessing to sensitive files:
{{cmd|<pre>
# chmod 0000 roundcubemail-0.8.6/{CHANGELOG,INSTALL,LICENSE,README,UPGRADING,installer,SQL}
</pre>}}

* Now you need to sync config files for Roundcube plugins. iRedMail enables two plugins by default, you can check file '''roundcubemail-[OLD_VERSION]/config/main.inc.php''' to see whether you have addition plugins enabled. For example:
** roundcubemail-0.8.6/plugins/password/: Used to allow mail users to change their own passwords. Config file is roundcubemail-0.8.6/plugins/password/config.inc.php.
** roundcubemail-0.8.6/plugins/managesieve/: Used to allow mail users to manage their own mail filter rules. Config file is roundcubemail-0.8.6/plugins/managesieve/config.inc.php.
{{cfg|roundcubemail-[OLD_VERSION]/config/main.inc.php|<pre>
$rcmail_config['plugins'] = array("password", "managesieve");
</pre>}}

Please sync settings between new Rondcubewebmail release and old one.

* Remove symbol link and create a new one, link to new release:
{{cmd|<pre>
# rm roundcubemail
# ln -s roundcubemail-0.8.6 roundcubemail
</pre>}}

That's all, restarting Apache service is required.

Note: Please track Roundcube log file to see whether there's missing PHP modules, you should install missed ones manually.

[[Category: FAQ]]
[[Category: iRedMail/FAQ]]

IRedMail/FAQ/Upgrade.Roundcube.Webmail

ZhangHuangbin — Thu, 28 Mar 2013 14:19:30 GMT

ZhangHuangbin:

__TOC__

----
WARNING: There's a zero day vulnerability found in Roundcubemail-0.8.5 and older releases, please upgrade your running Roundcube webmail to the latest roundcubemail-0.8.6 immediately.
----

This tutorial is used to upgrade Roundcube from old release to the latest release. Ideally, you can upgrade whichever old release to the latest Roundcube release with this tutorial. Post issues in our online support forum: http://www.iredmail.org/forum/

* Backup current Roundcube database first.

{{cmd|<pre>
#
# ---- For MySQL backend
#
# mysqldump -u root -p roundcubemail > /root/mysql-db-roundcubemail.sql

#
# ---- For PostgreSQL backend
#
# su - postgres
# pg_dump roundcubemail > ~/db-roundcubemail.sql
</pre>}}

* Download the latest Roundcube webmail here: http://roundcube.net/. Here we take 0.8.6 for example: /root/roundcubemail-0.8.6.tar.gz

* Extract it in the right place.

{{cmd|<pre>
# ---- For RHEL/CentOS/Scientific Linux ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /var/www/
# cd /var/www/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown -R apache:apache roundcubemail-0.8.6

# ---- For Debian/Ubuntu ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /usr/share/apache2/
# cd /usr/share/apache2/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown -R www-data:www-data roundcubemail-0.8.6

# ---- For Gentoo Linux ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /var/www/
# cd /var/www/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown -R apache:apache roundcubemail-0.8.6

# ---- For openSUSE ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /srv/www/
# cd /srv/www/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown -R wwwrun:www roundcubemail-0.8.6

# ---- For FreeBSD ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /usr/local/www/
# cd /usr/local/www/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown -R www:www roundcubemail-0.8.6
</pre>}}

* Copy config files '''db.inc.php''' and '''main.inc.php''' from old release to new release. For example:
{{cmd|<pre>
# cp -p roundcubemail-0.5.2/config/{db.inc.php,main.inc.php} roundcubemail-0.8.6/config/
</pre>}}

* Remove symbol link and create a new one, link to new release:
{{cmd|<pre>
# rm roundcubemail
# ln -s roundcubemail-0.8.6 roundcubemail
</pre>}}

* Enable Roundcube installer by update below setting in roundcubemail-0.8.6/config/main.inc.php:
{{cmd|<pre>
$rcmail_config['enable_installer'] = true;
</pre>}}

* Access Roundcube installer with this URL: httpS://your_server/mail/installer , it will validate required packages, PHP modules and database structure. If the installer reports your server misses some required packages or PHP modules, please install them manually to fix them.

* Set correct time zone in your PHP config file '''php.ini'''. For example:
** On RHEL/CentOS/Scientific Linux, it's '''/etc/php.ini'''
** On Debian/Ubuntu, it's '''/etc/php5/apache2/php.ini'''
** On Gentoo Linux, it's '''/etc/php/apache2-php5.3/php.ini'''
** On openSUSE, it's '''/etc/php5/apache2/php.ini'''
** on FreeBSD, it's '''/usr/local/etc/php.ini'''
{{cmd|<pre>
date.timezone = "Europe/Paris"
</pre>}}

* Restart Apache web server if you have new required packages or PHP modules installed.

* Upgrade Roundcube database structure by importing shipped SQL file:
{{cmd|<pre>
# mysql -uroot -p
mysql> USE roundcubemail;
mysql> SOURCE roundcubemail-0.8.6/SQL/mysql.update.sql;
</pre>}}

* Roundcube installer also gives the way to download main.inc.php and db.inc.php files, please download them and replace your old config files. Because old config files might miss some parameters. Don't forget to fix file permission after replaced:
{{cmd|<pre>
# ---- On RHEL/CentOS/Scientific Linux ----
# chown apache:apache roundcubemail-0.8.6/config/*

# ---- On Debian/Ubuntu ----
# chown www-data:www-data roundcubemail-0.8.6/config/*

# ---- On Gentoo Linux ----
# chown apache:apache roundcubemail-0.8.6/config/*

# ---- On openSUSE ----
# chown wwwrun:www roundcubemail-0.8.6/config/*

# ---- On FreeBSD ----
# chown www:www roundcubemail-0.8.6/config/*
</pre>}}

* After Roundcube installer finished upgrading process, disable installer in config file 'roundcubemail-0.8.6/config/main.inc.php' by updating below parameter:
{{cmd|<pre>
$rcmail_config['enable_installer'] = false;
</pre>}}

* Restrict accessing to sensitive files:
{{cmd|<pre>
# chmod 0000 roundcubemail-0.8.6/{CHANGELOG,INSTALL,LICENSE,README,UPGRADING,installer,SQL}
</pre>}}

* Now you need to sync config files for Roundcube plugins. iRedMail enables two plugins by default, you can check file '''roundcubemail-[OLD_VERSION]/config/main.inc.php''' to see whether you have addition plugins enabled. For example:
** roundcubemail-0.8.6/plugins/password/: Used to allow mail users to change their own passwords. Config file is roundcubemail-0.8.6/plugins/password/config.inc.php.
** roundcubemail-0.8.6/plugins/managesieve/: Used to allow mail users to manage their own mail filter rules. Config file is roundcubemail-0.8.6/plugins/managesieve/config.inc.php.
{{cfg|roundcubemail-[OLD_VERSION]/config/main.inc.php|<pre>
$rcmail_config['plugins'] = array("password", "managesieve");
</pre>}}

Please sync settings between new Rondcubewebmail release and old one.

That's all, restarting Apache service is recommended.

[[Category: FAQ]]
[[Category: iRedMail/FAQ]]

IRedMail/FAQ/Upgrade.Roundcube.Webmail

ZhangHuangbin — Thu, 28 Mar 2013 14:18:30 GMT

ZhangHuangbin:

__TOC__

----
WARNING: There's a zero day vulnerability found in Roundcubemail-0.8.5 and older releases, please upgrade your running Roundcube webmail to the latest roundcubemail-0.8.6 immediately.
----

This tutorial is used to upgrade Roundcube from old release to the latest release. Ideally, you can upgrade whichever old release to the latest Roundcube release with this tutorial. Post issues in our online support forum: http://www.iredmail.org/forum/

* Backup current Roundcube database first.

{{cmd|<pre>
#
# ---- For MySQL backend
#
# mysqldump -u root -p roundcubemail > /root/mysql-db-roundcubemail.sql

#
# ---- For PostgreSQL backend
#
# su - postgres
# pg_dump roundcubemail > ~/db-roundcubemail.sql
</pre>}}

* Download the latest Roundcube webmail here: http://roundcube.net/. Here we take 0.8.6 for example: /root/roundcubemail-0.8.6.tar.gz

* Extract it in the right place.

{{cmd|<pre>
# ---- For RHEL/CentOS/Scientific Linux ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /var/www/
# cd /var/www/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown apache:apache roundcubemail-0.8.6

# ---- For Debian/Ubuntu ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /usr/share/apache2/
# cd /usr/share/apache2/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown www-data:www-data roundcubemail-0.8.6

# ---- For Gentoo Linux ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /var/www/
# cd /var/www/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown apache:apache roundcubemail-0.8.6

# ---- For openSUSE ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /srv/www/
# cd /srv/www/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown wwwrun:www roundcubemail-0.8.6

# ---- For FreeBSD ----
# tar xzf /root/roundcubemail-0.8.6.tar.gz -C /usr/local/www/
# cd /usr/local/www/
# mkdir roundcubemail-0.8.6/{temp,logs}
# chown www:www roundcubemail-0.8.6
</pre>}}

* Copy config files '''db.inc.php''' and '''main.inc.php''' from old release to new release. For example:
{{cmd|<pre>
# cp -p roundcubemail-0.5.2/config/{db.inc.php,main.inc.php} roundcubemail-0.8.6/config/
</pre>}}

* Remove symbol link and create a new one, link to new release:
{{cmd|<pre>
# rm roundcubemail
# ln -s roundcubemail-0.8.6 roundcubemail
</pre>}}

* Enable Roundcube installer by update below setting in roundcubemail-0.8.6/config/main.inc.php:
{{cmd|<pre>
$rcmail_config['enable_installer'] = true;
</pre>}}

* Access Roundcube installer with this URL: httpS://your_server/mail/installer , it will validate required packages, PHP modules and database structure. If the installer reports your server misses some required packages or PHP modules, please install them manually to fix them.

* Set correct time zone in your PHP config file '''php.ini'''. For example:
** On RHEL/CentOS/Scientific Linux, it's '''/etc/php.ini'''
** On Debian/Ubuntu, it's '''/etc/php5/apache2/php.ini'''
** On Gentoo Linux, it's '''/etc/php/apache2-php5.3/php.ini'''
** On openSUSE, it's '''/etc/php5/apache2/php.ini'''
** on FreeBSD, it's '''/usr/local/etc/php.ini'''
{{cmd|<pre>
date.timezone = "Europe/Paris"
</pre>}}

* Restart Apache web server if you have new required packages or PHP modules installed.

* Upgrade Roundcube database structure by importing shipped SQL file:
{{cmd|<pre>
# mysql -uroot -p
mysql> USE roundcubemail;
mysql> SOURCE roundcubemail-0.8.6/SQL/mysql.update.sql;
</pre>}}

* Roundcube installer also gives the way to download main.inc.php and db.inc.php files, please download them and replace your old config files. Because old config files might miss some parameters. Don't forget to fix file permission after replaced:
{{cmd|<pre>
# ---- On RHEL/CentOS/Scientific Linux ----
# chown apache:apache roundcubemail-0.8.6/config/*

# ---- On Debian/Ubuntu ----
# chown www-data:www-data roundcubemail-0.8.6/config/*

# ---- On Gentoo Linux ----
# chown apache:apache roundcubemail-0.8.6/config/*

# ---- On openSUSE ----
# chown wwwrun:www roundcubemail-0.8.6/config/*

# ---- On FreeBSD ----
# chown www:www roundcubemail-0.8.6/config/*
</pre>}}

* After Roundcube installer finished upgrading process, disable installer in config file 'roundcubemail-0.8.6/config/main.inc.php' by updating below parameter:
{{cmd|<pre>
$rcmail_config['enable_installer'] = false;
</pre>}}

* Restrict accessing to sensitive files:
{{cmd|<pre>
# chmod 0000 roundcubemail-0.8.6/{CHANGELOG,INSTALL,LICENSE,README,UPGRADING,installer,SQL}
</pre>}}

* Now you need to sync config files for Roundcube plugins. iRedMail enables two plugins by default, you can check file '''roundcubemail-[OLD_VERSION]/config/main.inc.php''' to see whether you have addition plugins enabled. For example:
** roundcubemail-0.8.6/plugins/password/: Used to allow mail users to change their own passwords. Config file is roundcubemail-0.8.6/plugins/password/config.inc.php.
** roundcubemail-0.8.6/plugins/managesieve/: Used to allow mail users to manage their own mail filter rules. Config file is roundcubemail-0.8.6/plugins/managesieve/config.inc.php.
{{cfg|roundcubemail-[OLD_VERSION]/config/main.inc.php|<pre>
$rcmail_config['plugins'] = array("password", "managesieve");
</pre>}}

Please sync settings between new Rondcubewebmail release and old one.

That's all, restarting Apache service is recommended.

[[Category: FAQ]]
[[Category: iRedMail/FAQ]]