I see some unwanted behavior during using spamtest extension.
For example using simple rules from this page:
http://www.ietf.org/rfc/rfc3685.txt?number=3685
require ["spamtest", "fileinto", "relational", "comparator-i;ascii-numeric"];
if spamtest :value "eq" :comparator "i;ascii-numeric" "0"
{
fileinto "INBOX.unclassified";
}
elsif spamtest :value "ge" :comparator "i;ascii-numeric" "3"
{
fileinto "INBOX.spam-trap";
}
One message is checked twice using this rules.
Igor Brezac wrote:
>
> I have already done rfc spamtest and virustest extensions,
> https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=2400, I still need to
> do develop hooks for the backends. I've been too busy with my regular
> job lately, I hope to have something soon...
>
> -Igor
>
> On Thu, 31 Mar 2005, Andrew B. Panphiloff wrote:
>
>> Yesterday, I have ported sieve-spamasssassin patch from contrib
>> directory to cyrus-imapd-2.2.12 (see attachment).
>> Can anybody help me to do this patch rfc-compatible ?
>>
>> Ken Murchison wrote:
>>
>>> Andrew B. Panphiloff wrote:
>>>
>>>> Does cyrus-imapd support thees extensions ?
>>>
>>>
>>>
>>> Not currently.
>>>
>>>
>>>
>>
>>
>
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
