Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Issues with davmail and nnimap (Was: nnimap fails with TLS error when trying to open a davmail server)
Date: Mon, 10 Jun 2013 13:04:56 +0200	[thread overview]
Message-ID: <upzcvc5mgraf.fsf_-_@dod.no> (raw)
In-Reply-To: <m2y5aicwaa.fsf@lifelogs.com>

>>>>> Ted Zlatanov <tzz@lifelogs.com>:
> On Sat, 08 Jun 2013 21:22:13 +0200 Steinar Bang <sb@dod.no> wrote: 

SB> Are anyone else successfully using davmail and nnimap these days?

> I haven't heard of anyone (bug reports, feature requests) since then.
> Except you :)

Well, there was this article on "the other gnus group" (gmane.emacs.gnus.users)
 http://article.gmane.org/gmane.emacs.gnus.user/15365
 nntp://news.gmane.org/gmane.emacs.gnus.user/15365
with the same symptoms that I had, once I got past the TLS issue, ie.
 - All articles had "unknown" as the sender in the Summary buffer
 - Slow group entry

Sounds like a good candidate for offlineimap and caching on a separate
imap server, actually (except I'm reluctant to use any of my own disk
space to cache all of that redundant info, ie. quotes of the entire
thread in each message, and multiple copies of office documents with
very small differences sent around for comments).

I might as well just use the web interface directly.




  reply	other threads:[~2013-06-10 11:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-07 20:58 nnimap fails with TLS error when trying to open a davmail server Steinar Bang
2013-06-08  7:09 ` Andreas Schwab
2013-06-08 13:23   ` Steinar Bang
2013-06-08 14:29     ` Steinar Bang
2013-06-08 19:22       ` Steinar Bang
2013-06-10  6:30         ` Ted Zlatanov
2013-06-10 11:04           ` Steinar Bang [this message]
2013-08-27 14:55             ` Issues with davmail and nnimap Steinar Bang

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=upzcvc5mgraf.fsf_-_@dod.no \
    --to=sb@dod.no \
    --cc=ding@gnus.org \
    /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).