I thought about something like that as a possible reason, but I didn't
even get a DNS lookup for relays.ordb.org, so I assumed that something
else must be wrong as well. I haven't had time to check the
implementation of the matcher, but perhaps the source code should be
checked as well, making sure that the matcher don't match if the spam
check fails. Or perhaps my running James instance had an old IP address
cached for relays.ordb.org and some new system was hooked up to the old
IP address?
Tor
Bernd Fondermann schrieb:
According to this credible report
http://isc.sans.org/diary.html?storyid=4198&rss
which says
"Although ORDB.org was shut down on December 18, 2006, yesterday they
changed their behaviour, and instead of timing out, they are blocking
all IP addresses, that is, every e-mail server queried is being
reported as an open relay."
I think it is best to recommend that all James users should change
their configuration and remove ORDB.org immediately.
I will check the configuration source files in svn and open a JIRA to
remove ORDB.org from them if they are still contained.
Thanks,
Bernd
On Fri, Mar 28, 2008 at 12:25 AM, Tor-Einar Jarnbjo
<[EMAIL PROTECTED]> wrote:
I had the same problem a few days ago and the mailet with a match for
"InSpammerBlacklist=relays.ordb.org.", which redirects the mails to the
spam processor was found as the cause. In the default configuration,
James checks the blacklists njabl.org and ordb.org for known spam
sources and redirect the mails to a black hole if they match. ordb.org
has been down for several months now, but something must have happened
recently, causing the matcher to match all mails.
Tor
Hans Liebenberg schrieb:
Hi,
>
> All of a sudden after running perfectly for many months, my James
> server has started to route all smtp traffic to the SPAM processor.
> I have left my spam configuration as it was by default, i.e I haven't
> enabled any spam mailets e.g InSpammerBlacklist
>
> I have enabled DEBUG logging on my spool manager and I get the
> following output
>
>
> smtp log:
>
> 27/03/08 10:09:26 INFO smtpserver: Successfully spooled mail
> Mail1206605366485-1414 from [EMAIL PROTECTED] on
> 127.0.0.1 for [EMAIL PROTECTED]
>
> spoolmanager log:
>
> 27/03/08 10:09:26 DEBUG spoolmanager: Processing
> Mail1206605366485-1414 through root
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Servicing mail:
> Mail1206605366485-1414
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366485-1414 with
> [EMAIL PROTECTED]
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Servicing
> Mail1206605366485-1414 by Postmaster aliasing mailet
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366485-1414 with
> [EMAIL PROTECTED]
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366485-1414 with
> [EMAIL PROTECTED]
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366485-1414 with
> [EMAIL PROTECTED]
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366485-1414 with
> [EMAIL PROTECTED]
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366485-1414 with
> [EMAIL PROTECTED]
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366485-1414 with
> [EMAIL PROTECTED]
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366485-1414 with
> [EMAIL PROTECTED]
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366485-1414 with
> [EMAIL PROTECTED]
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366485-1414 with
> [EMAIL PROTECTED]
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366485-1414 with
> [EMAIL PROTECTED]
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366485-1414 with
> [EMAIL PROTECTED]
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Servicing
> Mail1206605366485-1414 by Set Mail Attribute Mailet
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366485-1414 with
> [EMAIL PROTECTED]
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366485-1414 with
> [EMAIL PROTECTED]
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366485-1414 with
> [EMAIL PROTECTED]
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366485-1414 with
> [EMAIL PROTECTED]
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366291-1413 with
> [EMAIL PROTECTED]
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Servicing
> Mail1206605366485-1414 by ToProcessor Mailet
> 27/03/08 10:09:26 DEBUG spoolmanager: Processed Mail1206605366485-1414
> through root
> 27/03/08 10:09:26 DEBUG spoolmanager: Result was spam
>
>
>
> How can I find out WHY it is resulting as spam from the root processor
> (which has no ToRepository=spam configs enabled).
> I have checked other log files but cant seem to find anything.
>
> Thanks Alot
> Hans
>
>
> ---------------------------------------------------------------------
> 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]
---------------------------------------------------------------------
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]
