Keep SES as the sending service and use a hosted mailbox for incoming mail, replies, folders, and phone access. The domain’s incoming MX route and its outgoing SMTP route do different jobs. You don't need to replace a working SES setup just to give staff an ordinary inbox.
Draw the conversation first: a customer writes to hello@example.com, an employee reads it in TrekMail, the reply goes through SES, and the customer’s next message returns to TrekMail. Then configure each connection with the credentials meant for it.
How incoming messages and replies travel
The domain's MX records direct incoming email to TrekMail. These records tell other email servers where to deliver messages addressed to example.com. A received message appears in the hello@example.com mailbox.
When an employee replies, TrekMail passes the outgoing message to the selected SMTP provider. With an SES profile configured, that provider is Amazon. The customer's next reply follows the MX records back to TrekMail. Devices use IMAP to read messages and work with server-side folders and message status.
Connecting SES for sending does not require moving the main domain's MX records to SES. Separate DNS records may be needed for sender verification and the return-path domain. Check what each record does before editing the active email DNS zone.
What to prepare in Amazon SES
Choose the AWS Region you will send from. The SMTP endpoint, credentials, and verified sender must match that Region. Changing only the server name while leaving settings from another Region may cause sending to fail.
You need dedicated SES SMTP credentials. Your AWS console password and mailbox password won't work here. See the Amazon SES SMTP interface documentation for the requirements.
Verify your sending domain or address in SES. For a domain, add the DNS records supplied by AWS and set up DKIM, the digital signature for outgoing messages. If you use a custom MAIL FROM domain for handling returns, configure its DNS too. Use the records from your own account; somebody else's example will not verify your domain.
A new SES account starts in the sandbox, a testing environment. Recipients are restricted to verified addresses or domains and the AWS mailbox simulator. Sending to customer addresses you have not verified requires production access in the relevant Region. Quotas and sender requirements still apply afterwards, so review the sandbox removal requirements before switching business correspondence.
Connect SES to the domain in TrekMail
Open the domain in TrekMail and go to SMTP. Create a provider profile with a clear name, the regional SMTP endpoint, port, encryption method, and SES SMTP credentials.
SES supports port 587 with STARTTLS or 465 with TLS from the start of the connection. Match the port to the encryption method. Test the connection, then select the saved profile for the domain. The custom SMTP provider guide covers the general process.
Employees continue using their TrekMail mailbox settings on phones and computers. The SES password stays in the outgoing service profile; you do not need to give it to every email user.
This arrangement also works with Nano, which requires your own SMTP provider for outgoing mail. SES is configured and paid for separately under AWS terms.
Test the finished setup
Send an ordinary message from hello@example.com to an external address you control. Check that the recipient sees the expected sender address. Reply and make sure the response arrives in the TrekMail mailbox.
Then inspect the received message's headers for DKIM and DMARC results. DMARC checks whether the visible sender domain aligns with authenticated message information. A successful connection to SES does not tell you how those checks went at the recipient's end.
Keep the two sets of connection settings apart
Write down the employee-facing settings and the provider-facing settings in different sections. The employee's app connects to the mailbox service for reading and sending. The domain's saved SES profile is the route TrekMail uses after accepting outgoing mail. Putting the SES endpoint into every employee's phone changes that arrangement and can make support harder.
Label the AWS Region beside the profile name. If you later create a second profile, use a name that distinguishes its purpose and Region rather than a vague label such as “new SMTP.” Keep the record free of credentials while identifying who can replace them. A future administrator should be able to identify the correct service account without receiving its secret in a general handover document.
Preserve the incoming MX route when you add SES verification records. If AWS supplies a record for a custom MAIL FROM subdomain, use the exact subdomain and purpose shown in that setup. Do not replace the main domain's incoming route simply because another instruction also mentions an MX record. Review record names and functions together before saving changes.
Diagnose the part of the conversation that failed
If the employee can read incoming mail but an outgoing reply fails, check the selected SES profile, regional credentials, sender verification and relevant limits. Keep the actual rejection text. A password failure and a recipient restriction need different corrections, so repeatedly changing the mailbox password is unlikely to explain both.
If the message reaches the outside recipient but their reply is missing, inspect the reply destination and incoming domain route. SES sending success does not prove that the mailbox address exists or receives mail. Also check whether Reply-To directs the answer somewhere other than the visible From address.
In the sandbox, choose a permitted test recipient or the AWS mailbox simulator for the appropriate check. That result does not establish that the account can already send to every real customer. Confirm production access and current limits in the selected Region before depending on the service for routine correspondence.
For any failed stage, record the account, Region, sender, recipient and time alongside the error. Do not include passwords. Assign responsibility for AWS account issues separately from mailbox access support. This helps the next administrator identify which service to check when a conversation fails.
Check one complete conversation before switching
Use a recipient your SES account is allowed to contact. Send from the business address, reply from the external mailbox, and check both directions on the employee’s phone. Inspect the actual sender and authentication results; a successful SMTP connection alone is insufficient.
Keep three credentials distinct: AWS console access, SES SMTP credentials for the selected Region, and the employee’s mailbox or app password. Record the Region and the person handling SES limits or rejection notices. Do not distribute the provider password to every phone. Production access is an AWS decision and does not remove sending requirements.
Compare the mailbox and sending conditions in the TrekMail plan guide.
Related reading
- Bring Your Own SMTP: When to Relay Through SES, SendGrid or Mailgun
- Website Transactional Email That Actually Arrives
- How do I keep two brands on different SMTP providers?
- Get your business email ready before the website launches
- Portal emails arrive, but customer replies vanish. What now?