Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: David Sumbler <david@nospam.co.uk>
Subject: Re: Mail folders inaccessible
Date: Thu, 10 Nov 2005 09:29:06 +0000	[thread overview]
Message-ID: <m37jbgn95p.fsf@ceres.staly.plus.com> (raw)
In-Reply-To: <v94q6kdi30.fsf@marauder.physik.uni-ulm.de>

Reiner Steib <reinersteib+from-uce@imap.cc> writes:

> On Thu, Nov 10 2005, David Sumbler wrote:
>
>> OK - the problem seems to be gradually resolving itself: as each
>> folder receives a new mail (according to Procmail rules), it
>> becomes accessible from Gnus again, with all the contents marked as
>> unread.
>
> Does procmail deliver directly into you Gnus nnfolder files?

No

> If so, don't do that, use `directory' in your `mail-sources'
> instead:
>
> ,----[ (info "(gnus)Mail Source Specifiers") ]
> | `directory'
> |      Get mail from several files in a directory.  This is typically used
> |      when you have procmail split the incoming mail into several files.
> |      That is, there is a one-to-one correspondence between files in that
> |      directory and groups, so that mail from the file `foo.bar.spool'
> |      will be put in the group `foo.bar'.  (You can change the suffix to
> |      be used instead of `.spool'.)  [...]
> | 
> |      An example directory mail source:
> | 
> |           (directory :path "/home/user-name/procmail-dir/"
> |                      :suffix ".prcml")
> `----

I use
(setq mail-sources '((directory :path "/home/david/Mail_folders/" :suffix ".prcml")))

David

-- 

David Sumbler

Please reply with a followup to the newsgroup.

However, if you _really_ want to send me an e-mail,
replace "nospam" in my address with "aeolia".


      reply	other threads:[~2005-11-10  9:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-09  9:42 David Sumbler
2005-11-09 23:59 ` David Sumbler
2005-11-10  8:26   ` Reiner Steib
2005-11-10  9:29     ` David Sumbler [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=m37jbgn95p.fsf@ceres.staly.plus.com \
    --to=david@nospam.co.uk \
    /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).