Difference between revisions of "CentOS 7.x Zimbra add additional ports for SMTP service when outgoing port 25 is blocked"

From Notes_Wiki
(Created page with "<yambe:breadcrumb self="Zimbra add additional ports for SMTP service when outgoing port 25 is blocked">CentOS 7.x Zimbra configuration|Zimbra configuration</yambe:breadcrumb>...")
 
m
Line 1: Line 1:
<yambe:breadcrumb self="Zimbra add additional ports for SMTP service when outgoing port 25 is blocked">CentOS 7.x Zimbra configuration|Zimbra configuration</yambe:breadcrumb>
<yambe:breadcrumb self="Zimbra add additional ports for SMTP service when outgoing port 25 is blocked">CentOS 7.x Zimbra configuration|Zimbra configuration</yambe:breadcrumb>
=CentOS 7.x Zimbra add additional ports for SMTP service when outgoing port 25 is blocked=
=CentOS 7.x Zimbra add additional ports for SMTP service when outgoing port 25 is blocked=
'''This is similar to [[CentOS 8.x postfix send email via other relayhost or smarthost without using port 25]]'''


It is possible for a email server eg mail.example.com to have public IP with bad reputation.  In that case we can configure another Zimbra server (eg mail.sbarjatiya.com) as Smart_host so that all emails of mail.example.com email server go via mail.sbarjatiya.com.  This solution works for public IP reputation cases but it does not works when outgoing port 25 is blocked on mail.example.com (Eg new AWS VM with email sending limitations or restricted broadband connection where outgoing port 25 is blocked).
It is possible for a email server eg mail.example.com to have public IP with bad reputation.  In that case we can configure another Zimbra server (eg mail.sbarjatiya.com) as Smart_host so that all emails of mail.example.com email server go via mail.sbarjatiya.com.  This solution works for public IP reputation cases but it does not works when outgoing port 25 is blocked on mail.example.com (Eg new AWS VM with email sending limitations or restricted broadband connection where outgoing port 25 is blocked).

Revision as of 13:17, 9 September 2020

<yambe:breadcrumb self="Zimbra add additional ports for SMTP service when outgoing port 25 is blocked">CentOS 7.x Zimbra configuration|Zimbra configuration</yambe:breadcrumb>

CentOS 7.x Zimbra add additional ports for SMTP service when outgoing port 25 is blocked

This is similar to CentOS 8.x postfix send email via other relayhost or smarthost without using port 25

It is possible for a email server eg mail.example.com to have public IP with bad reputation. In that case we can configure another Zimbra server (eg mail.sbarjatiya.com) as Smart_host so that all emails of mail.example.com email server go via mail.sbarjatiya.com. This solution works for public IP reputation cases but it does not works when outgoing port 25 is blocked on mail.example.com (Eg new AWS VM with email sending limitations or restricted broadband connection where outgoing port 25 is blocked).

In such cases we can work around by:

  1. Making mail.sbarjatiya.com zimbra server listen on additional SMTP ports (eg 2525) apart from port 25 using:
  2. After that mail.example.com Smart host setting can be made to point to mail.sbarjatiya.com at port 2525 instead of port 25.
  3. Add mail.sbarjatiya.com public IP as permitted sender in SPF record of mail.example.com
  4. Allow port 2525 in firewall of Linux host CentOS 7.x Basic firewalld configuration
  5. Allow port 2525 in network firewall (Eg security group or some other appropriate firewall)
  6. Whitelist mail.example.com public IP in MTATrustedNetworks in mail.sbarjatiya.com so that all emails are accepted without authentication.


<yambe:breadcrumb self="Zimbra add additional ports for SMTP service when outgoing port 25 is blocked">CentOS 7.x Zimbra configuration|Zimbra configuration</yambe:breadcrumb>