iRedMail Installation with MariaDB: Difference between revisions

From KlavoWiki
Jump to navigationJump to search
No edit summary
 
(8 intermediate revisions by the same user not shown)
Line 3: Line 3:


= Installation =
= Installation =
Before proceeding make sure that when you ping the hostname and FQDN of your computer/server that the reply address is 172.0.0.1
Before proceeding make sure that when you ping the hostname and FQDN of your computer/server that the reply address is 127.0.0.1
<pre>
<pre>
yum -y update
yum -y update
Line 10: Line 10:


<pre>
<pre>
yum -y install vim wget bzip2 deltarpm yum-cron openchange
yum -y install vim wget bzip2 deltarpm yum-cron openchange epel-release
rpm -Uvh http://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-7.noarch.rpm
</pre>
</pre>


<pre>
<pre>
cd /usr/src
cd /usr/src
wget https://bitbucket.org/zhb/iredmail/downloads/iRedMail-0.9.5-1.tar.bz2
wget https://bitbucket.org/zhb/iredmail/downloads/iRedMail-0.9.9.tar.bz2
bzip2 -dk iRedMail-0.9.5-1.tar.bz2
bzip2 -dk iRedMail-0.9.9.tar.bz2
tar xvf iRedMail-0.9.5-1.tar
tar xvf iRedMail-0.9.9.tar
rm -f iRedMail-0.9.5-1.t*
rm -f iRedMail-0.9.9.t*
cd iRedMail-0.9.5-1
cd iRedMail-0.9.9
bash iRedMail.sh
bash iRedMail.sh
</pre>
</pre>
Line 33: Line 32:
|-
|-
|Sensitive Info
|Sensitive Info
|/usr/src/iRedMail-0.9.5-1/config
|/usr/src/iRedMail-0.9.9/config
|-
|-
|Post installation information
|Post installation information
|/root/iRedMail-x.y.z/iRedMail.tips
|/root/iRedMail-0.9.9/iRedMail.tips
|}
|}


Line 55: Line 54:
|}
|}


= Distributions Lists and Aliases =
= Done =
== Aliases ==
That is it for the install.  Now the configuration is the difficult part if you need any special customisation otherwise the iRedAdmin will suffice.
Unless you have purchased the Professional version of iRedMail ther WEB GUI does not offer a method to create aliases or distribution lists.  Aliases and distribution lists can still be created but you will need to manually add entries to the vmail.alias MariaDB table.<br>


An alias can be for an email address on a different domain or to a domain hosted elsewhere.  An alias is basically forwarding that email to any other email address.
Refer to [[:Category:iRedMail]] for specific configuration tasks.
 
To create an alias of david@testforme.com for email address postmaster@testforme.com
<pre>
mysql -pmypasswordforMariaDB vmail
</pre>
 
<pre>
INSERT INTO alias (address, goto, name, accesspolicy, domain, created, is_alias, alias_to) VALUES ('david@testforme.com', 'postmaster@testforme.com', 'David Klaverstyn', 'public', 'testforme.com', now(), 1, 'postmaster@testforme.com');
</pre>
 
== Distribution List ==
A distribution list is an email address that is forwarded to two or more email address.  The email address can be either locally or externally hosted emails on different domains.
 
To create a distribution list of sales@testforme.com that contains the members tim@testforme.com, bill@microsoft.com and john@google.com.
 
<pre>
mysql -pmypasswordforMariaDB vmail
</pre>
 
<pre>
INSERT INTO alias (address, goto, name, accesspolicy, domain, created, islist) VALUES ('sales@testforme.com', 'tim@testforme.com,bill@microsoft.com,john@google.com', 'Sales List', 'public', 'testforme.com', now(), 1);
</pre>
 
== vmail.alias Table Description ==
<pre>
+--------------+--------------+------+-----+---------------------+-------+
| Field        | Type        | Null | Key | Default            | Extra |
+--------------+--------------+------+-----+---------------------+-------+
| address      | varchar(255) | NO  | PRI |                    |      |
| goto        | text        | YES  |    | NULL                |      |
| name        | varchar(255) | NO  |    |                    |      |
| moderators  | text        | YES  |    | NULL                |      |
| accesspolicy | varchar(30)  | NO  |    |                    |      |
| domain      | varchar(255) | NO  | MUL |                    |      |
| islist      | tinyint(1)  | NO  | MUL | 0                  |      |
| is_alias    | tinyint(1)  | NO  | MUL | 0                  |      |
| alias_to    | varchar(255) | NO  | MUL |                    |      |
| created      | datetime    | NO  |    | 1970-01-01 01:01:01 |      |
| modified    | datetime    | NO  |    | 1970-01-01 01:01:01 |      |
| expired      | datetime    | NO  | MUL | 9999-12-31 00:00:00 |      |
| active      | tinyint(1)  | NO  | MUL | 1                  |      |
+--------------+--------------+------+-----+---------------------+-------+
</pre>
 
== Access Policies ==
Available access policies are:
{|class="wikitable"
|public
|no restrictions
|-
|domain
|all users under same domain are allowed to send email to this mail list.
|-
|subdomain
|all users under same domain and sub-domains are allowed to send email to this mail list.
|-
|membersOnly
|only members of this mail list are allowed.
|-
|- style="vertical-align:top;"
|allowedOnly
|only moderators of this mail list are allowed. Moderators are email addresses stored in SQL column alias.moderators. With iRedAPD-1.4.5, it's ok to use *@domain.com as (one of) moderator for all users under mail domain 'domain.com'.
|-
|memebersAndModeratorsOnly
|only members and moderators of this mail list are allowed.
|}
 
== Send from an Alias ==
The only way I have been able to send from an alias address is to use the roundcube web mail interface.  Go into settings and create a new identity. Creating a new identity that does not existing in vmail.alias will have an error when sending the email.<br>
Using Outlook and EAS always sends from the primary email address of the logged in account.
 
<pre>
vi /opt/iredapd/libs/default_settings.py
</pre>
 
<pre>
ALLOWED_LOGIN_MISMATCH_SENDERS = ['email1@thisdomain.net','email2@thatdomain.com']
</pre>
 
<pre>
service iredapd restart
</pre>
 
= SSL Certificates =
I'm not going into specific details here.  I use StartSSL certificates as they are free for private use.<br>
'''Note''': I have noticed that if you try going to your WEB server and you get a blank page, I found this occurs when the SSL certificate does not match the certificate name or SAN on the certificate.
 
Certificate path location.
<pre>
/etc/pki/tls/certs/
</pre>
 
<pre>
openssl req -newkey rsa:2048 -nodes -keyout /etc/pki/tls/certs/sogo.key -out /etc/pki/tls/certs/sogo.csr
</pre>
 
<pre>
vi /etc/httpd/conf.d/ssl.conf
</pre>
 
<pre>
SSLCertificateFile /etc/pki/tls/certs/2_mail.myserver.com.crt
SSLCertificateKeyFile /etc/pki/tls/certs/sogo.key
SSLCACertificateFile /etc/pki/tls/certs/1_root_bundle.crt
</pre>


[[Category : iRedMail]]
[[Category : iRedMail]]

Latest revision as of 04:55, 24 June 2019

The following instructions were performed on CentOS 7.2 with a minimal install.
iRedMail provides self hosting email with SOGo providing Exchange Active Sync operations.

Installation

Before proceeding make sure that when you ping the hostname and FQDN of your computer/server that the reply address is 127.0.0.1 

yum -y update
reboot

yum -y install vim wget bzip2 deltarpm yum-cron openchange epel-release

cd /usr/src
wget https://bitbucket.org/zhb/iredmail/downloads/iRedMail-0.9.9.tar.bz2
bzip2 -dk iRedMail-0.9.9.tar.bz2
tar xvf iRedMail-0.9.9.tar
rm -f iRedMail-0.9.9.t*
cd iRedMail-0.9.9
bash iRedMail.sh

--> Wait. Looks like nothing is happening or broken but it is background processing.
--> Be patient. 10 minutes plus depending on CPU and internet speed.

Post Installation Information

Mailboxes /var/mail
Sensitive Info /usr/src/iRedMail-0.9.9/config
Post installation information /root/iRedMail-0.9.9/iRedMail.tips


URL's

Roundcube webmail https://your_server/mail/
SOGo Groupware https://your_server/SOGo
Web admin panel httpS://your_server/iredadmin/
Awstats httpS://your_server/awstats

Done

That is it for the install. Now the configuration is the difficult part if you need any special customisation otherwise the iRedAdmin will suffice.

Refer to Category:iRedMail for specific configuration tasks.

Retrieved from ‘https://klaverstyn.com.au/david/wiki/index.php?title=iRedMail_Installation_with_MariaDB&oldid=2359’