Okan, once expanded you should no more change the SAR.
You should instead change the expanded version in
jamesfolder/apps/james/SAR-INF/config.xml and then simply restart james.
JAMES will see the config is already there and won't override it.
Stefano
Okan Cetin ha scritto:
According to log file [1], it looks like james using another config.xml. For
example ;
12/05/08 21:26:42 INFO spoolmanager: Matcher All instantiated.
12/05/08 21:26:42 INFO spoolmanager: Mailet PostmasterAlias instantiated.
12/05/08 21:26:42 INFO spoolmanager: Matcher RelayLimit=30 instantiated.
12/05/08 21:26:42 INFO spoolmanager: Mailet Null instantiated.
12/05/08 21:26:42 INFO spoolmanager: Matcher
HasMailAttributeWithValue=org.apache.james.infected, true instantiated
There is a strange behaviour. I commented out PostmasterAlias in the
config.xml. If everything goes well, log file should like this :
12/05/08 21:26:42 INFO spoolmanager: Matcher testMatcher instantiated.
12/05/08 21:26:42 INFO spoolmanager: Mailet testMailet instantiated.
12/05/08 21:26:42 INFO spoolmanager: Matcher RelayLimit=30 instantiated.
12/05/08 21:26:42 INFO spoolmanager: Mailet Null instantiated.
12/05/08 21:26:42 INFO spoolmanager: Matcher
HasMailAttributeWithValue=org.apache.james.infected
My james folder :
/home/slack/works/james_2/james-2.3.1/
sar file :
/home/slack/works/james_2/james-2.3.1/apps/james.sar
james.sar includes /SAR-INF/config.xml :
<processor name="root">
<mailet match="testMatcher" class="testMailet" />
<!-- <mailet match="All" class="PostmasterAlias"/>
<mailet match="All" class="MailetTest"/>
-->
<!-- Important check to avoid looping -->
<mailet match="RelayLimit=30" class="Null"/>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
