Below is a diff of the default config.xml that ships with 2.3.1 and
mine. It's probably a good idea to mention that we've been using
James a long time, so there may be lots of legacy things hanging out
in our config.xml.
If the diff isn't helpful, I will send the config.xml file. Please
let me know.
Lots of places are merely the addition / deletion of comments, but I
left them in for completeness.
The file does work on 2.2.0 (minus the minor changes for upgrading
2.3.1).
DK
============== DIFF =================
5a6
<!ENTITY smtphandlerchainConfig SYSTEM "../conf/james-
smtphandlerchain.xml">
22c23
< <!-- http://james.apache.org/documentation_2_1.html -->
---
<!-- http://james.apache.org/server/2.3.0/ -->
34,43c35
62,67c54,55
< <servernames autodetect="false" autodetectIP="true">
---
<servernames autodetect="true" autodetectIP="true">
<!-- CONFIRM? -->
69,303d56
< <servername>lots of servernames</servername>
371c115
< <mailetpackage>com.myhost.mailet</mailetpackage>
---
<mailetpackage>org.apache.james.transport.mailets.smime</
mailetpackage>
376c119
< <matcherpackage>com.myhost.mailet</matcherpackage>
---
<matcherpackage>org.apache.james.transport.matchers.smime</
matcherpackage>
388c127
< <threads> 50 </threads>
---
<threads> 10 </threads>
395c134,138
< <!-- As of James 2.3.1 this is no longer pre-defined -->
---
<!-- This mailet redirects mail for the user 'postmaster'
at any local domain to -->
<!-- the postmaster address specified for the server. The
postmaster address -->
<!-- is required by rfc822. Do not remove this mailet
unless you are meeting -->
<!-- this requirement through other means (e.g. a XML/
JDBCVirtualUserTable mailet) -->
409a153,286
<!-- Check for viruses -->
<!-- -->
<!-- Does an antivirus scan check using a ClamAV daemon
(CLAMD). -->
<!-- -->
<!-- Interacts directly with the daemon using the "stream"
method, -->
<!-- which should have the lowest possible overhead. -->
<!-- The CLAMD daemon will typically reside on localhost,
but could reside on a -->
<!-- different host. -->
<!-- It may also consist on a set of multiple daemons,
each residing on a different -->
<!-- server and on different IP number. -->
<!-- In such case a DNS host name with multiple IP
addresses (round-robin load sharing) -->
<!-- is supported by the mailet (but on the same port
number). -->
<!-- -->
<!-- Handles the following init parameters: -->
<!-- <debug> -->
<!-- <host>: the host name of the server where CLAMD runs.
It can either be -->
<!-- a machine name, such as -->
<!-- "java.sun.com", or a textual representation of
its -->
<!-- IP address. If a literal IP address is supplied,
only the -->
<!-- validity of the address format is checked. -->
<!-- If the machine name resolves to multiple IP
addresses, round-robin load sharing will -->
<!-- be used. -->
<!-- The default is "localhost". -->
<!-- <port>: the port on which CLAMD listens. The default
is "3310". -->
<!-- <maxPings>: the maximum number of connection retries
during startup. -->
<!-- If the value is "0" no startup test will be done.
-->
<!-- The default is "6". -->
<!-- <pingIntervalMilli>: the interval (in milliseconds) -->
<!-- between each connection retry during startup. -->
<!-- The default is "30000" (30 seconds). -->
<!-- <streamBufferSize>: the BufferedOutputStream buffer
size to use -->
<!-- writing to the stream connection. The default is
"8192". -->
<!--
<mailet match="All" class="ClamAVScan"
onMailetException="ignore">
<debug> true </debug>
</mailet>
-->
<!-- If infected go to virus processor -->
<mailet
match="HasMailAttributeWithValue=org.apache.james.infected, true"
class="ToProcessor">
<processor> virus </processor>
</mailet>
<!-- Check attachment extensions for possible viruses -->
<!-- The "-z" option requests the check to be non-
recursively applied -->
<!-- to the contents of any attached '*.zip' file. -->
<!--
<mailet match="AttachmentFileNameIs=-d -z *.exe *.com
*.bat *.cmd *.pif *.scr *.vbs *.avi *.mp3 *.mpeg *.shs"
class="Bounce"
onMatchException="error">
<inline>heads</inline>
<attachment>none</attachment>
<passThrough>false</passThrough>
<prefix>[REJECTED]</prefix>
<notice>
The Security Policy of XXX does not allow to forward messages
containing attachments having any of the
extensions
.exe, .com, .bat, .cmd, .pif, .scr, .vbs, .avi, .mp3, .mpeg, .shs,
therefore your message has been rejected.
Please don't reply to this e-mail as it has been automatically sent
by the antivirus system.
Regards, Postmaster XXX.YYY
.....................................
</notice>
</mailet>
-->
<!-- Whitelist Management -->
<!-- Manages for each local user a "white list" of remote
addresses whose messages -->
<!-- should never be blocked as spam. -->
<!-- -->
<!-- If <automaticInsert> is true, it will check, for a
local sender, if a remote recipient -->
<!-- is already in the list: if not, it will be
automatically inserted. -->
<!-- This is under the interpretation that if a local
sender X sends a message to a -->
<!-- remote recipient Y, then later on if a message is
sent by Y to X it should be -->
<!-- considered always valid and never blocked; hence Y
should be in the white list -->
<!-- of X. -->
<!-- -->
<!-- Another mode of operations is when a local sender
sends a message to <whitelistManagerAddress> -->
<!-- with one of three specific values in the subject, to
-->
<!-- (i) send back a message displaying a list of the
addresses in his own list (<displayFlag>); -->
<!-- (ii) insert some new addresses in his own list
(<insertFlag>); -->
<!-- (iii) remove some addresses from his own list
(<removeFlag>). -->
<!-- In all of the three above cases the message will be
ghosted and the postmaster will reply -->
<!-- to the sender. -->
<!-- -->
<!-- The sender name is always converted to its primary
name (handling aliases). -->
<!--
<mailet match="SMTPAuthSuccessful"
class="WhiteListManager" onMailetException="ignore">
<repositoryPath>db://maildb</repositoryPath>
<automaticInsert>true</automaticInsert>
<whitelistManagerAddress>[EMAIL PROTECTED]</
whitelistManagerAddress>
<displayFlag>display</displayFlag>
<insertFlag>insert</insertFlag>
<removeFlag>remove</removeFlag>
</mailet>
-->
<!-- "not spam" bayesian analysis feeder. -->
<!--
<mailet match="[EMAIL PROTECTED]"
class="BayesianAnalysisFeeder">
<repositoryPath> db://maildb </repositoryPath>
<feedType>ham</feedType>
<maxSize>200000</maxSize>
</mailet>
-->
<!-- "spam" bayesian analysis feeder. -->
<!--
<mailet match="[EMAIL PROTECTED]"
class="BayesianAnalysisFeeder">
<repositoryPath> db://maildb </repositoryPath>
<feedType>spam</feedType>
<maxSize>200000</maxSize>
</mailet>
-->
<!-- sample SMIME mailets configuration -->
<!-- In order to use SMIME capabilities you need to
install the bouncycastle JCE -->
<!-- provider in your environment (james/lib) -->
<!-- e.g: bcprov-jdk14-129.jar from
http://www.bouncycastle.org/latest_releases.html
-->
<!--
<mailet match="IsSMIMEEncrypted" class="SMIMEDecrypt">
<keyStoreType>pkcs12</keyStoreType>
<keyStoreFileName>c:/path.pfx</keyStoreFileName>
<keyStorePassword>myKeyStorePass</keyStorePassword>
<keyAlias>myKeyAlias</keyAlias>
<keyAliasPassword>myKeyPass</keyAliasPassword>
</mailet>
<mailet match="IsSMIMESigned" class="SMIMECheckSignature">
<keyStoreType>pkcs12</keyStoreType>
<keyStoreFileName>c:/path.pfx</keyStoreFileName>
<keyStorePassword>myKeyStorePass</keyStorePassword>
<strip>false</strip>
<onlyTrusted>true</onlyTrusted>
</mailet>
-->
428a306,317
<!-- Anti-spam processing -->
<!-- The following two entries avoid double anti-spam
analysis -->
<!-- for forwarded messages. -->
<!-- Has spam checking already been done? -->
<mailet match="HasMailAttribute=spamChecked"
class="ToProcessor">
<processor> transport </processor>
</mailet>
<!-- Spam checking will not be done twice -->
<mailet match="All" class="SetMailAttribute">
<spamChecked>true</spamChecked>
</mailet>
436a326,340
<!-- Messages from authenticated senders never are spam -->
<mailet match="SMTPAuthSuccessful" class="ToProcessor">
<processor> transport </processor>
</mailet>
<!-- Messages signed by trusted users never are spam -->
<!-- Uncommenting the following entry, messages with valid
signatures will never be considered spam. -->
<!-- This can be a valid policy *if* SMIMECheckSignature
was invoked -->
<!-- with <onlyTrusted>true</onlyTrusted> set -->
<!--
<mailet
match="HasMailAttribute=org.apache.james.SMIMECheckSignature"
class="ToProcessor">
<processor> transport </processor>
</mailet>
-->
445,447c349,350
< <!-- White List: IP ADDRESS MASKED OUT WITH XXX -->
< <mailet match="RemoteAddrInNetwork=XXX.XXX.XXX.XXX"
---
<!-- People on this list agree to pay a penalty if they
send spam -->
<mailet match="InSpammerBlacklist=query.bondedsender.org."
452,454c355,357
< <!-- People on this list agree to pay a penalty if they
send spam
< <mailet match="InSpammerBlacklist=query.bondedsender.org"
< class="ToProcessor">
---
<!-- E-mail legally required not to be spam (see: http://www.habeas.com
) -->
<!--
<mailet match="HasHabeasWarrantMark" class="ToProcessor">
459c362,363
< <!-- E-mail legally required not to be spam (see:
http://www.habeas.com
) -->
---
<!-- If the sender is in a recipient's whitelist, it is a
valid sender, -->
<!-- and as such the message should not be considered spam
for such recipient. -->
461c365
< <mailet match="HasHabeasWarrantMark" class="ToProcessor">
---
<mailet match="IsInWhiteList=db://maildb"
class="ToProcessor" onMatchException="noMatch">
464a369
471c376
< <mailet match="InSpammerBlacklist=dnsbl.njabl.org"
---
<mailet match="InSpammerBlacklist=dnsbl.njabl.org."
477,480c382,393
< <mailet match="InSpammerBlacklist=relays.ordb.org"
< class="ToProcessor">
< <processor> spam </processor>
< <notice>550 Requested action not taken: rejected - see
http://www.ordb.org/
</notice>
---
<!-- Sample matching to kill a message (send to Null) -->
<!--
<mailet match="[EMAIL PROTECTED]" class="Null"/>
-->
<!-- Anti spam bayesian analysis -->
<!--
<mailet match="All" class="BayesianAnalysis"
onMailetException="ignore">
<repositoryPath>db://maildb</repositoryPath>
<maxSize>200000</maxSize>
<headerName>X-MessageIsSpamProbability</headerName>
<ignoreLocalSender>true</ignoreLocalSender>
483,486c396,397
< <mailet match="InSpammerBlacklist=sbl-xbl.spamhaus.org"
< class="ToProcessor">
< <processor> spam </processor>
< <notice>550 Requested action not taken: rejected - see
http://www.spamhaus.org/
</notice>
---
<mailet match="CompareNumericHeaderValue=X-
MessageIsSpamProbability > 0.90" class="SetMailAttribute"
onMatchException="noMatch">
<isSpam>true</isSpam>
489,492c400,402
< <mailet match="InSpammerBlacklist=dnsbl.ahbl.org"
< class="ToProcessor">
< <processor> spam </processor>
< <notice>550 Requested action not taken: rejected - see
http://www.ahbl.org/
</notice>
---
<mailet match="CompareNumericHeaderValue=X-
MessageIsSpamProbability > 0.90" class="SetMimeHeader"
onMatchException="noMatch">
<name>X-MessageIsSpam</name>
<value>true</value>
495,497c405,408
< <!-- Sample matching to kill a message (send to Null) -->
< <!--
< <mailet match="[EMAIL PROTECTED]" class="Null"/>
---
<mailet match="CompareNumericHeaderValue=X-
MessageIsSpamProbability > 0.99" class="ToProcessor"
onMatchException="noMatch">
<processor> spam </processor>
<notice>Spam not accepted</notice>
</mailet>
518c429,431
< <!-- <mailet match="All" class="NotifyPostmaster"/> -->
---
<!--
<mailet match="All" class="NotifyPostmaster"/>
-->
522c435
< <!-- <repositoryPath> file://var/mail/error/</
repositoryPath> -->
---
<repositoryPath> file://var/mail/error/</repositoryPath>
533,552d446
< <mailet match="All" class="JDBCVirtualUserTable">
< <table>db://maildb/VirtualUserTable</table>
< </mailet>
<
< <mailet match="RecipientIsRegex=^jmc-(.*)"
class="BounceMailet" />
<
< <!-- Store all post-blackhole emails in the
database -->
< <mailet match="MailMatcher" class="MailMailet"/>
558a453,503
<mailet match="SMTPAuthSuccessful" class="SetMimeHeader">
<name>X-UserIsAuth</name>
<value>true</value>
</mailet>
<mailet
match="HasMailAttribute=org.apache.james.SMIMECheckSignature"
class="SetMimeHeader">
<name>X-WasSigned</name>
<value>true</value>
</mailet>
<!-- Add a server-side signature -->
<!-- In order to use SMIME capabilities you need to
install the bouncycastle JCE -->
<!-- provider in your environment (james/lib) -->
<!-- e.g: bcprov-jdk14-129.jar from
http://www.bouncycastle.org/latest_releases.html
-->
<!--
<mailet match="All" class="SMIMESign"
onMailetException="ignore">
<keyStoreType>jks</keyStoreType>
<keyStoreFileName>path.keystore</keyStoreFileName>
<keyStorePassword>myKeyStorePass</keyStorePassword>
<keyAlias>myKeyAlias</keyAlias>
<keyAliasPassword>myKeyPass</keyAliasPassword>
<signerName>XXX Trusted Server</signerName>
<rebuildFrom>true</rebuildFrom>
<postmasterSigns>true</postmasterSigns>
<debug>true</debug>
</mailet>
-->
<!-- Experimental quota Matcher -->
<!-- This matcher need to calculate the mailbox size
everytime it is called. This can slow down things if there are many
mails in -->
<!-- the mailbox. Some users also report big problems with
the matcher if a JDBC based mailrepository is used. -->
<!-- Check if over quota -->
<!--
<mailet match="RecipientIsOverFixedQuota=20M"
class="Resend">
<sender>postmaster</sender>
<replyTo>postmaster</replyTo>
<reversePath>null</reversePath>
<inline>none</inline>
<attachment>message</attachment>
<prefix>[OVER QUOTA WARNING]</prefix>
<message>
When receiving the attached message, your mailbox is larger than 20
MB, which is the maximum allowed quota. The mailbox will not be
blocked, but we ask you to empty it ASAP.
It is likely that you have set, in your mail client account, the
option "leave a copy of messages on server". For any help ask your
administrators.
Regards, Postmaster XXX.YYY
.....................................
</message>
</mailet>
-->
600c543
< <!-- <outgoing> file://var/mail/outgoing/ </outgoing>
-->
---
<outgoing> file://var/mail/outgoing/ </outgoing>
608,610d552
<
< <delayTime> 60000 </delayTime>
< <delayTime> 60000 </delayTime>
619,623d560
< <!-- for testing...
< <delayTime> 10000 </delayTime>
< <maxRetries> 5 </maxRetries>
< -->
<
625,626c562
< <deliveryThreads> 30 </deliveryThreads>
< <debug>false</debug>
---
<deliveryThreads> 1 </deliveryThreads>
630a567,571
<!-- By default we send bounces to the "bounce"
processor -->
<!-- By removing this configuration James will fallback
to hardcoded bounce -->
<!-- notifications -->
<bounceProcessor>bounces</bounceProcessor>
648a590,600
<!-- If the gateway requires smtp authentication the
following directives -->
<!-- (gatewayusername/gatewayPassword) can be used. -->
<!--
<gatewayusername>login</gatewayusername>
<gatewayPassword>pass</gatewayPassword>
-->
<!-- Set the HELO/EHLO name to use when connectiong to
remote SMTP-Server -->
<!--
<mail.smtp.localhost>myMailServer</mail.smtp.localhost>
-->
668c620,622
< <!-- <mailet match="All" class="NotifyPostmaster"/> -->
---
<!--
<mailet match="All" class="NotifyPostmaster"/>
-->
673c627
< <!-- <repositoryPath>file://var/mail/spam/</
repositoryPath> -->
---
<repositoryPath>file://var/mail/spam/</repositoryPath>
682a639,658
<!-- messages containing viruses. -->
<processor name="virus">
<!-- To avoid a loop while bouncing -->
<mailet match="All" class="SetMailAttribute">
<org.apache.james.infected>true, bouncing</
org.apache.james.infected>
</mailet>
<!-- If the sender is authenticated, notify the infection
-->
<mailet match="SMTPAuthSuccessful" class="Bounce">
<inline>heads</inline>
<attachment>none</attachment>
<notice> Warning: We were unable to deliver the message
below because it was found infected by virus(es). </notice>
</mailet>
<!-- In any other situation ghost it, -->
<!-- as viruses almost always spoof the sender's address -->
<mailet match="All" class="Null" />
</processor>
684a661,665
<!-- To avoid bouncing/archiving spam, uncomment this
matcher/mailet configuration -->
<!--
<mailet match="HasMailAttribute=isSpam" class="Null"
onMatchException="noMatch"/>
-->
694c675,677
< <!-- <mailet match="All" class="NotifyPostmaster"/> -->
---
<!--
<mailet match="All" class="NotifyPostmaster"/>
-->
697c680
< <!-- <repositoryPath> file://var/mail/address-error/</
repositoryPath> -->
---
<repositoryPath> file://var/mail/address-error/</
repositoryPath>
698a682
<!--
699a684
-->
716c701,703
< <!-- <mailet match="All" class="NotifyPostmaster"/> -->
---
<!--
<mailet match="All" class="NotifyPostmaster"/>
-->
719c706
< <!-- <repositoryPath>file://var/mail/relay-denied/</
repositoryPath> -->
---
<repositoryPath>file://var/mail/relay-denied/</
repositoryPath>
720a708
<!--
721a710,737
-->
</mailet>
</processor>
<!-- This processor handle the bounces from RemoteDelivery:
As of James v2.3, this is the new -->
<!-- Default. -->
<!-- -->
<!-- DSNBounce properly create a DSN compliant bounce -->
<processor name="bounces">
<mailet match="All" class="DSNBounce">
<passThrough>false</passThrough>
<!-- optional subject prefix prepended to the original
message -->
<!--
<prefix>[bounce]</prefix>
-->
<!-- message, heads or none, default=message -->
<!--
<attachment>heads</attachment>
-->
<!-- the message sent in the bounce, the first
occurrence of the pattern [machine] is -->
<!-- replaced with the name of the executing machine -->
<!-- Default: Hi. This is the James mail server at
[machine] ... -->
<!--
<messageString>Here is [machine]. I'm not able to
deliver this message.</messageString>
-->
753a766,768
<!-- Change autodiscover to false if you would like to turn
off autodiscovery -->
<!-- and set the DNS servers manually in the <servers>
section -->
<autodiscover>true</autodiscover>
756,759c771,772
<
---
<!-- Maximum number of entries to maintain in the DNS cache -->
<maxcachesize>50000</maxcachesize>
762c775,778
< <remotemanager>
---
<!-- The RemoteManager server is enabled by default -->
<!-- Disabling blocks will stop them from listening, -->
<!-- but does not free as many resources as removing them would
-->
<remotemanager enabled="true">
783c794
< <helloName autodetect="false">out.myserver.net</
helloName>
---
<helloName autodetect="true">myMailServer</helloName>
784a796
<!-- CHECKME! -->
788a801,804
<!-- The prompt directive adds a prompt to every output
from RemoteManager -->
<!--
<prompt>james></prompt>
-->
824,830c831,832
< <helloName autodetect="false">myserver.net</helloName>
< <!--
<
< THIS SETTING IS NOT USED: Use the default.
<
< <connectiontimeout>30000</connectiontimeout>
< -->
---
<helloName autodetect="true">myMailServer</helloName>
<connectiontimeout>120000</connectiontimeout>
845a844,845
<!-- Please NOTE: you should add this IP also to your
RemoteAddrNotInNetwork -->
<!-- in order to avoid relay check for locallly generated
bounces -->
864,865c860,861
< <helloName autodetect="false">out.myserver.net</
helloName>
< <!--
---
<helloName autodetect="true">myMailServer</helloName>
<connectiontimeout>360000</connectiontimeout>
869c865,876
< <connectiontimeout>30000</connectiontimeout>
---
supported values:
true: required but announced only to not
authorizedAddresses
false: don't use AUTH
announce: like true, but always announce AUTH
capability to clients
The correct behaviour per RFC value would be false
or announce
but we still support true for backward compatibility
and because
some webmail client fails when AUTH is announced but
no authentication
information has been provided
-->
<!--
<authRequired>true</authRequired>
872c879,884
< <!-- Uncomment this if you want to require SMTP
authentication. -->
---
<!-- CHECKME! -->
<!-- Uncomment this if you want to authorize specific
addresses/networks.
If you use SMTP AUTH, addresses that match those
specified here will
be permitted to relay without SMTP AUTH. If you do
not use SMTP
AUTH, and you specify addreses here, then only
addresses that match
those specified will be permitted to relay.
874c886,894
< <authRequired>true</authRequired>
---
Addresses may be specified as a an IP address or
domain name, with an
optional netmask, e.g.,
127.*, 127.0.0.0/8, 127.0.0.0/255.0.0.0, and
localhost/8 are all the same
See also the RemoteAddrNotInNetwork matcher in the
transport processor.
You would generally use one OR the other approach.
-->
<authorizedAddresses>127.0.0.0/8</authorizedAddresses>
885,888c905
< <!-- Now enforcing ~5MB + 25% limit. Can restrict by
domain/account? -->
< <!-- NWC 3/11 changed from 125 to 50 because we keep
running out of connections -->
< <maxmessagesize>6400</maxmessagesize>
< <!--
---
<maxmessagesize>0</maxmessagesize>
890c907,911
< THIS SETTING IS NOT USED: BUG JAMES-151 is
"connectionLimit on services ignored"
---
<!-- This sets wether to enforce the use of HELO/EHLO
salutation before a -->
<!-- MAIL command is accepted. If unspecified, the value
defaults to true -->
<!--
<heloEhloEnforcement>true</heloEhloEnforcement>
-->
892c913,918
< <connectionLimit>50</connectionLimit>
---
<!-- SMTP Handler Chain customization -->
<!-- Uncomment this and edit james-smtphandlerchain.xml
configuration file to -->
<!-- enable the experimental fastfail features. Look at
the james-smtphandlerchain.xml -->
<!-- for further informations -->
<!--
&smtphandlerchainConfig;
907c929
< <nntpserver enabled="false">
---
<nntpserver enabled="true">
962c984
< <threadCount>2</threadCount>
---
<threadCount>1</threadCount>
968a991,1006
<!-- Spool repository configuration -->
<!-- The spool repository is the location where incoming mails
are temporarily stored -->
<!-- before being processed. -->
<spoolrepository destinationURL="file://var/mail/spool/"
type="SPOOL"/>
<!-- Alternative spool repository definition for JDBC use -->
<!--
<spoolrepository destinationURL="db://maildb/spool/spool"
type="SPOOL"/>
-->
<!-- Alternative spool repository definition for JDBC use -->
<!-- Stores message body in file system, rest in database -->
<!--
<spoolrepository destinationURL="dbfile://maildb/spool/spool"
type="SPOOL"/>
-->
1002a1041,1047
<!-- Set the size threshold for in memory handling
of storing operations -->
<!-- Default is currently 409600000 due to a bug
with mysql and binary stream -->
<!-- currently under investigation. Please change
this only if you know what -->
<!-- you do, this is EXPERIMENTAL -->
<!--
<inMemorySizeLimit>4096</inMemorySizeLimit>
-->
1015a1061,1067
<!-- Set the size threshold for in memory handling
of storing operations -->
<!-- Default is currently 409600000 due to a bug
with mysql and binary stream -->
<!-- currently under investigation. Please change
this only if you know what -->
<!-- you do, this is EXPERIMENTAL -->
<!--
<inMemorySizeLimit>4096</inMemorySizeLimit>
-->
1056,1065d1107
< </repositories>
<
< <!-- Spool repository configuration -->
< <!-- The spool repository is the location where incoming
mails
are temporarily stored -->
< <!-- before being processed. -->
< <!--
< <spoolRepository>
< <repository destinationURL="file://var/mail/spool/"
type="SPOOL"/>
< </spoolRepository>
< -->
1067,1079d1108
< <!-- Alternative spool repository definition for JDBC use -->
< <!-- Alternative spool repository definition for JDBC use -->
< <!-- Stores message body in file system, rest in database -->
< <!--
< <spoolRepository>
< <repository destinationURL="dbfile://maildb/spool/spool"
type="SPOOL"/>
< </spoolRepository>
< -->
< <!-- The Object Storage block -->
< <!-- -->
< <!-- Defines file storage details that are used for file-based
repositories. -->
< <objectstorage>
< <repositories>
1108d1136
< </objectstorage>
1112d1139
< <spoolrepository destinationURL="db://maildb/spool/spool"
type="SPOOL"/>
1134d1160
< <!--
1138c1164
< -->
---
1146a1173
<!--
1149a1177
-->
1177,1179c1205,1218
< <!-- James is distributed with a built in relevant copy of
the
mm.mysql JDBC -->
< <!-- driver. No additional driver is needed for mysql. Read
the mm.mysql LGPL -->
< <!-- license at apps\james\SAR-INF\lib
\mm.mysql.LICENCE -->
---
<!-- Default James distribution includes Apache Derby
database, -->
<!-- which is easy to embed - but we support all the major
SQL -->
<!-- databases - just reconfigure your JDBC configuration -->
<!--
<data-source name="maildb"
class="org.apache.james.util.dbcp.JdbcDataSource">
<driver>org.apache.derby.jdbc.EmbeddedDriver</driver>
<dburl>jdbc:derby:../apps/james/var/derbydb;create=true</
dburl>
<user></user>
<password></password>
<poolPreparedStatements>true</poolPreparedStatements>
<max>20</max>
</data-source>
-->
1182a1222,1224
<!-- You can download latest Connector/J from -->
<!-- http://dev.mysql.com/downloads/connector/j/3.1.html -->
<!-- -->
1191c1233
< <driver>org.gjt.mm.mysql.Driver</driver>
---
<driver>com.mysql.jdbc.Driver</driver>
1217a1257,1260
<!-- Here is a configuration for hsqldb (formerly
HypersonicSQL) -->
<!-- You can download the db from http://www.hsqldb.org/ .
Just put the -->
<!-- hsqldb.jar in the lib directory and uncomment the
following block -->
<!--
1219,1234c1262,1266
1272,1273c1302,1303
< <idle-timeout>5000</idle-timeout>
< <max-connections>40</max-connections>
---
<idle-timeout>300000</idle-timeout>
<max-connections>30</max-connections>
1293a1324,1328
<!-- In order to use the ssl factory under Java 1.5 and support
all Clients -->
<!-- (particularly Mozilla Thunderbird) you need to install the
Sun JCE -->
<!-- provider in your environment (james/lib) -->
<!-- e.g: jre/lib/ext/sunjce_provider.jar -->
<!-- -->
1298a1334
<ssl-factory>
1301a1338
<key-password>keysecret</key-password>
1306a1344
</ssl-factory>
1338c1376
< <max-threads>250</max-threads>
---
<max-threads>100</max-threads>
On Dec 11, 2007, at 12:35 AM, Stefano Bagnara wrote:
Either you send your config.xml or you tell us exactly what changes
you
did to config.xml in 2.2.0 and in 2.3.1.
Furthermore, looking at the apps/james/logs folder may help.
Stefano
Dain Kaplan ha scritto:
After an upgrade to the stable release of 2.3.1, following the
included
upgrade instructions, James starts up fine. Incoming mail also
seems to
be processed as well (after looking in the logs and watching the
spool
DB table).
However, mails simply don't show up in the user's inbox via POP3.
Authentication works fine through mail client (OS X Mail), and
incredibly old mail (somehow still on the server) was downloaded.
But
no new mail arrives (despite no errors in the logs).
Running: Java 1.5_013. Also with increased memory usage (settings
copied from 2.2.0 installation). A few "swap out of space" errors
have
been received as well.
After starting backup 2.2.0, any mails sent while 2.3.1 was running
are
lost (perhaps in the var folder? though the database is the storage
engine...)
Where is the mail going? Perhaps a setting of some kind is
missing?
The configuration really hasn't been messed with too much, so I am
at a
loss as to how to proceed.
Perhaps related to thread: "James can send but cannot receive
email...???"
DK
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
