Javier & Michael,

>
> >
> > I think it unpacks the files again.
>
>It shouldn't....
>
>What is happening that seems to indicate this?
>
> > Is there another file I should run or any other thing I have to
> > configure ??
>
>I don't think so, under $JAMES_HOME/apps/ you should now have a directory
>james/
>and now James should be running just fine. Anything else you want to
>configure should be in conf/config.xml.
>

It doesn't unpack the files the second time round.

> > What DNS should I put in DNS, the DNS of my computer or the internal
> > server DNS ????
>
>The conf/config.xml file seems to indicate that you can use either.
>Looking
>at the source code for org.apache.james.dnsserver.DNSServer, the DNSServer
>relies on stuff in the org.xbill.DNS package, and it looks like it
>operates
>like any DNS server would.
>
>I'm guessing you're staring at these two pieces of XML:
>
><!-- CONFIRM? -->
>       <!-- servernames identifies the DNS namespace served by this
>instance
>       of James.
>       If autodetect is TRUE, James wil attempt to discover its own name
>AND use
>       any specified servernames.  If autodetect is FALSE, James will use
>only
>       the specified servernames.  By default, the servername 'localhost'
>is
>       specified. This can be removed, if required. -->
>       <servernames autodetect="TRUE">
>         <!--
>         <servername>To override autodetected server names
>                     uncomment this.  </servername>-->
>         <servername>localhost</servername>
>       </servernames>
>
>...
>...
>
><!-- CONFIRM? Enter ip address of your DNS server, one per element -->
>   <dnsserver>
>         <servers>
>           <server>127.0.0.1</server>
>           <!--<server> put extra dns server address here </server>-->
>         </servers>
>         <authoritative>false</authoritative>
>   </dnsserver>
>
>
>I'm not entirely sure, but it seems like you can leave the defaults or use
>the DNS IP's of your ISP.

Your choice. If you leave the defaults as they are i.e. leave the 127.0.0.1 
and servername as localhost as part of your DNS settings, then you're 
restricted to sending and receiving mails locally from within the same host 
where James is installed.

If you want to extend it, and make your host recognisable from outside your 
domain, then you should place the FQDN of your isp's DNS servers so that 
your ip/domain is recognised on the public domain. You must remember that 
the setting is not restricted to ip, you can specify the domain names of 
your isp DNS servers as well which is the de facto behaviour of a DNS as 
well as ip. Next, if you want someone from outside to send mail to your 
James mail server, then you need to setup a set of MX records for your host. 
See www.dyndns.org for more info.

Hope this helps,

Sam.

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


_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com


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

Reply via email to