1

Topic: Upgrade compatibility

==== Required information ====
- iRedMail version: 0.7.3 / 0.8.7
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Linux/BSD distribution name and version:  Debian
- Related log if you're reporting an issue:
====

I need make migration of the one old server with Debian 6 (squeze) and iRedMail version 0.7.3/iRedAdmin-Pro-MySQL-1.3.0 (harware problem).

The new server is Debian 7 (wheezy) and now I go install new versions of iRedMail. But I see some diferences e I don´t know if it will have compatibility problems:

- Dovecot version: old server 1.2.15 / new server : 2.1.7 (is a problem?)

- Directory structure iRedMail:

Old iRedMail: /vmail/vmail1/domain/u/s/e/user/Maildir
                        /vmail/sieve/domain/user/

New iRedMail: /vmail/vmail1/domain/u/s/e/user/Maildir
                          /vmail/vmail1/domain/u/s/e/user/sieve

So I will have to manually copy the sieve directory of each account to the new location? Or there is a way to keep the same structure directory in new version?

Tks.

M Martinatti

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: Upgrade compatibility

Reference:
http://www.iredmail.org/wiki/index.php? … ail.Server

3

Re: Upgrade compatibility

Tks Zhang,

I'm in the process of migration in progress.

But I have a doubt about the Policyd / Cluebringer.

On the old server I have many inserts blacklists / whitelists in postfixpolicyd table (Cluebringer did not exist in older versions of iRedmail).

Migrating the postfixpolicyd table normally works? Or do I have to configure something in Cluebringer (Sorry, never used Cluebringer and do not know where it integrates the iRedMail).

Very tks.

Marcelo M.

4

Re: Upgrade compatibility

marcelomartinatti wrote:

Migrating the postfixpolicyd table normally works?

No. They use different SQL structure, so you cannot simply export Policyd database and import into Cluebringer database.

marcelomartinatti  wrote:

Or do I have to configure something in Cluebringer

You can try attached script, it can convert Policyd white/blacklists to Cluebringer format (raw SQL commands).

Please set correct SQL username/password in this file, then execute it:

# python policyd_to_cluebringer.py

Still not finish throttling migration, but if it's very important to you, please let me know and i will try to convert it.

Post's attachments

policyd_to_cluebringer.py 6.23 kb, 1 downloads since 2014-08-29 

You don't have the permssions to download the attachments of this post.