noel 2003/06/15 22:33:02
Modified: src/conf Tag: branch_2_1_fcs james-config.xml
Log:
Refactored processors for error-handling. Added comments. Default to using
<authorizedAddresses> for SMTP handler instead of RemoteAddrNotInNetwork. Added
comments.
Revision Changes Path
No revision
No revision
1.40.2.11 +72 -16 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.40.2.10
retrieving revision 1.40.2.11
diff -u -r1.40.2.10 -r1.40.2.11
--- james-config.xml 7 Jun 2003 00:25:50 -0000 1.40.2.10
+++ james-config.xml 16 Jun 2003 05:33:02 -0000 1.40.2.11
@@ -198,6 +198,14 @@
<!-- By default configuration all email that generates an error in placed in
-->
<!-- an error repository. -->
<processor name="error">
+ <!-- If you want to notify the sender their message generated an error,
uncomment this -->
+ <!--
+ <mailet match="All" class="Bounce"/>
+ -->
+ <!-- If you want to notify the postmaster that a message generated an
error, uncomment this -->
+ <!--
+ <mailet match="All" class="NotifyPostmaster"/>
+ -->
<!-- Logs any messages to the repository specified -->
<mailet match="All" class="ToRepository">
@@ -206,17 +214,7 @@
<!--
<repositoryPath> db://maildb/deadletter/error </repositoryPath>
-->
- <passThrough> true </passThrough>
</mailet>
-
- <!-- If you want to notify the sender their message generated an error,
uncomment this -->
- <!--
- <mailet match="All" class="Bounce"/>
- -->
- <!-- If you want to notify the postmaster that a message generated an
error, uncomment this -->
- <!--
- <mailet match="All" class="NotifyPostmaster"/>
- -->
</processor>
<!-- Processor CONFIGURATION SAMPLE: transport is a sample custom processor
for local or -->
@@ -229,7 +227,8 @@
<!-- 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>
+ <processor> local-address-error </processor>
+ <notice>550 - Requested action not taken: no such user here</notice>
</mailet>
<!-- CHECKME! -->
@@ -239,7 +238,7 @@
<!-- rejected as spam. This is one method of preventing your -->
<!-- server from being used as an open relay. Make sure you understand -->
<!-- how to prevent your server from becoming an open relay before -->
- <!-- changing this configuration. -->
+ <!-- changing this configuration. See also <authorizedAddresses> in SMTP
Server -->
<!-- -->
<!-- This matcher/mailet combination must come after local delivery has -->
<!-- been performed. Otherwise local users will not be able to receive -->
@@ -254,7 +253,8 @@
<!-- If you are using SMTP authentication then you can (and generally -->
<!-- should) disable this matcher/mailet pair. -->
<mailet match="RemoteAddrNotInNetwork=127.0.0.1" class="ToProcessor">
- <processor> spam </processor>
+ <processor> relay-denied </processor>
+ <notice>550 - Requested action not taken: relaying denied</notice>
</mailet>
<!-- Attempt remote delivery using the specified repository for the spool,
-->
@@ -333,6 +333,56 @@
-->
</mailet>
</processor>
+
+ <!-- This processor handles messages that are for local domains, where the
user is unknown -->
+ <processor name="local-address-error">
+ <!-- To notify the sender the address was invalid, uncomment this
matcher/mailet configuration -->
+ <!-- The original message is not attached to keep the bounce processor
from deliverying spam -->
+ <!--
+ <mailet match="All" class="Bounce">
+ <attachment>none</attachment>
+ </mailet>
+ -->
+
+ <!-- To notify the postmaster that a message had an invalid address,
uncomment this matcher/mailet configuration -->
+ <!--
+ <mailet match="All" class="NotifyPostmaster"/>
+ -->
+
+ <mailet match="All" class="ToRepository">
+ <repositoryPath> file://var/mail/address-error/</repositoryPath>
+ <!-- An alternative database repository example follows. -->
+ <!--
+ <repositoryPath> db://maildb/deadletter/address-error </repositoryPath>
+ -->
+ </mailet>
+ </processor>
+
+ <!-- This processor handles messages that are for foreign domains, where
relaying is denied -->
+ <!-- As of James v2.2, this processor can be deprecated by using the
<authorizedAddresses> tag
+ in the SMTP Server, and rejecting the message in the protocol
transaction. -->
+ <processor name="relay-denied">
+ <!-- To notify the sender the address was invalid, uncomment this
matcher/mailet configuration -->
+ <!-- The original message is not attached to keep the bounce processor
from deliverying spam -->
+ <!--
+ <mailet match="All" class="Bounce">
+ <attachment>none</attachment>
+ </mailet>
+ -->
+
+ <!-- To notify the postmaster that a relay request was denied, uncomment
this matcher/mailet configuration -->
+ <!--
+ <mailet match="All" class="NotifyPostmaster"/>
+ -->
+
+ <mailet match="All" class="ToRepository">
+ <repositoryPath>file://var/mail/relay-denied/</repositoryPath>
+ <!-- An alternative database repository example follows. -->
+ <!--
+ <repositoryPath> db://maildb/deadletter/relay-denied </repositoryPath>
+ -->
+ </mailet>
+ </processor>
</spoolmanager>
<!-- DNS Server Block -->
@@ -449,6 +499,7 @@
<authRequired>true</authRequired>
-->
+<!-- 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
@@ -459,10 +510,11 @@
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>
- -->
<!-- Uncomment this if you want to verify sender addresses, ensuring that
-->
<!-- the sender address matches the user who has authenticated. -->
@@ -522,6 +574,10 @@
<articleIDDomainSuffix>news.james.apache.org</articleIDDomainSuffix>
<!-- The news groups hosted in this NNTP repository. -->
+ <!-- Groups here will be added to those found in the file system,
+ but removing groups from here will NOT remove them from the
+ server. Change <newsgroups> to <newsgroups only="true"> to
+ restrict newsgroups to ONLY those found in this list. -->
<newsgroups>
<newsgroup>org.apache.james.dev</newsgroup>
<newsgroup>org.apache.james.user</newsgroup>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
