Typo.
This commit is contained in:
parent
8e5a445e51
commit
ecbd763576
|
@ -18,24 +18,24 @@
|
||||||
|
|
||||||
* New: Able to manage global, per-domain and per-user greylisting settings,
|
* New: Able to manage global, per-domain and per-user greylisting settings,
|
||||||
whitelist senders, and global whitelisted SPF domains.
|
whitelist senders, and global whitelisted SPF domains.
|
||||||
* Variable names changed in returned JSON data of user profile (`GET /api/user/<mail>`):
|
* iRedAdmin-Pro-SQL-2.7.0:
|
||||||
* name `forwarding` is replaced by `forwardings`, and it's now a list
|
* Variable names changed in returned JSON data of user profile (`GET /api/user/<mail>`):
|
||||||
object of user forwarding email addresses (was a string, multiple
|
* name `forwarding` is replaced by `forwardings`, and it's now a list
|
||||||
addresses were separated by comma).
|
object of user forwarding email addresses (was a string, multiple
|
||||||
* Variable names in returned JSON data of mail alias profile
|
addresses were separated by comma).
|
||||||
* name `islist` is gone.
|
* Variable names in returned JSON data of mail alias profile (`GET /api/alias/<mail>`):
|
||||||
* name `goto` is replaced by `members`, and it's now a list object of
|
* name `islist` is gone.
|
||||||
member email addresses (was a string, multiple addresses were separated
|
* name `goto` is replaced by `members`, and it's now a list object of
|
||||||
by comma).
|
member email addresses (was a string, multiple addresses were separated
|
||||||
* Variable names in returned JSON data of domain profile (`GET /api/domain/<domain>`):
|
by comma).
|
||||||
* name `catchall` always presents, and it's now a list object of catch-all
|
* Variable names in returned JSON data of domain profile (`GET /api/domain/<domain>`):
|
||||||
email address (was a string, multiple addresses were separated by comma).
|
* name `catchall` always presents, and it's now a list object of catch-all
|
||||||
|
email address (was a string, multiple addresses were separated by comma).
|
||||||
* iRedAdmin-Pro-SQL-2.7.0 also fixes several bugs:
|
* Fixed bugs:
|
||||||
- Cannot set per-user alias addresses while creating new mail user.
|
* Cannot set per-user alias addresses while creating new mail user.
|
||||||
- Cannot add or remove per-user alias addresses while updating user profile.
|
* Cannot add or remove per-user alias addresses while updating user profile.
|
||||||
- User mailbox quota was removed while updating user profile.
|
* User mailbox quota was removed while updating user profile.
|
||||||
- Not use default transport setting while creating new domain.
|
* Not use default transport setting while creating new domain.
|
||||||
|
|
||||||
## Summary
|
## Summary
|
||||||
|
|
||||||
|
|
|
@ -66,29 +66,26 @@
|
||||||
<ul>
|
<ul>
|
||||||
<li>New: Able to manage global, per-domain and per-user greylisting settings,
|
<li>New: Able to manage global, per-domain and per-user greylisting settings,
|
||||||
whitelist senders, and global whitelisted SPF domains.</li>
|
whitelist senders, and global whitelisted SPF domains.</li>
|
||||||
|
<li>iRedAdmin-Pro-SQL-2.7.0:<ul>
|
||||||
<li>Variable names changed in returned JSON data of user profile (<code>GET /api/user/<mail></code>):<ul>
|
<li>Variable names changed in returned JSON data of user profile (<code>GET /api/user/<mail></code>):<ul>
|
||||||
<li>name <code>forwarding</code> is replaced by <code>forwardings</code>, and it's now a list
|
<li>name <code>forwarding</code> is replaced by <code>forwardings</code>, and it's now a list
|
||||||
object of user forwarding email addresses (was a string, multiple
|
object of user forwarding email addresses (was a string, multiple
|
||||||
addresses were separated by comma).</li>
|
addresses were separated by comma).</li>
|
||||||
</ul>
|
</ul>
|
||||||
</li>
|
</li>
|
||||||
<li>Variable names in returned JSON data of mail alias profile<ul>
|
<li>Variable names in returned JSON data of mail alias profile (<code>GET /api/alias/<mail></code>):<ul>
|
||||||
<li>name <code>islist</code> is gone.</li>
|
<li>name <code>islist</code> is gone.</li>
|
||||||
<li>name <code>goto</code> is replaced by <code>members</code>, and it's now a list object of
|
<li>name <code>goto</code> is replaced by <code>members</code>, and it's now a list object of
|
||||||
member email addresses (was a string, multiple addresses were separated
|
member email addresses (was a string, multiple addresses were separated
|
||||||
by comma).</li>
|
by comma).</li>
|
||||||
</ul>
|
</ul>
|
||||||
</li>
|
</li>
|
||||||
<li>
|
<li>Variable names in returned JSON data of domain profile (<code>GET /api/domain/<domain></code>):<ul>
|
||||||
<p>Variable names in returned JSON data of domain profile (<code>GET /api/domain/<domain></code>):</p>
|
|
||||||
<ul>
|
|
||||||
<li>name <code>catchall</code> always presents, and it's now a list object of catch-all
|
<li>name <code>catchall</code> always presents, and it's now a list object of catch-all
|
||||||
email address (was a string, multiple addresses were separated by comma).</li>
|
email address (was a string, multiple addresses were separated by comma).</li>
|
||||||
</ul>
|
</ul>
|
||||||
</li>
|
</li>
|
||||||
<li>
|
<li>Fixed bugs:<ul>
|
||||||
<p>iRedAdmin-Pro-SQL-2.7.0 also fixes several bugs:</p>
|
|
||||||
<ul>
|
|
||||||
<li>Cannot set per-user alias addresses while creating new mail user.</li>
|
<li>Cannot set per-user alias addresses while creating new mail user.</li>
|
||||||
<li>Cannot add or remove per-user alias addresses while updating user profile.</li>
|
<li>Cannot add or remove per-user alias addresses while updating user profile.</li>
|
||||||
<li>User mailbox quota was removed while updating user profile.</li>
|
<li>User mailbox quota was removed while updating user profile.</li>
|
||||||
|
@ -96,6 +93,8 @@
|
||||||
</ul>
|
</ul>
|
||||||
</li>
|
</li>
|
||||||
</ul>
|
</ul>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
<h2 id="summary">Summary</h2>
|
<h2 id="summary">Summary</h2>
|
||||||
<p>iRedAdmin-Pro RESTful API will return message in JSON format.</p>
|
<p>iRedAdmin-Pro RESTful API will return message in JSON format.</p>
|
||||||
<ul>
|
<ul>
|
||||||
|
|
Loading…
Reference in New Issue