Your name in your customers' mail apps

Your dashboard and webmail can already use your own address. Mail apps can use your brand domain too, but only after its DNS and mail-host certificates are ready. Until then, TrekMail keeps showing the working platform mail-server names so a customer does not receive a certificate warning.

This feature makes the mail-client names imap.yourbrand.com and smtp.yourbrand.com available for the brand domain you choose. It is separate from branded dashboard and webmail addresses.

What your customers see

Before the branded mail-app status is Ready, mailbox setup shows the platform mail-server names:

• Incoming server: imap.trekmail.net
• Outgoing server: smtp.trekmail.net

When the status is Ready, setup pages and supported auto-setup responses use imap.yourbrand.com and smtp.yourbrand.com instead. The mailbox, password, ports, and underlying mail service do not change.

Some mail apps can discover the settings automatically. Others ask for manual IMAP and SMTP details. In either case, give customers the names and ports shown in the current setup page; do not publish a branded hostname until its status is Ready.

Turning it on

Open Domains → (your brand domain) → Branding. Under Branded access, turn on Mail apps on your domain. This is the base domain that represents your brand, such as yourbrand.com, not every customer domain you host.

The dashboard, webmail, and mail-app settings are independent. You can turn on this setting without a branded dashboard or webmail. Save it while previewing if you want, but records and mail-client hostnames become usable only while White Label is active.

Save the change, then use DNS for your brand on the same page. It shows records that need attention first. Records that already work stay under Show records already working, so a ready domain does not turn into a long checklist. Copy from this card, not from an old screenshot or a different account.

What you may need to add

The records belong on the brand domain. Their names are predictable, but targets can differ by environment, so use the exact values shown in DNS for your brand.

The card shows the exact target for each record that needs your action. Do not replace a CNAME with an IP address: a CNAME lets the platform change its infrastructure without asking you to edit DNS again.

You will not normally see smtp, mta-sts, autoconfig, or autodiscover repeated here. They are part of the domain's standard setup on DNS & Health. In particular, do not create a second smtp record just because you turned on Mail apps. Keep the existing correct SMTP record. If a related standard record later breaks, Branding may bring it back as an item that needs attention.

IMAP and SMTP are still activated together for mail clients. If Branding asks for imap or dav, use the target shown there. To review SMTP, open DNS & Health for the same domain. Do not create an A record with the same host name as a CNAME.

If you use Cloudflare, keep the mail-related CNAMEs DNS-only (grey cloud). A proxy can prevent a mail client from reaching the mail server or receiving the right certificate.

After you publish a record, use Check now, then return to the card for the result. It is normal for some rows to be ready before others. A successful row moves under Show records already working.

The display can also list a record that was once correct but has since changed. Repair only the marked record, then run another check.

What happens next

The service first verifies the DNS records that customers can use in their own domain setup. It then checks the mail-app addresses and provisions their certificates. Only after that does it give those names to mail clients. Use the status on the Branding page rather than an estimated wait time.

The switch reports where it has got to:

• Setup needed: one or more records still need to be added or corrected.
• Almost ready: the records are in place and the service is finishing the secure connection.
• 1 step left: email already works on your domain, but the DAV record for calendars and contacts still needs attention.
• Ready: the branded mail-client names are ready to use.

The waiting states are safe. DNS that customers publish can already use your brand, while mail clients continue with a working platform hostname until the branded client hosts are ready.

The order matters, and we handle it

Mail apps need a secure connection that matches the hostname. TrekMail therefore keeps imap.yourbrand.com and smtp.yourbrand.com out of the setup details until that connection is ready. If this step fails, use Check now after confirming the DNS records, then contact support with the hostname and its displayed status if it remains failed.

This is why a pending status should not be rushed. If you turn the setting on but do not complete the records, the platform mail-server names remain in use. Do not send the branded names to customers until the status is Ready.

If it stops working later

If a customer reports a setup or connection problem, open Branding and compare the flagged record with your DNS provider. Check the host, record type, target, and Cloudflare proxy setting. After fixing it, run Check now and wait for the displayed status to update.

What stays ours

The MX record. Mail addressed to your customers still arrives through the platform MX target shown in the domain's DNS settings. This is an infrastructure record, not a hostname someone enters into a mail app.

The feature brands the supported DNS values and mail-client hostnames. It does not promise to remove every platform detail from a technical DNS or message-header inspection.

Turning it off

Before switching it off, update any customer-facing setup guides to use the platform mail-server names shown in the current setup page. Then flip the switch off and save. The platform stops advertising the branded mail-client names while certificate cleanup is processed.

A phone or desktop app already configured with imap.yourbrand.com or smtp.yourbrand.com may need to be changed to the platform names after you turn the setting off. Test one mailbox before making the change for all customers.

Common questions

"Do my customers have to re-add their mailboxes?" No. Existing clients can keep their current platform settings. To show the branded names in an existing mail app, update its IMAP and SMTP hostnames after the status is Ready. New setup flows use the current names when the app supports discovery; otherwise enter the displayed settings manually.

"Why is SMTP not listed in DNS for your brand?" The domain already gets its SMTP record during normal domain setup, and DNS & Health continues to verify it. Branding does not duplicate a record that is already correct. Add or change SMTP only if DNS & Health says it needs attention.

"Can I use different names than imap and smtp?" No. These names are fixed so setup responses and customer instructions remain consistent. Choose the brand's base domain carefully, because that is the part you control.

"I have several domains. Which one is used?" The mail zone belongs to the selected brand's base domain. If that brand is your account default, domains using that brand advertise the same branded setup names. Use a separate custom brand when a group of domains needs a different identity.

"My customer needs to enter settings manually." Give them the IMAP and SMTP hostnames, ports, security method, and login name shown in the current setup page. Do not guess from an older setup guide.

What's next

• Set Up White Label Lite on Your Own Domain
• What stays TrekMail-branded
• Stuck on pending DNS?