Groupwise 6.5

There are two stages to achieve GroupWise integration:

• Routing – Ensure emails targeted as SMS messages get routed to the Esendex SMTP server.
• Authentication – Ensure the GroupWise server provides login information to the Esendex SMTP server.

By default, Groupwise routes all messages through a single SMTP server defined in its configuration screens. However, it has an option to route certain messages to a specific SMTP server based on their address. The Groupwise routing file enables you to route all addresses ending with "esendex.net" via the Esendex SMTP server.

Do the following on the GroupWise server:

1. Create (or edit) a file named route.cfg in the directory domain\wpgate\gwia
2. Add a line that reads:

   esendex.net ems.esendex.net

   Make sure you press enter at the end of the line, even if it is the last line in the file.

3. Save the file.

GroupWise uses a lookup file to determine whether to authenticate with any SMTP server listed in the Routing file. To add the Esendex login details, do the following on the GroupWise server:

1. Create (or edit) a file named gwauth.cfg in the directory domain\wpgate\gwia
2. Add a line that reads:

   ems.esendex.net <account-ref>\<username> <password>

   where <account-ref>, <username> and <password> are replaced by your Esendex details, for example:

   ems.esendex.net EX001234\person@mycompany.com password123

3. Make sure you press enter at the end of the line, even if it is the last line in the file.
4. Save the file.

Users can now send messages to <MobileNumber>@esendex.net for text SMS or <MobileNumber>@voice.esendex.net for voice SMS.