MBOX-Line: From dave at cridland.net  Wed Mar 21 22:19:48 2012
To: imap-protocol@u.washington.edu
From: Dave Cridland <dave@cridland.net>
Date: Fri Jun  8 12:34:48 2018
Subject: [Imap-protocol] [ann] lua imap server
In-Reply-To: <4F6A5811.4070503@gulbrandsen.priv.no>
References: <CBFD9662-269A-4573-8EF1-E07E7BE4671C@mac.com>
	<20120319204645.GA2859@launde.brong.net>
	<E9A1A407-E02D-4FE8-82EC-B5DDC8F0EDE2@mac.com>
	<17068.1332195426.345309@puncture> <17068.1332235633.171765@puncture>
	<C6227176-73D4-455D-91D1-601384A7591E@mac.com>
	<20897.1332282025.074478@puncture>
	<C51F6872-1FC8-416A-9BEA-BEA1907ECCF1@mac.com>
	<CAC4RtVAtrYAge6zhoYZsLEiT=MncxLDi6XeEsm6keinMhFFF3A@mail.gmail.com>
	<E96504DE-48E6-425B-85A5-37F581DF9FA1@mac.com>
	<20897.1332365878.053493@puncture>
	<4F6A5811.4070503@gulbrandsen.priv.no>
Message-ID: <20897.1332393588.939634@puncture>

On Wed Mar 21 22:37:05 2012, Arnt Gulbrandsen wrote:
> Hey. If it's OK for him that new messages are visible only when the
> client next connects/selects/noops, then so it is. That may not be a
> tradeoff many people would make, but if it's an informed choice...

This isn't a case of limiting functionality; it's a case of  
unexpected and broken behaviour which will show as screwy semantics  
to the end user.

If there was an IMAP based archive of some mailing list, it'd be  
entirely possible people might switch to reading it solely through  
the archive, in which case they'd be reliant on proper semantics - so  
it's not as if this case is somehow special.

If this server is simply designed as an amusing novelty, then I'd  
agree that it doesn't really matter, but if it's intended to have  
actual usage, it needs fixing.

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade

