How do I establish Outlook or Thunderbird access to an ISPConfig server residing inside a SonicWall managed firewall?
I have just recently setup a new ISPConfig mail server for a small company. The mail server resides within the internal network managed by a SonicWall. I have opened appropriate ports and allowed traffic through so the mail server is functioning fine. The Roundcube interface works fine for the employees to login and check their mail, but some of the clients would like to have Outlook or Mozilla Thunderbird function outside of the network so I believe access through the firewall needs to be established on the SonicWall to accomodate this with appropriate settings placed in their device's Thunderbird or Outlook installation to reflect this.
David Johnson, CD
what ports are being used internally? configure the same to be available externally i.e. 25,110,587
do you mean, by default, all internal clients are restricted to access external mail servers, only outgoing HTTP/HTTPS traffic is allowed?
it the above is NOT your situation, you commonly don't need to configure anything for external mail server access, as by default all outgoing traffic is allowed.
if you do have restricted access for outgoing traffic in addition to general HTTP/HTTPS traffic, the following outgoing ports are required.
Port 25 for insecure SMTP
Port 110 for insecure POP
Port 993 for securedIMAP
Port 995 for secured POP
Port 465 or 587 for secured SMTP
no rule is required for incoming mail traffic.
it the above is NOT your situation, you commonly don't need to configure anything for external mail server access, as by default all outgoing traffic is allowed.
if you do have restricted access for outgoing traffic in addition to general HTTP/HTTPS traffic, the following outgoing ports are required.
Port 25 for insecure SMTP
Port 110 for insecure POP
Port 993 for securedIMAP
Port 995 for secured POP
Port 465 or 587 for secured SMTP
no rule is required for incoming mail traffic.
You did setup a SSL certificate and are using HTTPS for the webmail right?
Personally I'd restrict Port 25 to incoming traffic only, block or completely disable Port 143 (imap) and use SSL/TLS connections
You'll need that SSL certificate to setup SSL/TLS on the mail server if it hasn't been setup already
Personally I'd restrict Port 25 to incoming traffic only, block or completely disable Port 143 (imap) and use SSL/TLS connections
You'll need that SSL certificate to setup SSL/TLS on the mail server if it hasn't been setup already
ASKER
External clients were to trying to connect on the wrong port and needed SSL. When the port was modified to the correct port and set to SSL mail worked for the external clients.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.