MBOX-Line: From joel+imap-protocol at panacea.null.org  Wed Dec 30 05:29:30 2009
To: imap-protocol@u.washington.edu
From: Joel Reicher <joel+imap-protocol@panacea.null.org>
Date: Fri Jun  8 12:34:43 2018
Subject: [Imap-protocol] Childless noselect mailboxes
In-Reply-To: <Gophermail.2.0.0912300657280.23421@vs-w.tc.umn.edu>
References: <1262106049.26478.745.camel@timo-desktop>
	<alpine.OSX.2.00.0912290938230.18442@hsinghsing.panda.com>
	<1262111858.26478.842.camel@timo-desktop>
	<alpine.OSX.2.00.0912291042070.18442@hsinghsing.panda.com>
	<1262114250.26478.864.camel@timo-desktop>
	<alpine.DEB.2.00.0912300000110.22394@Higashi-Tomobiki>
	<Gophermail.2.0.0912300657280.23421@vs-w.tc.umn.edu>
Message-ID: <4218.1262179770@succubus.panacea.null.org>

Brian Hayden writes:
> They see a 
> file as analogous to a mail message, not a mailbox. And if you stop for a 
> second to think about it, it's obvious why--a file and a mail message both 
> contain text data.

A MIME part can contain text data too.

I think it's likely that users view messages as the "privileged" container
that is at the end of the name hierarchy only because they are using
interfaces that place it there. Being a container does not, in itself,
seem to give messages any kind of special status, because lots of other
things are containers too.

Cheers,

	- Joel

