https://wiki.ipbrick.com/index.php?action=history&feed=atom&title=IPBrick_-_Mail_Server_Configuration 2026-05-13T13:16:50Z Revision history for this page on the wiki MediaWiki 1.23.2 https://wiki.ipbrick.com/index.php?title=IPBrick_-_Mail_Server_Configuration&diff=614&oldid=prev 2015-11-17T12:50:42Z

<p>Created page with &quot;&#039;&#039;&#039;*** Page under construction ***&#039;&#039;&#039; In this page we present some suggestions to optimize email service functioning in IPBrick installations. = Improvements = Improvements...&quot;</p> <p><b>New page</b></p><div>'''*** Page under construction ***'''<br /> <br /> In this page we present some suggestions to optimize email service functioning in IPBrick installations.<br /> <br /> = Improvements =<br /> Improvements performed with these configurations:<br /> * General settings – fine adjustment of advanced settings of the email service<br /> * Mail submission – mail submission service for end users, SMTP service for users/clients in ports 587, 465 and 2525<br /> * IMAP proxy – proxy service of IMAP connections, which improves performance of clients' connections and forwarding between several servers<br /> * AutoConfig, AutoDiscover – auto-configuration support service of email clients<br /> <br /> <br /> = Scenarios =<br /> These are adjusted accordingly to the standard scenarios, namely:<br /> * Scenario 1 – single server – stand-alone – a single IPBrick.IC server, which will serve the accesses through LAN and/or internet<br /> * Scenario 2 – Multi-server – several servers scenario, considering an IPBrick.I, where the email boxes are lodged, and an IPBrick.C, which will work as a front-end mail-relay, anti-virus and anti-spam for the internet<br /> <br /> == Scenario 1 – Single Server ==<br /> Network diagram with a single server:<br /> <br /> [[File:sg30rc1_esquema_rede_stand_alone.png]]<br /> <br /> Ahead, we assume that IP network settings are:<br /> * LAN IP (eth0): 192.168.69.199 (/24)<br /> * Internet IP (eth1): 10.0.0.253 (/24)<br /> * in the LAN, the DNS server is secured by this server (srv-ipbrick01)<br /> <br /> == Scenario 2 – Multi-server ==<br /> <br /> Network diagram with several servers; for this exercise we assume two machines:<br /> <br /> [[File:sg30rc1_esquema_multi_servidor.png]]<br /> <br /> Ahead, we assume that IP configuration data are:<br /> * srv-ipbrick01.domain.com<br /> ** LAN IP (eth0): 192.168.69.1 (/24)<br /> * srv-ipbrick02.domain.com<br /> ** LAN IP (eth0): 192.168.69.254 (/24)<br /> ** Internet IP (eth1): 10.0.0.253 (/24)<br /> * in the LAN, the DNS server is secured by server srv-ipbrick01<br /> <br /> NOTE: In this scenario, the communications server srv-ipbrick02 is configured as IPBRICK.CLIENTE of MASTER srv-ipbrick01.<br /> <br /> = General Settings =<br /> Overall review of mail settings – lets analyse/review each setting and redefine the values according to the scenario. Presentation as provided by IPBrick's menu.<br /> <br /> == IPBrick.C – Email – Configuration ==<br /> * Locally delivered domains – here it's necessary to refer the mail domains served by the organization, in this case “domain.com”, e the server itself (FQDN of the server, srv-ipbrick01.domain.com, and srv-ipbrick02.domain.com)<br /> * Authorized domains for relay – refer the same domains that were mentioned in the previous item (locally delivered)<br /> * Authorized networks for relay – adjust to get only and solely the IPs (/32) of the own servers; the users will connect to the intranet server to send will authentication, for example:<br /> ** Scenario 1 – single server<br /> *** 192.168.69.199 / 32 – Authorized without authentication<br /> *** Other networks – Authorized with TLS authentication<br /> ** Scenario 2 – Multi-server<br /> *** srv-ipbrick01<br /> **** 192.168.69.1 / 32 - Authorized without authentication<br /> *** Other networks – Authorized with TLS authentication<br /> *** srv-ipbrick02<br /> **** 192.168.69.1 / 32 - Authorized without authentication<br /> **** 192.168.69.254 / 32 - Authorized without authentication<br /> **** Other networks – Unauthorized<br /> * SMTP routes – usually IPBrick server is prepared to send emails directly to the internet without having to use a relay server; however, in certain configurations, it may be necessary – in these scenarios we assume that we can send directly to the internet, and the configuration recommended here is:<br /> ** Scenario 1 – without SMTP routes defined<br /> ** Scenario 2 - srv-ipbrick02 (communications) has no defined routes, only srv-ipbrick01 has one route, namely:<br /> *** Domain: this field stays empty (it represents all domains)<br /> *** Server: srv-ipbrick02.domain.com<br /> <br /> == IPBrick.C – Email – Configure: Definitions ==<br /> * Maximum size of a message – by default, it is unlimited, but we will define an example of message limit of 30 MB for attachments<br /> ** converter to bytes and adjust to base64 encoding (add 30%): 30 [MB] * 1024 [KB]<br /> * 1024 [bytes] * 1,3 = 40894464 bytes<br /> * Maximum waiting time in a queue – by default, 7 days (604800s); lets define it for 14400s (4h)<br /> <br /> = Mail submission – Submission for clients =</div>

Dbabo