This:
19/09/02 09:55:06 DEBUG spoolmanager.root: Checking Mail with RelayLimit
19/09/02 09:55:06 DEBUG spoolmanager.root: Checking Mail with
InSpammerBlacklist
19/09/02 09:55:07 DEBUG spoolmanager.root: Servicing Mail by ToProcessor
Mailet
implies that the first InSpammerBlacklist matcher is trapping your message:
<mailet match="InSpammerBlacklist=blackholes.mail-abuse.org"
class="ToProcessor">
What happens if you manually lookup the sender's reversed IP address
prepended to that zone name?
--- Noel
-----Original Message-----
From: Svante Berglund [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 19, 2002 16:32
To: 'James Users List'
Subject: blackhole filters decide everything is spam
Hi all.
"My blackhole filters, as setup in the default config file, appear to be
deciding that everything is spam." This is quoted from a mail I found in
the james-user archive and it describes my problem pretty well.
According to the conversation back then (2002-04-19) nobody had any real
suggestions other than only allowing one or two servers sending incoming
mail (remoteAddrNotInNetwork). Since I have the same problem I�m curious
if someone has found a solution to the problem (maybe it�s in my
config?).
Regards
Svante
Ps I�m sending this through my old james 1.2.1 which works fine with the
spam-check
Win2k
James 2.1a1
>From config.xml
<!-- 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>
<notice> Rejected - see http://www.mail-abuse.org/rbl/
</notice>
</mailet>
<mailet match="InSpammerBlacklist=dialups.mail-abuse.org"
class="ToProcessor">
<processor> spam </processor>
<notice> Dialup - see http://www.mail-abuse.org/dul/
</notice>
</mailet>-->
<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) -->
<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 -->
<!-- <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.*"-->
<mailet match="RemoteAddrNotInNetwork=127.0.0.1,217.215.75.111"
class="ToProcessor">
<processor> spam </processor>
</mailet>
>From spoolmanager
19/09/02 09:55:06 INFO spoolmanager: ==== Begin processing mail
Mail1032465306310-1====
19/09/02 09:55:06 INFO spoolmanager: Processing Mail1032465306310-1
through root
19/09/02 09:55:06 DEBUG spoolmanager.root: Servicing mail:
Mail1032465306310-1
19/09/02 09:55:06 DEBUG spoolmanager.root: Checking Mail1032465306310-1
with org.apache.james.transport.matchers.All@d53f5b
19/09/02 09:55:06 DEBUG spoolmanager.root: Servicing Mail1032465306310-1
by Postmaster aliasing mailet
19/09/02 09:55:06 DEBUG spoolmanager.root: Checking Mail1032465306310-1
with org.apache.james.transport.matchers.SenderInFakeDomain@329642
19/09/02 09:55:06 DEBUG spoolmanager.root: Checking Mail1032465306310-1
with org.apache.james.transport.matchers.RelayLimit@1bed71
19/09/02 09:55:06 DEBUG spoolmanager.root: Checking Mail1032465306310-1
with org.apache.james.transport.matchers.InSpammerBlacklist@cbdb20
19/09/02 09:55:07 DEBUG spoolmanager.root: Servicing Mail1032465306310-1
by ToProcessor Mailet
19/09/02 09:55:07 INFO spoolmanager: ==== Begin processing mail
Mail1032465306310-1====
19/09/02 09:55:07 INFO spoolmanager: Processing Mail1032465306310-1
through spam
19/09/02 09:55:07 DEBUG spoolmanager.spam: Servicing mail:
Mail1032465306310-1
19/09/02 09:55:07 DEBUG spoolmanager.spam: Checking Mail1032465306310-1
with org.apache.james.transport.matchers.All@f64158
19/09/02 09:55:07 DEBUG spoolmanager.spam: Servicing Mail1032465306310-1
by ToRepository Mailet
19/09/02 09:55:07 INFO spoolmanager: ==== Removed from spool mail
Mail1032465306310-1====
--
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]>
