![]() Because of this, hMailServer will accept messages for any recipient matching your domain name and attempt to forward the message to your internal server. One problem with this configuration is that hMailServer does not know which recipients exists on the internal domain. If hMailServer receives an email for an unknown domain, it will be rejected. If hMailServer receives an email addressed to your domain name, it will forward the message to the backend server. You should not add the domain to the server in the DMZ - only the route. In the Target SMTP host field, enter the host name of the internal email server.In the Domain field, enter your domain name, for example.Another common set up is companies who are running MicrosoftExchange internally but do not want to expose this server to the Internet. One common reason for this set up is that you want anti spam and virus protection to be run outside your internal network. This example explains how to set up a hMailServer installation in a DMZ which forwards all incoming email to a backend server. Example 3 - Setting up a server in DMZ forwarding to an internal email server If hMailServer can find the recipient in the local installation, the email will be put in the local account instead - hMailServer only forwards email using routes if the recipients cannot be find locally. If hMailServer receives an email addressed to the domain, and it cannot find the recipient in the local installation, it will now deliver the email to the host name you specified in the route. In the Target SMTP host field, enter the host name where email for this domain should be forwarded.This may be useful for example if we have updated the MX records for a domain but still want to receive email for the domain on the old IP address in case some SMTP sender has not updated their DNS cache. In this example, the domain is a "local" domain which we are hosting ourselves. This example explains how to route all email sent to the domain to another server. ![]() Example 2 - Route all email sent to the domain to another server Henceforth, all email sent to will go through mx., instead of through the default server,. ![]() In the Target SMTP host field, enter mx.Go to Settings -> Protocols -> SMTP -> Routes.The following example explains how to configure all email for the domain to go through mx. instead of through the default server, : Examples Example 1 - Creating a new route Use Server requires authentication to specify user name and password if the target SMTP host requires authentication. On the other hand, if the target SMTP host goes up, you don't want to wait 10 hours for the server to retry. For example, if the target SMTP host is down, there is no need to retry every minute. Minutes between every retry lets you specify the number of minutes between hMailServer's retries. If the route is used for MX backup, you will most likely want to set this to a rather high value. Use Number of retries to specify the number of times you want hMailServer to retry when sending to this domain. If you only want local users to be able to deliver messages to the route, select that the recipient should be treated as an external domain. By default, the IP ranges in hMailServer does not permit deliveries from external users to external recipients without the use of SMTP authentication.The default IP ranges in hMailServer permits delivery from external addresses to local addresses without any SMTP authentication. If you want external users (users on other email servers) to be able to send email to the route, select that " When recipient matches route, treat recipient as local".In the same manner, if you configure the recipient to be treated as external, and the IP ranges specifies that SMTP authentication is required for deliveries to external addresses, hMailServer will require SMTP authentication before accepting the delivery. If you configure hMailServer to treat recipients matching the route as local addresses, and IP ranges does not permit deliveries to local addresses, the delivery will not be accepted by hMailServer. Combined with the settings in the IP ranges, this specifies when deliveries should be permitted, and whether or not SMTP authentication is required. Using the two security settings, " When sender matches route" and "When recipient matches route", you specify whether the sender and recipient should be seen as local or external. When a person tries to send an email where the recipient matches a route, hMailServer will use IP ranges and the security settings in the route to determine whether the delivery should be made. This should typically be an internet host name such as. The host to which the emails that this route applies to will be delivered.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |