summaryrefslogtreecommitdiff
path: root/docs/en/services/mx/index.html
diff options
context:
space:
mode:
authorUnknown <kwadronaut@leap.se>2018-02-27 11:45:37 +0100
committerkwadronaut <kwadronaut@leap.se>2018-02-27 11:47:29 +0100
commit4c6fab10e8d4beffeb50ad4ae0abffbdf4c03a5a (patch)
tree4b599e43c2ed87a5b1a0cd4e218553f1aa497b3f /docs/en/services/mx/index.html
parent8e4a41291aa68b36a3ddff0af8ffec8191d72952 (diff)
Update documentation
After 0.10 release there were some updates and fixes, including how to upgrade to 0.10. Pulling all changes in, fixes https://0xacab.org/leap/leap_se/merge_requests/21
Diffstat (limited to 'docs/en/services/mx/index.html')
-rw-r--r--docs/en/services/mx/index.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/en/services/mx/index.html b/docs/en/services/mx/index.html
index 048f5198..3fed61b4 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 &ldquo;flock&rdquo;, 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, &ldquo;flock&rdquo; is resolved to &ldquo;robin&rdquo;, which then gets resolved to &ldquo;<a href="&#109;&#x61;&#x69;&#108;&#x74;&#111;&#58;&#x72;&#111;&#x62;&#105;&#x6e;&#64;&#98;&#105;&#x72;&#x64;&#x2e;&#111;&#114;&#103;">&#114;&#x6f;&#x62;&#105;&#x6e;&#64;&#x62;&#x69;&#x72;&#100;&#x2e;&#x6f;&#x72;&#x67;</a>&rdquo;.</li>
-<li>virtual domains: by specifying the full domain, as in the case of &ldquo;<a href="&#109;&#97;&#105;&#x6c;&#116;&#x6f;&#x3a;&#x63;&#x68;&#105;&#99;&#107;&#x61;&#x64;&#x65;&#x65;&#x40;&#x61;&#118;&#x69;&#97;&#110;&#x2e;&#x6f;&#x72;&#x67;">&#x63;&#x68;&#105;&#x63;&#107;&#97;&#x64;&#101;&#x65;&#x40;&#97;&#x76;&#x69;&#x61;&#x6e;&#x2e;&#111;&#114;&#103;</a>&rdquo;, 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&rsquo;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, &ldquo;flock&rdquo; is resolved to &ldquo;robin&rdquo;, which then gets resolved to &ldquo;<a href="&#x6d;&#x61;&#105;&#x6c;&#x74;&#x6f;&#x3a;&#114;&#x6f;&#98;&#x69;&#110;&#64;&#x62;&#105;&#114;&#100;&#x2e;&#111;&#x72;&#x67;">&#114;&#x6f;&#x62;&#105;&#x6e;&#x40;&#x62;&#105;&#x72;&#x64;&#x2e;&#111;&#x72;&#103;</a>&rdquo;.</li>
+<li>virtual domains: by specifying the full domain, as in the case of &ldquo;<a href="&#109;&#97;&#x69;&#108;&#116;&#x6f;&#x3a;&#99;&#x68;&#105;&#99;&#107;&#x61;&#x64;&#101;&#101;&#x40;&#97;&#x76;&#105;&#x61;&#110;&#46;&#111;&#x72;&#x67;">&#x63;&#104;&#x69;&#x63;&#x6b;&#x61;&#x64;&#101;&#101;&#x40;&#97;&#x76;&#x69;&#x61;&#110;&#46;&#x6f;&#x72;&#x67;</a>&rdquo;, 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&rsquo;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 &ldquo;@deliver.local&rdquo; as one of the destination addresses. When &ldquo;@local.delivery&rdquo; is found, alias resolution stops and the mail is delivered to that username.</li>
</ol>