From: John McClary Prevost <visigoth@cs.cmu.edu>
Cc: Steve Dunham <dunham@cps.msu.edu>
Subject: Re: IMAP support
Date: 05 Aug 1997 23:29:26 -0400 [thread overview]
Message-ID: <vpd3eooyoo9.fsf@naiad.fac.cs.cmu.edu> (raw)
In-Reply-To: Steve Dunham's message of Sat, 02 Aug 1997 12:15:44 -0400
>>>>> "sd" == Steve Dunham <dunham@cps.msu.edu> writes:
sd> Is anyone actively working on IMAP support? The only IMAP
sd> backend I can find is at
sd> /afs/afs_sites/cs.cmu.edu/project/systems-visigoth/src/emacs/nnimap
That's it. Actually, try nnimap-dev for the one I run (which isn't
much different.) I've been putting of working on it for a while.
Partly because I've been busy with work, and partly because I've been
waiting for Quassia.
sd> which has the following problems:
sd> Can't tell the difference between read and unread messages
sd> Can't delete messages
I -can- make it do the above, but it will take mondo time to refresh
your group buffer. The current model for a backend passing this info
to Gnus is to pass it when you scan groups for new messages. I've
asked that a new method be added so that:
a) Gnus can ask the backend "how many new/existing/tagged messages"
are there (IMAP can answer this quickly).
b) Gnus can ask on group entry what the current message flags are,
since this is expensive in IMAP and shouldn't be done unless you
actually want to read the group.
I'm blocking on at least a stub description for the above methods,
then I can do more. I've also not made some changes which Lars would
like to see before nnimap enters Gnus because the new methods would
make them unnecessary.
sd> Doesn't handle server disconnect gracefully. (i.e. it can't reconnect)
A bug which I admit is my problem, and I've been too lazy about
fixing. I'm working on moving my main mail stuff to IMAP, which means
I'll get a move on it soon.
sd> It also seems to use a bit more bandwidth to get the message
sd> list than the evil mail reader I'm currently stuck with.
At the moment, I grab full RFC822 headers, if I recall. I intend to
switch to using envelopes and a few other relevant headers.
sd> I'm just wondering if anyone is working on it. (As you can
sd> tell from the message header, I'm getting desperate.)
Wow. That -is- desperate.
John.
next prev parent reply other threads:[~1997-08-06 3:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-02 16:15 Steve Dunham
1997-08-06 3:29 ` John McClary Prevost [this message]
1998-06-19 2:16 imap support Simon Josefsson
1998-06-19 14:02 ` Jake Colman
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=vpd3eooyoo9.fsf@naiad.fac.cs.cmu.edu \
--to=visigoth@cs.cmu.edu \
--cc=dunham@cps.msu.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).