1

Topic: Migrating users to a back up server

==== Required information ====
- iRedMail version: 0.8.3
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): LDAP
- Linux/BSD distribution name and version: CentOS 6.3 46bit
- Related log if you're reporting an issue:
====
We are new users of iredMail we purchase a iRedAdmin-Pro openLDAP now we are simulating a mmigration of ldif database to new server in case our active server crush but we are unable or to have it successfuly migrate all our existing user to new server do we a link that we can follow just for us to feel comfortable if in case our server crush we can easily migrate our backup users to a new server we are an existing user of ClearOS and the it has a faetures of export and import users which is very helpful to us

2

Re: Migrating users to a back up server

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

3

Re: Migrating users to a back up server

Hi ZhangHuangbin,

thanks for the guide we will try this so that we can be sure once the time comes we can put a live server again in a very short time, also another question our setup has 400 clients they are now complaining in sending it is slow unlike the previous server we have which is ClearOS 5.2 is disabling the GREYLISTING will make it faster

4

Re: Migrating users to a back up server

Sending is slow? Or receiving is slow? Sending should be fast, receiving will delay for several minutes or even hours.

5

Re: Migrating users to a back up server

yes sending like on the marketing department they usually send to more than 20 users within our domain the email get stock on the outbox and it won't go away fast unlike before I already disable the GREYLISTING and now i'm trying the Allow_User_To_Send_Without_Authentication please help me we are receiving a lot of complain from our users...

6

Re: Migrating users to a back up server

Greylisting impacts incoming emails, not outgoing ones.

Please try bypass spam/virus scanning for outgoing emails in Amavisd first:

- Edit /etc/amavisd/amavisd.conf, find below lines:

$policy_bank{'MYUSERS'} = {
    ...
    # don't perform spam/virus/header check.
    #bypass_spam_checks_maps => [1],
    #bypass_virus_checks_maps => [1],
    #bypass_header_checks_maps => [1],

    # allow sending any file names and types
    #bypass_banned_checks_maps => [1],
    ...
};

- Remove the leading '#' to bypass spam/virus scanning for OUTGOING emails.
- Restarting Amavisd service, then try again.