When someone changes their name or another identifying detail, the old email address may still be familiar to customers, suppliers, or colleagues. Keeping it can help messages reach the right person, but an alias without a clear owner or end date can create confusion and privacy risks. Make the decision based on likely sender behavior, the work tied to the address, and who is responsible for messages—not on convenience alone. Then record the decision and set a review date so temporary continuity does not quietly become permanent.
The useful bits
- Keep an old address only when identifiable senders are still likely to use it.
- Assign one accountable owner and define how incoming messages will be handled.
- Set a review date and remove or revise the alias when its purpose ends.
Start with the reason senders may still use it
Consider where the former address appears and who is likely to rely on it: ongoing client conversations, supplier records, shared project files, or correspondence already in progress. The stronger the connection to active work, the more useful a transition period may be. An address appearing only in old internal notes is a weaker reason to preserve it.
Ask whether senders can readily learn the new address. If the employee has already updated a public-facing contact page and informed active contacts, confusion may fade sooner. If external records cannot be updated quickly, a temporary alias may help catch messages that would otherwise go to an obsolete address.
- List the active relationships or records that still use the old address.
- Separate ongoing business correspondence from archival or inactive references.
- Identify any other route for senders to find the current contact.
Estimate confusion without treating every possibility as a reason
Expected sender confusion is about plausible, current use—not the fact that an address exists somewhere online. Look at recent business conversations and the channels your organization controls. Are people still replying to old threads? Are customers likely to copy an address from a saved contact? Does a team process still direct messages there?
Avoid using an alias as a substitute for updating records you can control. Change the address in relevant signatures, contact pages, templates, and internal documentation. Tell active correspondents the preferred address in a clear, routine way. These steps reduce future reliance on the old one and make the later review meaningful.
Make ownership explicit before keeping it
An alias should have a named responsible person or role. Decide who will notice incoming messages, who may respond, and what to do with messages that are misdirected or sensitive. If the former address points to a current employee, confirm that the employee is comfortable handling the expected mail and that the arrangement fits your organization’s access practices.
Do not assume an alias is a separate mailbox or login. In BITTU Mail, a mailbox alias is not automatically an independent mailbox/login; confirm what the configured address does before relying on it. If a workspace administrator is considering an address change or alias, available controls can depend on role, plan, and provisioning state. The administrator should verify the actual configuration and permissions rather than infer them from the address name.
Set a boundary and a review date
Record the purpose, owner, start date, and a specific date to reconsider the arrangement. At review, check whether messages still arrive, whether they concern active work, and whether senders have been redirected. Choose an interval that fits the work’s normal communication cycle; there is no single duration that suits every organization.
A review date is not an automatic promise to retain the alias until then. If ownership changes, the employee’s access changes, or unexpected sensitive messages arrive, reassess sooner. At the review, either remove the alias if the service and administrator controls allow it, or document why it remains and schedule another review. Avoid indefinite retention by default.
Example: A supplier continues replying to a thread addressed to [old.name@example.com], while the employee now uses [new.name@example.com]. The workspace administrator confirms the old address is configured as an alias, assigns the employee as the message owner, updates the supplier contact record, and schedules a review. At that review, the owner checks whether supplier messages still use the old address before recommending removal or a documented extension.
Check the arrangement in practice
After an authorized administrator makes or changes the configuration, confirm it with a controlled message from an account you are permitted to use. Verify that the intended recipient receives it and can identify which address the sender used. Then check the handling process: the responsible person can see the message, knows whether to reply from the new address, and can distinguish misdirected mail from work they own.
This check confirms only the tested setup and message flow; it does not establish that every sender or provider will behave the same way. Do not use a real customer message or sensitive information as a test. If delivery or ownership is unclear, pause reliance on the alias and ask the authorized workspace administrator to inspect the configuration.
- Confirm the old address has a defined owner and purpose.
- Send a harmless test message and verify the intended recipient and handling.
- Update the sender-facing records you control.
- Record the review date and the criteria for keeping or ending the alias.
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction