You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by Serge Knystautas <se...@lokitech.com> on 2003/06/12 19:09:39 UTC

Apache Wiki: JamesQuickstart

I don't think James has a very detailed quickstart guide, so I started 
to put together one (if we already have one I wasn't aware, then so much 
for my lunch break).

<http://nagoya.apache.org/wiki/apachewiki.cgi?JamesQuickstart>

If anybody has the time/interest to help complete this, catch my typos 
and huge gaps, that'd be great!  Like Noel said, I think James is one of 
the easiest mail servers to start, but this can hopefully help.

When this is a bit more complete and certain, we can link it from the 
home page and eventually turn this into an xdoc to include with the 
distribution.

-- 
Serge Knystautas
President
Lokitech >> software . strategy . design >> http://www.lokitech.com
p. 301.656.5501
e. sergek@lokitech.com


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


Re: Apache Wiki: JamesQuickstart

Posted by Serge Knystautas <se...@lokitech.com>.
Serge Knystautas wrote:
> I don't think James has a very detailed quickstart guide, so I started 
> to put together one (if we already have one I wasn't aware, then so much 
> for my lunch break).

Also just to clarify/differentiate, Claude's article on IBM really is 
great to introduce Java developers to James, while I'm hoping this 
quickstart guide will do the same for systems people.  I wanted to 
mention this since you can see bits in the guide were borrowed from his 
article.

I expect this guide would avoid any discussion of mailets or the 
development capabilities in James and just focus on how this could give 
you a mail server very easily.

-- 
Serge Knystautas
President
Lokitech >> software . strategy . design >> http://www.lokitech.com
p. 301.656.5501
e. sergek@lokitech.com


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


Re: Apache Wiki: JamesQuickstart

Posted by bill parducci <bi...@parducci.net>.
> Ok, I can tell them to check that locally this resolution matches. 
> Usually the problem seemed to be the outside world not having problems, 
> but I would like to catch as many of these as possible.
> 
> I guess if you have NAT-issues you could have problems because that 
> external result won't match your local IP address.

...that and if you have a forwarding MX configuration the 'world' often 
sees the forwarder(s) as the MX and the forwarders see the internal 
mailserver as the MX for the *same* domain.

b




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


Re: Apache Wiki: JamesQuickstart

Posted by Serge Knystautas <se...@lokitech.com>.
bill parducci wrote:
> for starters, i would suggest a '2b' for *IX users:
> 
> 2b. (IX users) Make run.sh and phoenix.sh executable (`chmod +x ruh.sh 
> phoneix.sh`)

Doh!  Can't we fix this in our build script so these are executable?

> also -- this may be kind of beyond 'quick starting' --, but for those 
> users trying to setup forwarding MXs, etc. you may want to expand #7 to 
> include MX record evaluation from a 'local' perspective. for example, on 
> an *IX box  `host -t mx foo.bar` (`nslookup -q=mx foo.bar` on NT) will 
> list all the MXs for the domain in question *as seen by that box*. it 
> may sound esoteric, but i have seen a number of problems float by the 
> list because of DNS assumptions (it is not uncommon for a mailserver to 
> be have multiple identities).

Ok, I can tell them to check that locally this resolution matches. 
Usually the problem seemed to be the outside world not having problems, 
but I would like to catch as many of these as possible.

I guess if you have NAT-issues you could have problems because that 
external result won't match your local IP address.

-- 
Serge Knystautas
President
Lokitech >> software . strategy . design >> http://www.lokitech.com
p. 301.656.5501
e. sergek@lokitech.com


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


RE: Apache Wiki: JamesQuickstart

Posted by "Noel J. Bergman" <no...@devtech.com>.
> 2b. (IX users) Make run.sh and phoenix.sh executable
>     (`chmod +x ruh.sh phoenix.sh`)

We need to add a file set with an explicit mode attribute.  Feel free to
submit a patch to build.xml.

See: http://ant.apache.org/manual/CoreTasks/tar.html

	--- Noel


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


Re: Apache Wiki: JamesQuickstart

Posted by bill parducci <bi...@parducci.net>.
for starters, i would suggest a '2b' for *IX users:

/*
2.  Extra the gz or zip file to a local directory.
2b. (IX users) Make run.sh and phoenix.sh executable (`chmod +x ruh.sh 
phoneix.sh`)
3. Start bin/run.sh (unix) or bin\run.bat (windows) You will see 
something like the following:
*/

also -- this may be kind of beyond 'quick starting' --, but for those 
users trying to setup forwarding MXs, etc. you may want to expand #7 to 
include MX record evaluation from a 'local' perspective. for example, on 
an *IX box  `host -t mx foo.bar` (`nslookup -q=mx foo.bar` on NT) will 
list all the MXs for the domain in question *as seen by that box*. it 
may sound esoteric, but i have seen a number of problems float by the 
list because of DNS assumptions (it is not uncommon for a mailserver to 
be have multiple identities).

b




Serge Knystautas wrote:
> I don't think James has a very detailed quickstart guide, so I started 
> to put together one (if we already have one I wasn't aware, then so much 
> for my lunch break).
> 
> <http://nagoya.apache.org/wiki/apachewiki.cgi?JamesQuickstart>
> 
> If anybody has the time/interest to help complete this, catch my typos 
> and huge gaps, that'd be great!  Like Noel said, I think James is one of 
> the easiest mail servers to start, but this can hopefully help.
> 
> When this is a bit more complete and certain, we can link it from the 
> home page and eventually turn this into an xdoc to include with the 
> distribution.
> 



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


RE: Apache Wiki: JamesQuickstart

Posted by Erik Beijnoff <er...@beijnoff.com>.
> I don't think James has a very detailed quickstart guide, so 
> I started 
> to put together one (if we already have one I wasn't aware, 
> then so much 
> for my lunch break).
> 
<http://nagoya.apache.org/wiki/apachewiki.cgi?JamesQuickstart>


Thanks! That helped me out a lot. Just getting started with James. Fine
piece of work.

/Erik Beijnoff



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