Give each domain an explicit outgoing route if two brands must keep different sending providers. For example, a studio may retain its existing external service while a shop uses TrekMail managed sending on an eligible plan. Treat the route, approved sender, and person responsible as a single entry in your setup notes.
The practical risk is a broad change that also moves a brand you meant to leave alone. Check which domains inherit a default and which have an explicit choice before editing shared profiles or applying settings to all domains.
List the domains and their sending routes
For each domain, record who should send its messages and who manages the account with that provider. For example, example.com might use a profile named “Studio,” while example.net uses “Store.” Choose names that will still make sense several months later.
An SMTP profile holds the server, port, encryption method, and credentials. One profile can serve several domains if the external service allows sending for each of them. Saving the profile in TrekMail doesn't create that permission at the provider.
Check domain verification and outgoing mail authentication before setup. The provider may require its own DNS records. A profile created for the first client is not automatically authorized to send for a second.
Assign a profile to a specific domain
Open the domain and its SMTP tab. Select an existing profile or create one using the details supplied by the provider. Test the connection, save the settings, and confirm that the selected route belongs to the intended domain.
A connection check shows that the server is reachable and accepts the credentials. Afterwards, send a real message from the domain to an external mailbox. That can reveal sender restrictions that a simple connection test doesn't catch.
See the domain SMTP routing guide. For a new external service, use the SMTP profile setup guide as well.
Employees' email apps use their mailbox settings. TrekMail selects the external sending provider, so changing a domain's route does not normally require giving every user a new provider password.
Understand the difference between a default and a bulk change
A default is useful for new domains. If an agency generally uses one provider, it can choose that route as the starting option. Adding the next client will not require repeating the same choice.
A domain with an explicitly selected route keeps its own setting. This lets you have a general rule alongside individual client exceptions.
Apply to all domains changes existing domains in the account. Check the entire list before using it. You could switch clients with specific requirements along with the new client's domain. Bulk changes are available only to users with the appropriate permissions.
There is another dependency to watch. If several domains use one saved profile, changing its server or password affects all of them. Check where it is used before editing it.
Test each sending arrangement
Send a message from every domain and reply from an external address. Check the visible From address, where the reply arrives, and the sending report at the chosen provider. Keep the error for any failed message. It helps distinguish an incorrect password from an unauthorized sender or exhausted quota.
TrekMail managed sending is available on Starter and above. Nano needs a working external SMTP profile. The external provider retains its own restrictions, while TrekMail's account and sending checks continue to apply.
Prepare a change record for both brands
Use a small table with the domain, present route, intended route, approved sender, provider owner and reason for the change. Include the second brand even if you intend to leave it alone. That row is the control check: after the change, it should still use its original approved route.
List the other domains using any profile you plan to edit. A saved profile is a shared set of connection details, so replacing its password can affect more than the domain currently open on screen. Where only one brand is changing provider, review whether a separate profile is more appropriate than editing the one other domains still depend on.
Decide who can approve the change and who can reach the external provider if a message fails. Keep credentials out of the table. The useful handover says which account owns the route and where the authorised administrator can manage it, rather than exposing the provider password to every mailbox user.
Check provider approval as well as a saved setting
Before switching the first brand, confirm that the chosen external provider permits its sender domain and that required verification is complete. A profile name such as “Store” is your label, not evidence of provider approval. The provider's own limits and sender rules apply to the actual account and domain.
After selecting the route, send to an external mailbox and inspect the provider's available record of the message. Use the evidence it supplies rather than assuming that a successful message followed the new route. Check the visible sender and reply destination too. These are different acceptance results, and each can reveal a configuration mistake.
Repeat the same message test for the second brand. If it follows the wrong route, review explicit domain assignments, the default and any bulk action separately. Do not make another apply-to-all change merely to restore one brand without checking what else it would affect.
Keep recovery specific to the affected route
If the changed route fails, collect the error before replacing settings. Credentials, sender authorisation and provider limits require different responses. A different route may be available, but it must be deliberately configured and permitted for that sender; two saved profiles do not create an automatic backup service.
Retain the previous configuration details through the acceptance period without distributing its secrets. If a return to the former route is necessary, confirm that the old provider still allows the domain and repeat both brands' tests after making the correction. Record the final selected routes so the next administrator does not mistake the temporary recovery arrangement for the long-term plan.
Hand over the two routes
Keep the accepted route for each brand with its test result and responsible contact. Note any shared profile so the next administrator can find its other users before changing it. Review this record when adding another domain, replacing provider credentials or changing the account default.
Related reading
- Bring Your Own SMTP: When to Relay Through SES, SendGrid or Mailgun
- Multi Domain Email Hosting: Scale Without Losing Control
- Three brands in one email account: who should see what?
- How do I stop replying from the wrong business address?
- I already use Amazon SES. Where do I read customer replies?