Typo.
This commit is contained in:
Zhang Huangbin
parent
0f0621f4fb
commit
aa8e5512f2
|
|
@ -2,6 +2,8 @@
|
|||
|
||||
[TOC]
|
||||
|
||||
Contributed by __Joshua Boniface__, Sep 21, 2014.
|
||||
|
||||
## Introduction
|
||||
|
||||
iRedMail is a very nifty piece of software. Setting up a full mail server on modern Linux is indeed possible; there are guides for every part of the system, preconfigured templates, and many-a mailing list post. However, iRedMail does something special: it makes it easy. Easy to install, easy to administer, and and easy to use. However, there are very few guides on how to deploy a *complete*, clustered iRedMail solution. Let's talk a bit about what I mean by that.
|
||||
|
|
|
|||
35
SUMMARY.md
35
SUMMARY.md
|
|
@ -1465,3 +1465,38 @@
|
|||
* [Turn on debug mode in OpenLDAP](turn.on.debug.mode.in.openldap.md)
|
||||
# Frequently Asked Questions
|
||||
* [Why append timestamp in maildir path](why.append.timestamp.in.maildir.path.md)
|
||||
# Install iRedMail
|
||||
* [Perform silent/unattended iRedMail installation](unattended.iredmail.installation.md)
|
||||
# How to
|
||||
* [Completely disable Amavisd + ClamAV + SpamAssassin](0-completely.disable.amavisd.clamav.spamassassin.md)
|
||||
* [Enable SMTPS service (SMTP over SSL, port 465)](0-enable.smtps.md)
|
||||
* [Amavisd + SpamAssassin not working, no mail header (X-Spam-*) inserted.](1-amavisd.no.x-spam.headers.md)
|
||||
* [Disable spam virus scanning for outgoing mails](1-disable.spam.virus.scanning.for.outgoing.mails.md)
|
||||
* [Quarantining](1-quarantining.md)
|
||||
* [Allow user to send email without authentication](allow.user.to.send.email.without.authentication.md)
|
||||
* [Configure Thunderbird as mail client (IMAP, SMTP and global ldap address book)](configure.thunderbird.md)
|
||||
* [Ignore Trash folder in mailbox quota](ignore.trash.folder.in.quota.md)
|
||||
* [LDAP: Add an alias domain](ldap.add.alias.domain.md)
|
||||
* [LDAP: Add a mail alias account](ldap.add.mail.alias.md)
|
||||
* [LDAP: Add a mail list account](ldap.add.mail.list.md)
|
||||
* [LDAP: User mail forwarding.](ldap.user.mail.forwarding.md)
|
||||
* [Monitor incoming and outgoing mails with BCC](monitor.incoming.and.outgoing.mails.with.bcc.md)
|
||||
* [Pipe incoming email for certain user to external script ](pipe.incoming.email.for.certain.user.to.external.script.md)
|
||||
* [Force Dovecot to recalculate mailbox quota](recalculate.mailbox.quota.md)
|
||||
* [SQL: Create an mail alias account with SQL command line](sql.create.mail.alias.md)
|
||||
* [Store SpamAssassin bayes in SQL](store.spamassassin.bayes.in.sql.md)
|
||||
# Third-party integrations.
|
||||
* [SOGo: How to install SOGo on CentOS 6 with iRedMail (MySQL backend)](sogo-centos-6-mysql.md)
|
||||
# Cluster solutions
|
||||
* [An Ultra-HA, full Mult-Master E-mail cluster with iRedMail, MariaDB, and IPVS ](full.mult-master.iredmail.cluster.with.mariadb.and.ipvs.md)
|
||||
# Backup, restore and migration
|
||||
* [Migrate iRedAdmin open source edition to iRedAdmin-Pro](migrate.or.upgrade.iredadmin.md)
|
||||
* [Migrate old iRedMail server to the latest stable release](migrate.to.new.iredmail.server.md)
|
||||
* [Password hashes](password.hashes.md)
|
||||
# Troubleshooting and Debug
|
||||
* [Turn on debug mode in Amavisd](turn.on.debug.mode.in.amavisd.md)
|
||||
* [Turn on debug mode in Cluebringer](turn.on.debug.mode.in.cluebringer.md)
|
||||
* [Turn on debug mode in Dovecot](turn.on.debug.mode.in.dovecot.md)
|
||||
* [Turn on debug mode in OpenLDAP](turn.on.debug.mode.in.openldap.md)
|
||||
# Frequently Asked Questions
|
||||
* [Why append timestamp in maildir path](why.append.timestamp.in.maildir.path.md)
|
||||
|
|
|
|||
|
|
@ -25,6 +25,7 @@
|
|||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
<p>Contributed by <strong>Joshua Boniface</strong>, Sep 21, 2014.</p>
|
||||
<h2 id="introduction">Introduction</h2>
|
||||
<p>iRedMail is a very nifty piece of software. Setting up a full mail server on modern Linux is indeed possible; there are guides for every part of the system, preconfigured templates, and many-a mailing list post. However, iRedMail does something special: it makes it easy. Easy to install, easy to administer, and and easy to use. However, there are very few guides on how to deploy a <em>complete</em>, clustered iRedMail solution. Let's talk a bit about what I mean by that.</p>
|
||||
<p>I know e-mail, having deployed Debian-Linux-based carrier-grade mail platforms as part of my job. Setting up a cluster for production use, you want something that's fault-tolerant on every level. If you have 3 physical servers, you want to make sure you can keep your systems running even if you have to bring one down for maintenance, or due to a catastrophic hardware fault. You want to make sure you don't lose anything because one server crashed. However, many HA setups are not full multi-master; sure, you can lose a node, but it better not be server<em>1</em>. The setup I propose below addresses this: it doesn't matter which of your N nodes fails, you can always perform every task you need; and without proper monitoring, you might not even notice you have a problem! Some may think this is overkill, but the result is very compelling for anyone who values a 100% uptime!</p>
|
||||
|
|
|
|||
Loading…
Reference in New Issue