SpamExperts outgoing filtering requires an authorised relay route and authentication method. These credentials can be different from an employee's mailbox password. Use the values provided for the actual service rather than copying another domain's settings.
IN THIS ARTICLE
01 Identify the existing sending route
- Confirm outgoing filtering is active for the domain and identify the sending server or application owner.
- Open the outgoing authentication management where your role permits it, or request the required configuration from us.
- Choose the supported authentication method for the sending system. Keep IP-based trust restricted to an approved, stable source when it is used.
- Enter the relay hostname, port, TLS mode and authentication details in the sending system.
- Send a harmless test and confirm it appears in outgoing logs under the correct domain and identity.
02 Replace a password-based relay credential
- List every application using the credential, including website forms, billing notices and scheduled jobs. Arrange a short change window and pause affected queues if they would repeatedly retry an old password.
- At domain level, open Outgoing > Manage Authentication; at admin level the edit guide uses Outgoing > Manage Users. Find the intended authentication method and select Edit.
- For an authenticating user or domain, enter the new Password and Confirm Password, then save. An IP-only authentication method has no equivalent password rotation.
- Update each dependent application in its protected configuration. Keep its approved relay host, TLS mode and identity unchanged unless the change plan requires otherwise.
- Send one labelled test from each application and verify its outgoing log and external receipt before resuming normal queues.
- Remove obsolete stored copies and investigate any continued authentication failures from a missed application.
03 Protect and rotate
Store relay secrets in the application's protected configuration or approved secret store. Record which applications use each credential so rotation can be completed without leaving an unnoticed old sender behind.
Common questions
Can I use my normal mailbox password?
Only when the service explicitly uses that identity. A domain relay authentication account may have a separate username and secret.
Why does authentication succeed but delivery fail?
The sender address, content, rate controls or recipient destination may still cause rejection. Inspect the exact outgoing log response.
Should I disable authentication for easier setup?
No. Use the supported authorised route. An unrestricted relay can allow other systems to send through your service.
After changing a credential, verify every legitimate sender and remove the obsolete secret. If the change follows compromise, inspect outgoing traffic and identity locks before restoring normal sending. Do not put a relay password in a support ticket or publicly accessible application repository.