summaryrefslogtreecommitdiff
path: root/docs/en/services/mx.html
diff options
context:
space:
mode:
authorelijah <elijah@riseup.net>2016-09-14 15:09:32 -0700
committerelijah <elijah@riseup.net>2016-09-14 15:09:32 -0700
commit811deee9e5b8cc42a3ea424ef873e9d69eb50cba (patch)
tree7e48be21fe30dca8add4c848c40e49702894a479 /docs/en/services/mx.html
parent836876b4b0763e01526c9aa9c1fc34e1d82416aa (diff)
updated docs
Diffstat (limited to 'docs/en/services/mx.html')
-rw-r--r--docs/en/services/mx.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/en/services/mx.html b/docs/en/services/mx.html
index 0d693204..a15ff88c 100644
--- a/docs/en/services/mx.html
+++ b/docs/en/services/mx.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="&#x6d;&#97;&#105;&#108;&#x74;&#111;&#x3a;&#114;&#111;&#x62;&#105;&#110;&#x40;&#x62;&#x69;&#x72;&#x64;&#x2e;&#111;&#114;&#x67;">&#x72;&#111;&#x62;&#105;&#110;&#x40;&#x62;&#105;&#114;&#100;&#x2e;&#x6f;&#114;&#x67;</a>&rdquo;.</li>
-<li>virtual domains: by specifying the full domain, as in the case of &ldquo;<a href="&#109;&#97;&#105;&#108;&#116;&#111;&#58;&#x63;&#x68;&#x69;&#99;&#107;&#97;&#100;&#x65;&#x65;&#x40;&#97;&#x76;&#105;&#97;&#110;&#46;&#111;&#114;&#103;">&#99;&#104;&#x69;&#99;&#x6b;&#x61;&#x64;&#101;&#x65;&#x40;&#97;&#x76;&#105;&#x61;&#x6e;&#x2e;&#111;&#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>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;&#97;&#105;&#108;&#x74;&#111;&#x3a;&#114;&#111;&#98;&#x69;&#110;&#64;&#98;&#x69;&#x72;&#100;&#x2e;&#111;&#x72;&#103;">&#x72;&#x6f;&#98;&#105;&#110;&#64;&#x62;&#x69;&#114;&#x64;&#x2e;&#111;&#x72;&#x67;</a>&rdquo;.</li>
+<li>virtual domains: by specifying the full domain, as in the case of &ldquo;<a href="&#x6d;&#x61;&#105;&#x6c;&#x74;&#111;&#x3a;&#x63;&#104;&#x69;&#99;&#x6b;&#x61;&#100;&#x65;&#101;&#64;&#x61;&#x76;&#105;&#x61;&#110;&#46;&#111;&#x72;&#103;">&#x63;&#104;&#x69;&#99;&#107;&#97;&#x64;&#101;&#101;&#64;&#x61;&#x76;&#x69;&#x61;&#110;&#x2e;&#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>