Arsnael commented on a change in pull request #654:
URL: https://github.com/apache/james-project/pull/654#discussion_r708970241



##########
File path: README.adoc
##########
@@ -15,15 +20,21 @@ It has a modular architecture based on a rich set of 
*modern* and *efficient* co
 Create your *own personal solution* for emails treatment by assembling the 
components you need thanks to the Inversion
 of Control mail platform offered and  go further customizing filtering and 
routing rules using *James Mailet Container*.
 
-Supported protocols are: IMAP, SMTP, JMAP, POP3 and more...
+Supported protocols are: IMAP, SMTP, link:https://jmap.io[JMAP], POP3 and 
more...
+
+The 
link:https://james.staged.apache.org/james-project/3.7.0/servers/distributed.html[*Distributed
 server*] focuses on delivering a easy-to-operate scalable mail server based on 
modern technologies

Review comment:
       ```suggestion
   The 
link:https://james.staged.apache.org/james-project/3.7.0/servers/distributed.html[*Distributed
 server*] focuses on delivering an easy-to-operate scalable mail server based 
on modern technologies
   ```

##########
File path: docs/modules/servers/partials/ManageSieveMailet.adoc
##########
@@ -0,0 +1,13 @@
+=== Manage Sieve scripts via a mailet
+
+Each user can manage his SIEVE scripts through the `ManageSieveMailet` mailet.
+
+To use the manage SIEVE mailet :
+
+* You need to create the user sievemanager@DOMAIN ( if you don't, the SMTP 
server will check the domain, recognize it, and look for an absent local user, 
and will generate an error ).
+* You can send Manage Sieve commands by mail to sievemanager@DOMAIN. Your 
subject must contain the command. Scripts needs to be added as attachments and 
need the ".sieve" extension.

Review comment:
       ```suggestion
   * You can send Manage Sieve commands by mail to sievemanager@DOMAIN. Your 
subject must contain the command. Scripts need to be added as attachments and 
need the ".sieve" extension.
   ```




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to