Re: [sieve] Sieve deleteheader and :count match type

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Tue, 17 January 2017 12:20 UTC

From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: sieve@ietf.org
Date: Tue, 17 Jan 2017 12:20:13 +0000
User-Agent: Trojita/v0.5-9-g8961725; Qt/4.8.6; X11; Linux; Devuan GNU/Linux 1.0 (jessie)
Mime-Version: 1.0
Message-Id: <b5c375c0-6617-4cf1-8721-5f19d39ed3f1@gulbrandsen.priv.no>
In-Reply-To: <01Q9RHX13ZFM00004H@mauve.mrochek.com>
References: <82102421-fed0-13eb-f557-83c878618a04@andrew.cmu.edu> <01Q9RHX13ZFM00004H@mauve.mrochek.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/sieve/Uqgxz0_KLfbQT5Yqa-2qFzpC_Yk>
Subject: Re: [sieve] Sieve deleteheader and :count match type
Precedence: list

NED+mta-filters@mauve.mrochek.com writes:
> I also don't think that saying that :count tests perform a preliminary count 
> like :index :last is especially useful - can you think of a case where you'd 
> want to delete all headers of a given type based on how many of them are 
> present? I can't.

It's far-fetched, but deleting both subject fields if there are two or 
more? I think most people choose to use the first. Choosing to delete both 
isn't entirely unreasonable, though.

The same applies to other header fields that may occur at most once.

Arnt

[sieve] Sieve deleteheader and :count match type Ken Murchison
Re: [sieve] Sieve deleteheader and :count match t… NED+mta-filters
Re: [sieve] Sieve deleteheader and :count match t… Ken Murchison
Re: [sieve] Sieve deleteheader and :count match t… Arnt Gulbrandsen
Re: [sieve] Sieve deleteheader and :count match t… NED+mta-filters
Re: [sieve] Sieve deleteheader and :count match t… Arnt Gulbrandsen