You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by Danny Angus <da...@apache.org> on 2008/03/19 13:08:21 UTC
Apache James Google Summer of Code 2008
The Apache James team (http://james.apache.org) are pleased to
announce that once more we are proposing ideas for Google Summer of
Code student projects.
This years ideas are:
1) To develop a VERP[1] Mailet to allow James to write VERP modified
return addresses on outbound messages, and an inbound mailet/matcher
to identify VERP bounces and invoke configurable "do something" code.
2) James' provided mailing list manager is fine for small closed
groups, but lacks the functionality of a more robust MLM, the project
is to add some all or more of the following features: subscriber and
message moderation, double opt-in and bounce handling.
We all look forward to welcoming Student proposals for these or any
other ideas, and would welcome discussion of the ideas on the James
Server Developers mailing list [2].
[1] VERP - http://cr.yp.to/proto/verp.txt
[2] James mailing lists - http://james.apache.org/mail.html
Danny Angus (PMC Chair Apache James) on behalf of the Apache James Project.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: All messages going to SPAM processor
Posted by Tor-Einar Jarnbjo <to...@jarnbjo.name>.
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
> <to...@jarnbjo.name> 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 noreply@newsletter.marketingweb.co.za on
>> > 127.0.0.1 for [bambombonani@hotmail.com]
>> >
>> > 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
>> > org.apache.james.transport.matchers.All@3c2d7440
>> > 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
>> > org.apache.james.transport.matchers.RecipientIs@4c2b349d
>> > 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
>> > Mail1206605366485-1414 with
>> > org.apache.james.transport.matchers.RecipientIs@288b567c
>> > 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
>> > Mail1206605366485-1414 with
>> > com.cambrient.mailstreams.mailend.mm.InitMatcher@53dafbaf
>> > 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
>> > Mail1206605366485-1414 with
>> > com.cambrient.mailstreams.mailend.mm.ContactsuiteMatcher@4dc1c92b
>> > 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
>> > Mail1206605366485-1414 with
>> > com.cambrient.mailstreams.mailend.mm.ContactsuiteVerifierMatcher@7e717d91
>> > 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
>> > Mail1206605366485-1414 with
>> > com.cambrient.mailstreams.mailend.mm.ContactsuiteDAMatcher@4ceafb71
>> > 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
>> > Mail1206605366485-1414 with
>> > org.apache.james.transport.matchers.FetchedFrom@5721df2a
>> > 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
>> > Mail1206605366485-1414 with
>> > org.apache.james.transport.matchers.RelayLimit@70c26b16
>> > 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
>> > Mail1206605366485-1414 with
>> > org.apache.james.transport.matchers.HasMailAttributeWithValue@2682d210
>> > 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
>> > Mail1206605366485-1414 with
>> > org.apache.james.transport.matchers.HasMailAttribute@56ad2c30
>> > 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
>> > Mail1206605366485-1414 with
>> > org.apache.james.transport.matchers.All@3302fc5
>> > 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
>> > org.apache.james.transport.matchers.SMTPAuthSuccessful@50903025
>> > 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
>> > Mail1206605366485-1414 with
>> > org.apache.james.transport.matchers.InSpammerBlacklist@2a48f675
>> > 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
>> > Mail1206605366485-1414 with
>> > org.apache.james.transport.matchers.InSpammerBlacklist@3b8e609b
>> > 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
>> > Mail1206605366485-1414 with
>> > org.apache.james.transport.matchers.InSpammerBlacklist@4ec1a0eb
>> > 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
>> > Mail1206605366291-1413 with
>> > org.apache.james.transport.matchers.InSpammerBlacklist@3b8e609b
>> > 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: server-user-unsubscribe@james.apache.org
>> > For additional commands, e-mail: server-user-help@james.apache.org
>> >
>> >
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-user-help@james.apache.org
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: All messages going to SPAM processor
Posted by Bernd Fondermann <be...@googlemail.com>.
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
<to...@jarnbjo.name> 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 noreply@newsletter.marketingweb.co.za on
> > 127.0.0.1 for [bambombonani@hotmail.com]
> >
> > 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
> > org.apache.james.transport.matchers.All@3c2d7440
> > 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
> > org.apache.james.transport.matchers.RecipientIs@4c2b349d
> > 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> > Mail1206605366485-1414 with
> > org.apache.james.transport.matchers.RecipientIs@288b567c
> > 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> > Mail1206605366485-1414 with
> > com.cambrient.mailstreams.mailend.mm.InitMatcher@53dafbaf
> > 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> > Mail1206605366485-1414 with
> > com.cambrient.mailstreams.mailend.mm.ContactsuiteMatcher@4dc1c92b
> > 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> > Mail1206605366485-1414 with
> > com.cambrient.mailstreams.mailend.mm.ContactsuiteVerifierMatcher@7e717d91
> > 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> > Mail1206605366485-1414 with
> > com.cambrient.mailstreams.mailend.mm.ContactsuiteDAMatcher@4ceafb71
> > 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> > Mail1206605366485-1414 with
> > org.apache.james.transport.matchers.FetchedFrom@5721df2a
> > 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> > Mail1206605366485-1414 with
> > org.apache.james.transport.matchers.RelayLimit@70c26b16
> > 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> > Mail1206605366485-1414 with
> > org.apache.james.transport.matchers.HasMailAttributeWithValue@2682d210
> > 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> > Mail1206605366485-1414 with
> > org.apache.james.transport.matchers.HasMailAttribute@56ad2c30
> > 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> > Mail1206605366485-1414 with
> > org.apache.james.transport.matchers.All@3302fc5
> > 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
> > org.apache.james.transport.matchers.SMTPAuthSuccessful@50903025
> > 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> > Mail1206605366485-1414 with
> > org.apache.james.transport.matchers.InSpammerBlacklist@2a48f675
> > 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> > Mail1206605366485-1414 with
> > org.apache.james.transport.matchers.InSpammerBlacklist@3b8e609b
> > 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> > Mail1206605366485-1414 with
> > org.apache.james.transport.matchers.InSpammerBlacklist@4ec1a0eb
> > 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> > Mail1206605366291-1413 with
> > org.apache.james.transport.matchers.InSpammerBlacklist@3b8e609b
> > 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: server-user-unsubscribe@james.apache.org
> > For additional commands, e-mail: server-user-help@james.apache.org
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: All messages going to SPAM processor
Posted by Hans Liebenberg <ha...@cambrient.com>.
Brilliant that worked! I thought my InSpammerBlacklist was already
commented out in the config file but I read it incorrectly.
But I guess I still need to investigate why we are listed there as
receiving smtp servers may be checking against it too.
Thanks!
Tor-Einar Jarnbjo 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 noreply@newsletter.marketingweb.co.za on
>> 127.0.0.1 for [bambombonani@hotmail.com]
>>
>> 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
>> org.apache.james.transport.matchers.All@3c2d7440
>> 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
>> org.apache.james.transport.matchers.RecipientIs@4c2b349d
>> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
>> Mail1206605366485-1414 with
>> org.apache.james.transport.matchers.RecipientIs@288b567c
>> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
>> Mail1206605366485-1414 with
>> com.cambrient.mailstreams.mailend.mm.InitMatcher@53dafbaf
>> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
>> Mail1206605366485-1414 with
>> com.cambrient.mailstreams.mailend.mm.ContactsuiteMatcher@4dc1c92b
>> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
>> Mail1206605366485-1414 with
>> com.cambrient.mailstreams.mailend.mm.ContactsuiteVerifierMatcher@7e717d91
>>
>> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
>> Mail1206605366485-1414 with
>> com.cambrient.mailstreams.mailend.mm.ContactsuiteDAMatcher@4ceafb71
>> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
>> Mail1206605366485-1414 with
>> org.apache.james.transport.matchers.FetchedFrom@5721df2a
>> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
>> Mail1206605366485-1414 with
>> org.apache.james.transport.matchers.RelayLimit@70c26b16
>> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
>> Mail1206605366485-1414 with
>> org.apache.james.transport.matchers.HasMailAttributeWithValue@2682d210
>> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
>> Mail1206605366485-1414 with
>> org.apache.james.transport.matchers.HasMailAttribute@56ad2c30
>> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
>> Mail1206605366485-1414 with
>> org.apache.james.transport.matchers.All@3302fc5
>> 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
>> org.apache.james.transport.matchers.SMTPAuthSuccessful@50903025
>> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
>> Mail1206605366485-1414 with
>> org.apache.james.transport.matchers.InSpammerBlacklist@2a48f675
>> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
>> Mail1206605366485-1414 with
>> org.apache.james.transport.matchers.InSpammerBlacklist@3b8e609b
>> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
>> Mail1206605366485-1414 with
>> org.apache.james.transport.matchers.InSpammerBlacklist@4ec1a0eb
>> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
>> Mail1206605366291-1413 with
>> org.apache.james.transport.matchers.InSpammerBlacklist@3b8e609b
>> 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: server-user-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-user-help@james.apache.org
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: All messages going to SPAM processor
Posted by Dennis Thrysøe <dt...@conscius.com>.
They began returning false positives to make people stop using the
service :)
I saw the story on slashdot a couple of days ago.
-dennis
Tor-Einar Jarnbjo 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: All messages going to SPAM processor
Posted by Tor-Einar Jarnbjo <to...@jarnbjo.name>.
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 noreply@newsletter.marketingweb.co.za on
> 127.0.0.1 for [bambombonani@hotmail.com]
>
> 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
> org.apache.james.transport.matchers.All@3c2d7440
> 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
> org.apache.james.transport.matchers.RecipientIs@4c2b349d
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366485-1414 with
> org.apache.james.transport.matchers.RecipientIs@288b567c
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366485-1414 with
> com.cambrient.mailstreams.mailend.mm.InitMatcher@53dafbaf
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366485-1414 with
> com.cambrient.mailstreams.mailend.mm.ContactsuiteMatcher@4dc1c92b
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366485-1414 with
> com.cambrient.mailstreams.mailend.mm.ContactsuiteVerifierMatcher@7e717d91
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366485-1414 with
> com.cambrient.mailstreams.mailend.mm.ContactsuiteDAMatcher@4ceafb71
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366485-1414 with
> org.apache.james.transport.matchers.FetchedFrom@5721df2a
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366485-1414 with
> org.apache.james.transport.matchers.RelayLimit@70c26b16
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366485-1414 with
> org.apache.james.transport.matchers.HasMailAttributeWithValue@2682d210
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366485-1414 with
> org.apache.james.transport.matchers.HasMailAttribute@56ad2c30
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366485-1414 with
> org.apache.james.transport.matchers.All@3302fc5
> 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
> org.apache.james.transport.matchers.SMTPAuthSuccessful@50903025
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366485-1414 with
> org.apache.james.transport.matchers.InSpammerBlacklist@2a48f675
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366485-1414 with
> org.apache.james.transport.matchers.InSpammerBlacklist@3b8e609b
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366485-1414 with
> org.apache.james.transport.matchers.InSpammerBlacklist@4ec1a0eb
> 27/03/08 10:09:26 DEBUG spoolmanager.root: Checking
> Mail1206605366291-1413 with
> org.apache.james.transport.matchers.InSpammerBlacklist@3b8e609b
> 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: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
All messages going to SPAM processor
Posted by Hans Liebenberg <ha...@cambrient.com>.
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 noreply@newsletter.marketingweb.co.za on 127.0.0.1 for [bambombonani@hotmail.com]
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 org.apache.james.transport.matchers.All@3c2d7440
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 org.apache.james.transport.matchers.RecipientIs@4c2b349d
27/03/08 10:09:26 DEBUG spoolmanager.root: Checking Mail1206605366485-1414 with org.apache.james.transport.matchers.RecipientIs@288b567c
27/03/08 10:09:26 DEBUG spoolmanager.root: Checking Mail1206605366485-1414 with com.cambrient.mailstreams.mailend.mm.InitMatcher@53dafbaf
27/03/08 10:09:26 DEBUG spoolmanager.root: Checking Mail1206605366485-1414 with com.cambrient.mailstreams.mailend.mm.ContactsuiteMatcher@4dc1c92b
27/03/08 10:09:26 DEBUG spoolmanager.root: Checking Mail1206605366485-1414 with com.cambrient.mailstreams.mailend.mm.ContactsuiteVerifierMatcher@7e717d91
27/03/08 10:09:26 DEBUG spoolmanager.root: Checking Mail1206605366485-1414 with com.cambrient.mailstreams.mailend.mm.ContactsuiteDAMatcher@4ceafb71
27/03/08 10:09:26 DEBUG spoolmanager.root: Checking Mail1206605366485-1414 with org.apache.james.transport.matchers.FetchedFrom@5721df2a
27/03/08 10:09:26 DEBUG spoolmanager.root: Checking Mail1206605366485-1414 with org.apache.james.transport.matchers.RelayLimit@70c26b16
27/03/08 10:09:26 DEBUG spoolmanager.root: Checking Mail1206605366485-1414 with org.apache.james.transport.matchers.HasMailAttributeWithValue@2682d210
27/03/08 10:09:26 DEBUG spoolmanager.root: Checking Mail1206605366485-1414 with org.apache.james.transport.matchers.HasMailAttribute@56ad2c30
27/03/08 10:09:26 DEBUG spoolmanager.root: Checking Mail1206605366485-1414 with org.apache.james.transport.matchers.All@3302fc5
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 org.apache.james.transport.matchers.SMTPAuthSuccessful@50903025
27/03/08 10:09:26 DEBUG spoolmanager.root: Checking Mail1206605366485-1414 with org.apache.james.transport.matchers.InSpammerBlacklist@2a48f675
27/03/08 10:09:26 DEBUG spoolmanager.root: Checking Mail1206605366485-1414 with org.apache.james.transport.matchers.InSpammerBlacklist@3b8e609b
27/03/08 10:09:26 DEBUG spoolmanager.root: Checking Mail1206605366485-1414 with org.apache.james.transport.matchers.InSpammerBlacklist@4ec1a0eb
27/03/08 10:09:26 DEBUG spoolmanager.root: Checking Mail1206605366291-1413 with org.apache.james.transport.matchers.InSpammerBlacklist@3b8e609b
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: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org