Email Aliases: Difference between revisions
Appearance
Content deleted Content added
Document the way wildcard aliases are (mis)handled |
Document how wildcard aliases work - I think I've got it right now |
||
| Line 35: | Line 35: | ||
You can set an alias where the left hand side of the 'Email to' is empty. This will show in the alias list as something like: |
You can set an alias where the left hand side of the 'Email to' is empty. This will show in the alias list as something like: |
||
-any-@example.co.uk catchall@example.co.uk |
-any-@example.co.uk catchall@example.co.uk |
||
But the instructions on the web page are |
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 send 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 processing and delivery to that mailbox will happen. |
|||
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: |
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: |
||