hmLoadTopic({
hmKeywords:"Domain Gateways,Editing,Editing Gateways,Gateway,Gateway Manager,Gateway Manager,Gateway Manager Domains,Gateway Manager Editor",
hmTitle:"Gateway Manager",
hmDescription:"The Gateway Manager is reached from the Setup » Gateway Manager... menu selection. This feature provides a limited yet useful secondary level of support for hosting multiple...",
hmPrevLink:"domain-manager_activesync_clients.html",
hmNextLink:"gateway_global.html",
hmParentLink:"index.html",
hmBreadCrumbs:"Setup Menu",
hmTitlePath:"Setup Menu > Gateway Manager",
hmHeader:"<h1 class=\"p_Heading1\" style=\"page-break-after: avoid;\"><span class=\"f_Heading1\">Gateway Manager<\/span><\/h1>\n\r",
hmBody:"<p class=\"p_BodyText\"><span class=\"f_BodyText\">The Gateway Manager is reached from the <\/span><span class=\"f_MenuPath\">Setup » Gateway Manager...<\/span><span class=\"f_BodyText\"> menu selection. This feature provides a limited yet useful secondary level of support for hosting multiple domains or acting as a backup mail server for someone.<\/span><\/p>\n\r<p class=\"p_BodyText\"><span class=\"f_BodyText\">For example:<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Suppose you wish to act as a backup server or mail-drop for a third party, receiving its incoming email and storing it in a folder on your server, but you do not wish to host its domain fully, maintaining its individual user accounts. Let<\/span><span style=\"font-family: \'Times New Roman\',Times,Georgia,serif; color: #010100;\">\'<\/span><span class=\"f_ControlIndent\">s use &quot;example<\/span><span style=\"font-family: \'Courier New\',Courier,monospace; color: #010100;\">.com<\/span><span class=\"f_ControlIndent\">&quot; as its name.<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">The first thing you will do is create the gateway by clicking <\/span><span class=\"f_ControlIndent\" style=\"font-weight: bold;\">New gateway<\/span><span class=\"f_ControlIndent\"> on the Gateway Manager and then entering &quot;<\/span><span style=\"font-family: \'Courier New\',Courier,monospace; color: #010100;\">example.com<\/span><span class=\"f_ControlIndent\">&quot; as its name. Now all mail that MDaemon receives for that domain will be <\/span><span class=\"f_BodyText\">separated from the main mail stream and placed <\/span><span class=\"f_ControlIndent\">in the folder designated on the gateway\'s <a href=\"gateway_gateway.html\" class=\"topiclink\">Domain<\/a> screen, regardless of the specific individuals to which each message is addressed.<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Next, you will designate the collection or delivery methods that you wish to allow or use to get the domain\'s email to its actual email server, where its user accounts are hosted. There are two ways to do this: use the <\/span><span class=\"f_ControlIndent\" style=\"font-style: italic;\">Deliver stored messages each time MDaemon processes remote mail<\/span><span class=\"f_ControlIndent\"> option on the <a href=\"gateway_gateway.html\" class=\"topiclink\">Domain screen<\/a>, or use the <a href=\"gateway_dequeuing.html\" class=\"topiclink\">Dequeuing<\/a> options. Optionally, you can also create an MDaemon account and change its <a href=\"ae_mail-folder-groups.html\" class=\"topiclink\">Mail Folder<\/a> to the <a href=\"gateway_gateway.html\" class=\"topiclink\">same storage folder<\/a> that your gateway uses. This will allow a mail client to connect to MDaemon to collect example.com\'s email.<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Finally, you will likely have to edit the DNS settings for <\/span><span class=\"f_PlainText\">example.com<\/span><span class=\"f_ControlIndent\"> so that your MDaemon server is a designated MX host for that domain.<\/span><\/p>\n\r<p class=\"p_BodyText\"><span class=\"f_BodyText\">There are many other features and options available, but the above example is the basic form that a typical gateway will take. If, however, you require an atypical configuration then you may have to do some things differently, such as when you wish to use a domain name that doesn\'t actually exist on the Internet, like &quot;<\/span><span class=\"f_PlainText\">company.mail<\/span><span class=\"f_BodyText\">.&quot; Receiving messages for an otherwise invalid domain name such as that is possible, but the domain name must be &quot;hidden&quot; inside a <a href=\"domain-manager.html\" class=\"topiclink\">default domain<\/a> address. Using that method, addresses can be constructed that will pass through the default domain and on to the gateway. For example, if your default domain is <\/span><span class=\"f_PlainText\">example.com<\/span><span class=\"f_BodyText\"> and you have a gateway for <\/span><span class=\"f_PlainText\">company.mail<\/span><span class=\"f_BodyText\">, then someone could send a message to &quot;<\/span><span style=\"font-family: \'Courier New\',Courier,monospace; color: #010100;\">bob@company.mail<\/span><span class=\"f_BodyText\">&quot; by using the address, &quot;<\/span><span style=\"font-family: \'Courier New\',Courier,monospace; color: #010100;\">bob{company.mail}@example.com<\/span><span class=\"f_BodyText\">.&quot; Since &quot;<\/span><span style=\"font-family: \'Courier New\',Courier,monospace; color: #010100;\">example.com<\/span><span class=\"f_BodyText\">&quot; is the registered domain hosted by MDaemon, this message would be delivered properly, but when MDaemon received the message in that format it would convert the address to &quot;<\/span><span style=\"font-family: \'Courier New\',Courier,monospace; color: #010100;\">bob@company.mail<\/span><span class=\"f_BodyText\">&quot; and deliver the message to the folder specified for that gateway. Of course the simplest method is still to register a valid domain name for the gateway and then point its DNS or MX record to <\/span><span class=\"f_PlainText\">example.com<\/span><span class=\"f_BodyText\">.<\/span><\/p>\n\r<p class=\"p_BodyText_Center\"><img style=\"margin:0 auto 0 auto;width:32.5000rem;height:26.0000rem;border:none\" src=\".\/images\/gateway-manager.png\"\/><\/p>\n\r<p class=\"p_DialogSectionHeading\" style=\"page-break-after: avoid;\"><span class=\"f_DialogSectionHeading\">Gateway List<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">The navigation pane on the left side of this dialog contains the list of your gateways, with links to each screen used for configuring the various gateway-specific settings. It also provides access to the <a href=\"gateway_global.html\" class=\"topiclink\">Global Gateway Settings<\/a> screen<\/span><span class=\"f_ControlIndent\">. The list on the right is used for deleting and renaming domains. You can double-click a gateway in this list to switch to the gateway editor for configuring its settings.<\/span><\/p>\n\r<p class=\"p_DialogSectionHeading\" style=\"page-break-after: avoid;\"><span class=\"f_DialogSectionHeading\">Gateway Domain Management<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">New gateway<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">To create a new gateway: click <\/span><span class=\"f_ControlIndent\" style=\"font-weight: bold;\">New gateway<\/span><span class=\"f_ControlIndent\">, enter the gateway name (e.g. example.mail) in the Create\/Rename Gateway Domain dialog, and click <\/span><span class=\"f_ControlIndent\" style=\"font-weight: bold;\">OK<\/span><span class=\"f_ControlIndent\">.<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_Comment\">Typically<\/span><span class=\"f_ControlIndent\"> the value entered here will be the registered Internet domain name that a DNS server resolves to the IP address of the local machine running the server, or a qualified alias of that name. <\/span><span class=\"f_BodyText\">Alternatively, you may choose to use an internal-only or otherwise non-valid, non-public domain name (such as &quot;<\/span><span class=\"f_T_Code\">company.mail<\/span><span class=\"f_BodyText\">&quot;) for your gateway name. This, however, would require you to use the nested domain name method outlined in the example above, or require you to utilize some other content filtering scheme to get the messages where they belong.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Delete gateway<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">To delete a gateway: select it from the list and click <\/span><span class=\"f_ControlIndent\" style=\"font-weight: bold;\">Delete gateway<\/span><span class=\"f_ControlIndent\">, and click <\/span><span class=\"f_ControlIndent\" style=\"font-weight: bold;\">Yes<\/span><span class=\"f_ControlIndent\"> to confirm your decision.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Rename gateway<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">To change a gateway\'s name: select it from the list, click <\/span><span class=\"f_ControlIndent\" style=\"font-weight: bold;\">Rename gateway<\/span><span class=\"f_ControlIndent\">, type the new name in the Create\/Rename Gateway Domain dialog, and click <\/span><span class=\"f_ControlIndent\" style=\"font-weight: bold;\">OK<\/span><span class=\"f_ControlIndent\">.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Copy gateway<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">If you wish to create a new gateway with settings that match another gateway, select a gateway from the list, click this button, and then specify a name for the new gateway.<\/span><\/p>\n\r<h2 class=\"p_Heading2\" style=\"page-break-after: avoid;\"><span class=\"f_Heading2\">Gateway Editor<\/span><\/h2>\n\r<p class=\"p_BodyText\"><span class=\"f_BodyText\">The Gateway Editor is used for editing each gateway\'s settings. It includes the following screens:<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\"><a href=\"gateway_gateway.html\" class=\"topiclink\">Domain<\/a><\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Use this screen to enable\/disable the gateway, designate the folder used for storing the domain\'s messages, and configure other delivery and attachment-handling options.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\"><a href=\"gateway--verification.html\" class=\"topiclink\">Verification<\/a><\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">If the remote domain’s server is configured to keep an LDAP or Active Directory server up to date with all of its mailboxes, aliases, and mailing lists, or if it runs a Minger server to provide remote address verification, you can use this dialog to specify that server and thus verify the validity of recipient addresses of incoming messages. When a recipient address is found to be invalid the message will be rejected. With this method you can avoid having to assume that all recipients of a domain’s messages are valid.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\"><a href=\"gateway_forwarding.html\" class=\"topiclink\">Forwarding<\/a><\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">With this screen you can declare a host or address to which the domain<\/span><span style=\"font-family: \'Times New Roman\',Times,Georgia,serif; color: #010100;\">\'<\/span><span class=\"f_ControlIndent\">s mail will be forwarded as soon as it arrives. There are also options for stating whether a copy of these messages should be kept locally and for designating the port on which the forwarded messages should be sent.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\"><a href=\"gateway_dequeuing.html\" class=\"topiclink\">Dequeuing<\/a><\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Using the options on this screen, you can configure MDaemon to respond to ETRN and ATRN requests made on behalf of the domain in order to dequeue its messages. You can also configure several other dequeuing related options.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\"><a href=\"gateway_quotas.html\" class=\"topiclink\">Quotas<\/a><\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">This dialog is used for assigning a limit to the amount of disk space that the domain may use and the maximum number of messages that may be stored.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\"><a href=\"gateway_options.html\" class=\"topiclink\">Settings<\/a><\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">This screen contains a number of other options that will apply to the selected domain gateway. For example, you can enable\/disable AntiVirus and AntiSpam scanning for the gateway, designate whether or not authentication is required when dequeuing mail, designate an authentication password, and several other options.<\/span><\/p>\n\r<p class=\"p_SeeAlso\" style=\"page-break-after: avoid; border-right: none; border-bottom: none; border-left: none;\"><span class=\"f_SeeAlso\">See:<\/span><\/p>\n\r<p class=\"p_SeeAlsoLinks\" style=\"page-break-after: avoid;\"><span class=\"f_SeeAlsoLinks\"><a href=\"gateway_global.html\" class=\"topiclink\">Global Gateway Settings<\/a><\/span><\/p>\n\r<p class=\"p_SeeAlsoLinks\" style=\"page-break-after: avoid;\"><span class=\"f_SeeAlsoLinks\"><a href=\"domain-manager.html\" class=\"topiclink\">Domain Manager<\/a><\/span><\/p>\n\r"
})
