serge       02/04/16 14:58:36

  Modified:    src/xdocs FAQ.xml
  Log:
  Added a few more FAQs about the  state of IMAP support and virtual hosting, and then 
some quick tips on classpath issues.
  
  Revision  Changes    Path
  1.7       +27 -4     jakarta-james/src/xdocs/FAQ.xml
  
  Index: FAQ.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-james/src/xdocs/FAQ.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- FAQ.xml   8 Mar 2002 15:21:58 -0000       1.6
  +++ FAQ.xml   16 Apr 2002 21:58:36 -0000      1.7
  @@ -21,6 +21,9 @@
   <li><a href="#3">I can send messages to James, but nobody is receiving them.  What 
do I do?</a></li>
   <li><a href="#4">I can send people messages via James, but nobody can send me 
messages.  What do I do?</a></li>
   <li><a href="#5">I'm trying to debug messages that James is trying to deliver.  
Where should I look?</a></li>
  +<li><a href="#6">What about IMAP support?</a></li>
  +<li><a href="#7">What about support virtual hosting?</a></li>
  +<li><a href="#8">Where do I stick classes and jars?</a><li>
   </ul>
   </p>
   
  @@ -110,12 +113,32 @@
   
     </subsection>
   
  -</section>
  -
  +  <a name="6"></a>
  +  <subsection name="What about IMAP support?">
  +  <p>Unfortunately IMAP support is currently stalled.  There is a proposal in CVS, 
but IMAP is a significantly more complex than other mail protocols, both from a 
protocol command support and in terms of complexity you need on the server.  If you 
are interested in taking the proverbial ball and running with it, we would all very 
much appreciated. (I personally am incredibly frustrated with an old Netscape Mail 
server, but I've sworn myself to upgrade only to James's IMAP once ready as 
incentive.)
  +  <br />Serge Knystautas</p>
   
   
  -</body>
  -</document>
  +  <a name="7"></a>
  +  <subsection name="What about support virtual hosting?">
  +  <p>Virtual hosting is something the developers are still wrestling with.  The 
challenge is that POP3 does not support virtual hosting in that it does not have a 
command to indicate what domain the user is in.  What this means is the mail server 
needs to develop a 'mapping' or 'translation', e.g., '[EMAIL PROTECTED]' gets a 
username 'domaina.user1'.  This allows the mail server to have a single username 
namespace.  We have seen a few good proposals put forward, but nothing that seemed the 
clear solution as ideally we could have this part solve the next issue.</p>
  +  <p>Beyond that, James needs to refine virtual hosting for mailet processing.  The 
mailet API has a Mail.getUser() method that no longer would be useable as a reliable 
indicator of whether they were in the local username namespace.  To date we are 
unclear of the best way to bring this translation into the mailet processing.  
Similarly, it would be nice to support different mailet processing based on the 
domain, although this is somewhat feasible using the limited processing flow offered 
with a HostIs/ForwardTo combination.</p>
  +  <p>This is one of the most requested feature, so hopefully this will be resolved 
soon.
  +  <br />Serge Knystautas</p>
  +  </subsection>
   
  +  <a name="8"></a>
  +  <subsection name="Where do I stick classes and jars?">
  +  <p>We are largely reliant on what Avalon is doing in terms of classloading, but 
here are a few tips and suggestions:
  +  <ul>
  +  <li>Stick jars in the james/lib directory and add them to the classpath in 
run.bat or run.sh.</li>
  +  <li>Custom mailets and matchers must be included in the james.bar (which is just 
a zip like a jar or war file).</li>
  +  </ul>
  +  Eventually we hope to support mailet reloading and a special lib and classes 
directory within the james directory that custom mailets can load from, but for now 
these are hopefully some useful tips.
  +  <br />Serge Knystautas</p>
  +  </subsection>
  +</section>
   
   
  +</body>
  +</document>
  
  
  

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to