I have been paying avid attention to this thread because it deals with an
issue that affects my server as well. Currently my server works much like
the Cyrus one does with expunged messages -- and I take some comfort in
finding that I am not alone.
The only alternatives I see, given the
I'm sure that this must be covered somewhere in RFC3501, but I can't
find it, so I'd appreciate some guidance... Consider the following LIST
response from an IMAP server, where the hierarchy delimiter is '/':
* LIST (\\Noselect) / Public Folders/
How should the trailing hierarchy delimiter
On Sun, 2004-01-04 at 18:57, Pete Maclean wrote:
The only alternatives I see, given the particular constraints upon my
server, are to behave like the UW server and disallow multiple concurrent
selections or make a copy of every mailbox as it is selected. However,
implementing the latter
There was a good discussion related to this on this list a few months ago,
presumably during the time you were off. If you search the archives for
September 2003 I think you will find a lot of relevant information. There
is one thread with a subject of LIST and there may be more.
Cheers,
On Mon, 2004-01-05 at 06:47, Mark Crispin wrote:
With mbox this could be done by adding a new header (X-IMAP-Expunged:
timestamp).
Indeed, but the problem with traditional UNIX mailbox format is that
shared access itself is a problem if the messages can move about in the
mailbox. Plus,
On Mon, 5 Jan 2004, Timo Sirainen wrote:
the problem with traditional UNIX mailbox format is that
shared access itself is a problem
I don't think it's that much of a problem. It may be slow when other
applications modify it though. My plan is:
- whenever mtime or size changes unexpectedly,
On Mon, 5 Jan 2004, David Harris wrote:
Consider the following LIST
response from an IMAP server, where the hierarchy delimiter is '/':
* LIST (\\Noselect) / Public Folders/
How should the trailing hierarchy delimiter on the mailbox name be
interpreted? Does it have a special meaning of
