Option 1: SMTP Authentication using port 587
Use case:
- Typically the preferred option if SMTP Auth is supported
- Device or application must use TLS 1.2 (TLS 1.0 and 1.1 are not supported)
- Outbound port 25 is restricted
Configure your device or application
Configure your server, application, or device to relay outbound using SMTP Auth. Use the following information to fill in the server and credential requirements:
- Server - smtp.cloudmail.email
- Port - 587
- Username - A valid address from your User list
- Password - The password created/used for this address
The Username and Password information is set on the User's Settings page (below). This is the full email address and password you will use when configuring SMTP Auth.
To configure/change a password, navigate to the User Profile:
- Login to the Console with a manager account
- Search for the address in the Finder tool or navigate to the individual user via Domain -> Users -> Select the User
- Click the three dots on the far right-hand side
Troubleshooting SMTP Authenticated Relay
Issue
The device or application is failing to connect.
Solution
- Make sure the device or application supports TLS 1.2. Some older multi-function printers or copiers do not support TLS 1.2, and will not be able to relay scanned documents
- Ensure the TLS 1.2 connection is being made over port 587
- Double-check that the server address is smtp.cloudmail.email
Issue
The device or application connects successfully, but emails are not relayed.
Solution
- If the Sender address differs from the SMTP Auth username, make sure the Sender address is a valid address in the console. If the address does not exist, the system will reject the relay for having an invalid sender address.
- If the application is using dynamic sender addresses, commonly used with CRM and some web forms for email tracking functions, the email system will not be compatible with the application. A different relay service will need to be considered.
Option 2: Standard outbound relay through port 25
Use case:
- If SMTP Authentication is not an option
- TLS 1.2 is not supported
Configure your device or application
Configure your server, application, or device to relay using the following information:
- Server: <your-domain>.outbound.emailservice.io (use the hyphen not period before TLDfor example yourdomain-com.outbound.emailservic.io)
- Port: 25 (if port 25 is blocked, use 2525)
- Login to the Console with a manager account
- Navigate to the domain where the device, application, or server is located
- Select the "Mail Flow" tab
- Scroll to the "Outbound email source IPs" section of the page
- Select the "Add" option under "Where is your email coming from?"
- Input the public IP address of the device, application, or server that the system should accept outbound messages from
- Make sure the Sender address of the emails exists in the User list in the console
Troubleshooting Standard Relay
Issue
The device or application is failing to connect.
Solution
- Make sure the device, application, or server's public IP address is correctly added to the Console, per Step 6 above. If possible, try https://www.whatsmyip.org/ to confirm you have the correct IP address.
- Some ISPs will block port 25. Try using port 2525.
Issue
The device or application connects successfully, but emails are not relayed.
Solution
- If the Sender address differs from the SMTP Auth username, make sure the Sender address is a valid address in the spam filter. If the address does not exist, the spam filter will reject the relay for having an invalid sender address.
- If the application is using dynamic sender addresses, commonly used with CRM and some web forms for email tracking functions, the e-mail relay will not be compatible with the application. A different relay service will need to be considered.
