<?xml version="1.0" encoding="UTF-8"?>
<!--
  Licensed to the Apache Software Foundation (ASF) under one
  or more contributor license agreements.  See the NOTICE file
  distributed with this work for additional information
  regarding copyright ownership.  The ASF licenses this file
  to you under the Apache License, Version 2.0 (the
  "License"); you may not use this file except in compliance
  with the License.  You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

  Unless required by applicable law or agreed to in writing,
  software distributed under the License is distributed on an
  "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
  KIND, either express or implied.  See the License for the
  specific language governing permissions and limitations
  under the License.    
-->
<document>

  <properties>
    <title>Mailing lists</title>
    <author email="site-dev@james.apache.org">James Project Web Team</author>
  </properties>

  <body>

    <section name="James Mailing lists">
      <p>
        <i>Please read the <a href="#Guidelines">guidelines</a> below</i> before subscribing to our lists and join our 
community.</p>
      <subsection name="Server User List">
        <p>
          <b>Low Traffic</b>&#160;
          <a href="mailto:server-user-subscribe@james.apache.org">Subscribe</a>
          <a href="mailto:server-user-unsubscribe@james.apache.org">Unsubscribe</a>
          <a href="http://www.mail-archive.com/server-user@james.apache.org/">Archive</a>
        </p>
        <p> 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). </p>
      </subsection>
      <subsection name="Server Developer List">
        <p>
          <b>High Traffic</b>&#160;
          <a href="mailto:server-dev-subscribe@james.apache.org">Subscribe</a>
          <a href="mailto:server-dev-unsubscribe@james.apache.org">Unsubscribe</a>
          <a href="http://www.mail-archive.com/server-dev@james.apache.org/">Archive</a>
        </p>
        <p> This is the list where participating developers of 
the 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. <b>Do not send 
mail to this list with usage questions or configuration problems</b> -- 
that's what server-user@james is for. </p>
      </subsection>
      <subsection name="Mime4j">
        <p>
          <b>Medium Traffic</b>&#160;
          <a href="mailto:mime4j-dev-subscribe@james.apache.org">Subscribe</a>
          <a href="mailto:mime4j-dev-unsubscribe@james.apache.org">Unsubscribe</a>
          <a href="http://mail-archives.apache.org/mod_mbox/james-mime4j-dev">Archive</a>
        </p>
        <p>Discussions on the <a href='http://james.apache.org/mime4j'>Mime4j</a> 
        parser library.</p>
      </subsection>
      <subsection name="Site Developer List">
        <p>
          <b>Very Low Traffic</b>&#160;
          <a href="mailto:site-dev-subscribe@james.apache.org">Subscribe</a>
          <a href="mailto:site-dev-unsubscribe@james.apache.org">Unsubscribe</a>
          <a href="http://www.mail-archive.com/site-dev@james.apache.org/">Archive</a>
        </p>
        <p> This is the list where participating developers of 
the the Apache James project discuss changes/additions to the James 
websites etc. Subscribers to this list get notifications of every commit 
of the website reaources<b>Do not send mail to this list with James 
software problems</b> -- that's what server-user@james is for. </p>
      </subsection>
      <subsection name="James General List">
        <p>
          <b>Low Traffic</b>&#160;
          <a href="mailto:general-subscribe@james.apache.org">Subscribe</a>
          <a href="mailto:general-unsubscribe@james.apache.org">Unsubscribe</a>
          <!-- <a 
href="http://www.mail-archive.com/general@james.apache.org/"> 
Archive</a> -->
        </p>
        <p> This is the list for general discussions 
relating to the running of the project, it is the public list of the 
James project management committee (PMC) and is a public list open to 
all. <b>Do not send mail to this list with James software problems</b> 
-- that's what server-user@james is for. </p>
      </subsection>
      <subsection name="Mailet API List">
        <p>
          <b>Very Low Traffic</b>&#160;
          <a href="mailto:mailet-api-subscribe@james.apache.org">Subscribe</a>
          <a href="mailto:mailet-api-unsubscribe@james.apache.org">Unsubscribe</a>
        </p>
        <p> This is the public list for the Mailet API subproject, discussing all <a href="http://james.apache.org/mailet/index.html">Mailet API</a> design and implementation related topics. Questions about using Mailets and their configuration should be addressed to the server-user list.</p>
      </subsection>
    </section>
	
    <section name="How to unsubscribe your old email address">
        <p>
        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".
        </p>
        <pre>
        Microsoft Mail Internet Headers Version 2.0
        ...
        List-Unsubscribe: &lt;mailto:server-user-unsubscribe@james.apache.org&gt;
        List-Help: &lt;mailto:server-user-help@james.apache.org&gt;
        List-Post: &lt;mailto:server-user@james.apache.org&gt;
        List-Id: "James Server Users List" &lt;server-user.james.apache.org&gt;
        Reply-To: "James Server Users List" &lt;server-user@james.apache.org&gt;
        Delivered-To: mailing list server-user@james.apache.org
        ...
        Return-Path: server-user-return-12345-<i>john=host.domain</i>@james.apache.org
        ...
        </pre>
        <p>
        The <i>Return-Path</i> header contains the email address which is subscribed. 
        </p>      
        <p>To stop subscription for the address john@host.domain , send an email to <pre>server-dev-unsubscribe-john=host.domain@james.apache.org</pre>
          or to  <pre>server-user-unsubscribe-john=host.domain@james.apache.org</pre>.
        </p>  
    </section>

    <section name="Archives">
      <p> There are several sites on the net that archive and 
provide searching for our mailing lists in HTML readable format.
</p>
      <p>
        <ul>
          <li>Archives with many Jakarta lists: <ul>
              <li>
                <a href="http://mail-archives.apache.org/mod_mbox/#james">List 
Index on mail-archives.apache.org</a>
              </li>
              <li>
                <a href="/mail/">Full mbox archives of all lists.</a>
              </li>
              <li>
                <a href="http://www.mail-archive.com/">Mail-Archive</a>
              </li>
              <li>
                <a href="http://geocrawler.com/">Geocrawler</a>
              </li>
              <li>
                <a href="http://marc.theaimsgroup.com/">Mailing list Archives</a>
              </li>
              <li>
                <a href="http://www.servlets.com/archive/">Servlets.com 
servlet and JSP list archives</a>
              </li>
            </ul>
          </li>
        </ul>
      </p>
    </section>
    
    <section name="Guidelines">
      <p>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 broadcast to everyone who is 
subscribed to that mailing list. Mailing lists provide a simple and 
effective communication mechanism for discussion and decision making. 
</p>
      <p> The Apache Software Foundation has well established reasons for 
using email and not other types of forum. <br/> We are 
<strong>not</strong> interested in hearing proposals to use NNTP (news 
groups) or web forums or any other medium.<br/> You may use a mail-news 
gateway, gmail or anything else you like but email is, and will remain, 
the official medium. </p>
      <p> With potentially thousands of subscribers, 
there is a common etiquette that you should observe. Please keep on 
reading. </p>
      <p>
        <strong> Respect the mailing list type </strong>
      </p>
      <p>
        <ul>
          <li> "User" lists are lists where you can send questions 
and comments about configuration, setup, usage and other "user" types of 
questions. </li>
          <li> "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. </li>
        </ul>
      </p>
      <p>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.</p>
      <p>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.</p>
      <p>
        <strong> Join the lists that are appropriate for 
your discussion. </strong>
        <br/> Please make sure that you are joining 
the list that is appropriate 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". </p>
      <p>
        <strong> Ask smart questions. </strong>
        <br/> 

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 <a href="http://www.catb.org/~esr/faqs/smart-questions.html">"<b>Asking 
Smart Questions</b>"</a> precisely on this topic. Although somewhat 
militant, it is definitely worth reading.<br/>
        <b>Note</b>: 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 <a href="http://www.catb.org/~esr/faqs/smart-questions.html#forum">choose 
your forum</a> carefully. </p>
      <p>
        <strong> Keep your email short and to the point. </strong>
        <br/> 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. </p>
      <p>
        <strong> Do your best to ensure that you are 
not sending HTML or "Stylelized" email to the list. </strong>
        <br/> 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.</p>
      <p>
        <strong> Watch where you are sending email. </strong>
        <br/> 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. <em> 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 <a href="http://www.unicom.com/pw/reply-to-harmful.html">condemning</a> our 
convention and <a href="http://www.metasystema.org/essays/reply-to-useful.mhtml"> 
condoning</a> it. Bringing this up for debate on a mailing list will add 
nothing new and is considered off-topic. </em>
      </p>
      <p>
        <strong> Do not cross post messages. </strong>
        <br/> 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. </p>
</section>

  </body>

</document>
