Lets begin:
Open the Windows Command prompt as admin and type in the following Netshell commands to open the required ports for hMailServer
PS: We only discuss the officially recommended encrypted ports for Mailtransport.
Email-Sendingpart:
- SMTP (required for hMailserver for send and receive Emails from and to the Internet)
netsh advfirewall firewall add rule name="SMTP" dir=in action=allow protocol=TCP localport=25
netsh advfirewall firewall add rule name="SMTP" dir=out action=allow protocol=TCP localport=25
- Submission (required if your hMailServer is configured for STARTTLS MailApp sent access)
netsh advfirewall firewall add rule name="Submission" dir=in action=allow protocol=TCP localport=587
netsh advfirewall firewall add rule name="Submission" dir=out action=allow protocol=TCP localport=587
- SMTPS (required if your hMailServer is configured for SSL/TLS MailApp sent access - could be necessary for example: MS-Outlook)
netsh advfirewall firewall add rule name="SMTPS" dir=in action=allow protocol=TCP localport=465
netsh advfirewall firewall add rule name="SMTPS" dir=out action=allow protocol=TCP localport=465
- IMAPS (required if you want to use your MailApp to view Emails via SSL/TLS from your hMailServer)
netsh advfirewall firewall add rule name="IMAP" dir=in action=allow protocol=TCP localport=993
netsh advfirewall firewall add rule name="IMAP" dir=out action=allow protocol=TCP localport=993
- POP3S (required if you want to use your MailApp for download and delete serverside Emails via SSL/TLS from hMailServer)
netsh advfirewall firewall add rule name="POP3S" dir=in action=allow protocol=TCP localport=995
netsh advfirewall firewall add rule name="POP3S" dir=out action=allow protocol=TCP localport=995
Take a look if the above Netsh commands are executed correctly and the response is allways "OK". If not, this indicates a diffrent Windows Firewallrule with the same name is allready in affect or your Windows Firewall simply isnt running.