JamesQuickstart

DRAFT 000000000000 This was created on June 11, 2003 and is still being confirmed by new users. If this doesn't work for you, please let us know at server-user@james.apache.org.

If you edit this, and please do if you've useful changes, please check the numeric references. For example, the steps related to the DNS servers reference each other to help make sure that users understand what they need to do.

0

This page was written to help new users get started using James as quickly as possible.

1. Download the latest stable 2.x release from http://james.apache.org.

2. Extract the gz or zip file to a local directory.

3. Start <code>bin/run.sh</code> (unix) or <code>bin\run.bat</code> (windows) You will see something like the following:

   Using PHOENIX_HOME:   D:\James\james-2.1.3
   Using PHOENIX_TMPDIR: D:\James\james-2.1.3\temp
   Using JAVA_HOME:      c:\programming\java14
   
   Phoenix 4.0.1
   
   James 2.1.3
   Remote Manager Service started plain:4555
   POP3 Service started plain:110
   SMTP Service started plain:25
   NNTP Service started plain:119
   Fetch POP Disabled 

   On Unix platforms, <code>bin/run.sh</code> runs James in the console. To stop it, hit Ctrl-C. Alternatively you can use <code>bin/phoenix.sh</code>, which gives you sysinit functions such as start, stop, restart, and check.

4. Kill the process (either do kill or ctrl-c or whatever you want). Starting James once was necessary to extract its directory structure and expose the configuration files to edit.

5. Determine the DNS server to use. On Windows, type <code>ipconfig /all</code> and look for the DNS servers. On Unix, look at <code>/etc/resolv.conf</code>. You will need this information in step #9.

6. Determine your local IP address for reference. On Windows, run <code>ipconfig</code> to see your IP Address. On Unix, run <code>/sbin/ifconfig</code> and look for your inet addr.

7. Check the DNS configuration of the domain you want James to handle using http://www.dnsreport.com. If you want to handle email for <code>foobar.com</code>, put that domain name in the DNS Report field. On the report, you will want to check the MX record section to make sure the MX records point to the IP address you determined in the previous step, and that everything else about your domain's MX passes.

8. Edit <code>apps/james/SAR-INF/config.xml</code>. Look over a section called <servernames> and put the domain you want to accept messages for within <servername> elements, e.g.,

   <servernames>
   {{{  <servername> foobar.com </servername> 

</servernames>

• }}} Be sure you do not edit the instructional part of the conf file.

• Continue editing <code>apps/james/SAR-INF/config.xml</code> and look for a section called <dnsserver>. Put the DNS servers (from step #5 above) there, e.g.,:

  <dnsserver>
  {{{  <servers> 
      <server> 10.0.0.15 </server> 
      <server> 10.0.0.22 </server> 
    </servers> 
    <authoritative> false </authoritative> 

</dnsserver>

• }}}

• Start James again using <code>bin/run.sh</code> or <code>bin\run.bat</code>

TOWRITE: How to test James is working for you. (use an external mail account to send a message to and from. need to create a local account too, maybe add a local IP address to use as the sender).

TOWRITE: Discuss possible errors...

1. dynamic IP address issues
2. ISP blocking outgoing port 25
3. Email address with IP address instead of a domain name (possible workarounds)
4. Messages going to spam because of sender's IP address (James catching as relay)
5. Messages not getting accepted because your IP address/server is considered a relay.
6. Another server already running preventing ports from binding.

suna