1

Topic: Email Server force use other port

==== Required information ====
- iRedMail version (check /etc/iredmail-release): 0.9.7
- Linux/BSD distribution name and version: Ubuntu 16.04
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): LDAP
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? No
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

Hi,

I want to setup an iRedMail Server that will force use port 588 for SMTP and 144 po IMAP both using STARTTLS.

We have an existing email server which is run also by iRedMail v 0.8.7 which currently using 587 and 143 STARTTLS.

How would I able to configure the server?

Thanks

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: Email Server force use other port

*) Curious, what's the purpose of this port number change?
*) For 587, you can replace the transport name 'submission' by '588' directly.
*) For IMAP, you can update Dovecot config file like below:

service imap-login {
    inet_listener imap {
        port = 143
    }
    inet_listener imaps {
        port = 993
        ssl = yes
    }

    ...
}

3

Re: Email Server force use other port

Since we have an existing server already which is port forwarded using port 587 and 143 to that servers IP Address in our firewall, we need to use other ports so that they will not conflict in port forwarding settings with each other.



ZhangHuangbin wrote:

*) Curious, what's the purpose of this port number change?
*) For 587, you can replace the transport name 'submission' by '588' directly.
*) For IMAP, you can update Dovecot config file like below:

service imap-login {
    inet_listener imap {
        port = 143
    }
    inet_listener imaps {
        port = 993
        ssl = yes
    }

    ...
}