Re: comparators and "error"

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Wed, 10 May 2006 14:17 UTC

Message-Id: <uz7vWkOmZkAm0782VYzPfg.md5@libertango.oryx.com>
Date: Wed, 10 May 2006 16:20:46 +0200
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: ietf-mta-filters@imc.org
Subject: Re: comparators and "error"
Cc: Alexey Melnikov <alexey.melnikov@isode.com>
References: <buylDuhckrLTBjUJ7Xr9Kg.md5@libertango.oryx.com> <4461F280.3050900@isode.com>
In-Reply-To: <4461F280.3050900@isode.com>
Content-Type: text/plain; format="flowed"
MIME-Version: 1.0
Sender: owner-ietf-mta-filters@mail.imc.org
Precedence: bulk

Alexey Melnikov writes:
> Arnt Gulbrandsen wrote:
>> 2. Even though a collation specification distinguishes between 
>> "no-match" and "error", there's no requirement that all protocols 
>> must. If the distinction between "no-match" and "error" is pointless 
>> in e.g. sieve, can't simply sieve treat the two as equal? Ie. 
>> "match" is true, "no-match" is false and "error" is false?
>
> Yes, that is a possibility.
>
> Maybe we should add a new match type :failedmatch which can help 
> distinguish the no-match case from the error?

Mark Davis suggested renaming "error" as "undefined". I disagreed then, 
but I think I agree now.

Arnt

comparators and "error" Arnt Gulbrandsen
Re: comparators and "error" Dave Cridland
Re: comparators and "error" Alexey Melnikov
Re: comparators and "error" Arnt Gulbrandsen
Re: comparators and "error" Dave Cridland
Re: comparators and "error" Arnt Gulbrandsen
Re: comparators and "error" Dave Cridland