Typo in migrate.to.new.iredmail.server.html.
This commit is contained in:
parent
184673b30e
commit
c9c3640448
|
@ -2,39 +2,48 @@
|
|||
|
||||
[TOC]
|
||||
|
||||
`WARNING`: Please try it on a test server first. if it works well, then try it on product server.
|
||||
!!! warning
|
||||
|
||||
Since new iRedMail server will install same components as old server, you can choose what data you want to migrate. Most important data are:
|
||||
Please practise the migration on a test server first, make sure you understand
|
||||
the whole procedure and migrate all required data.
|
||||
|
||||
Since new iRedMail server will install same components as old server, you can choose what data you want to migrate.
|
||||
|
||||
Most important data are:
|
||||
|
||||
* email accounts stored in SQL/LDAP.
|
||||
* user mailboxes. Stored under /var/vmail by default.
|
||||
* SQL database of Roundcube webmail. It stores per-user webmail preferences, and address book.
|
||||
* Policyd/Cluebringer database. It stores white/blacklists records, greylisting records, etc.
|
||||
* <strike>Policyd/Cluebringer database. It stores white/blacklists records, greylisting records, etc.</strike> Note: Policyd/Cluebringer were removed since iRedMail-0.9.3.
|
||||
* Amavisd database.
|
||||
* It stores per-recipient white/blacklists in SQL tables: `mailaddr`, `policy`, `users`, `wblist`.
|
||||
* Basic info of in/out emails are stored in SQL tables: `maddr`, `msgs`, `msgrcpt`. Quarantined emails are stored in `quarantine`, it requires other 3 tables. If you don't have any quarantined emails, it's safe to delete all records in these 4 tables.
|
||||
|
||||
__WARNING__: Do not restore database `mysql` exported from old server, it contains SQL usernames/passwords for Roundcube/Amavisd/Policyd/Cluebringer used on old server. New iRedMail server has the same SQL usernames, but different passwords. So please do not restore it.
|
||||
!!! warning
|
||||
|
||||
Do not restore database `mysql` exported from old server, it contains SQL
|
||||
usernames/passwords for Roundcube/Amavisd/iRedAPD/iRedAdmin/... used on
|
||||
old server. New iRedMail server has the same SQL usernames, but different
|
||||
passwords. So please do not restore it.
|
||||
|
||||
## Client settings (Outlook, Thunderbird)
|
||||
|
||||
Since iRedMail-0.8.7, iRedMail enforces secure POP3/IMAP/SMTP connections.
|
||||
Mail client programs must issue 'STARTTLS' command before authentication,
|
||||
so please update your mail client programs you must change your mail client
|
||||
programs (e.g. Outlook, Thunderbird) to use TLS connection.
|
||||
Since iRedMail-0.8.7, iRedMail enforces secure POP3/IMAP/SMTP connections,
|
||||
please update your mail client applications to use TLS connection.
|
||||
|
||||
* For SMTP service, use port `587` with `STARTTLS` (or `TLS`).
|
||||
* For IMAP service, use port `143` with `STARTTLS` (or `TLS`).
|
||||
* For POP3 service, use port `110` with `STARTTLS` (or `TLS`).
|
||||
* For IMAP service, use port `143` with `STARTTLS` (or `TLS`), or port `993` with `SSL`.
|
||||
* For POP3 service, use port `110` with `STARTTLS` (or `TLS`), or port `995` with `SSL`.
|
||||
|
||||
Additional notes:
|
||||
!!! note
|
||||
|
||||
* If you want to enable smtp authentication on port `25` (again, not
|
||||
recommended), please comment out Postfix parameter `smtpd_tls_auth_only = yes`
|
||||
in its config file `/etc/postfix/main.cf`.
|
||||
|
||||
* if you want to enable SMTPS (SMTP over SSL, port `465`) to support legency
|
||||
mail clients, please follow this tutorial: [How to enable SMTPS service](./enable.smtps.html).
|
||||
* if you want to enable SMTPS (SMTP over SSL, port `465`) to support
|
||||
legency mail clients, please follow this tutorial:
|
||||
[How to enable SMTPS service](./enable.smtps.html).
|
||||
|
||||
## LDAP: migrate mail accounts
|
||||
|
||||
|
@ -111,20 +120,18 @@ structure related changes. Check [upgrade tutorials for iRedMail](./iredmail.rel
|
|||
|
||||
## Migrate mailboxes (Maildir format)
|
||||
|
||||
!!! warning
|
||||
|
||||
* Make sure the maildir path stored in SQL/LDAP matches the mailbox
|
||||
path on file system, so that mail clients can find migrated mail messages.
|
||||
* After migrated mailboxes, you may want to recalculate mailbox quota by
|
||||
following our tutorial:
|
||||
[Force Dovecot to recalculate mailbox quota](./recalculate.mailbox.quota.html)
|
||||
|
||||
* Copy all mailboxes (in Maildir format) to new iRedMail server with tools like `rsync`.
|
||||
* Set correct file owner and permission of mailboxes. Default owner is `vmail`,
|
||||
group is `vmail`, permission is `0700`.
|
||||
|
||||
> WARNING:
|
||||
>
|
||||
> * please make sure maildir path stored in SQL/LDAP matches the mailbox
|
||||
> path on file system, so that mail clients can find imported emails.
|
||||
>
|
||||
> * After migrated mailboxes, you may want to recalculate mailbox quota by
|
||||
> following our tutorial:
|
||||
> [Force Dovecot to recalculate mailbox quota](./recalculate.mailbox.quota.html)
|
||||
|
||||
|
||||
* With SQL backends, you can get full maildir path of user with below SQL command:
|
||||
|
||||
```
|
||||
|
|
|
@ -29,31 +29,41 @@
|
|||
<li><a href="#references">References</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
<p><code>WARNING</code>: Please try it on a test server first. if it works well, then try it on product server.</p>
|
||||
<p>Since new iRedMail server will install same components as old server, you can choose what data you want to migrate. Most important data are:</p>
|
||||
<div class="admonition warning">
|
||||
<p class="admonition-title">Warning</p>
|
||||
<p>Please practise the migration on a test server first, make sure you understand
|
||||
the whole procedure and migrate all required data.</p>
|
||||
</div>
|
||||
<p>Since new iRedMail server will install same components as old server, you can choose what data you want to migrate.</p>
|
||||
<p>Most important data are:</p>
|
||||
<ul>
|
||||
<li>email accounts stored in SQL/LDAP.</li>
|
||||
<li>user mailboxes. Stored under /var/vmail by default.</li>
|
||||
<li>SQL database of Roundcube webmail. It stores per-user webmail preferences, and address book.</li>
|
||||
<li>Policyd/Cluebringer database. It stores white/blacklists records, greylisting records, etc.</li>
|
||||
<li><strike>Policyd/Cluebringer database. It stores white/blacklists records, greylisting records, etc.</strike> Note: Policyd/Cluebringer were removed since iRedMail-0.9.3.</li>
|
||||
<li>Amavisd database.<ul>
|
||||
<li>It stores per-recipient white/blacklists in SQL tables: <code>mailaddr</code>, <code>policy</code>, <code>users</code>, <code>wblist</code>.</li>
|
||||
<li>Basic info of in/out emails are stored in SQL tables: <code>maddr</code>, <code>msgs</code>, <code>msgrcpt</code>. Quarantined emails are stored in <code>quarantine</code>, it requires other 3 tables. If you don't have any quarantined emails, it's safe to delete all records in these 4 tables.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
<p><strong>WARNING</strong>: Do not restore database <code>mysql</code> exported from old server, it contains SQL usernames/passwords for Roundcube/Amavisd/Policyd/Cluebringer used on old server. New iRedMail server has the same SQL usernames, but different passwords. So please do not restore it.</p>
|
||||
<div class="admonition warning">
|
||||
<p class="admonition-title">Warning</p>
|
||||
<p>Do not restore database <code>mysql</code> exported from old server, it contains SQL
|
||||
usernames/passwords for Roundcube/Amavisd/iRedAPD/iRedAdmin/... used on
|
||||
old server. New iRedMail server has the same SQL usernames, but different
|
||||
passwords. So please do not restore it.</p>
|
||||
</div>
|
||||
<h2 id="client-settings-outlook-thunderbird">Client settings (Outlook, Thunderbird)</h2>
|
||||
<p>Since iRedMail-0.8.7, iRedMail enforces secure POP3/IMAP/SMTP connections.
|
||||
Mail client programs must issue 'STARTTLS' command before authentication,
|
||||
so please update your mail client programs you must change your mail client
|
||||
programs (e.g. Outlook, Thunderbird) to use TLS connection.</p>
|
||||
<p>Since iRedMail-0.8.7, iRedMail enforces secure POP3/IMAP/SMTP connections,
|
||||
please update your mail client applications to use TLS connection.</p>
|
||||
<ul>
|
||||
<li>For SMTP service, use port <code>587</code> with <code>STARTTLS</code> (or <code>TLS</code>).</li>
|
||||
<li>For IMAP service, use port <code>143</code> with <code>STARTTLS</code> (or <code>TLS</code>).</li>
|
||||
<li>For POP3 service, use port <code>110</code> with <code>STARTTLS</code> (or <code>TLS</code>).</li>
|
||||
<li>For IMAP service, use port <code>143</code> with <code>STARTTLS</code> (or <code>TLS</code>), or port <code>993</code> with <code>SSL</code>.</li>
|
||||
<li>For POP3 service, use port <code>110</code> with <code>STARTTLS</code> (or <code>TLS</code>), or port <code>995</code> with <code>SSL</code>.</li>
|
||||
</ul>
|
||||
<p>Additional notes:</p>
|
||||
<div class="admonition note">
|
||||
<p class="admonition-title">Note</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p>If you want to enable smtp authentication on port <code>25</code> (again, not
|
||||
|
@ -61,10 +71,12 @@ recommended), please comment out Postfix parameter <code>smtpd_tls_auth_only = y
|
|||
in its config file <code>/etc/postfix/main.cf</code>.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>if you want to enable SMTPS (SMTP over SSL, port <code>465</code>) to support legency
|
||||
mail clients, please follow this tutorial: <a href="./enable.smtps.html">How to enable SMTPS service</a>.</p>
|
||||
<p>if you want to enable SMTPS (SMTP over SSL, port <code>465</code>) to support
|
||||
legency mail clients, please follow this tutorial:
|
||||
<a href="./enable.smtps.html">How to enable SMTPS service</a>.</p>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
<h2 id="ldap-migrate-mail-accounts">LDAP: migrate mail accounts</h2>
|
||||
<p>Steps to migrate LDAP mail accounts:</p>
|
||||
<ul>
|
||||
|
@ -130,28 +142,26 @@ mysql> ALTER TABLE domain DROP disableduserprofiles;
|
|||
all upgrade tutorials for your current iRedMail release, then apply SQL
|
||||
structure related changes. Check <a href="./iredmail.releases.html">upgrade tutorials for iRedMail</a>.</p>
|
||||
<h2 id="migrate-mailboxes-maildir-format">Migrate mailboxes (Maildir format)</h2>
|
||||
<div class="admonition warning">
|
||||
<p class="admonition-title">Warning</p>
|
||||
<ul>
|
||||
<li>Make sure the maildir path stored in SQL/LDAP matches the mailbox
|
||||
path on file system, so that mail clients can find migrated mail messages.</li>
|
||||
<li>After migrated mailboxes, you may want to recalculate mailbox quota by
|
||||
following our tutorial:
|
||||
<a href="./recalculate.mailbox.quota.html">Force Dovecot to recalculate mailbox quota</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
<ul>
|
||||
<li>Copy all mailboxes (in Maildir format) to new iRedMail server with tools like <code>rsync</code>.</li>
|
||||
<li>Set correct file owner and permission of mailboxes. Default owner is <code>vmail</code>,
|
||||
group is <code>vmail</code>, permission is <code>0700</code>.</li>
|
||||
</ul>
|
||||
<blockquote>
|
||||
<p>WARNING:</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p>please make sure maildir path stored in SQL/LDAP matches the mailbox
|
||||
path on file system, so that mail clients can find imported emails.</p>
|
||||
<p>Set correct file owner and permission of mailboxes. Default owner is <code>vmail</code>,
|
||||
group is <code>vmail</code>, permission is <code>0700</code>.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>After migrated mailboxes, you may want to recalculate mailbox quota by
|
||||
following our tutorial:
|
||||
<a href="./recalculate.mailbox.quota.html">Force Dovecot to recalculate mailbox quota</a></p>
|
||||
<p>With SQL backends, you can get full maildir path of user with below SQL command:</p>
|
||||
</li>
|
||||
</ul>
|
||||
</blockquote>
|
||||
<ul>
|
||||
<li>With SQL backends, you can get full maildir path of user with below SQL command:</li>
|
||||
</ul>
|
||||
<pre><code>mysql> USE vmail;
|
||||
mysql> SELECT CONCAT(storagebasedirectory, '/', storagenode, '/', maildir) FROM mailbox WHERE username='user@domain.com';
|
||||
</code></pre>
|
||||
|
|
Loading…
Reference in New Issue