editor
471
edits
Email Aliases: Difference between revisions
Describe alias chaining (makes explaining the wildcard problem easier)
m (Tidy) Tags: Mobile edit Mobile web edit |
(Describe alias chaining (makes explaining the wildcard problem easier)) Tags: Mobile edit Mobile web edit |
||
|
These will then be listed in the Alias list as:
:[[File:Clueless-email-alias-example3.png|none|600px|thumb|Alias for Bob]]
== Alias 'chaining' ==
Aliases are processed repeatedly until the chain stops. If you view the headers of a message you can see how many times the aliases were processed - each pass adds a header "X-AA-Info: Message ran through Aliases".
So if you have aliases of:
a@example.co.uk b@example.co.uk
b@example.co.uk c@example.co.uk
c@example.co.uk d@example.co.uk
then mail sent to any of these addresses will be sent to "d@example.co.uk"
== Wildcard entries ==
But the instructions on the web page are a little misleading - this is indeed a catch all to 'match any addresses for which there is not another alias (even if there is a mailbox that matches)' - but the alias file is processed repeatedly until there are no more aliases, and you can find most mail gets sent to the catch all address. You need aliases for the delivery mailboxes - entering the mailbox address in the domain in the 'Email to' with an empty 'Send to', so you get something like:
mailbox_name@example.co.uk -unchanged-@example.co.uk
and this will terminate the alias
If you're not careful on the web interface, you can end up pressing 'OK' where all the fields are empty. This gives an entry in the alias list something like:
| |||