Sending Branded Emails From Your Own Domain

For branded mailbox and invitation emails, the default sender is the platform sender configured for TrekMail. The visible brand name and email layout can still use your identity, but the address may show the platform domain. Account-owner, billing, and other platform correspondence are separate flows and should not be presented as branded customer mail.

The Transactional sender setting lets eligible branded emails use an address on a domain in your account, such as noreply@yourbrand.com or hello@yourbrand.com. The address must pass the validation described below; it is not a general-purpose send-as field.

Why it works with no extra setup

When the address passes validation, choosing it does not add a separate DNS record just for this setting. The domain must already belong to your account and have the required DKIM provisioning. If it does not, the form rejects the address instead of saving an unsigned sender.

The safe rule is simple:

• Add the sender domain to your TrekMail account and complete its required DNS setup.
• Choose an address on that account-owned, DKIM-provisioned domain.
• Save the branding and send a real test message before giving the address to customers.

The validation is there so the platform can use the domain's existing DKIM-provisioned configuration for the branded sender. This makes the address eligible for the platform's normal authenticated sending path; it is not a guarantee that every recipient provider will place every message in the inbox.

If you change DNS or transfer the domain later, recheck its DNS status and send another test message before relying on the branded sender. Do not use a customer password reset or a large invitation batch as that test.

Turn it on

Open the Branding tab and find Transactional sender. Enter an address on an account-owned, DKIM-provisioned domain, such as noreply@yourbrand.com, team@yourbrand.com, or hello@yourbrand.com, then save. If the form rejects it, add or repair the domain's DNS setup first rather than trying a different unverified address.

Messages that use the active branded email identity use that address as the visible From. Send a test invitation or recovery message and check the received email before relying on it. A recipient may see:

From: YourBrand <noreply@yourbrand.com>

instead of:

From: YourBrand <noreply@trekmail.net>

The display name still comes from the saved Brand name. The sender setting changes the address, not the customer-facing copy, brand assets, or support process.

What stays unchanged

A few things are deliberately untouched even when this setting is on:

• Support email remains separate. Supported branded emails use it as Reply-To when you have saved one. If it is blank, no Reply-To header is added. Test a received message instead of assuming every platform email follows the same reply path.
• Delivery handling remains platform-managed. This setting changes the visible sender. It does not give you a separate bounce mailbox or a delivery guarantee.
• Email preferences remain separate. Choosing a sender does not configure preference or unsubscribe behaviour for another email flow.
• The existing DKIM setup is reused. The form requires a DKIM-provisioned domain in your account; it does not ask you for a new selector or key for this sender setting.

What stays TrekMail

A technical user reading raw email headers, such as View source in Gmail or full headers in Apple Mail, can still see transport details:

• The Received: chain shows the path through the outbound mail servers.
• The Return-Path: can show a platform-managed delivery route.

These are infrastructure details, not the name and address recipients normally use to identify the sender. The Transactional sender setting controls the visible From address; it does not promise that every raw-header detail is white-labelled or that a provider will make a delivery decision in a particular way.

Common questions

Do I need a separate DKIM key for the sender domain? No separate key is created for this setting. The sender domain must already be in your account and have its DKIM key provisioned. If it does, save the address and test a supported branded email.

What if the domain is not ready yet? The form refuses the address. Add the domain under Domains, complete the DNS and DKIM setup shown there, then return to Branding. It does not silently save an unsigned sender.

Can I use a sender on a different domain than my mailboxes? Yes, if that domain is also in this TrekMail account and has a DKIM key provisioned. The setting is validated against the account's domains, so an address on a domain outside the account cannot be saved.

What if a recipient reports a delivery problem? First confirm the saved sender, the domain's current DNS status, and a copy of the received message or delivery error. A valid sender address is necessary, but it cannot guarantee inbox placement at every recipient provider.

Can I have one sender for password resets and another for mailbox invites? Branding currently has one Transactional sender field. It supplies the visible From address for supported branded email flows; configure one sender that your team can maintain and test.

Will my customers see anything different in their reply chain? If you saved a Support email, supported branded messages use it as Reply-To, so Reply opens a message to that inbox. If it is blank, the message has no Reply-To header. Use a monitored Support email and send a test before telling customers where replies will go.

Does this affect my SPF lookup limit? This setting does not add a separate SPF record just for the Transactional sender. Keep the domain's normal DNS setup healthy and use the DNS status shown in the dashboard after any domain change.

When you should not change this setting

A few situations argue for keeping the configured platform sender for now:

• The sender domain is not yet in your TrekMail account with DKIM provisioned.
• You are testing a hostname or domain you do not control.
• You are between domain transfers or DNS changes and cannot yet confirm the domain's current status.

Safe rollout

1. Confirm that the sender domain is in this account and shows a healthy DKIM setup.
2. Save the Transactional sender and a monitored Support email, if you want replies.
3. Send a supported branded email to a test recipient outside your team.
4. Check the visible From address, Reply-To address, and the link host in the received message.
5. Only then use the sender for customer onboarding or a larger invitation batch.

What's next

• Set up White Label Lite: the full setup walkthrough.
• What stays TrekMail-branded: the honest list of internal touches a curious customer might still spot.
• Adding a Domain: the prerequisite step. You need a verified domain before transactional emails will sign correctly.
• Checking DNS Status: verify your DKIM, SPF and DMARC records are healthy before flipping this setting on.