james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From se...@apache.org
Subject cvs commit: jakarta-james/src/conf james-config.xml
Date Mon, 03 Jun 2002 14:59:07 GMT
serge       2002/06/03 07:59:06

  Modified:    src/conf james-config.xml
  Log:
  Lowercased TRUE in useTLS configuration sections.
  
  Revision  Changes    Path
  1.26      +98 -98    jakarta-james/src/conf/james-config.xml
  
  Index: james-config.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-james/src/conf/james-config.xml,v
  retrieving revision 1.25
  retrieving revision 1.26
  diff -u -r1.25 -r1.26
  --- james-config.xml	16 May 2002 23:49:27 -0000	1.25
  +++ james-config.xml	3 Jun 2002 14:59:06 -0000	1.26
  @@ -1,21 +1,21 @@
   <?xml version="1.0"?>
   <!--  Configuration file for Apache Jakarta James Mail and news server -->
   
  -<!--  This file contains important settings that control the behaviour 
  -      of all of the services and repositories. 
  +<!--  This file contains important settings that control the behaviour
  +      of all of the services and repositories.
   
                                  README!
   
   This configuration file is designed to run without alteration for simple tests.
   It assumes you have a DNS server on localhost and assigns a root pasword of root.
   
  -In case the defaults do not suit you, the items you are most likely to need to change 
  +In case the defaults do not suit you, the items you are most likely to need to change
   are preceeded by a CHECKME! or CONFIRM? comment in the left margin.
   
   For production use you will probably need to make more extensive changes, see
   http://jakarta.apache.org/james/configuration_v2_0.html
   
  -$Revision: 1.25 $ Committed on $Date: 2002/05/16 23:49:27 $ by: $Author: hammant $-->
  +$Revision: 1.26 $ Committed on $Date: 2002/06/03 14:59:06 $ by: $Author: serge $-->
   
   <config>
      <James>
  @@ -25,25 +25,25 @@
   
   <!-- 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.
-->
  +         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>
  -      
  +
         <!-- Set whether user names are case sensitive or insensitive -->
         <!-- Set whether to enable local aliases -->
         <usernames ignoreCase="TRUE" enableAliases="TRUE" enableForwarding="TRUE"/>
  -      
  +
         <!-- The inbox repository is the location for users inboxes -->
         <!-- Default setting: file based repository - enter path ( use  "file:///" for
absolute) -->
         <inboxRepository>
            <repository destinationURL="file://var/mail/inboxes/" type="MAIL"/>
         </inboxRepository>
  -      
  -      <!-- Alternative inbox repository definition for DB use. 
  +
  +      <!-- Alternative inbox repository definition for DB use.
           The format for the destinationURL is "db://<data-source>/<table>"
                  <data-source> is the datasource name set up in the database-connections
block, below
                  <table> is the name of the table to store user inboxes in
  @@ -52,12 +52,12 @@
            <repository destinationURL="db://maildb/inbox/" type="MAIL"/>
         </inboxRepository>-->
      </James>
  -   
  +
      <!-- The James Spool Manager block  -->
      <spoolmanager>
         <!-- number of spool threads -->
         <threads> 10 </threads>
  -      
  +
         <!-- Set the packages from which to load mailets and matches -->
         <mailetpackages>
            <mailetpackage>org.apache.james.transport.mailets</mailetpackage>
  @@ -65,18 +65,18 @@
         <matcherpackages>
            <matcherpackage>org.apache.james.transport.matchers</matcherpackage>
         </matcherpackages>
  -      
  +
         <!-- Processor CONFIGURATION SAMPLE: root is the first processor all mail enters-->
         <processor name="root">
  -         
  +
            <!-- Checks that the MAIL FROM command was for a valid domain. Important for
spam prevention. -->
            <!--<mailet match="SenderInFakeDomain" class="ToProcessor">
               <processor> spam </processor>
            </mailet> -->
  -         
  +
            <!-- Important check to avoid race conditions -->
            <mailet match="RelayLimit=30" class="Null"/>
  -         
  +
            <!-- Check for delivery from a known spam server -->
            <mailet match="InSpammerBlacklist=blackholes.mail-abuse.org" class="ToProcessor">
               <processor> spam </processor>
  @@ -90,114 +90,114 @@
               <processor> spam </processor>
               <notice> Open spam relay - see http://www.mail-abuse.org/rss/ </notice>
            </mailet>
  -         
  +
            <!-- Sample matching to kill a message (send to Null) -->
            <mailet match="RecipientIs=badboy@badhost" class="Null"/>
  -         
  +
            <!-- Send remaining mails to the transport processor for either  local or remote
delivery -->
            <mailet match="All" class="ToProcessor">
               <processor> transport </processor>
            </mailet>
         </processor>
  -      
  +
         <!-- Processor CONFIGURATION SAMPLE: error is the processor mails with failure
conditions enter -->
         <processor name="error">
  -      
  +
            <!-- Logs any messages to the repository specified -->
            <mailet match="All" class="ToRepository">
               <repositoryPath> file://var/mail/error/</repositoryPath>
  -				<!-- alternative database repository example below -->
  +                <!-- alternative database repository example below -->
               <!-- <repositoryPath> db://maildb/deadletter/error </repositoryPath>
-->
               <passThrough> true </passThrough>
            </mailet>
  -         
  +
            <!-- If you want to notify the sender their message was marked as spam, uncomment
this         -->
            <!--<mailet match="All" class="NotifySender"/>-->
            <!-- If you want to notify the postmaster that a message was marked  as spam,
uncomment this  -->
            <!--<mailet match="All" class="NotifyPostmaster"/>-->
         </processor>
  -      
  +
         <!--  Processor CONFIGURATION SAMPLE: transport is a sample custom  processor
for local or remote delivery -->
         <processor name="transport">
  -      
  +
            <!-- Is the recipient is for a local account, deliver it locally -->
            <mailet match="RecipientIsLocal" class="LocalDelivery"/>
  -         
  +
            <!-- If the host is handled by this server and it did not get  locally delivered,
 this is an invalid recipient -->
            <mailet match="HostIsLocal" class="ToProcessor">
               <processor>error</processor>
            </mailet>
  -         
  +
   <!-- CHECKME!    Anti-relay mailet: Add your network address here,
                     e.g. "RemoteAddrNotInNetwork=127.0.0.1, abc.de.*, 192.168.0.*"-->
  -						
  +
            <!-- This matcher-mailet pair can prevent relaying...
             if you change  this,  you risk making your mail server an open relay point for
 spam.
  -			 
  +
                   NOTE 1: the order of matcher-mailets is important: it must come after
                   valid local recipients have been dealt with but before any attempt is
                   made to delivery the mail remotely.
  -					 
  +
                   NOTE 2: Add your own network, if you want to relay mail outwards
  -					 
  +
                   NOTE 3: If you use SMTP AUTH, you may want to comment this
                   so users who are on the road can still use the server -->
  -					 
  +
            <mailet match="RemoteAddrNotInNetwork=127.0.0.1" class="ToProcessor">
               <processor> spam </processor>
            </mailet>
  -         
  +
            <!-- Attempt remote delivery using the specified repository for the spool,
                  using delay time to retry delivery and the maximum number of retries -->
            <mailet match="All" class="RemoteDelivery">
               <outgoing> file://var/mail/outgoing/ </outgoing>
  -				<!-- alternative database repository example below -->
  +                <!-- alternative database repository example below -->
               <!-- <outgoing> db://maildb/spool/outgoing </outgoing> -->
  -				
  +
               <!-- Number of milliseconds between delivery attempts -->
               <delayTime> 21600000 </delayTime>
  -				
  +
               <!-- Number of failed attempts before returning to the sender -->
               <maxRetries> 5 </maxRetries>
  -				
  +
               <!-- The number of threads that should be trying to deliver outgoing messages
-->
               <deliveryThreads> 1 </deliveryThreads>
  -				
  -            <!-- A single mail server to deliver all outgoing messages.  
  -				This is useful if this is a backup or failover machine, 
  -				or if you otherwise want all messages to be sent only to particular mail server, 
  -				regardless of the email addresses specified in the message -->
  +
  +            <!-- A single mail server to deliver all outgoing messages.
  +                This is useful if this is a backup or failover machine,
  +                or if you otherwise want all messages to be sent only to particular mail
server,
  +                regardless of the email addresses specified in the message -->
               <!--<gateway> otherserver.mydomain.com </gateway>-->
  -				
  -            <!-- If your gateway mail server is listening on a port other than 25, 
  -				you can set James to connect to it on that port -->
  +
  +            <!-- If your gateway mail server is listening on a port other than 25,
  +                you can set James to connect to it on that port -->
               <!--<gatewayPort> 25 </gatewayPort>-->
            </mailet>
  -         
  +
         </processor>
  -      
  -      <!--  Processor CONFIGURATION SAMPLE: spam is where messages detected as relaying
or other problems will get sent.  
  -		You can either log these, bounce these, or just ignore them. -->
  +
  +      <!--  Processor CONFIGURATION SAMPLE: spam is where messages detected as relaying
or other problems will get sent.
  +        You can either log these, bounce these, or just ignore them. -->
         <processor name="spam">
            <!-- If you wanted, you could just destroy messages, uncomment this matcher/mailet-->
            <!--<mailet match="All" class="Null"/>-->
  -         
  +
            <!-- If you want to notify the sender their message was marked as spam, uncomment
this-->
            <!--<mailet match="All" class="NotifySender"/>-->
  -         
  +
            <!-- If you want to notify the postmaster that a message was marked as  spam,
uncomment this-->
            <!--<mailet match="All" class="NotifyPostmaster"/>-->
  -         
  +
            <!-- Out of the box, this will log the message to a repository -->
            <mailet match="All" class="ToRepository">
               <repositoryPath>file://var/mail/spam/</repositoryPath>
  -				
  -				<!-- alternative database repository example below -->
  +
  +                <!-- alternative database repository example below -->
               <!-- <repositoryPath> db://maildb/deadletter/spam </repositoryPath>
-->
            </mailet>
         </processor>
      </spoolmanager>
  -   
  +
   <!-- CONFIRM? Enter ip address of your DNS server, one per element -->
      <dnsserver>
         <servers>
  @@ -206,13 +206,13 @@
         </servers>
         <authoritative>false</authoritative>
      </dnsserver>
  -   
  +
      <remotemanager>
         <port>4555</port>
         <!--  uncomment this if you want to bind to a specific  inetaddress -->
         <!--<bind> </bind>-->
         <!--  uncomment this if you want to use TLS (SSL)  on this port -->
  -      <!--<useTLS>TRUE</useTLS>-->
  +      <!--<useTLS>true</useTLS>-->
         <handler>
            <!-- helloName is the single host name this instance of James will
                  use to identify itself  for example, in SMTP and POP3 greetings. If
  @@ -228,17 +228,17 @@
            <connectiontimeout> 60000 </connectiontimeout>
         </handler>
      </remotemanager>
  -   
  +
      <pop3server>
         <!-- port 995 is the well-known/IANA registered port for POP3S  ie over SSL/TLS
-->
         <!-- port 100 is the well-known/IANA registered port for Standard POP3 -->
         <port>110</port>
  -      
  +
         <!--  uncomment this if you want to bind to a specific  inetaddress -->
         <!--<bind> </bind>-->
         <!--  uncomment this if you want to use TLS (SSL)  on this port -->
  -      <!--<useTLS>TRUE</useTLS>-->
  -      
  +      <!--<useTLS>true</useTLS>-->
  +
         <handler>
            <!-- helloName is the single host name this instance of James will
                  use to identify itself  for example, in SMTP and POP3 greetings. If
  @@ -249,15 +249,15 @@
            <connectiontimeout>120000</connectiontimeout>
         </handler>
      </pop3server>
  -   
  +
      <smtpserver>
         <port>25</port>
  -      
  +
         <!--  uncomment this if you want to bind to a specific  inetaddress -->
         <!--<bind> </bind>-->
         <!--  uncomment this if you want to use TLS (SSL)  on this port -->
  -      <!--<useTLS>TRUE</useTLS>-->
  -      
  +      <!--<useTLS>true</useTLS>-->
  +
         <handler>
            <!--helloName is the single host name this instance of James will
                use to identify itself  for example, in SMTP and POP3 greetings. If
  @@ -285,12 +285,12 @@
         <!-- port 563 is the well-known/IANA registered port for nntp over SSL/TLS -->
         <!-- port 119 is the well-known/IANA registered port for Standard nntp -->
         <port>119</port>
  -      
  +
         <!--  uncomment this if you want to bind to a specific  inetaddress -->
         <!--<bind> </bind>-->
         <!--  uncomment this if you want to use TLS (SSL)  on this port -->
  -      <!--<useTLS>TRUE</useTLS>-->
  -      
  +      <!--<useTLS>true</useTLS>-->
  +
         <handler>
            <!-- helloName is the single host name this instance of James will
               use to identify itself  for example, in SMTP and POP3 greetings. If
  @@ -301,21 +301,21 @@
            <connectiontimeout>120000</connectiontimeout>
         </handler>
      </nntpserver>
  -   
  +
      <nntpauth>
         <!-- make this true, if you want only authenticated users to access NNTP-->
         <authRequired>false</authRequired>
      </nntpauth>
  -   
  +
      <nntp-repository>
         <!-- make this true to disallow posting to all newsgroups-->
         <readOnly>false</readOnly>
  -      
  +
         <rootPath>file:///var/nntp/groups</rootPath>
         <tempPath>file:///var/nntp/temp</tempPath>
         <articleIDPath>file:///var/nntp/articleid</articleIDPath>
         <articleIDDomainSuffix>news.james.apache.org</articleIDDomainSuffix>
  -      
  +
         <!-- these additional news groups would be created and exposed-->
         <newsgroups>
            <newsgroup>org.apache.james.dev</newsgroup>
  @@ -323,7 +323,7 @@
            <newsgroup>org.apache.avalon.dev</newsgroup>
            <newsgroup>org.apache.avalon.user</newsgroup>
         </newsgroups>
  -      
  +
         <spool>
            <configuration>
               <spoolPath>file:///var/nntp/spool</spoolPath>
  @@ -333,7 +333,7 @@
               <threadIdleTime>1000</threadIdleTime>
            </configuration>
         </spool>
  -      
  +
      </nntp-repository>
      <!-- The High Level Storage block -->
      <mailstore>
  @@ -403,22 +403,22 @@
               </config>
            </repository>
         </repositories>
  -      
  +
         <!-- Spool repository configuration -->
  -      <!-- The spool repository is a singular location where incoming mails are temporarily
stored before being processed. 
  -		(ex. file://c:/james/spool/) -->
  +      <!-- The spool repository is a singular location where incoming mails are temporarily
stored before being processed.
  +        (ex. file://c:/james/spool/) -->
         <!-- Default setting: file based repository - enter path ( :/// for absolute)
-->
         <spoolRepository>
            <repository destinationURL="file://var/mail/spool/" type="SPOOL"/>
         </spoolRepository>
  -      
  +
         <!-- Alternative spool repository definition for JDBC use -->
         <!--<spoolRepository>
            <repository destinationURL="db://maildb/spool/spool" type="SPOOL"/>
         </spoolRepository>-->
      </mailstore>
  -   
  -   
  +
  +
      <!-- The User Storage block -->
      <users-store>
         <!-- Configure User Repositories here.
  @@ -432,68 +432,68 @@
         Note: Two user repositories are required for default configuration:
         LocalUsers - the users for whom you are providing POP3, NNTP, or AUTH service
         list-james - the users of the james@localhost mailiinglist-->
  -      
  +
         <!-- Default: File-based user repositories  Use these configurations to store
user info in the filesystem  -->
         <!-- The LocalUsers repository, for storing James' User info. -->
         <repository name="LocalUsers" class="org.apache.james.userrepository.UsersFileRepository">
            <destination URL="file://var/users/"/>
         </repository>
  -      
  +
         <!-- The list used by the default ListServ mailet -->
         <repository name="list-james" class="org.apache.james.userrepository.UsersFileRepository">
            <destination URL="file://var/lists/list-james/"/>
         </repository>
  -      
  +
         <!-- Database backed user repositories
                Use these configurations to store user info in a database.
                Note: the <data-source> element must refer to a connection configured
                in the <database-connections> configuration section. -->
  -             
  +
         <!-- The LocalUsers repository, for storing James' User info. -->
         <!--<repository name="LocalUsers" class="org.apache.james.userrepository.JamesUsersJdbcRepository"
destinationURL="db://maildb/users">
            <sqlFile>file://conf/sqlResources.xml</sqlFile>
         </repository>-->
  -      
  +
         <!-- The list used by the default ListServ mailet -->
         <!--<repository name="list-james" class="org.apache.james.userrepository.ListUsersJdbcRepository"
destinationURL="db://maildb/lists/list-james">
            <sqlFile>file://conf/sqlResources.xml</sqlFile>
         </repository>-->
      </users-store>
  -   
  +
      <!-- The database-connections block -->
      <database-connections>
         <!-- Confugure database connections here. These connections are referred to by
name elsewhere in the config file -->
         <!-- CHECKME! To allow James to use a database, configure the database connection
here -->
         <data-sources>
  -      
  +
            <!-- Example, connecting to a MySQL database called "mail" on localhost-->
            <!--<data-source name="maildb" class="org.apache.james.util.mordred.JdbcDataSource">
               <driver>org.gjt.mm.mysql.Driver</driver>
               <dburl>jdbc:mysql://127.0.0.1/mail</dburl>
               <user>username</user>
               <password>password</password>  -->
  -				<!-- Maximum concurrent connections james may open to this database-->
  -				<!-- If you see "SQLException: Giving up... no connections available." in your 
  -				log files or bounced mail increase this value 
  +                <!-- Maximum concurrent connections james may open to this database-->
  +                <!-- If you see "SQLException: Giving up... no connections available."
in your
  +                log files or bounced mail increase this value
               <max>10</max>
            </data-source>-->
  -         
  +
            <!--<data-source name="maildb" class="org.apache.james.util.mordred.JdbcDataSource">
               <driver>com.inet.tds.TdsDriver</driver>
               <dburl>jdbc:inetdae7:127.0.0.1?database=James</dburl>
               <user>sa_james</user>
               <password>blahblah</password> -->
  -				<!-- Maximum concurrent connections james may open to this database-->
  -				<!-- If you see "SQLException: Giving up... no connections available." in your 
  -				log files or bounced mail increase this value 
  +                <!-- Maximum concurrent connections james may open to this database-->
  +                <!-- If you see "SQLException: Giving up... no connections available."
in your
  +                log files or bounced mail increase this value
               <max>10</max>
            </data-source>-->
  -			
  +
         </data-sources>
      </database-connections>
  -   
  -   <!-- Configuration for Cornerstone Blocks only after here NOTHING BELOW THIS SHOULD
NEED CHANGING, 
  -	(unless you want secure sockets (TLS)) -->
  +
  +   <!-- Configuration for Cornerstone Blocks only after here NOTHING BELOW THIS SHOULD
NEED CHANGING,
  +    (unless you want secure sockets (TLS)) -->
      <!-- The Storage block -->
      <objectstorage>
         <repositories>
  
  
  

--
To unsubscribe, e-mail:   <mailto:james-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:james-dev-help@jakarta.apache.org>


Mime
View raw message