You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by rc...@apache.org on 2020/08/25 10:11:57 UTC

[james-project] 04/08: JAMES-3187 Mailing lists subsection of the community documentation

This is an automated email from the ASF dual-hosted git repository.

rcordier pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/james-project.git

commit 11da66c8cee934de4fec943b2d44731084ee9d77
Author: Rene Cordier <rc...@linagora.com>
AuthorDate: Fri Aug 14 11:48:45 2020 +0700

    JAMES-3187 Mailing lists subsection of the community documentation
---
 docs/modules/community/pages/mailing-lists.adoc | 165 +++++++++++++++++++++++-
 1 file changed, 164 insertions(+), 1 deletion(-)

diff --git a/docs/modules/community/pages/mailing-lists.adoc b/docs/modules/community/pages/mailing-lists.adoc
index dc3bd18..68dedf1 100644
--- a/docs/modules/community/pages/mailing-lists.adoc
+++ b/docs/modules/community/pages/mailing-lists.adoc
@@ -1,3 +1,166 @@
 = Mailing lists
 
-(TODO)
+Please read the <<_guidelines>> below before subscribing to our lists and join our community.
+
+== James mailing lists
+
+=== Server user list
+
+*Low traffic*
+mailto:server-user-subscribe@james.apache.org[Subscribe]
+mailto:server-user-unsubscribe@james.apache.org[Unsubscribe]
+http://www.mail-archive.com/server-user@james.apache.org[Archive]
+
+This is the list where users of the Apache James (Server) meet and discuss issues. Developers are also expected to be
+subscribed to this list to offer support to users of Apache James (Server).
+
+=== Server developer list
+
+*High traffic*
+mailto:server-dev-subscribe@james.apache.org[Subscribe]
+mailto:server-dev-unsubscribe@james.apache.org[Unsubscribe]
+http://www.mail-archive.com/server-dev@james.apache.org[Archive]
+
+This is the list where participating developers of the Apache James Project meet and discuss issues, code changes/additions,
+etc. Subscribers to this list get notices of each and every code change, build results, testing notices, etc. Do not
+send mail to this list with usage questions or configuration problems -- that's what server-user@james is for.
+
+=== Mime4j
+
+*Medium traffic*
+mailto:mime4j-dev-subscribe@james.apache.org[Subscribe]
+mailto:mime4j-dev-unsubscribe@james.apache.org[Unsubscribe]
+http://mail-archives.apache.org/mod_mbox/james-mime4j-dev[Archive]
+
+Discussions on the http://james.apache.org/mime4j[Mime4j] parser library.
+
+=== Site developer list
+
+*Low traffic*
+mailto:site-dev-subscribe@james.apache.org[Subscribe]
+mailto:site-dev-unsubscribe@james.apache.org[Unsubscribe]
+http://www.mail-archive.com/site-dev@james.apache.org[Archive]
+
+This is the list where participating developers of the Apache James project discuss changes/additions to the James
+websites etc. Subscribers to this list get notifications of every commit of the website resources. Do not send mail to
+this list with James software problems -- that's what server-user@james is for.
+
+=== James general list
+
+*Low traffic*
+mailto:general-subscribe@james.apache.org[Subscribe]
+mailto:general-unsubscribe@james.apache.org[Unsubscribe]
+http://www.mail-archive.com/general@james.apache.org[Archive]
+
+This is the list for general discussions related to the running of the project, it is the public list of the
+James project management committee (PMC) and is a public list opened to all. Do not send mail to this list with James
+software problems -- that's what server-user@james is for.
+
+=== Mailet API list
+
+*Low traffic*
+mailto:mailet-api-subscribe@james.apache.org[Subscribe]
+mailto:mailet-api-unsubscribe@james.apache.org[Unsubscribe]
+https://mail-archives.apache.org/mod_mbox/james-mailet-api[Archive]
+
+This is the public list for the Mailet API subproject, discussing all http://james.apache.org/mailet/index.html[Mailet API]
+design and implementation related topics. Questions about using Mailets and their configuration should be addressed
+to the server-user list.
+
+== How to unsubscribe your old email address
+
+First, find out the particular email adress to which ezmlm is sending. The email headers are visible in Microsoft Outlook
+via the messages menu "View | Options".
+
+    Microsoft Mail Internet Headers Version 2.0
+    ...
+    List-Unsubscribe: <ma...@james.apache.org>
+    List-Help: <ma...@james.apache.org>
+    List-Post: <ma...@james.apache.org>
+    List-Id: "James Server Users List" <server-user.james.apache.org>
+    Reply-To: "James Server Users List" <se...@james.apache.org>
+    Delivered-To: mailing list server-user@james.apache.org
+    ...
+    Return-Path: server-user-return-12345-john=host.domain@james.apache.org
+    ...
+
+The _Return-Path_ header contains the email address which is subscribed.
+
+To stop subscription for the address _john@host.domain_, send an email to
+
+`server-dev-unsubscribe-john=\host.domain@james.apache.org`
+
+or to
+
+`server-user-unsubscribe-john=\host.domain@james.apache.org`
+
+== Guidelines
+
+A mailing list is an electronic discussion forum that anyone can subscribe to. When someone sends an email message to
+the mailing list, a copy of that message is broadcasted to everyone who is subscribed to that mailing list.
+Mailing lists provide a simple and effective communication mechanism for discussion and decision making.
+
+The *Apache Software Foundation* has well established reasons for using email and not other types of forum.
+You may use a mail-news gateway, gmail or anything else you like but email is, and will remain, the official medium.
+
+With potentially thousands of subscribers, there is a common etiquette that you should observe. Please keep on reading.
+
+*Respect the mailing list type*
+
+* "User" lists are lists where you can send questions and comments about configuration, setup, usage and other "user"
+types of questions.
+* "Developer" lists are lists where you can send questions, comments and contributions about the project's software
+source code and general "development" types of questions.
+
+Some questions are appropriate for posting on both the "user" and the "developer" lists. In this case, pick one and
+only one. Do not cross post.
+
+Asking a configuration question on the developers list is frowned upon because developers' time is as precious as yours.
+By contacting them directly instead of the users list you are abusing resources. It is unlikely that you will get a
+quicker answer this way, those developers who have time to devote to providing support are also subscribed to the users
+list. If you contact individuals directly, or post your user issues to the developer list you may get no answer at all.
+
+*Join the lists that are appropriate for your discussion*
+
+Please make sure that you are joining the list that is appropriated for the topic that you would like to discuss.
+The general list is for discussions about the management and direction of the James project, not for "general support".
+
+*Ask smart questions*
+
+Every volunteer project obtains its strength from the people involved in it. You are welcome to join any of our mailing
+lists. You can choose to lurk, or actively participate; it's up to you. The level of community responsiveness to
+specific questions is generally directly proportional to the amount of effort you spend formulating your question.
+Eric Raymond and Rick Moen have even written an essay entitled "Asking Smart Questions" precisely on this topic.
+Although somewhat militant, it is definitely worth reading.
+
+*Note*: Please do NOT send your Java problems to the two authors. They welcome feedback on the FAQ's contents, but are
+simply not a Java help resource. Follow the essay's advice and choose your forum carefully.
+
+*Keep your email short and to the point*
+
+If your email is more than about a page of text, chances are that it won't get read by very many people. It is much
+better to try to pack a lot of informative information (see above about asking smart questions) into as small of an
+email as possible. If you are replying to a previous email only quote the parts that you are replying to and to remove
+the unnecessary bits. This makes it easier for people to follow a thread as well as making the email archives easier
+to search and read.
+
+*Do your best to ensure that you are not sending HTML or "Stylelized" email to the list*
+
+If you are using Outlook or Outlook Express or Eudora, chances are that you are sending HTML email by default. There is
+usually a setting that will allow you to send "Plain Text" email. If you are using Microsoft products to send email,
+there are several bugs in the software that prevent you from turning off the sending of HTML email.
+
+*Watch where you are sending email*
+
+The majority of our mailing lists have set the Reply-To to go back to the list. That means that when you Reply to a
+message, it will go to the list and not to the original author directly. The reason is because it helps facilitate
+discussion on the list for everyone to benefit from. Be careful of this as sometimes you may intend to reply to a
+message directly to someone instead of the entire list. The appropriate contents of the Reply-To header is an age-old
+debate that should not be brought up on the mailing lists. You can examine opposing points of view condemning our
+convention and condoning it. Bringing this up for debate on a mailing list will add nothing new and is considered off-topic.
+
+*Do not cross post messages*
+
+In other words, pick one mailing list and send your messages to that mailing list only. Do not send your messages to
+multiple mailing lists. The reason is that people may be subscribed to one list and not to the other. Therefore, some
+people will only see part of the conversation.


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org