Yes, I am absolutely sure that message is getting caught by SpamAssassin, I
am adding a special subject to the message which is getting caught by
spamassassin. I am not sure why it's not shown in this log but message is
getting caught by spamassassin.

ClamAV puts messages in other repository (called virus).

2010/8/25 Eric Charles <[email protected]>

>  Hi Max,
>
> From the log, it seems that CLAMD mailet is executed, but not SpamAssassin.
> Are you sure mail is passing via
>
>
>  <mailet
> match="HasMailAttributeWithValue=org.apache.james.spamassassin.flag, YES"
> class="ToProcessor">
>   <processor>spam</processor>
>  </mailet>
>
> and is redirected to the spam processor ?
>
> Log shows that mail is stored in db://maildb/messages/spam/, but is it the
> one of "spam" processor ?
>
> I also don't see the "...
>
> ...reached the end of this processor, and is automatically deleted.  This
> may
> indicate a configuration error."
>
>
> So I wonder if it really goes there?
>
> I will also retest, but it was working at my side (it was reprocessing from
> spam)
>
> Tks,
>
> Eric
>
> PS: I also use James 3 from trunk
>
>
>
>
>
>
> On 25/08/2010 13:51, Max Levinson wrote:
>
>> Hi Eric,
>>
>> Unfortunately configuration which you've suggested is not working for
>> me(just a reminder I am on James 3 from trunk):
>>
>>
>>  <processor name="spam">
>>   <mailet match="All" class="ToRepository">
>>    <repositoryPath>db://maildb/messages/spam/</repositoryPath>
>>    <passTrough>true</passTrough>
>>   </mailet>
>>   <mailet match="[email protected]" class="FromRepository">
>>    <repositoryPath>db://maildb/messages/spam</repositoryPath>
>>    <processor>transport</processor>
>>    <delete>true</delete>
>>   </mailet>
>>  </processor>
>>
>>
>> This is what I am getting in the logs (message is getting caught by
>> spamassassin and it put it into spam repository but FromRepository is not
>> working after that)
>>
>> DEBUG 11:31:20,897 | james.smtpserver | Lookup command handler for
>> command:
>> DATA
>> DEBUG 11:31:21,089 | james.smtpserver | executing james message handler
>> org.apache.james.protocols.smtp.core.esmtp.mailsizeesmtpextens...@a9f827
>> DEBUG 11:31:21,092 | james.smtpserver | executing james message handler
>> org.apache.james.smtpserver.adddefaultattributesmessageh...@8ce0ea
>> DEBUG 11:31:21,104 | james.smtpserver | executing james message handler
>> org.apache.james.smtpserver.sendmailhand...@1023565
>> DEBUG 11:31:21,106 | james.smtpserver | sending mail
>> INFO  11:31:22,217 | james.smtpserver | Successfully spooled mail
>> Mail1282735881052-1 from [email protected] on 209.85.214.182 for [
>> [email protected]]
>> INFO  11:31:22,538 | james.mailetcontext | OK (by CLAMD on localhost/
>> 127.0.0.1)
>> INFO  11:31:31,062 | james.mailetcontext | Storing mail
>> Mail1282735881052-1
>> in db://maildb/messages/spam/
>> DEBUG 11:31:52,383 | james.smtpserver | Lookup command handler for
>> command:
>> QUIT
>>
>>
>> 2010/8/24 Eric Charles<[email protected]>
>>
>>   Hi Max,
>>>
>>> If you define the FromRepository before the ToRepository(spam), the mail
>>> will not reside in the spam repo, so it will be not retrieved during the
>>> processing of itself (probably well retrieved during the processing of
>>> the
>>> following one).
>>>
>>> Moreover, you have to define<passThrough>true</passThrough>  in the
>>> mailet
>>> in your spam processor. This is used to say James to not "Ghost" the mail
>>> and to continue its processing.
>>>
>>> This gives use:
>>>
>>>
>>> <processor name="root">
>>>  <mailet nomatch="SenderHostIsLocal" class="SpamAssassin">
>>>   <spamdHost>localhost</spamdHost>
>>>   <spamdPort>783</spamdPort>
>>>  </mailet>
>>>  <mailet
>>> match="HasMailAttributeWithValue=org.apache.james.spamassassin.flag, YES"
>>> class="ToProcessor">
>>>   <processor>spam</processor>
>>>  </mailet>
>>> </processor>
>>>
>>>
>>>  <processor name="spam">
>>>  <mailet match="All" class="ToRepository">
>>>   <repositoryPath>db://maildb/messages/spam/</repositoryPath>
>>>   <passTrough>true</passTrough>
>>>  </mailet>
>>>  <mailet match="[email protected]" class="FromRepository">
>>>
>>>  <repositoryPath>db://maildb/messages/spam</repositoryPath>
>>>  <processor>   transport</processor>
>>>  <delete>true</delete>
>>>  </mailet>
>>>  </processor>
>>>
>>> I didn't test that exact configuration, but an equivalent one.
>>>
>>> If you leave like that, the [email protected] should be reprocessed by
>>> the
>>> transport processor.
>>> You will have for the other spams a message such as:
>>> WARN  19:55:14,752 | james.spoolmanager | Message Mail1282672514625-3
>>> reached the end of this processor, and is automatically deleted.  This
>>> may
>>> indicate a configuration error.
>>>
>>> If you don't like it, you may add
>>>
>>> <mailet match="All" class="Null"/>
>>>
>>> after the FromRepository mailet.
>>>
>>> Tks,
>>>
>>> Eric
>>>
>>>
>>>
>>> On 24/08/2010 12:54, Max Levinson wrote:
>>>
>>>  It is currently in a root processor.
>>>>
>>>>  <processor name="root">
>>>>   <mailet nomatch="SenderHostIsLocal" class="SpamAssassin">
>>>>    <spamdHost>localhost</spamdHost>
>>>>    <spamdPort>783</spamdPort>
>>>>   </mailet>
>>>>   <mailet
>>>> match="HasMailAttributeWithValue=org.apache.james.spamassassin.flag,
>>>> YES"
>>>> class="ToProcessor">
>>>>    <processor>spam</processor>
>>>>   </mailet>
>>>>   <mailet match="[email protected]" class="FromRepository">
>>>>
>>>>   <repositoryPath>db://maildb/messages/spam</repositoryPath>
>>>>   <processor>   transport</processor>
>>>>   <delete>true</delete>
>>>>   </mailet>
>>>> </processor>
>>>>
>>>>
>>>>  <processor name="spam">
>>>>   <mailet match="All" class="ToRepository">
>>>>    <repositoryPath>db://maildb/messages/spam/</repositoryPath>
>>>>   </mailet>
>>>>  </processor>
>>>>
>>>> They way I see it is if message is already in spam repository and
>>>> recipient
>>>> is [email protected] or any other matcher triggering it, FromRepository
>>>> mailet moves this email to transport processor, sort of release.
>>>>
>>>> Does it make sense, but unfortunately it is not working :(
>>>>
>>>> Maybe I do something wrong, and you need to use FromRepository mailet in
>>>> different way?
>>>>
>>>> Thanks.
>>>>
>>>>
>>>> 2010/8/24 Eric Charles<[email protected]>
>>>>
>>>>
>>>>   Hi Max,
>>>>
>>>>> In which processor (root, transport, spam ?) did you put the
>>>>> FromRepository
>>>>> mailet.
>>>>> I never used it, but I would put it just after the ToRepository in
>>>>> spam.
>>>>>
>>>>> If it still doesn't work at your side, I will give it a try.
>>>>> Tell me...
>>>>>
>>>>> Tks,
>>>>>
>>>>> Eric
>>>>>
>>>>>
>>>>>
>>>>> On 23/08/2010 10:59, Max Levinson wrote:
>>>>>
>>>>>  Hi guys, can anyone help on this?
>>>>>
>>>>>> 2010/8/19 Max Levinson<[email protected]>
>>>>>>
>>>>>>
>>>>>>  Hi Norman,
>>>>>>
>>>>>>  I just got achance to test it, as you know I am on James 3 from
>>>>>>> trunk.
>>>>>>>
>>>>>>> Have anyone actually tried this mailet with James 3.
>>>>>>>
>>>>>>> It's not working for me, unfortunately.
>>>>>>>
>>>>>>>   <mailet match="[email protected]" class="FromRepository">
>>>>>>>   <repositoryPath>db://maildb/messages/spam</repositoryPath>
>>>>>>>   <processor>    transport</processor>
>>>>>>>   <delete>true</delete>
>>>>>>>   </mailet>
>>>>>>>
>>>>>>> It says in the logs that mailet was initialised, but it's not
>>>>>>> resending
>>>>>>> email.
>>>>>>>
>>>>>>> What can be the problem?
>>>>>>>
>>>>>>> 2010/8/16 Norman Maurer<[email protected]>
>>>>>>>
>>>>>>> Hi Max,
>>>>>>>
>>>>>>>  check the FromRepository Mailet...
>>>>>>>
>>>>>>>> http://james.apache.org/server/2.3.2/provided_mailets.html
>>>>>>>>
>>>>>>>> Bye,
>>>>>>>> Norman
>>>>>>>>
>>>>>>>> 2010/8/16 Max Levinson<[email protected]>:
>>>>>>>>
>>>>>>>>  Hi guys,
>>>>>>>>
>>>>>>>>> I have a situation which requires your help, I have this DB
>>>>>>>>> repository:
>>>>>>>>>
>>>>>>>>>  <processor name="spam">
>>>>>>>>>  <mailet match="All" class="ToRepository">
>>>>>>>>>   <repositoryPath>db://maildb/messages/spam/</repositoryPath>
>>>>>>>>>  </mailet>
>>>>>>>>>  </processor>
>>>>>>>>>
>>>>>>>>> All spam goes here, what if a user will decide to release a message
>>>>>>>>> from
>>>>>>>>> this repository(let's say release), how this can be achieved.
>>>>>>>>>
>>>>>>>>> Maybe there is a mailet which can resend a message from repository?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>  ---------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>>  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]
>
>

Reply via email to