When the company’s phone number or website changes, a single webmail template doesn't prove every employee’s signature changed with it. First identify which sender addresses use the domain template and which messages are composed in Outlook, Apple Mail or another app.
Check a new message and a reply after the change
Choose two mailboxes and send a new message and a reply to an outside address you control. Change the From address where the user represents another brand. Check the actual received text, links and image display, then compare webmail with a mail app. In Default mode, existing identities may keep an earlier signature; Enforced applies the domain rule in webmail. Keep a list of users who need an app-side update and tell them which approved wording to copy. Do not assume an SMTP connection inserts a signature.
Write a signature that fits the whole domain
Include information that really is the same for the relevant mailboxes. A company name, website, and office number suit a shared block. One employee's personal mobile number can quickly cause mistakes when included in a general template.
Do not expect the system to replace a person's name or job title automatically in ordinary text. If you need personal details, decide where employees will keep them and how they should fit with the shared information. Prepare separate signatures on the appropriate domains for different brands.
Keep the text useful without images. If you add a logo, include the company name and contact details as ordinary text beside it. Someone reading with image loading disabled should still see the essential information.
Choose how the signature applies
Domain signature settings offer Off, Default, and Enforced. They serve different purposes.
Off disables the shared signature. Users manage their own signatures independently.
Default supplies an initial signature for new sender identities. It is useful when you want to give an employee a starting point they can edit. Updating the domain template should not be treated as a mandatory update to every signature already configured.
Enforced uses the domain signature as a webmail rule in place of the sender identity's personal signature. Choose this when the company needs consistent information in messages composed through TrekMail webmail.
Pick the mode that fits your working process. A starting template may be enough if employees can use different contact blocks. If the company centrally maintains a required block, use enforcement in webmail and a separate arrangement for external apps.
Check the signature when changing the sender
One person may have several addresses, such as anna@studio.example and sales@shop.example. The signature should match the address selected in the From field, not just the person signed in to the mailbox.
TrekMail connects signature settings to authorized sender identities and their domains. Open the identity and signature settings, review the available addresses, and create a draft with each one.
Check a new message, a reply, and a message whose sender has been changed. Look at where the contact block appears relative to the previous correspondence and whether an extra signature has been added manually.
Use two mailboxes on the same domain for a broader check. Open their messages as an external recipient and compare the wording, links, line breaks, and image display. That shows the result more clearly than relying on one editor preview.
Build a short change list before editing
Start with the information that has changed: the old phone number, the new number, the affected company domains and the person approving the wording. Check whether another brand in the account still uses the old number. A template change should follow the selected domain's responsibility, not overwrite unrelated businesses simply because they share an administrator.
List the ways employees compose messages. Include webmail, desktop apps and phones, and note any shared or alias sender addresses used for customer replies. This list becomes the rollout checklist. It also explains why changing the domain template and sending one test from an administrator's mailbox cannot cover everyone.
Keep the signature short enough that employees can recognise an outdated copy. A clear company name, working contact details and the necessary personal information are easier to review than a large block of decorative text. If a legal or commercial statement is required, have the appropriate person approve that wording rather than assuming a template feature supplies it.
Check the result outside the editor
Send to an external mailbox using the approved test addresses. Inspect a fresh message, then reply to it and inspect the reply. Look for the new number, the actual destination of a website link and any duplicated contact blocks. A link can display updated text while still opening an old destination, so check both parts.
Test one sender on each affected domain. If an employee changes the From address to represent a second brand, the received message should contain that brand's details. Include a reply to a message originally addressed to an alias, because the selected reply identity may differ from the default for a new message.
If images are part of the signature, review the message with remote images hidden as well as visible. The essential contact information should remain readable in text. Check line breaks on a narrow screen and make sure a large logo does not bury the phone number the company needs customers to use.
Follow up on app-side changes
Give app users the approved text and a clear request to confirm when their copy is updated. Menu names vary by app and version, so describe the result they need: the correct block for new messages and replies from each work account. Do not represent a webmail setting as a server-wide modification to every SMTP message.
Choose a small sample of external replies after the update rather than treating acknowledgements alone as proof. If an old number still appears, identify the composing app and sender identity before editing the domain rule again. The stale copy may live in an app's local signature or inside quoted correspondence. A historical message should not be confused with a newly inserted signature.
Keep future changes consistent
Choose who updates the shared template when the phone number, website, or company name changes. Keep the approved wording in one place so employees do not have to reconstruct it from old messages.
Give Outlook and Apple Mail users the same approved wording with separate instructions. The domain's webmail setting doesn't rewrite the body of a message composed in an external app. If a shared block is required for a particular group of mailboxes, agree in advance which interface that group should use for business email.
Further setup
The domain signature guide explains the modes and their webmail scope.
