diff options
| author | Micah Anderson <micah@riseup.net> | 2016-11-22 09:26:27 -0500 |
|---|---|---|
| committer | Micah Anderson <micah@riseup.net> | 2016-11-22 09:26:27 -0500 |
| commit | 842087d4640f691aee08ec5a011dfb397b569dde (patch) | |
| tree | 4e93ce71658698ba93558b7471de92851ff8fdb9 /docs/en/services/mx/index.html | |
| parent | 34a381efa8f6295080c843f86bfa07d4e41056af (diff) | |
| parent | ec4ec9d17c6fb08030a6178f7131f8a95cc9bdd5 (diff) | |
Merge branch 'develop'
Switching to using 'master' for development, the 'develop' branch will
no longer receive commits, so we are merging what is in 'develop' into
master.
Diffstat (limited to 'docs/en/services/mx/index.html')
| -rw-r--r-- | docs/en/services/mx/index.html | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/en/services/mx/index.html b/docs/en/services/mx/index.html index 6899e0cc..e8e06e80 100644 --- a/docs/en/services/mx/index.html +++ b/docs/en/services/mx/index.html @@ -156,8 +156,8 @@ mx - LEAP Platform Documentation <ol> <li>alias lists: by specifying an array of destination addresses, as in the case of “flock”, the single email will get copied to each address.</li> -<li>chained resolution: alias resolution will recursively continue until there are no more matching aliases. For example, “flock” is resolved to “robin”, which then gets resolved to “<a href="mailto:robin@bird.org">robin@bird.org</a>”.</li> -<li>virtual domains: by specifying the full domain, as in the case of “<a href="mailto:chickadee@avian.org">chickadee@avian.org</a>”, the alias will work for any domain you want. Of course, the MX record for that domain must point to appropriate MX servers, but otherwise you don’t need to do any additional configuration.</li> +<li>chained resolution: alias resolution will recursively continue until there are no more matching aliases. For example, “flock” is resolved to “robin”, which then gets resolved to “<a href="mailto:robin@bird.org">robin@bird.org</a>”.</li> +<li>virtual domains: by specifying the full domain, as in the case of “<a href="mailto:chickadee@avian.org">chickadee@avian.org</a>”, the alias will work for any domain you want. Of course, the MX record for that domain must point to appropriate MX servers, but otherwise you don’t need to do any additional configuration.</li> <li>local delivery: for testing purposes, it is often useful to copy all incoming mail for a particular address and send those copies to another address. You can do this by adding “@deliver.local” as one of the destination addresses. When “@local.delivery” is found, alias resolution stops and the mail is delivered to that username.</li> </ol> |