I'll paste my cleansed config.xml below. A few facts may help:
-I've disabled servers except the smtp service and spool manager - their
entries are removed from here and from assembly.xml.
-We have a custom mailet - I've tried commenting it out but that has no
effect on the spooler behavior - it decides to regard the mail as spam
either way. When the spam filters are all commented out, our custom
mailet get the mail and handles it as expected, so I'm pretty sure our
custom mailet isn't the culprit.
-I've tried setting enableForwarding="TRUE" but that had no effect on
the behavior I'm seeing.
The goal here is for a message to come in and, if it passes the spam
filters, hit out custom mailet and then, even if our custom processor
doesn't want it, file it in the bit bucket.
Thanks.
-Brad
config.xml:
<?xml version="1.0"?>
<config>
<!-- The James block -->
<James>
<postmaster> [EMAIL PROTECTED] </postmaster>
<!-- 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. -->
<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="FALSE"
enableForwarding="FALSE"/>
<!-- The inbox repository is the location for users inboxes -->
<!-- Default setting: file based repository - enter path ( :///
for absolute) -->
<inboxRepository>
<repository destinationURL="file://var/mail/inboxes/"
type="MAIL">
</repository>
</inboxRepository>
<!-- 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
The user name is used as <repositoryName> for this repository
config.
<inboxRepository>
<repository destinationURL="db://maildb/inbox/"
type="MAIL">
</repository>
</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>
</mailetpackages>
<matcherpackages>
<matcherpackage>org.apache.james.transport.matchers</matcherpackage>
</matcherpackages>
<!-- Processor CONFIGURATION SAMPLE:
root is the first processor all mails enter -->
<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">
</mailet>
<!-- Check for delivery from a known spam server -->
<!-- any of these three anti-spam mailets will dump all messages at the
moment -Brad 041902 -->
<mailet match="InSpammerBlacklist=blackholes.mail-abuse.org"
class="ToProcessor">
<processor> spam </processor>
<notice> Rejected - see http://www.mail-abuse.org/rbl/
</notice>
</mailet>
<!-- currently commented out - isn't working correctly
<mailet match="InSpammerBlacklist=dialups.mail-abuse.org"
class="ToProcessor">
<processor> spam </processor>
<notice> Dialup - see http://www.mail-abuse.org/dul/
</notice>
</mailet>
-->
<!-- currently commented out - isn't working correctly
<mailet match="InSpammerBlacklist=relays.mail-abuse.org"
class="ToProcessor">
<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) -->
<!-- commented out- Brad 041602
<mailet match="RecipientIs=badboy@badhost" class="Null">
</mailet>
-->
<!-- Sends 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>
<!-- <repositoryPath> db://conf/mail-error.properties
</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">
</mailet>
-->
<!-- If you want to notify the postmaster that a message was
marked
as spam, uncomment this -->
<mailet match="All" class="NotifyPostmaster">
</mailet>
</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">
</mailet>
<!-- This matcher-mailet pair can prevent relaying... if you
change
this, you risk making your mail server an open relay point
for
spammers .
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=x.x.x.x,y.y.y.y"
class="ToProcessor">
<processor> spam </processor>
</mailet>
<!-- Custom Processor -Brad 041702 -->
<mailet match="All" class="our.custom.processsor">
<processor-specific-tags>
</processor-specific-tags>
</mailet>
<!-- 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>
<!-- Send all messages reaching this point to the bit bucket -
our processor already had a chance at them -Brad 041702 -->
<mailet match="All" class="Null">
</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>
<!-- <outgoing> db://conf/mail-outgoing.properties
</outgoing> -->
<delayTime> 21600000 </delayTime>
<maxRetries> 5 </maxRetries>
</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 name="spam">
<!-- If you wanted, you could just destroy messages, uncomment
this
matcher/mailet
<mailet match="All" class="Null">
</mailet>
-->
<!-- If you want to notify the sender their message was marked
as
spam, uncomment this
<mailet match="All" class="NotifySender">
</mailet>
-->
<!-- If you want to notify the postmaster that a message was
marked
as spam, uncomment this
<mailet match="All" class="NotifyPostmaster">
</mailet>
-->
<!-- Out of the box, this will log the message to a repository
-->
<mailet match="All" class="ToRepository">
<repositoryPath>file://var/mail/spam/</repositoryPath>
</mailet>
</processor>
</spoolmanager>
<dnsserver>
<servers>
<server>a.a.a.a</server>
</servers>
<authoritative>false</authoritative>
</dnsserver>
<smtpserver>
<port>XXXXX</port>
<bind>d.d.d.d</bind>
<!--<useTLS>TRUE</useTLS> uncomment this if you want to use TLS
(SSL)
on this port -->
<handler>
<!-- helloName is the single host name this instance of James
will
use to identify itself for example, in SMTP and POP3
greetings. If
autodetect is TRUE, James will attempt to discover its own
name OR
use 'localhost'. If autodetect is FALSE, James will use the
value
given OR 'localhost' -->
<helloName autodetect="TRUE">filtered.abc.com</helloName>
<connectiontimeout>360000</connectiontimeout>
<!--<authRequired>true</authRequired> uncomment this if you
want
SMTP AUTH support. This is useful if you have users who need
to use
the email server on the road, while not having your server act
as an
open relay! -->
<!--<verifyIdentity>true</verifyIdentity> uncomment this if
you want
to verify that the MAIL FROM: address is the same user that
authenticated. This prevents a user of your mail server from
acting
as somebody else -->
<!-- This sets the maximum allowed message size for the
smtphandler
in KBytes. The value defaults to 0, which means no limit. -->
<maxmessagesize>0</maxmessagesize>
</handler>
</smtpserver>
<!-- The High Level Storage block -->
<mailstore>
<repositories>
<repository
class="org.apache.james.mailrepository.AvalonMailRepository">
<protocols>
<protocol>file</protocol>
</protocols>
<types>
<type>MAIL</type>
</types>
</repository>
<repository
class="org.apache.james.mailrepository.AvalonSpoolRepository">
<protocols>
<protocol>file</protocol>
</protocols>
<types>
<type>SPOOL</type>
</types>
</repository>
<!-- These repositories store the entire message in the
database -->
<repository
class="org.apache.james.mailrepository.JDBCMailRepository">
<protocols>
<protocol>db</protocol>
</protocols>
<types>
<type>MAIL</type>
</types>
<config>
<sqlFile>file://conf/sqlResources.xml</sqlFile>
</config>
</repository>
<repository
class="org.apache.james.mailrepository.JDBCSpoolRepository">
<protocols>
<protocol>db</protocol>
</protocols>
<types>
<type>SPOOL</type>
</types>
<config>
<sqlFile>file://conf/sqlResources.xml</sqlFile>
</config>
</repository>
<!-- These repositories store message delivery and headers in
the DB, and the body to the filesystem -->
<repository
class="org.apache.james.mailrepository.JDBCMailRepository">
<protocols>
<protocol>dbfile</protocol>
</protocols>
<types>
<type>MAIL</type>
</types>
<config>
<sqlFile>file://conf/sqlResources.xml</sqlFile>
<filestore>file://var/dbmail</filestore>
</config>
</repository>
<repository
class="org.apache.james.mailrepository.JDBCSpoolRepository">
<protocols>
<protocol>dbfile</protocol>
</protocols>
<types>
<type>SPOOL</type>
</types>
<config>
<sqlFile>file://conf/sqlResources.xml</sqlFile>
<filestore>file://var/dbmail</filestore>
</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/) -->
<!-- Default setting: file based repository - enter path ( :///
for absolute) -->
<spoolRepository>
<repository destinationURL="file://var/mail/spool/"
type="SPOOL">
</repository>
</spoolRepository>
<!-- Alternative spool repository definition for JDBC use -->
<!-- <spoolRepository>
<repository destinationURL="db://maildb/message/spool"
type="SPOOL">
</repository>
</spoolRepository>
-->
</mailstore>
<!-- The User Storage block -->
<users-store>
<!-- Configure User Repositories here.
User repositories are required for the following purposes:
- hold information about Users of the James mail server
- hold lists of users for the listserv mailet
Currently, 2 different storage options are available:
- file-based storage using Java serialisation
- database-backed storage
(Use of database or file-system is defined on a
"per-repository" basis)
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>
-->
<!-- An example mailinglist repository, with no "listName"
parameter
specified. Uses the default value from the sql definition
file. -->
<!-- Testing purposes only. -->
<!-- <repository name="list-test"
class="org.apache.james.userrepository.ListUsersJdbcRepository"
destinationURL="db://maildb/lists">
<sqlFile>file://conf/sqlResources.xml</sqlFile>
</repository>
-->
<!-- An example UserRepository for DefaultUser implementations.
-->
<!-- Testing purposes only. -->
<!-- <repository name="default-users"
class="org.apache.james.userrepository.DefaultUsersJdbcRepository"
destinationURL="db://maildb/DefaultUsers">
<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>
</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>
</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)) -->
<!-- The Storage block -->
<objectstorage>
<repositories>
<repository
class="org.apache.avalon.cornerstone.blocks.masterstore.File_Persistent_Object_Repository">
<protocols>
<protocol>file</protocol>
</protocols>
<types>
<type>OBJECT</type>
</types>
<models>
<model>SYNCHRONOUS</model>
<model>ASYNCHRONOUS</model>
<model>CACHE</model>
</models>
</repository>
<repository
class="org.apache.avalon.cornerstone.blocks.masterstore.File_Persistent_Stream_Repository">
<protocols>
<protocol>file</protocol>
</protocols>
<types>
<type>STREAM</type>
</types>
<models>
<model>SYNCHRONOUS</model>
<model>ASYNCHRONOUS</model>
<model>CACHE</model>
</models>
</repository>
</repositories>
</objectstorage>
<!-- The Socket Manager block -->
<sockets>
<server-sockets>
<factory name="plain"
class="org.apache.avalon.cornerstone.blocks.sockets.DefaultServerSocketFactory"
/>
<!--
<factory name="ssl"
class="org.apache.avalon.cornerstone.blocks.sockets.TLSServerSocketFactory">
<keystore>
<file>conf/keystore</file>
<password>secret</password>
<type>JKS</type>
<protocol>TLS</protocol>
<algorithm>SunX509</algorithm>
<authenticate-client>false</authenticate-client>
</keystore>
</factory>
-->
</server-sockets>
<client-sockets>
<factory name="plain"
class="org.apache.avalon.cornerstone.blocks.sockets.DefaultSocketFactory"
/>
</client-sockets>
</sockets>
<thread-manager>
<thread-group>
<name>default</name>
<!-- normal priority == 5, max-priority = 10 -->
<priority>5</priority>
<!-- are threads deamon threads ? -->
<is-daemon>false</is-daemon>
<max-threads>40</max-threads>
<!-- these are ignored at the moment but will be fixed in later
revisions -->
<min-threads>20</min-threads>
<min-spare-threads>20</min-spare-threads>
</thread-group>
</thread-manager>
</config>
-------------------------
Serge Knystautas wrote:
>
> Yes, I would like to understand why that's failing as well, but I don't
> quite know what else to tell you. Can you share the conf for all your
> processors?... this kinda feels like a 'mundane detail' kinda problem
> (for those who've seen the movie Office Space).
> --
> Serge Knystautas
> Loki Technologies - Unstoppable Websites
> http://www.lokitech.com/
>
> Brad Wallace wrote:
> > I have verified that those two servers are not in the blackhost list - I
> > performed a DNS lookup on the inverse addresses as described at
> > mail-abusers.org. ie, for my inbound relay server x, let's say ip is
> > h.i.j.k, I looked up k.j.i.h.blackholes.mail-abusers.org and got:
> >
> > can't find k.j.i.h.blackholes.mail-abuse.org.: Non-existent host/domain
> >
> >
> > You're right, since I'm controlling my inbound relay servers, I can just
> > turn off the spam filters and I should be safe, but I'd like to be
> > confident that I don't need to front james servers with inbound mail
> > relay boxes at all. Or even consider using james servers as those
> > inbound relay boxes.
> >
> >
> > Thanks again.
> >
> >
> > -Brad
> >
> >
> > Serge Knystautas wrote:
> >
> >>Have you checked that servers x.x.x.x and y.y.y.y are not in the
> >>spamming blacklist? That'd be my first and only guess reading over your
> >>email. You are looking at the appropriate logs to see what's happening
> >>with the messages.
> >>
> >>Aside from checking if those servers are in the blacklist, I would even
> >>urge that you comment out the blacklists. You are only allowing
> >>incoming mail from 2 servers to be processed (as I understand it)... the
> >>blacklist filters only check the address of the remote connection, so
> >>since you're already dumping messages from IP addresses aside from those
> >>2, there's no need to also check the blacklists.
> >>--
> >>Serge Knystautas
> >>Loki Technologies - Unstoppable Websites
> >>http://www.lokitech.com/
> >>
> >>Brad Wallace wrote:
> >>
> >>>My blackhole filters, as setup in the default config file, appear to be
> >>>deciding that everything is spam. I've configured my allowed inbound
> >>>servers thus:
> >>>
> >>> <mailet match="RemoteAddrNotInNetwork=x.x.x.x,y.y.y.y"
> >>>class="ToProcessor">
> >>> <processor> spam </processor>
> >>> </mailet>
> >>>
> >>>where x.x.x.x and y.y.y.y. are inbound mail relay servers which deliver
> >>>mail to James. This seems to work fine if I comment out the blackhole
> >>>filters. With any of the three blackhole filters enabled (not commented
> >>>out), all mail gets processes as spam according to the spoolmanager
> >>>logfile. I have the following DNS entry:
> >>>
> >>> <dnsserver>
> >>> <servers>
> >>> <server>a.a.a.a</server>
> >>> </servers>
> >>> <authoritative>false</authoritative>
> >>> </dnsserver>
> >>>
> >>>
> >>>I've verified using nslookup from the command line on the machine
> >>>running james that this DNS server is reachable and functional and that
> >>>neither of my inbound relay servers (x.x.x.x and y.y.y.y) are on any of
> >>>the three blackhole lists. I can retrieve information about
> >>>mail-abuse.org from this DNS server, so I believe the DNS side is fine.
> >>>
> >>>
> >>>Here's the first of my three blackhole list entries (any one of which
> >>>seems to be sufficient for all mail to be classified as spam):
> >>>
> >>> <mailet match="InSpammerBlacklist=blackholes.mail-abuse.org"
> >>> class="ToProcessor">
> >>> <processor> spam </processor>
> >>> <notice> Rejected - see http://www.mail-abuse.org/rbl/
> >>></notice>
> >>> </mailet>
> >>>
> >>>here's what I see in the spoolmanager log:
> >>>
> >>>Fri Apr 19 22:09:44 GMT 2002 [INFO ] (spoolmanager): ==== Begin
> >>>processing mail Mail1019254184039-0 ====
> >>>Fri Apr 19 22:09:44 GMT 2002 [INFO ] (spoolmanager): Processing
> >>>Mail1019254184039-0 through root
> >>>Fri Apr 19 22:09:44 GMT 2002 [DEBUG ] (spoolmanager.root): Servicing
> >>>mail: Mail1019254184039-0
> >>>Fri Apr 19 22:09:44 GMT 2002 [DEBUG ] (spoolmanager.root): Checking
> >>>Mail1019254184039-0 with org.apache.james.transport.matchers.All@55e55f
> >>>Fri Apr 19 22:09:44 GMT 2002 [DEBUG ] (spoolmanager.root): Servicing
> >>>Mail1019254184039-0 by Postmaster aliasing mailet
> >>>Fri Apr 19 22:09:44 GMT 2002 [DEBUG ] (spoolmanager.root): Checking
> >>>Mail1019254184039-0 with
> >>>org.apache.james.transport.matchers.RelayLimit@45c859
> >>>Fri Apr 19 22:09:44 GMT 2002 [DEBUG ] (spoolmanager.root): Checking
> >>>Mail1019254184039-0 with
> >>>org.apache.james.transport.matchers.InSpammerBlacklist@2c1e6b
> >>>Fri Apr 19 22:09:44 GMT 2002 [DEBUG ] (spoolmanager.root): Servicing
> >>>Mail1019254184039-0 by ToProcessor Mailet
> >>>Fri Apr 19 22:09:44 GMT 2002 [INFO ] (spoolmanager): ==== Begin
> >>>processing mail Mail1019254184039-0-!917652054 ====
> >>>Fri Apr 19 22:09:44 GMT 2002 [INFO ] (spoolmanager): Processing
> >>>Mail1019254184039-0-!917652054 through spam
> >>>Fri Apr 19 22:09:44 GMT 2002 [DEBUG ] (spoolmanager.spam): Servicing
> >>>mail: Mail1019254184039-0-!917652054
> >>>Fri Apr 19 22:09:44 GMT 2002 [DEBUG ] (spoolmanager.spam): Checking
> >>>Mail1019254184039-0-!917652054 with
> >>>org.apache.james.transport.matchers.All@5b05b2
> >>>Fri Apr 19 22:09:44 GMT 2002 [DEBUG ] (spoolmanager.spam): Servicing
> >>>Mail1019254184039-0-!917652054 by ToRepository Mailet
> >>>Fri Apr 19 22:09:44 GMT 2002 [INFO ] (spoolmanager): ==== Removed from
> >>>spool mail Mail1019254184039-0-!917652054 ====
> >>>Fri Apr 19 22:09:44 GMT 2002 [INFO ] (spoolmanager): ==== Removed from
> >>>spool mail Mail1019254184039-0-!917652054 ====
> >>>
> >>>
> >>>and the mail ends up in my spam folder.
> >>>
> >>>I'm running James 2.0a2 on solaris under java-1.3.1_02.
> >>>
> >>>
> >>>Please let me know if I can provide more details. Thanks much.
> >>>
> >>>
> >>>-Brad
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
