Re: [MORG] POP3 LIST+ Extension: Monitoring for mailbox changes

Mark Crispin <> Sat, 05 February 2011 21:29 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 25B0C3A69E9 for <>; Sat, 5 Feb 2011 13:29:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id RP26sLxT7IGt for <>; Sat, 5 Feb 2011 13:29:18 -0800 (PST)
Received: from Panda.COM ( []) by (Postfix) with ESMTP id 038B73A696F for <>; Sat, 5 Feb 2011 13:29:18 -0800 (PST)
Received: from ([]) by Panda.COM ([]) with ESMTP via TCP; Sat, 05 Feb 2011 13:29:14 -0800
Date: Sat, 5 Feb 2011 13:29:13 -0800 (PST)
From: Mark Crispin <>
In-Reply-To: <>
Message-ID: <>
References: <> <1296844981.18488.385.camel@hurina> <>
User-Agent: Alpine 2.00 (OSX 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Subject: Re: [MORG] POP3 LIST+ Extension: Monitoring for mailbox changes
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 05 Feb 2011 21:29:19 -0000

On Sat, 5 Feb 2011, Steffen Lehmann wrote:
> To scan through all messages of a mailbox can be a time/CPU/memory
> consuming task for a server on big mailboxes.

This discussion is fascinating, but it begs the question:

If you care about such matters, why use POP3 and not IMAP?

POP3 does a certain specific task, and it does that task well.  POP3 was
never intended for any other task.

Each new extension (to either IMAP or POP3) creates new client/server
incompatibility paths.  You may think that you are staying on top of
things by implementing every extension, no matter how minimal the market
requirement.  You learn otherwise when your customers slam you over
interoperability problems that are fixed only by disabling the extension
in your product.

I can't help but thing that MORG has devolved into a group of people
desperate to stay on the gravy train of Building New Email Protocols,
never mind that the train has become increasingly irrelevant.

The more realistic only care about placing a veneer of "IETF approval" on
a private mechanism for their client/server products.  But then there are
the others, who live in a true Fantasy Land in which everybody will
presently implement all 69 random extensions.

This disease isn't confined to MORG either.  The entire IETF suffers from
it.  I am thoroughly enjoying the IPv6 debacle as it unfolds, and look
forward to many years of entertainment.

-- Mark --
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.