From: "rob pike, esq." <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] manual suggestions and upas/fs bug
Date: Wed, 18 Sep 2002 13:03:50 -0400 [thread overview]
Message-ID: <216360284.1032354229@[10.149.2.206]> (raw)
In-Reply-To: <200209180206.g8I26fl0000579@orthanc.ab.ca>
> (For the record: I'm a server author ;-)
>
> If I ever get my P9 network re-built I plan to fix up the IMAP
> code.
Great. For the record, the upas/fs implementation of IMAP is
something of a hack; of more interest to me is the correctness
of the stand-alone IMAP server, imap4d. (I'm using it as I write
this.) It's been tested - and fixed - against a number of clients
but it was written by someone learning IMAP as he went, so I'm sure
it's still got some issues.
-rob
next prev parent reply other threads:[~2002-09-18 17:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 23:05 Russ Cox
2002-09-18 2:06 ` Lyndon Nerenberg
2002-09-18 17:03 ` rob pike, esq. [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-17 13:28 Russ Cox
2002-09-17 4:58 Russ Cox
2002-09-17 4:34 David Swasey
2002-09-17 20:18 ` Lyndon Nerenberg
2002-09-16 19:29 David Swasey
2002-09-17 1:58 ` Lyndon Nerenberg
2002-09-17 8:47 ` Douglas A. Gwyn
2002-09-17 9:17 ` Lucio De Re
2002-09-18 8:37 ` Douglas A. Gwyn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='216360284.1032354229@[10.149.2.206]' \
--to=rob@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).