Gnus development mailing list
 help / color / mirror / Atom feed
From: Leonidas Tsampros <ltsampros@upnet.gr>
To: ding@gnus.org
Subject: Re: Using gnus with locally stored email (repost from users ml)
Date: Tue, 05 Oct 2010 12:32:19 +0300	[thread overview]
Message-ID: <87zkutrnmk.fsf@bifteki.lan> (raw)
In-Reply-To: <i8emtd$mgg$2@dough.gmane.org> (Gary's message of "Tue, 05 Oct 2010 10:16:45 +0200")

Gary <gnus@garydjones.name> writes:

> Sorry, I know this isn't the right place really, but I asked on the
> users ml and didn't really get where I am trying to get to.
>
> I've got a whole pile of locally stored mail in mbox files in ~/Mail and
> subdirectories thereof. Mutt is pretty easily configured to handle that,
> and that's what I used exclusively until a few months ago. I'm not
> married to mbox, I could also use maildir or any other format that mutt
> and gnus are both capable of reading.
>
> 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 :)
>
> If I can, I would still like the email to be accessible to mutt, even if
> I only rarely use it. Would nnfolder screw that up? Otherwise, that
> looks like the closest to what I already have, right?
>
> Or do I want
>   (setq mail-sources
>         '((directory :path "/home/gary/Mail")))
>
> Actually I tried just that, and nothing happened, so I guess I have to
> also set something else? I'm rather confused about the
> relationship/differences between mail sources and backends...

Hi Gary,

this is exactly the setup I use. My primary select methos is a local
university nntp server we have and as the secondary methods I have the
following:

(setq gnus-secondary-select-methods '((nnml "")
				      (nnimap "10.6.0.20")))

Then I have these in my .conf:

(setq nnml-directory "~/Mail.Gnus")
(setq mail-source-delete-incoming t)

(setq mail-sources '((directory :path "~/Mail"
				:suffix "")))

So, Emacs now reads all Mail on all mboxes under ~/Mail, and 'ingests'
them into the nnml backend which is under "~/Mail.Gnus".  Now at this
point and in order to emulate procmail's behaviour, I use fancy
splitting:

;; fancy mail splitting
(setq nnmail-resplit-incoming t)
(setq nnmail-split-methods 'nnmail-split-fancy)
(setq nnmail-split-fancy
      '(|
       ("list-id" "ding\\.gnus\\.org" "mail.gnus.ding")))


In case I have any mistakes in my explanations, please correct me.

I hope this helps.

PS: I'm really bored and I never changed the fetchmail/procmail
configuration in order not to do double splitting (I just update
the fancy splitting rules)

Regards
Leonidas



      parent reply	other threads:[~2010-10-05  9:32 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
2010-10-05  9:32 ` Leonidas Tsampros [this message]

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=87zkutrnmk.fsf@bifteki.lan \
    --to=ltsampros@upnet.gr \
    --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).