Gnus development mailing list
 help / color / mirror / Atom feed
From: Joe Casadonte <jcasadonte@northbound-train.com>
Subject: nnimap - not quite there yet?
Date: 08 Aug 2001 16:29:29 -0400	[thread overview]
Message-ID: <u8zgub8ie.fsf@terrapin.northbound-train.com> (raw)



Before I spend copious amounts of free-time trying to fix what I'm
about to rant about, perhaps someone could tell me if there are
already plans to fix these things.  Or possibly fixes are already in
Oort (though I downloaded it and grepped thru the Changelog quickly
and didn't see anything specifically on these issues).  My setup is a
little odd, and perhaps I need to change it, but until I do, I have
the following problems.

My setup: I have multiple accounts on multiple IMAP servers.
Specifically, 8 accounts on one IMAP server and one on another.  I
differentiate these accounts as being various virtual servers in my
gnus-secondary-select-methods list.

My problems:

1) Despite everything I've tried, mostly with levels, I cannot avoid
   having all accounts logged into at Gnus startup.  I only want two
   or three accounts checked, and I'll check the others once every
   couple of days.  Perhaps I need to define the virtual servers but
   make them inactive somehow, and then manually activate them from
   the server buffer?  Aside from not knowing how to do that off-hand,
   it seems a bit of a PITA.

2) Again, despite attempts to change the behavior (mostly with levels)
   I cannot avoid having nnimap check every folder when I do a
   gnus-group-get-new-news.  The folders don't /activate/, mind you, but
   I have to sit thru every one of them being checked.

3) For each virtual IMAP server, an imap process is launched and kept
   hanging around.  With 9 virtual servers, that's just too much.  It
   would be much better if there was one IMAP process that kept
   flipping back and forth.  Yeah, there's a lag with login and all,
   but I'd rather have that then multiple connections hanging around
   doing nothing.  One solution is to have a pool of IMAP connections,
   the limit to which could be configurable (1 for me, N for others).

4) As has been mentioned elsewhere in recent threads, nnimap (and all
   of Gnus for that matter) is not terribly fault tolerant.  If a
   server connection goes down, the connection needs to be severed
   manually before it can be reconnected.  Again, this is more of a
   general Gnus issue, I think, but nnimap seems a bit more stubborn
   then nntp.

Some of these things are OK from an IMAP standpoint, but I'm trying to
buy into the whole "mail is just strangely formatted news" idiom, and
these are some of the things holding me back.  Having said all of
that, I'd be more then happy to jump in and try to fix some of them,
being a firm believer in being a part of the solution (as well as the
problem).

Thanks for listening!

--
Regards,

joe
Joe Casadonte
jcasadonte@northbound-train.com

------------------------------------------------------------------------------
         Llama Fresh Farms => http://www.northbound-train.com
   Gay Media Resource List => http://www.northbound-train.com/gaymedia.html
            Perl for Win32 => http://www.northbound-train.com/perlwin32.html
               Emacs Stuff => http://www.northbound-train.com/emacs.html
          Music CD Trading => http://www.northbound-train.com/cdr.html
------------------------------------------------------------------------------
                       Live Free, that's the message!
------------------------------------------------------------------------------



             reply	other threads:[~2001-08-08 20:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-08 20:29 Joe Casadonte [this message]
2001-08-08 22:11 ` Kai Großjohann
2001-08-09 19:56   ` Joe Casadonte
2001-08-09 21:52     ` Kai Großjohann
2001-08-09 22:06       ` Paul Jarc
2001-08-09 22:39         ` Kai Großjohann
2001-08-17 19:33       ` Simon Josefsson
2001-08-08 23:45 ` Amos Gouaux
2001-08-09  6:41 ` Peter Weiss, Sun Microsystems, Germany
2001-08-09 20:23   ` Joe Casadonte
2001-08-09 21:31     ` Joe Casadonte

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=u8zgub8ie.fsf@terrapin.northbound-train.com \
    --to=jcasadonte@northbound-train.com \
    /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).