How to Configure the PageGate Email Interface for Domain or Sub=Domain Transcript for Video:
Welcome to the video tutorial on how to configure PageGate to host a messaging domain. In this tutorial, we’ll be going over how to configure PageGate’s GetMail module to host an email domain so you can email messages to your recipients and groups.
Before we begin, PageGate must be installed and you must have recipients and groups configured for this to work. For more information on how to install the program and configure recipients and groups, have a look at the support section of our website at www.notepage.net
Also, part of this configuration is not done in PageGate. To have PageGate host an email domain or sub-domain, you must first create the domain or sub-domain in question and redirect its MX record to the IP of the PageGate server. For example, let’s say that you have an email domain of happyhappyjoyjoy.com
You could ask the administrator for that email domain to create a sub-domain of messaging.happyhappyjoyjoy.com and to redirect the MX record for that new sub-domain to the IP of the PageGate server. As soon as that happens, every recipient and group listed in the PageGate Admin becomes a valid email address on the new domain or sub-domain. To use our example, let’s say that we have a group called RNS; we could send an email to RNS@messaging.happyhappyjoyjoy.com and the contents of that email would be delivered to every member of the RNS group, whether they were cell phones, pagers, email addresses, updates to social media, etc.
So, once the domain or sub-domain exists and is redirected to the PageGate server, here’s what you’ll need to do in PageGate.
The first step is to run the PageGate Admin.
Next, we’ll want to go to Interfaces – GetMail – Settings. Here on the right, set the ‘Local Domain’ field to match the name of the domain or sub-domain you’re routing to PageGate. To use our example, you might use messaging.happyhappyjoyjoy.com. Once you’ve entered the domain name, check Enabled, click Apply and tell it Yes, you do want this to be enabled for all existing groups and recipients.
Next, go to the Program – Settings section. Here on the right, in the ‘Run on this Server’ section, make sure you have GetMail enabled.
Let’s also talk for a moment about mailbox addressing. Typically speaking, the part before the @ of email you send to PageGate will need to match the name of a recipient or group as it exists in the PageGate Admin. To use our earlier example, if we wanted to send a message to our IT Alerts group, we would want to address the email to it_alerts@yourdomain. However, each recipient and group can be configured to accept multiple mailbox names.
Let’s say that we wanted to send an email to italerts@yourdomain as well as it_alerts. If you go in to the Email sub-section of any recipient or group in the program, you’ll see the ‘Email Aliases’ button. This allows you to add as many alias names to this recipient or group as you may need. So, if we click Add, we could add italerts as an alias for this mailbox and if you sent an email italerts@yourdomain, this new setting tells GetMail that traffic for italerts should go to the it_alerts group.
So, let’s go back to the GetMail interface screen for a moment to go over each item there. As noted earlier, the ‘Local Domain’ field controls the name of the domain PageGate should receive messages for. The Postmaster field should be set to a valid email address. This email address is sent all warnings, alerts and bad messages generated by the GetMail module. Leaving this field blank will drop all automatic reply messages that would normally go to the postmaster. This field is also used when no valid sender’s information is present in an outbound email message.
Everything from the ‘Relay All Mail’ checkbox down controls the delivery of outbound messages and has no influence over inbound traffic. Since PageGate has a mail server engine, if port 25 is open and its public IP address is part of the SPF record for your email domain, you can deliver email directly from the PageGate server rather than relaying it through your Exchange or other SMTP server. If you’re using direct delivery, you can choose to use the system’s DNS servers or you can specify a static set of DNS servers. Alternatively, you can check ‘Relay All Mail’ and configure the program to relay its outbound SMTP traffic through the specified SMTP server.
It’s also possible to configure PageGate’s GetMail to accept messages for multiple domains. For example, let’s say that you had the domains messaging.happyhappyjoyjoy.com, messaging.rns.com and messaging.brushyourteeth.com redirected to the PageGate server and that you wanted PageGate to accept messages for all three domains. Well, you can only specify one domain in the Local Domain field but you can still have the program accept messages for all domains by creating a Domain Aliases file.
It is possible, yes. Place a file named DomainAliases (there is no extension on the file) in the PageGate program directory. Each line of that file can reference a Domain name you'd like the PageGate to accept traffic for. To do so, you’ll need to run Notepad.
Here in notepad, each additional domain name should go on a line by itself.
Once you have the additional domains entered, to go File – Save, then browse to the PageGate program directory.
Change the ‘Files of Type’ to All Files so Notepad won’t put a .txt extension on the file, then name the file DomainAliases with no extension. It’s important to note that this file’s name is case sensitive, so be sure to name the file ‘DomainAliases’ exactly.
After you save the file, you will need to cycle the master PageGate service to have the program read in the new settings.
This concludes the overview of how to configure GetMail to host a domain or sub-domain.