Use Other provider when the business email service is not Google Workspace, Microsoft 365, or Zoho Mail and the provider supports authenticated outgoing mail. Obtain the exact outgoing-server details from the provider or company email administrator before starting. The connection may be limited to organizations in the controlled email field pilot.
Collect the provider details
Ask the email provider for the sender address, mailbox username, app password, public outgoing-server hostname, port, and secure-connection requirement. Common ports are 465 for a wrapped secure connection and 587 for a connection that is secured after it starts, but the provider's instructions are authoritative.
Use a provider-issued app password when one is supported or required. Do not reuse an owner or employee's everyday sign-in password unless the provider's documented setup explicitly requires that method and company policy permits it. Ellich rejects private or local-only server addresses; the outgoing server must be safely reachable as a public service.
Set the routing scope and save
Open Admin / Communications / Email and choose the scope first:
- Company default supplies the sender to every location without an override.
- This location supplies the sender only to the current location and takes priority there.
Select Other provider. Enter the sender name, sender email, monitored reply-to email, mailbox username, app password, outgoing server, port, and secure-connection choice exactly as supplied. Select Save and continue to test. Saving does not activate the sender.
Connecting an outgoing server does not modify the domain's MX records or nameservers. The provider or domain administrator remains responsible for SPF, DKIM, DMARC, aliases, and permission to use the From address. Customer replies go to the reply-to address, so confirm that the inbox is monitored.
Run the required test
Enter an approved Test recipient and select Send test. Ellich requires a successful test before enabling the route. Accepted means the email service accepted the message; it does not prove inbox delivery. Check the destination inbox and spam folder, then review Recent email activity for later evidence when the provider supplies it.
If the test fails, compare the hostname, port, secure-connection choice, username format, sender permission, and app password with the provider's current instructions. Do not weaken transport security just to make a test pass. Pilot restrictions may also block recipients that are not on the approved test list.
Disconnect and revoke the password
Select Disconnect beside the sender when it should no longer be used. Then delete or revoke the dedicated app password at the email provider. Ellich cannot guarantee that a provider-side password is retired merely because the local connection was removed. Finally, check whether the location inherits a company default or now shows no sender.
For compatibility controls, domain details, and recipient blocks, see Configure and test outbound email. Share only sanitized error text with support, never passwords, server account access, or authorization codes.