Re: [imap5] Feature set? - was Re: Designing a new replacement protocol for IMAP
Brandon Long <blong@google.com> Wed, 22 February 2012 21:29 UTC
Return-Path: <blong@google.com>
X-Original-To: imap5@ietfa.amsl.com
Delivered-To: imap5@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B35321E8034 for <imap5@ietfa.amsl.com>; Wed, 22 Feb 2012 13:29:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.849
X-Spam-Level:
X-Spam-Status: No, score=-102.849 tagged_above=-999 required=5 tests=[AWL=0.128, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DrLQO3Z8w5Av for <imap5@ietfa.amsl.com>; Wed, 22 Feb 2012 13:29:00 -0800 (PST)
Received: from mail-qw0-f51.google.com (mail-qw0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4A29E21E801F for <imap5@ietf.org>; Wed, 22 Feb 2012 13:29:00 -0800 (PST)
Received: by qan41 with SMTP id 41so686722qan.10 for <imap5@ietf.org>; Wed, 22 Feb 2012 13:28:59 -0800 (PST)
Received-SPF: pass (google.com: domain of blong@google.com designates 10.229.134.199 as permitted sender) client-ip=10.229.134.199;
Authentication-Results: mr.google.com; spf=pass (google.com: domain of blong@google.com designates 10.229.134.199 as permitted sender) smtp.mail=blong@google.com; dkim=pass header.i=blong@google.com
Received: from mr.google.com ([10.229.134.199]) by 10.229.134.199 with SMTP id k7mr17454408qct.60.1329946139917 (num_hops = 1); Wed, 22 Feb 2012 13:28:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding:x-system-of-record; bh=xBooyYpdx2166dyPXQYmiAnHhmbgZgTrWFicFtCgNKU=; b=gAl6y0DbxBaCo695rf7vZieLFssKMQx6U1gwQzwzG4czfaZQ4Mx5f4d4czXkU0fsW9 92uwDAHDZ1768XQncxDpVBti4hZPUkBA0DBQsQ6fP4lFnpefRBDm+uJuybOPQl2FDmjq G7mnpKJVPk5Yv0mmmXlzs7mykAqnA8jfOjV7o=
Received: by 10.229.134.199 with SMTP id k7mr14758259qct.60.1329946139739; Wed, 22 Feb 2012 13:28:59 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.134.199 with SMTP id k7mr14758244qct.60.1329946139499; Wed, 22 Feb 2012 13:28:59 -0800 (PST)
Received: by 10.229.216.201 with HTTP; Wed, 22 Feb 2012 13:28:59 -0800 (PST)
In-Reply-To: <4F454E97.2070306@qbik.com>
References: <3077.1329391344.173214@puncture> <4F3CEB35.9080200@qbik.com> <1329394296.953.140661037317197@webmail.messagingengine.com> <4F3CFD35.10501@qbik.com> <alpine.LSU.2.00.1202161626400.30682@hermes-2.csi.cam.ac.uk> <4F3D6E57.8010301@qbik.com> <20120216224124.GC4578@dan.olp.net> <CABa8R6uxeFVSDQzzSS6ziV8b2roYdw38GMpjEm+1DGkhD3MdVg@mail.gmail.com> <20120216232954.GB5356@dan.olp.net> <4F3DA4A6.5020304@qbik.com> <20120217171457.GB4503@dan.olp.net> <4F3F5234.2080406@qbik.com> <4F3F56E7.3080004@panozzo.it> <4F3F784B.2000809@qbik.com> <CABa8R6ss=a5cXxO0TgF0df-E0irLT7HU5k9gXh0GXoShWcwbEA@mail.gmail.com> <4F454E97.2070306@qbik.com>
Date: Wed, 22 Feb 2012 13:28:59 -0800
Message-ID: <CABa8R6tBHVGJEG-LR_iM5AwZonih9sc1f=MfYGDqBgh6W11=OQ@mail.gmail.com>
From: Brandon Long <blong@google.com>
To: Adrien de Croy <adrien@qbik.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
X-Gm-Message-State: ALoCoQlwf1C/ztxd714Wrs6wgmIC/q6UubQbU78v3ZWlA6u7kf7y3gkflVoYB/8ABdoW4tAi3q/poq8R+XQSDNyt1cZzmQG7X59RhmVWQYR5jOS7hh8slZ85SFJrdI8jFYi0bPHggnU8
Cc: "Discussion on drastically slimming-down IMAP." <imap5@ietf.org>
Subject: Re: [imap5] Feature set? - was Re: Designing a new replacement protocol for IMAP
X-BeenThere: imap5@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion on drastically slimming-down IMAP." <imap5.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imap5>, <mailto:imap5-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imap5>
List-Post: <mailto:imap5@ietf.org>
List-Help: <mailto:imap5-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imap5>, <mailto:imap5-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2012 21:29:01 -0000
On Wed, Feb 22, 2012 at 12:22 PM, Adrien de Croy <adrien@qbik.com> wrote: > > > On 23/02/2012 8:24 a.m., Brandon Long wrote: >> >> On Sat, Feb 18, 2012 at 2:07 AM, Adrien de Croy<adrien@qbik.com> wrote: >>> >>> Having to get another cert will provide an incentive for the admin to >>> care >>> about it. >> >> You seem to believe that all servers can always be entirely free from >> sending spam. That's pretty funny. > > > sorry, where do I propose that? You're proposing revoking a server's certificate for spamming. Based on what level? What level of fault? Would Gmail get its certificate revoked because 1% of the email it sends is spam? > I'm just proposing a system that allows the identification of organisations > that inject and relay spam. That then allows enforcement of accountability. We can already do this via IP addresses and sender domains and SPF/DKIM authentication. Yes, its just a proxy and sometimes its wrong, but it works fairly well. >> How about spam sent from a hijacked account? How many hijacked >> accounts a day do you think there are on a service with 1B email >> users? > > How many other crimes are there committed a day, do you propose we don't go > after criminals? Heh. Do you know how many spam messages are sent a day? How large an enforcement organization do you propose to go after them all? And how long do you think that would take? Not to mention that multiple people and governments have different definitions of spam. When we see a new spam campaign, we need to be able to shut it down in less than hours. A recent time that we helped the US government go after a malware operation, it took them a year before the first arrests. A year where we had to leave the botnets and operations alone so they could gather the evidence necessary to make the arrests. Police action doesn't scale the same way that spammers do. >> Or how much money do you think a spammer is willing to spend to buy an >> account, even on a free service? Or do you think its actually >> possible to force everyone who wants an email account to pay for it at >> this point? And if so, how much money? $5/year is cheap in parts of >> the world, and really expensive in others, should poor parts of the >> world be relegated to the email ghetto because their accounts are so >> cheap that spammer abuse them constantly, while they have the least >> resources to keep them out? > > > why do you assume the system would be structured like this? Sounds like a > system that would fail. Then who pays for this enforcement? Who pays for the certification? >> Which is all pretty irrelevant, for most users today spam is already a >> solved problem. > > it certainly is not a solved problem for anyone. Ignorance is not the > answer. > > Jut because a business doesn't know how many customers they are losing due > to over-agressive spam filtering doesn't mean it has no cost to them. Of course it has a cost. I'm saying the cost of your solution is higher. > The system (and I admit it's ambitious) would need co-operation from > governments. As if all the governments of the world agree on anything, much less the definition of spam. > there's no need for ma and pa to have a certificate, they can submit to > their ISP. The ISP would need a certificate. There's no reason to assume > the certs would be managed by the existing CA infrastructure. I'd propose > that should be a function of Governments, and there are already special > provisions for governments to issue certificates. They could be for long > periods as well. The purpose is to identify and provide a means to revoke. > Renewing annually seems like a waste of time for that, unless you think the > certificate may be breached. And what if the CA is breached? Ie, like the 2-3 that have happened in the last year? > Organisations wanting to deliver directly could get a certificate as well. > > As to determination about whether someone spams or not. Well most countries > have systems to establish whether crimes are committed and go after and > punish those responsible. There are already spamming laws all over the > place. I'm proposing setting up a system that allows for identification of > perpetrators and enforcement, and enables services to be set up to solve > issues independently (e.g. if a government refuses to prosecute a spammer). Weee, now we're talking about extra-governmental authorities making the rules. Its always great to argue with an RBL maintainer about whether or not something is spam. Or maybe what you're proposing is more like SOPA/PIPA, we can have an organization like the RIAA deciding what's good. Even better, the government of Iran can just prevent their providers from accepting any mail certified by other governments. Or here's an even more fun one: We just emailed all of our users about the changes to our privacy policy, a move we made at the request of the US government. And we had RBL organizations complaining that it was spam. Who wins? Our answer is simple: the user decides what is spam, not someone else. Our job is to make our spam filter match each user's expectations. > Revokation of certificates would be a function of government after due > process. People couldn't just buy new ones (unless they get them from > corrupt government officials), because their previous spamming would be > associated with them as a person. In short, treat spamming like any other > crime - which it certainly is. No corrupt government officials in the world, that's for sure. And they already treat spamming as a crime, have for years. Done a lot of good at reducing the spam load, eh? > I think if governments were aware of the costs of spamming they may take a > different view on it. How many hours are wasted deleting spam? How much > money is spent on anti-spam? How much network capacity (which costs money) > is wasted transporting spam? Not as much as you'd think, turns out spam is much smaller than regular mail at this point, at least for consumers. A large percentage of mail, but on the order of 40x smaller in size (on average). And email in general is not generally a large user of network capacity. How many email messages, even at 100k average, does it take to equal a single iphone app download? Or a streamed video from Youtube? > How many opportunities are lost due to false > positives? Personally I believe the real economic costs of spam are > astronomical. Someone needs to do a study, and come up with some numbers > they can back up. Regardless of those costs, your proposal would cost more and still not solve the problem. > Otherwise we should just all join FB and just use that for communication and > ditch mail altogether. We have the stats on what percentage of our users receiving mail mark messages as spam or not spam. Its tiny. For most people, they don't see the spam, and maybe they don't see enough to actually check their spam label, but its just not an issue. As to where the kids are going these days, who knows. Email is certainly not the only game in town. Brandon
- Re: [imap5] Designing a new replacement protocol … Giovanni Panozzo
- Re: [imap5] Designing a new replacement protocol … Bron Gondwana
- [imap5] Designing a new replacement protocol for … Bron Gondwana
- Re: [imap5] Designing a new replacement protocol … Thomas Koch
- Re: [imap5] Designing a new replacement protocol … Bron Gondwana
- Re: [imap5] Designing a new replacement protocol … Bron Gondwana
- Re: [imap5] Designing a new replacement protocol … Jeroen van Meeuwen (Kolab Systems)
- Re: [imap5] Designing a new replacement protocol … Dave Cridland
- Re: [imap5] Designing a new replacement protocol … Arnt Gulbrandsen
- Re: [imap5] Designing a new replacement protocol … Dave Cridland
- Re: [imap5] Designing a new replacement protocol … Thomas Koch
- Re: [imap5] Designing a new replacement protocol … Cyrus Daboo
- Re: [imap5] Designing a new replacement protocol … Filip Navara
- Re: [imap5] Designing a new replacement protocol … Cyrus Daboo
- Re: [imap5] Designing a new replacement protocol … Bron Gondwana
- Re: [imap5] Designing a new replacement protocol … Adrien de Croy
- Re: [imap5] Designing a new replacement protocol … Bron Gondwana
- Re: [imap5] Designing a new replacement protocol … Cyrus Daboo
- Re: [imap5] Designing a new replacement protocol … Bron Gondwana
- Re: [imap5] Designing a new replacement protocol … Anil SRIVASTAVA
- Re: [imap5] Designing a new replacement protocol … Mark Crispin
- Re: [imap5] Designing a new replacement protocol … Alexey Melnikov
- Re: [imap5] Designing a new replacement protocol … Bron Gondwana
- Re: [imap5] Designing a new replacement protocol … Adrien de Croy
- Re: [imap5] Designing a new replacement protocol … Adrien de Croy
- Re: [imap5] Designing a new replacement protocol … Bron Gondwana
- Re: [imap5] Designing a new replacement protocol … Mark Crispin
- Re: [imap5] Designing a new replacement protocol … Adrien de Croy
- Re: [imap5] Designing a new replacement protocol … Bron Gondwana
- Re: [imap5] Designing a new replacement protocol … Bron Gondwana
- Re: [imap5] Designing a new replacement protocol … Mark Crispin
- Re: [imap5] Designing a new replacement protocol … Tony Finch
- Re: [imap5] Designing a new replacement protocol … Timo Sirainen
- Re: [imap5] Designing a new replacement protocol … Bron Gondwana
- Re: [imap5] Designing a new replacement protocol … Alexey Melnikov
- Re: [imap5] Designing a new replacement protocol … Bron Gondwana
- Re: [imap5] Designing a new replacement protocol … Arnt Gulbrandsen
- Re: [imap5] Designing a new replacement protocol … Petite Abeille
- Re: [imap5] Designing a new replacement protocol … Bron Gondwana
- Re: [imap5] Designing a new replacement protocol … Jan Kundrát
- Re: [imap5] Designing a new replacement protocol … Bron Gondwana
- Re: [imap5] Designing a new replacement protocol … Mark Crispin
- Re: [imap5] Designing a new replacement protocol … Timo Sirainen
- Re: [imap5] Designing a new replacement protocol … Michel Sébastien
- Re: [imap5] Designing a new replacement protocol … Bron Gondwana
- Re: [imap5] Designing a new replacement protocol … Adrien de Croy
- Re: [imap5] Designing a new replacement protocol … Bron Gondwana
- [imap5] Feature set? - was Re: Designing a new re… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Dave Cridland
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Timo Sirainen
- Re: [imap5] Designing a new replacement protocol … Giovanni Panozzo
- Re: [imap5] Designing a new replacement protocol … Dave Cridland
- Re: [imap5] Designing a new replacement protocol … Adrien de Croy
- Re: [imap5] Designing a new replacement protocol … Adrien de Croy
- Re: [imap5] Designing a new replacement protocol … Dave Cridland
- Re: [imap5] Designing a new replacement protocol … Adrien de Croy
- Re: [imap5] Designing a new replacement protocol … Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Curtis King
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Designing a new replacement protocol … Brandon Long
- Re: [imap5] Designing a new replacement protocol … Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Arnt Gulbrandsen
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Bron Gondwana
- Re: [imap5] Feature set? - was Re: Designing a ne… Arnt Gulbrandsen
- Re: [imap5] Feature set? - was Re: Designing a ne… Arnt Gulbrandsen
- Re: [imap5] Feature set? - was Re: Designing a ne… Dave Cridland
- Re: [imap5] Designing a new replacement protocol … Michel Sébastien
- Re: [imap5] Feature set? - was Re: Designing a ne… Brandon Long
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Sebastian Hagedorn
- Re: [imap5] Feature set? - was Re: Designing a ne… Giovanni Panozzo
- Re: [imap5] Feature set? - was Re: Designing a ne… Dave Cridland
- Re: [imap5] Designing a new replacement protocol … Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Bron Gondwana
- Re: [imap5] Designing a new replacement protocol … Dave Cridland
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Michel Sébastien
- Re: [imap5] Feature set? - was Re: Designing a ne… Dave Cridland
- Re: [imap5] Feature set? - was Re: Designing a ne… Dave Cridland
- Re: [imap5] Feature set? - was Re: Designing a ne… Bron Gondwana
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Dave Cridland
- Re: [imap5] Designing a new replacement protocol … Michel Sébastien
- Re: [imap5] Designing a new replacement protocol … Tony Finch
- Re: [imap5] Designing a new replacement protocol … Dave McMurtrie
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Designing a new replacement protocol … Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Arnt Gulbrandsen
- Re: [imap5] Designing a new replacement protocol … Dave McMurtrie
- Re: [imap5] Feature set? - was Re: Designing a ne… Bron Gondwana
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Dave Cridland
- Re: [imap5] Feature set? - was Re: Designing a ne… Bron Gondwana
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Designing a new replacement protocol … Bron Gondwana
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Designing a new replacement protocol … Tony Finch
- Re: [imap5] Designing a new replacement protocol … Bron Gondwana
- Re: [imap5] Feature set? - was Re: Designing a ne… Cyrus Daboo
- Re: [imap5] Designing a new replacement protocol … Tony Finch
- Re: [imap5] Feature set? - was Re: Designing a ne… Cyrus Daboo
- Re: [imap5] Feature set? - was Re: Designing a ne… Cyrus Daboo
- Re: [imap5] Designing a new replacement protocol … Cyrus Daboo
- Re: [imap5] Feature set? - was Re: Designing a ne… Sebastian Hagedorn
- Re: [imap5] Feature set? - was Re: Designing a ne… Tony Finch
- Re: [imap5] Designing a new replacement protocol … Bron Gondwana
- Re: [imap5] Designing a new replacement protocol … Bron Gondwana
- Re: [imap5] Feature set? - was Re: Designing a ne… Dave Cridland
- Re: [imap5] Feature set? - was Re: Designing a ne… Arnt Gulbrandsen
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Designing a new replacement protocol … Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Designing a new replacement protocol … Adrien de Croy
- Re: [imap5] Designing a new replacement protocol … Bron Gondwana
- Re: [imap5] Feature set? - was Re: Designing a ne… Bron Gondwana
- Re: [imap5] Feature set? - was Re: Designing a ne… Dan White
- Re: [imap5] Feature set? - was Re: Designing a ne… Mark Crispin
- Re: [imap5] Feature set? - was Re: Designing a ne… Brandon Long
- Re: [imap5] Feature set? - was Re: Designing a ne… Dan White
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Bron Gondwana
- Re: [imap5] Feature set? - was Re: Designing a ne… Arnt Gulbrandsen
- Re: [imap5] Feature set? - was Re: Designing a ne… Jan Kundrát
- Re: [imap5] Feature set? - was Re: Designing a ne… Tony Finch
- Re: [imap5] Feature set? - was Re: Designing a ne… Tony Finch
- Re: [imap5] Feature set? - was Re: Designing a ne… Tony Finch
- Re: [imap5] Feature set? - was Re: Designing a ne… Dan White
- Re: [imap5] Feature set? - was Re: Designing a ne… Bron Gondwana
- Re: [imap5] Feature set? - was Re: Designing a ne… Dan White
- Re: [imap5] Feature set? - was Re: Designing a ne… Mark Crispin
- Re: [imap5] Feature set? - was Re: Designing a ne… Bron Gondwana
- Re: [imap5] Feature set? - was Re: Designing a ne… Bron Gondwana
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Bron Gondwana
- Re: [imap5] Feature set? - was Re: Designing a ne… Giovanni Panozzo
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Tony Finch
- Re: [imap5] Feature set? - was Re: Designing a ne… Bron Gondwana
- Re: [imap5] Feature set? - was Re: Designing a ne… Sebastian Hagedorn
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Bron Gondwana
- Re: [imap5] Feature set? - was Re: Designing a ne… Bron Gondwana
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Bron Gondwana
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Tony Finch
- Re: [imap5] Feature set? - was Re: Designing a ne… Tony Finch
- Re: [imap5] Feature set? - was Re: Designing a ne… Bron Gondwana
- Re: [imap5] Feature set? - was Re: Designing a ne… Bron Gondwana
- Re: [imap5] Feature set? - was Re: Designing a ne… Tony Finch
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Filip Navara
- Re: [imap5] Feature set? - was Re: Designing a ne… Bron Gondwana
- Re: [imap5] Feature set? - was Re: Designing a ne… Bron Gondwana
- Re: [imap5] Feature set? - was Re: Designing a ne… Dave Cridland
- Re: [imap5] Feature set? - was Re: Designing a ne… Tony Finch
- Re: [imap5] Feature set? - was Re: Designing a ne… Bron Gondwana
- Re: [imap5] Feature set? - was Re: Designing a ne… Filip Navara
- Re: [imap5] Feature set? - was Re: Designing a ne… Dave Cridland
- Re: [imap5] Feature set? - was Re: Designing a ne… Bron Gondwana
- Re: [imap5] Feature set? - was Re: Designing a ne… Dave Cridland
- Re: [imap5] Feature set? - was Re: Designing a ne… Bron Gondwana
- Re: [imap5] Feature set? - was Re: Designing a ne… Tony Finch
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Tony Finch
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Arnt Gulbrandsen
- Re: [imap5] Feature set? - was Re: Designing a ne… Brandon Long
- Re: [imap5] Feature set? - was Re: Designing a ne… Bron Gondwana
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Brandon Long
- Re: [imap5] Feature set? - was Re: Designing a ne… Jan Kundrát
- Re: [imap5] Feature set? - was Re: Designing a ne… Tony Hansen
- Re: [imap5] Feature set? - was Re: Designing a ne… Arnt Gulbrandsen
- Re: [imap5] Feature set? - was Re: Designing a ne… Mark Crispin
- Re: [imap5] Feature set? - was Re: Designing a ne… Dave Cridland
- Re: [imap5] Feature set? - was Re: Designing a ne… Brandon Long
- Re: [imap5] Feature set? - was Re: Designing a ne… Arnt Gulbrandsen
- Re: [imap5] Feature set? - was Re: Designing a ne… Brandon Long
- Re: [imap5] Feature set? - was Re: Designing a ne… Adrien de Croy
- Re: [imap5] Feature set? - was Re: Designing a ne… Brandon Long
- Re: [imap5] Feature set? - was Re: Designing a ne… Dave Cridland
- [imap5] Beep Dave Crocker
- Re: [imap5] Beep Tony Finch
- Re: [imap5] Beep Dave Crocker
- Re: [imap5] Beep Bron Gondwana
- Re: [imap5] Beep Adrien W. de Croy
- Re: [imap5] Beep Adrien W. de Croy