An invitation reaching the customer proves only the outgoing part of a portal’s email setup. Check the reply address and the mailbox behind it next. A portal can send as orders@example.com while a reply is directed elsewhere by Reply-To, or the address may have no working incoming route.
Use one invitation or order update as a traceable example. Record who sends it, what address the recipient sees, and who in the business should read the reply. The following setup applies to a portal with configurable SMTP, not a built-in integration with every application.
Decide which server the portal connects to
There can be two connections in this setup. First, the portal signs in to TrekMail SMTP as a mailbox. Second, TrekMail passes outgoing messages to the external SMTP provider selected for the domain.
The first connection uses mailbox credentials or a separate app password. The second uses an external provider profile saved in the TrekMail dashboard. These settings serve different purposes, so do not automatically copy the external provider's password into the portal.
You can connect the application directly to an external sending service if that is your chosen arrangement. In that case, check the settings, sender permissions, and limits with that service. The steps below cover a portal connected to a TrekMail mailbox.
Find the portal documentation for Custom SMTP, Email delivery, or Outgoing mail. Check whether the setting covers every notification you need. Some applications configure invitations, order updates, and password resets separately.
Prepare the address and a dedicated password
Create orders@example.com and assign someone to read its replies. Make sure the domain can receive mail and has an available sending route. Starter and higher plans include managed sending; Nano needs your own SMTP provider.
Create an app password specifically for the portal, with a clear label such as “Order portal.” You can then revoke it when changing services without affecting other connections. Follow the app password guide.
Choose an authorized From address. Entering any address into the portal's form doesn't grant permission to send as it. If you want an alias or shared address, configure its permission first and check that the chosen connection method supports it.
Set Reply-To separately if replies should reach another working address. This field controls the reply recipient; it does not replace sender verification.
Enter the settings supplied for the mailbox
Get the exact values from Apps & devices for the mailbox. The standard outgoing server is smtp.trekmail.net. If your mailbox settings show another hostname, use that one.
The portal will usually need:
- SMTP host: the mailbox's outgoing server.
- Port and encryption: 465 with SSL/TLS, or 587 with STARTTLS.
- Username: the full mailbox address.
- Password: the app password created for the portal.
- From: an address authorized for sending.
Encryption protects the connection between the application and email server. Do not choose port 465 and STARTTLS as an arbitrary combination; the mode must match the port. The TrekMail IMAP and SMTP reference helps match the fields when the portal uses different labels.
Save the settings and run the built-in connection test. If the app has no test, send a test notification next.
Check the complete customer message flow
Create a test order or invitation for an external address you control. Check the subject, From address, company name, and links. Then reply and make sure the message reaches the person responsible.
Test the specific notification that prompted the setup. A successful message from the SMTP test form doesn't prove the application uses those settings for password recovery or other service messages.
Messages sent by the portal may not appear in the mailbox's Sent folder. Saving a copy can be the application's responsibility. Use the portal's available logs and rejection messages to monitor delivery.
Estimate the expected load. A few invitations per day and thousands of notifications in a short period have different quota requirements. SMTP configuration alone does not turn an ordinary mailbox into a bulk mailing service.
Compare the address shown with the address used for replies
Open the received notification in the outside mailbox and press Reply without sending immediately. Inspect the proposed recipient. That is the address the customer will normally answer. If it is a no-reply address, an old provider address or a mistyped mailbox, correct the portal's intended reply configuration and send a fresh notification before testing again.
Next, send the harmless reply and look in the staff member's real working inbox, not only in an administrator's test mailbox. If an alias or forward is involved, record its destination. Confirm that someone is responsible for reading that destination during normal business hours. A technically accepted message can still be unattended if everybody assumes another colleague owns the address.
Keep From, Reply-To and SMTP username distinct in the notes. The username authenticates the sending connection. From identifies the sender presented to the customer. Reply-To, when supplied, selects the reply recipient. Using the same value everywhere can be appropriate for a simple setup, but it is not a rule that fixes every missing reply.
Verify the real notification after changing settings
Repeat the actual action that sends the customer message: an invitation, order update or another harmless test event. Use test accounts and content that do not affect real customer work. Check the resulting message rather than relying on the portal's generic SMTP success banner.
If the portal has several notification settings, record which event used which configuration. A recovery email might come from a different sender or use a separate delivery service. Change the relevant setting deliberately and review the next received message to confirm its effect.
Keep enough evidence for support: event type, sender, outside recipient, approximate time and the available application error. Avoid recording app passwords or private customer data. Once the exchange works, document where delivery errors and replies will be checked in routine use. Someone should be able to follow the same conversation later without reconstructing the original installation from memory.
Keep portal mail separate from platform notifications
The portal’s SMTP configuration covers the messages the portal sends through that connection. A domain’s custom route does not automatically control TrekMail’s own platform notifications. Record the application and event behind a failed message before changing settings for a different service.
Related reading
- Website Transactional Email That Actually Arrives
- Domain Email Alias vs Mailbox: Decision Guide
- I already use Amazon SES. Where do I read customer replies?
- How do I keep two brands on different SMTP providers?
- Moving your website? Keep business email working