A SiteWorx email alias sends messages addressed to one local address to another destination. Use it for a role address such as [email protected] when the destination mailbox should handle those messages.
IN THIS ARTICLE
What you need before you begin
Confirm the destination exists, accepts mail and is authorised to receive the content. Check whether the source address already has a mailbox or another routing rule. Do not create a forwarding loop between two addresses.
01 Forward email with a SiteWorx alias
- Open Hosting Features > Email > Aliases and choose Add an Alias or the plus control.
- Enter the source address name and choose its correct domain. In Forwards To, enter the complete destination email address.
- Review the source and destination carefully, then add the alias. If the destination is external, consider its spam and authentication policies.
- Send a test from an unrelated external sender to the alias. Check the destination inbox and spam folder, and inspect any bounce message if delivery fails.
- Use the alias’s edit action to change its destination later, or remove it when the forwarding relationship ends. Review aliases during staff changes.
02 Example: route a role address to the team inbox
For a role address [email protected], enter sales as the alias name, select example.com as its domain and enter [email protected] in Forwards To. Replace both example domains with addresses you control. Send a message from a third account and confirm it reaches the team inbox. Ensure that inbox does not forward the message back to [email protected]. This routing entry does not create a separate sales mailbox or password.
Confirm the expected result
The intended recipient should receive the test with enough original information to identify the sender. Confirm whether any local mailbox copy is required rather than assuming the alias automatically preserves one.
Why does the SiteWorx alias fail to forward to an external inbox?
If forwarding fails while local delivery works, the external provider may reject forwarded mail under its policies. Review the actual delivery error with support. Repeatedly creating additional aliases will not resolve a loop or authentication rejection, and an alias does not provide a separate mailbox login.