1

Topic: Investigating iRedMail adoption to replace existing service

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.5.1
- Deployed with iRedMail Easy or the downloadable installer? downloadble installer
- Linux/BSD distribution name and version:  Ubuntu 20.04 (patched)
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? No
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

I have a router/firewall that port forwards traffic to my internal server running several websites by server name (site1.example.com, site2.example.com. etc.). These are all hosted on the same server using Apache2 and rewrite rules.  They are protected by Letsencrypt.  Been working for years.

To test, I purchased a new domain name and set up all the pre-requisite DNS stuff via GoDaddy.  I then created a new mail server on a different virtual machine to host iRedmail.  I have followed the guides and have a working internal server.  However, connectivity is my issue. 

I can use Roundcube on my internal network and have tested email going in and out but I cannot get a mail client, specifically IOS mail, to connect.  I have forwarded ports 25, 465, and 587 to the mail server but no joy.

One other bit of information; when I did my initial install, t called for version 1.5.0.  This did not include SOGo.  I later downloaded and re-ran the iRedmail install script.

Thanks for any assistance.
-T

----

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

2 (edited by Cthulhu 2022-01-23 03:02:34)

Re: Investigating iRedMail adoption to replace existing service

imap uses port 143 (or 993 which should be avoided)
submission uses port 587

port 465 isn't used at all, but without open port 143 you wont be able to connect, since ports 25 is ONLY for incoming mail, not for smtp login

3

Re: Investigating iRedMail adoption to replace existing service

Thanks for the reply.  Turns out the re-install affected backend configuration.  Doing an install from scratch and adding port 143 were both needed.