![]() ![]() if you virusscan on hmailservers directorys. Use a virusscanning function through hmailserver that is all. You will also need to make sure the Client PC Outgoing Server Address is the same address as it is for your Incoming Server Name otherwise you will need to disable the Sending Function of your Email Client Application because it will also attempt to connect to hMailServer.Īgain if you set your Email Client Application PC to connect using the External hostname or External IP Address as I indicated in my earlier post, you shouldn't be having this problem as far as I can tell unless you have Firewall issues or your Local Network doesn't have NAT Loop Back Functionality because then you would be using the External Addressing in both cases. On the Client PC did you specify for the server name the External hostname or External IP Address of your Local Network which is running hMailServer? The hMailServer PC will also need to have its Firewall open for Port 143 as well as having your Router Forwarding Port 143 to the Local (LAN) IP Address of your PC running hMailServer.Īlso, since you only want to access the IMAP email messages on your hMailServer, you will need to make sure the Incoming Client PC Server address is the External hostname or External IP Address of your Local Network PC running hMailServer. This hopefully will give an indication where the error is. Be sure to specify what your Error Message(s) are. You must be receiving some error message presumably on your Client PC since you say it won't connect but does connect when inside your Local Network. The main difference (if not the only difference) for the computers inside your Local Network would be to use the External Public Hostname for your Local Network as the email server name in your Client Computer connections to hMailServer. This should involve very little difference in your Client Computer Connections to hMailServer. This way the configuration for the Client Computers connections to hMailServer are the same no matter if hMailServer is accessed external to my Local Network or from within my Local Network. This means I can reference my External Public IP Address from within my Local Network and it will be able to access my Local Network from within my Local Network by using an External Public IP Address of the Local Network.įor this type of situation, I find it better to configure my Client Computer accesses to hMailServer in my Local Network, whether they be within my Local Network or External to my Local Network, the same. ![]() DoneĪfter the above steps have been performed, your users in your network will be able to send email to eachother, using the internal addresses.My Router has NAT Loop Back functionality (otherwise known as hair pinning). Note that the server name is typically not the same as the domain name. As user name, you should use the full email address, for example As server address, use the name or IP address of the computer which hMailServer runs on. When the accounts have been created and firewall configured, it's time to configure your email clients. Make sure that any firewall running on the same server as hMailServer is configured to allow incoming traffic on ports 25, 110 (for POP3) and 143 (for IMAP). ![]() Create the accountsĪfter the domain is created, create accounts for your users. For example, you can set up accounts named and Configure firewalls Make sure the domain is enabled / active. To prevent confusion, it's recommended that you do not choose a domain name already used by someone else on the Internet. Type in a made-up domain name such as companyname.local. Start hMailServer Administrator and select Add domain. Users in your network will be able to send and receive email via the server. They will not be able to send or receive email from other users on the Internet. This document describes how to set up an email server for internal usage only. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |