Author: eric
Date: Sun Nov 7 08:21:20 2010
New Revision: 1032226
URL: http://svn.apache.org/viewvc?rev=1032226&view=rev
Log:
Replace config.xml with correct xml file.
Modified:
james/server/trunk/src/site/xdoc/config-dns.xml
james/server/trunk/src/site/xdoc/config-fetchmail.xml
james/server/trunk/src/site/xdoc/config-listmanager.xml
james/server/trunk/src/site/xdoc/config-mailetcontainer.xml
james/server/trunk/src/site/xdoc/config-mailstores.xml
james/server/trunk/src/site/xdoc/config-pop3.xml
james/server/trunk/src/site/xdoc/config-remotemanager.xml
james/server/trunk/src/site/xdoc/config-smtp-lmtp.xml
james/server/trunk/src/site/xdoc/dev-extend-custom-mailet.xml
james/server/trunk/src/site/xdoc/dev-provided-mailets.xml
james/server/trunk/src/site/xdoc/manage-domains.xml
james/server/trunk/src/site/xdoc/manage-users.xml
james/server/trunk/src/site/xdoc/manage-virtualusers.xml
Modified: james/server/trunk/src/site/xdoc/config-dns.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/config-dns.xml?rev=1032226&r1=1032225&r2=1032226&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-dns.xml (original)
+++ james/server/trunk/src/site/xdoc/config-dns.xml Sun Nov 7 08:21:20 2010
@@ -28,7 +28,7 @@
<section name="DNS Configuration">
<p>DNS Transport services are controlled by a configuration block in
- the config.xml. This block affects SMTP remote delivery.</p>
+ the dnsservice.xml. This block affects SMTP remote delivery.</p>
<p>The dnsserver tag defines the boundaries of the configuration
block. It encloses all the relevant configuration for the DNS server.
Modified: james/server/trunk/src/site/xdoc/config-fetchmail.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/config-fetchmail.xml?rev=1032226&r1=1032225&r2=1032226&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-fetchmail.xml (original)
+++ james/server/trunk/src/site/xdoc/config-fetchmail.xml Sun Nov 7 08:21:20
2010
@@ -95,10 +95,10 @@
<section name="Fetchmail Configuration Parameters">
<p>The Fetchmail configuration parameters are part of the James
configuration,
- whose base file is <code>config.xml</code>. For clarity and flexibility,
the
+ whose base file is <code>fetchmail.xml</code>. For clarity and
flexibility, the
Fetchmail configuration parameters are stored in the file
<code>james-Fetchmail.xml</code>, which is referenced within
- <code>config.xml</code>.</p>
+ <code>fetchmail.xml</code>.</p>
<p>The configuration parameters are described below.</p>
Modified: james/server/trunk/src/site/xdoc/config-listmanager.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/config-listmanager.xml?rev=1032226&r1=1032225&r2=1032226&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-listmanager.xml (original)
+++ james/server/trunk/src/site/xdoc/config-listmanager.xml Sun Nov 7 08:21:20
2010
@@ -83,7 +83,7 @@
the subscriber list. There is a separate repository for each mailing
list, and is completely independent of the user repository used by
James to manage e-mail accounts. This is configured in the
- <users-store> block of config.xml.</p>
+ <users-store> block of james-listmanager.xml.</p>
<p>The following illustrates a database-backed repository using JDBC
with the ListUsersJdbcRepository class. Notice that there will be a
Modified: james/server/trunk/src/site/xdoc/config-mailetcontainer.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/config-mailetcontainer.xml?rev=1032226&r1=1032225&r2=1032226&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-mailetcontainer.xml (original)
+++ james/server/trunk/src/site/xdoc/config-mailetcontainer.xml Sun Nov 7
08:21:20 2010
@@ -25,81 +25,92 @@
<body>
-<section name="Mailet Container Configuration">
+ <section name="Mailet Container Configuration">
+
+ <p>The SpoolManager is controlled by a single configuration block in the
mailetcontainer.xml.
+ The spoolmanager tag defines the boundaries of the configuration block.
The behavior of
+ the SpoolManager, most importantly the routing of mail messages through
the processor tree,
+ is controlled by this block.</p>
+
+ <p>The spoolmanager tag has only one children. It is:</p>
+ <ul>
+ <li><strong>threads</strong> - This is a required positive integer
element. It specifies
+ the number of threads the SpoolManager will use to process messages in the
spool. This
+ parameter tends to substantially impact performance, so it is advisable to
tune it in production
+ configurations.</li>
+ </ul>
+
+ <p>Spoolmanager depends on mailet and matcher packages, configured by
these tags:</p>
+ <ul>
+ <li><strong>mailetpackages</strong> - This is a required container tag.
It contains some number
+ of <strong>mailetpackage</strong> children. The body of each of these
<strong>mailetpackage</strong>
+ elements is a Java package name. It is these packages that contain the
classes to be instantiated
+ as mailets.</li>
+ <li><strong>matcherpackages</strong> - This is a required container tag.
It contains some number
+ of <strong>matcherpackage</strong> children. The body of each of these
<strong>matcherpackage</strong>
+ elements is a Java package name. It is these packages that contain the
classes to be instantiated
+ as matchers.</li>
+ </ul>
+
+ <p>The remaining SpoolManager configuration elements are complex enough to
require a more in-depth
+ discussion.</p>
+
+ <subsection name="Processor Configuration">
+
+ <p>In addition to the child elements discussed above, the SpoolManager
tag can have several
+ <strong>processor</strong> children. It is these tags and their
children that define the processor tree
+ for the SpoolManager.</p>
+
+ <p>Each processor has a required attribute, <strong>name</strong>. The
value of this attribute must be
+ unique for each processor tag. The name of a processor is significant.
Certain processors are required
+ (specifically root and error). The name "ghost" is forbidden as a
processor name, as it is used to denote
+ a message that should not undergo any further processing.</p>
+
+ <p>The James SpoolManager creates a correspondance between processor
names and the "state" of a mail as defined
+ in the Mailet API. Specifically, after each mailet processes a mail,
the state of the message is examined. If
+ the state has been changed, the message does not continue in the current
processor. If the new state is "ghost"
+ then processing of that message terminates completely. If the new state
is anything else, the message is
+ re-routed to the processor with the name matching the new state.</p>
+ <p>The root processor is a required processor. All new messages that
the SpoolManager finds on the spool are
+ directed to this processor.</p>
+
+ <p>The error processor is another required processor. Under certain
circumstances James itself will redirect messages
+ to the error processor. It is also the standard processor to which
mailets redirect messages when an error
+ condition is encountered.</p>
+
+ <p>The transport and spam processors are two useful, but optional,
processors that are included in the out of
+ the box configuration. These processors include logic for actual mail
delivery and spam handling respectively. More
+ information on these processors can be found in the default
mailetcontainer.xml.</p>
+ <p>Each processor element has zero or more <strong>mailet</strong> child
elements. Each of these elements describes a
+ matcher/mailet pair. The ordering of the <strong>mailet</strong>
children is crucial to the configuration, as
+ it is the order in which pairs will be traversed in the processor.</p>
+ <p>It is this <strong>mailet</strong> element that is at the core of the
SpoolManager configuration.</p>
+
+ </subsection>
+
+ <subsection name="The Mailet Tag">
+
+ <p>Consider the following simple <strong>mailet</strong> tag:</p>
+ <mailet match="RemoteAddrNotInNetwork=127.0.0.1"
class="ToProcessor"><br/>
+ <processor>spam</processor><br/>
+ </mailet><br/>
+ <p>The mailet tag has two required attributes, <strong>match</strong>
and <strong>class</strong>.</p>
+ <p>The <strong>match</strong> attribute is set to the value of the
specific Matcher class to be instantiated with a an
+ optional argument. If present, the argument is separated from the
Matcher class name by an '='. Semantic
+ interpretation of the argument is left to the particular mailet.</p>
+ <p>The <strong>class</strong> attribute is set to the value of the
Mailet class that is to be instantiated.</p>
+ <p>Finally, the children of the <strong>mailet</strong> tag define the
configuration that is passed to the Mailet. The
+ tags used in this section should have no attributes or children. The
names and bodies of the elements will be passed to
+ the mailet as (name, value) pairs.</p>
+ <p>So in the example above, a Matcher instance of RemoteAddrNotInNetwork
would be instantiated, and the value "127.0.0.1"
+ would be passed to the matcher. The Mailet of the pair will be an
instance of ToProcessor, and it will be passed the (name, value)
+ pair of ("processor", "spam").</p>
+ <p>James includes a number of pre-packaged Mailets and Matchers. A list
of provided Mailets may be found
+ <a href="provided-mailets.html">here</a>. A list of provided Matchers
may be found <a href="provided-matchers.html">here</a>.</p>
+
+ </subsection>
+
+ </section>
-<p>The SpoolManager is controlled by a single configuration block in the
config.xml.
-The spoolmanager tag defines the boundaries of the configuration block. The
behavior of
-the SpoolManager, most importantly the routing of mail messages through the
processor tree,
-is controlled by this block.</p>
-
-<p>The spoolmanager tag has only one children. It is:</p>
-<ul>
-<li><strong>threads</strong> - This is a required positive integer element.
It specifies
-the number of threads the SpoolManager will use to process messages in the
spool. This
-parameter tends to substantially impact performance, so it is advisable to
tune it in production
-configurations.</li>
-</ul>
-
-<p>Spoolmanager depends on mailet and matcher packages, configured by these
tags:</p>
-<ul>
-<li><strong>mailetpackages</strong> - This is a required container tag. It
contains some number
-of <strong>mailetpackage</strong> children. The body of each of these
<strong>mailetpackage</strong>
-elements is a Java package name. It is these packages that contain the
classes to be instantiated
-as mailets.</li>
-<li><strong>matcherpackages</strong> - This is a required container tag. It
contains some number
-of <strong>matcherpackage</strong> children. The body of each of these
<strong>matcherpackage</strong>
-elements is a Java package name. It is these packages that contain the
classes to be instantiated
-as matchers.</li>
-</ul>
-
-<p>The remaining SpoolManager configuration elements are complex enough to
require a more in-depth
-discussion.</p>
-
-<subsection name="Processor Configuration">
-<p>In addition to the child elements discussed above, the SpoolManager tag can
have several
-<strong>processor</strong> children. It is these tags and their children that
define the processor tree
-for the SpoolManager.</p>
-<p>Each processor has a required attribute, <strong>name</strong>. The value
of this attribute must be
-unique for each processor tag. The name of a processor is significant.
Certain processors are required
-(specifically root and error). The name "ghost" is forbidden as a processor
name, as it is used to denote
-a message that should not undergo any further processing.</p>
-<p>The James SpoolManager creates a correspondance between processor names and
the "state" of a mail as defined
-in the Mailet API. Specifically, after each mailet processes a mail, the
state of the message is examined. If
-the state has been changed, the message does not continue in the current
processor. If the new state is "ghost"
-then processing of that message terminates completely. If the new state is
anything else, the message is
-re-routed to the processor with the name matching the new state.</p>
-<p>The root processor is a required processor. All new messages that the
SpoolManager finds on the spool are
-directed to this processor.</p>
-<p>The error processor is another required processor. Under certain
circumstances James itself will redirect messages
-to the error processor. It is also the standard processor to which mailets
redirect messages when an error
-condition is encountered.</p>
-<p>The transport and spam processors are two useful, but optional, processors
that are included in the out of
-the box configuration. These processors include logic for actual mail
delivery and spam handling respectively. More
-information on these processors can be found in the default config.xml.</p>
-<p>Each processor element has zero or more <strong>mailet</strong> child
elements. Each of these elements describes a
-matcher/mailet pair. The ordering of the <strong>mailet</strong> children is
crucial to the configuration, as
-it is the order in which pairs will be traversed in the processor.</p>
-<p>It is this <strong>mailet</strong> element that is at the core of the
SpoolManager configuration.</p>
-</subsection>
-<subsection name="The Mailet Tag">
-<p>Consider the following simple <strong>mailet</strong> tag:</p>
-<mailet match="RemoteAddrNotInNetwork=127.0.0.1"
class="ToProcessor"><br/>
-<processor>spam</processor><br/>
-</mailet><br/>
-<p>The mailet tag has two required attributes, <strong>match</strong> and
<strong>class</strong>.</p>
-<p>The <strong>match</strong> attribute is set to the value of the specific
Matcher class to be instantiated with a an
-optional argument. If present, the argument is separated from the Matcher
class name by an '='. Semantic
-interpretation of the argument is left to the particular mailet.</p>
-<p>The <strong>class</strong> attribute is set to the value of the Mailet
class that is to be instantiated.</p>
-<p>Finally, the children of the <strong>mailet</strong> tag define the
configuration that is passed to the Mailet. The
-tags used in this section should have no attributes or children. The names
and bodies of the elements will be passed to
-the mailet as (name, value) pairs.</p>
-<p>So in the example above, a Matcher instance of RemoteAddrNotInNetwork would
be instantiated, and the value "127.0.0.1"
-would be passed to the matcher. The Mailet of the pair will be an instance of
ToProcessor, and it will be passed the (name, value)
-pair of ("processor", "spam").</p>
-<p>James includes a number of pre-packaged Mailets and Matchers. A list of
provided Mailets may be found
-<a href="provided-mailets.html">here</a>. A list of provided Matchers may be
found <a href="provided-matchers.html">here</a>.</p>
-</subsection>
-</section>
</body>
</document>
Modified: james/server/trunk/src/site/xdoc/config-mailstores.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/config-mailstores.xml?rev=1032226&r1=1032225&r2=1032226&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-mailstores.xml (original)
+++ james/server/trunk/src/site/xdoc/config-mailstores.xml Sun Nov 7 08:21:20
2010
@@ -56,13 +56,13 @@
jar/zip files for the JDBC driver in the lib subdirectory of the James
installation directory. Any additional
libraries upon which the JDBC library depends that are not part of the
standard Java distribution should also be
added to this directory.</p>
- <p>Second, the config.xml must be modified so that Phoenix initializes
the database connections. The relevant
+ <p>Second, the mailstore.xml must be modified so that Phoenix
initializes the database connections. The relevant
configuration is in the database-connections block. The
database-connections tag has only a single child tag,
data-sources. This latter tag is a simple container tag for a number of
child elements. It is these child
elements, <strong>data-source</strong> elements, that define the
database connections.</p>
<p>Each <strong>data-source</strong> tag has a required attribute,
<strong>name</strong>. This value
must be unique to each <strong>data-source</strong> element. It is this
<strong>name</strong> that will
- be used to specify the database connection in other parts of the
config.xml file.</p>
+ be used to specify the database connection in other parts of the
mailstore.xml file.</p>
<p>The <strong>data-source</strong> element has five children, all of
whom are required.
<ul>
<li><strong>driver</strong> - The class name of the database driver to
be used.</li>
@@ -72,7 +72,7 @@
<li><strong>max</strong> - The maximum number of JDBC connections to be
used concurrently by this data-source.</li>
</ul>
</p>
- <p>Generally, you simply configure these entries in the config.xml
+ <p>Generally, you simply configure these entries in the mailstore.xml
file, which are commented, in order to use a database with James. You
would then use the db: or dbfile: prefix instead of the file: prefix
for a particular repository. You are currently free to mix and match
@@ -102,7 +102,7 @@
<subsection name="Sample James Configuration">
- <p>The config.xml file has commented out examples for MySQL and
+ <p>The mailstore.xml file has commented out examples for MySQL and
MSSQL data sources, and for each of the standard repositories. For
example, to use MySQL, you would uncomment and adjust the following
data-source element.</p>
@@ -123,7 +123,7 @@
</data-source>
</source>
- <p>Once the data-source element has been created, it can be referenced
elsewhere in the config.xml
+ <p>Once the data-source element has been created, it can be referenced
elsewhere in the mailstore.xml
file. For example, the following element tells James to use the maildb
data-source and dbfile
storage mechanism for the message spool:</p>
Modified: james/server/trunk/src/site/xdoc/config-pop3.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/config-pop3.xml?rev=1032226&r1=1032225&r2=1032226&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-pop3.xml (original)
+++ james/server/trunk/src/site/xdoc/config-pop3.xml Sun Nov 7 08:21:20 2010
@@ -25,7 +25,7 @@
<body>
<section name="POP3 Configuration">
-<p>The POP3 service is controlled by a configuration block in the config.xml.
+<p>The POP3 service is controlled by a configuration block in the
pop3server.xml.
The pop3server tag defines the boundaries of the configuration block. It
encloses
all the relevant configuration for the POP3 server. The behavior of the POP
service is
controlled by the attributes and children of this tag.</p>
Modified: james/server/trunk/src/site/xdoc/config-remotemanager.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/config-remotemanager.xml?rev=1032226&r1=1032225&r2=1032226&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-remotemanager.xml (original)
+++ james/server/trunk/src/site/xdoc/config-remotemanager.xml Sun Nov 7
08:21:20 2010
@@ -26,7 +26,7 @@
<body>
<section name="RemoteManager Configuration">
- <p>The RemoteManager is controlled by a configuration block in the
config.xml.
+ <p>The RemoteManager is controlled by a configuration block in the
remotemanager.xml.
The remotemanager tag defines the boundaries of the configuration block.
It encloses
all the relevant configuration for the RemoteManager. The behavior of the
RemoteManager is
controlled by the attributes and children of this tag.</p>
Modified: james/server/trunk/src/site/xdoc/config-smtp-lmtp.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/config-smtp-lmtp.xml?rev=1032226&r1=1032225&r2=1032226&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-smtp-lmtp.xml (original)
+++ james/server/trunk/src/site/xdoc/config-smtp-lmtp.xml Sun Nov 7 08:21:20
2010
@@ -27,7 +27,7 @@
<section name="SMTP Configuration">
- <p>The SMTP service is controlled by a configuration block in the
config.xml.
+ <p>The SMTP service is controlled by a configuration block in the
smptserver.xml.
The smtpserver tag defines the boundaries of the configuration block. It
encloses
all the relevant configuration for the SMTP server. The behavior of the
SMTP service is
controlled by the attributes and children of this tag.</p>
@@ -102,7 +102,7 @@
<subsection name="Configuring James for Authenticated SMTP">
<p>Configuring James for Authentication SMTP is a multi-step process.
It requires several adjustments of
- the config.xml. To enable SMTP AUTH, do the following:</p>
+ the smtpserver.xml. To enable SMTP AUTH, do the following:</p>
<p>First, as mentioned above, SMTP AUTH requires that James be able to
distinguish between mail intended
for local delivery and mail intended for remote delivery. James makes
this determination by matching the
domain to which the mail was sent against the <servernames>
element of the James configuration block. Any
Modified: james/server/trunk/src/site/xdoc/dev-extend-custom-mailet.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/dev-extend-custom-mailet.xml?rev=1032226&r1=1032225&r2=1032226&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/dev-extend-custom-mailet.xml (original)
+++ james/server/trunk/src/site/xdoc/dev-extend-custom-mailet.xml Sun Nov 7
08:21:20 2010
@@ -118,7 +118,7 @@ or
/path/to/james/conf/lib/ subdirectory.
</p>
<p>
-2. After this is done get sure you add the mailet package to the config.xml.
For example:
+2. After this is done get sure you add the mailet package to the
mailetcontainer.xml. For example:
<p>
<source>
<!-- Set the Java packages from which to load mailets and matchers -->
Modified: james/server/trunk/src/site/xdoc/dev-provided-mailets.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/dev-provided-mailets.xml?rev=1032226&r1=1032225&r2=1032226&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/dev-provided-mailets.xml (original)
+++ james/server/trunk/src/site/xdoc/dev-provided-mailets.xml Sun Nov 7
08:21:20 2010
@@ -97,7 +97,7 @@ for this list.</li>
<li><strong>repositoryPath</strong> (required) - The repositoryPath which is
used.</li>
<li><strong>headerName</strong> - The HeaderName which get adds to holds the
Probalitity. Default is <i>X-MessageIsSpamProbability</i>.</li>
<li><strong>ignoreLocalSender</strong> - Set to true if you want to ignore
messages from local senders. By local sender we mean a return-path
-with a local server part (server listed in <servernames> in config.xml).
Default is <i>false</i>.</li>
+with a local server part (server listed in <servernames> in
mailetcontainer.xml). Default is <i>false</i>.</li>
<li><strong>maxSize</strong> - Set this to the maximum message size (in bytes)
after analysis will be skipped. Default is <i>100000</i>.</li>
</ul>
</p>
@@ -278,7 +278,7 @@ Default <i>false</i>.</li>
<ul>
<li><strong>mappings</strong> (required) - a URL of the form
db://<data-source>/<table>, where
<table> is the table in the database containing the alias info and
<data-source> is the name
-of the data-source in config.xml that is to be used.</li>
+of the data-source in mailetcontainer.xml that is to be used.</li>
<li><strong>source-column</strong> (required) - the column containing the
aliases.</li>
<li><strong>target-column</strong> (required) - the column containing the
alias targets.</li>
</ul>
@@ -292,7 +292,7 @@ of the data-source in config.xml that is
<ul>
<li><strong>table</strong> (required) - the URL describing the database table.
This URL has the form
db://<data-source>/<table> where <data-source> and
<table> are the names of
-the data-source as defined in config.xml and the table in the database.</li>
+the data-source as defined in mailetcontainer.xml and the table in the
database.</li>
<li><strong>sqlquery</strong> (optional) - the text of the SQL query used by
the mailet to do user
lookup. The default is "select VirtualUserTable.target-address from
VirtualUserTable, VirtualUserTable as VUTDomains where (VirtualUserTable.user
like ? or VirtualUserTable.user like '\\%') and (VirtualUserTable.domain like ?
or (VirtualUserTable.domain like '\\%' and VUTDomains.domain like ?)) order by
concat(VirtualUserTable.user,'@',VirtualUserTable.domain) desc limit 1"</li>
</ul>
Modified: james/server/trunk/src/site/xdoc/manage-domains.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/manage-domains.xml?rev=1032226&r1=1032225&r2=1032226&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/manage-domains.xml (original)
+++ james/server/trunk/src/site/xdoc/manage-domains.xml Sun Nov 7 08:21:20 2010
@@ -42,7 +42,7 @@
<li>Telnet to the host and port on which the RemoteManager is listening.
For command-line telnet clients
this is generally done by typing "telnet <host> <port>"
where <host> is the James
- hostname and <port> is the RemoteManager port specified in the
James config.xml.</li>
+ hostname and <port> is the RemoteManager port specified in the
James domainlist.xml.</li>
<li>You will be prompted for your administrator userid and password.
Enter the values you specified
in the James remotemanager.xml.</li>
Modified: james/server/trunk/src/site/xdoc/manage-users.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/manage-users.xml?rev=1032226&r1=1032225&r2=1032226&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/manage-users.xml (original)
+++ james/server/trunk/src/site/xdoc/manage-users.xml Sun Nov 7 08:21:20 2010
@@ -37,7 +37,7 @@
<li>Telnet to the host and port on which the RemoteManager is listening.
For command-line telnet clients
this is generally done by typing "telnet <host> <port>"
where <host> is the James
- hostname and <port> is the RemoteManager port specified in the
James config.xml.</li>
+ hostname and <port> is the RemoteManager port specified in the
James userrepository.xml.</li>
<li>You will be prompted for your administrator userid and password.
Enter the values you specified
in the James remotemanager.xml.</li>
Modified: james/server/trunk/src/site/xdoc/manage-virtualusers.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/manage-virtualusers.xml?rev=1032226&r1=1032225&r2=1032226&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/manage-virtualusers.xml (original)
+++ james/server/trunk/src/site/xdoc/manage-virtualusers.xml Sun Nov 7
08:21:20 2010
@@ -46,13 +46,13 @@ removemapping [tou...@todomain] [fromMap
<section name="Manage Virtual Users via Telnet">
- <p>Once James is up and listening, adding a user is simple:</p>
+ <p>Once James is up and listening, adding a virtual user is simple:</p>
<p><ol>
<li>Telnet to the host and port on which the RemoteManager is listening.
For command-line telnet clients
this is generally done by typing "telnet <host> <port>"
where <host> is the James
- hostname and <port> is the RemoteManager port specified in the
James config.xml.</li>
+ hostname and <port> is the RemoteManager port specified in the
James remotemanager.xml.</li>
<li>You will be prompted for your administrator userid and password.
Enter the values you specified
in the James remotemanager.xml.</li>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
