Gnus development mailing list
 help / color / mirror / Atom feed
From: Richard Riley <rileyrg@googlemail.com>
To: ding@gnus.org
Subject: Re: Using gnus with locally stored email (repost from users ml)
Date: Tue, 05 Oct 2010 11:34:40 +0200	[thread overview]
Message-ID: <k662xhf0en.fsf@news.eternal-september.org> (raw)
In-Reply-To: <yb0sk0lnghy.fsf@dod.no> (Steinar Bang's message of "Tue, 05 Oct 2010 11:19:53 +0200")

Steinar Bang <sb@dod.no> writes:

>>>>>> Gary <gnus@garydjones.name>:
>
>> As I've been moving ever more to emacs, I find myself using gnus more
>> and more, but haven't tried integrating locally stored email (for
>> which I still use fetchmail & procmail). What's my best way of doing
>> that? I still want to suck some email down to my own HD, and that's
>> not going to change, so please don't suggest using imap :)
>
> I use nnimap with agent.  That has worked for me for quite a few years.
>
> But then I don't need to have the agent-cached email available to other
> email clients, such as mutt.
>
> Others are using server-local IMAP-servers.
>

I dont know how to set up gnus to read his current mbox but guess its
easy - then the "migration" will be to simply move from that group to
another group.

What I like, especially after Lars recent imap elispathon, is to use
local dovecot servers on all my machines. This stores using maildir but
provides an imap interface for gnus (and other mail readers including
mutt). IMAP sync using offlineimap then makes much more sense to me than
using fetchmail since its bidirectional and all things "sync" between my
gmail accounts and various machines with their own dovecot servers.

The benefit being each machine has its own email cache and search etc
are lightning fast.




  parent reply	other threads:[~2010-10-05  9:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-05  8:16 Gary
2010-10-05  9:19 ` Steinar Bang
2010-10-05  9:34   ` Bojan Nikolic
2010-10-06  6:19     ` Gary
2010-10-05  9:34   ` Richard Riley [this message]
2010-10-05  9:32 ` Leonidas Tsampros

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=k662xhf0en.fsf@news.eternal-september.org \
    --to=rileyrg@googlemail.com \
    --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).