From: Reiner Steib <reinersteib+from-uce@imap.cc>
Subject: Re: mail sources and groups
Date: Thu, 17 Nov 2005 17:07:41 +0100 [thread overview]
Message-ID: <v9fypv1cmq.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <mailman.15641.1132236229.20277.info-gnus-english@gnu.org>
On Thu, Nov 17 2005, Ian Zimmerman wrote:
> My main mail source is a directory with multiple spool folders,
> into which I split with procmail. I prefer splitting with procmail
> to Gnus' built-in nnmail-split mechanism for various reasons and
> don't want to change that. Now what if I want to fetch from the
> default system mailbox /var/mail/foo as well? I can add an mbox
> source for it,
,----[ <f1> v mail-sources RET ]
| mail-sources is a variable defined in `mail-source.el'.
| Its value is
| ((file)
| (directory :path "/foo/bar/procmail/" :suffix ""))
|
| Documentation:
| *Where the mail backends will look for incoming mail.
| This variable is a list of mail source specifiers.
| See Info node `(gnus)Mail Source Specifiers'.
`----
> but how does Gnus know what group these articles belong to? Do I
> have to define nnmail-split-methods?
Yes.
> Will that clash with the procmail way (i.e. will all articles then
> be routed to the one and only group in nnmail-split-methods,
> ignoring the procmail split)?
No. Just don't change `nnmail-resplit-incoming':
,----[ (info "(gnus)Mail Source Specifiers") ]
| There is also the variable `nnmail-resplit-incoming', if you set
| that to a non-`nil' value, then the normal splitting process is
| applied to all the files from the directory, *Note Splitting
| Mail::.
`----
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
prev parent reply other threads:[~2005-11-17 16:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 14:03 Ian Zimmerman
2005-11-17 14:51 ` ecocode
2005-11-17 16:07 ` Reiner Steib [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=v9fypv1cmq.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+from-uce@imap.cc \
--cc=Reiner.Steib@gmx.de \
/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).