Gnus development mailing list
 help / color / mirror / Atom feed
From: "Matt Armstrong" <matt+dated+1007770937.e3ec50@lickey.com>
Cc: ding@gnus.org
Subject: Re: maildir - whats the skinny?
Date: Sun, 02 Dec 2001 17:22:10 -0700	[thread overview]
Message-ID: <878zcltaod.fsf@squeaker.lickey.com> (raw)
In-Reply-To: <m1wv05s2l4.fsf@reader.newsguy.com> (Harry Putnam's message of "Sun, 02 Dec 2001 14:02:15 -0800")

Harry Putnam <reader@newsguy.com> writes:

> If I have procmail writing to maildir and creating directories as
> needed, then writing the numbered messages under that directory.  Do I
> need to tell gnus about teh subdirectory?

I believe the answer is yes -- I think it'd be a new mail source of
type "maildir".


> We might see ~/maildir/group1
>
> Then procmail might create maildir/group4.  Later maildir/group6 etc
> Do I need to tell gnus in advance about these names? Or does gnus know
> to look in maildir and recurse, the subdirectories.  Naming nnml
> groups after them?

The only way I know of for Gnus to automatically discover new groups
based on procmail output is with the "directory" style mail-source.  I
have this in my .gnus:

(setq mail-sources '((directory :path "~/.incoming")))

But this expects unix mbox files with a .spool suffix to be in that
dir, not maildirs.

I'm not sure if Gnus supports a similar thing with maildirs.  Last
time I investigated, I concluded that it didn't.


> The examples in gnus info:
>   Two example maildir mail sources:
>
>           (maildir :path "/home/user-name/Maildir/"
>                    :subdirs ("cur" "new"))
>
>           (maildir :path "/user@remotehost.org:~/Maildir/"
>                    :subdirs ("new"))

I believe the maildir mail source names a single mail folder.

-- 
matt



  reply	other threads:[~2001-12-03  0:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-02 22:02 Harry Putnam
2001-12-03  0:22 ` Matt Armstrong [this message]
2001-12-03  4:08   ` Harry Putnam
2001-12-03  4:58     ` Matt Armstrong
2001-12-03  6:45       ` Paul Jarc
2001-12-03  7:11         ` Matt Armstrong
2001-12-03 16:30           ` Paul Jarc
2001-12-03 17:09             ` Paul Jarc
2001-12-03 17:40               ` Matt Armstrong
2001-12-03 17:56                 ` Paul Jarc
2001-12-03 18:31                   ` Matt Armstrong
2001-12-03 19:09                     ` Henrik Enberg
2001-12-04  9:07                   ` Kai Großjohann
2001-12-03  9:50       ` Harry Putnam
2001-12-03  7:44 ` Kai Großjohann
2001-12-03  9:23   ` Harry Putnam
2001-12-03 16:34     ` Paul Jarc

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=878zcltaod.fsf@squeaker.lickey.com \
    --to=matt+dated+1007770937.e3ec50@lickey.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).