From: Nevin Kapur <nevin@jhu.edu>
Subject: Re: Problems with getting new mail at any particular level.
Date: 14 Mar 2001 09:47:04 -0500 [thread overview]
Message-ID: <m366hcpfvb.fsf@fermat.mts.jhu.edu> (raw)
In-Reply-To: <vaf7l1sg1e9.fsf@lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Wed, 14 Mar 2001 10:12:14 +0100")
On Wed, 14 Mar 2001, Kai Großjohann wrote:
> On 14 Mar 2001, Nevin Kapur wrote:
>
>> Fortunately, I found I workaround. My usual setup is to use
>> procmail to split my incoming mail into just two folders FM and
>> NFM, and then use Gnus' fancy spitting by setting
>> nnmail-resplit-incoming to t, for finer control. I use
>
> I see. I think if you hit `1 g' and the only level-1 group is
> nnml:foo, then Gnus will only look at ~/.spool/foo.
I think this is correct. I stepped through debugging
mail-sources-fetch and this was the behavior I observed.
> I take it that there are no groups nnml:FM and nnml:NFM?
Exactly.
I am interested in hearing from folks who use procmail and the
directory entry in mail-sources. Does '1 g' work for them? Does
anybody else use procmail *and* nnmail-resplit-incoming? Does '1 g'
work in that case?
--
Nevin
next prev parent reply other threads:[~2001-03-14 14:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-13 20:06 Nevin Kapur
2001-03-13 22:18 ` Kai Großjohann
2001-03-13 22:25 ` Nevin Kapur
2001-03-13 22:58 ` Kai Großjohann
2001-03-14 5:19 ` Nevin Kapur
2001-03-14 9:12 ` Kai Großjohann
2001-03-14 14:47 ` Nevin Kapur [this message]
2001-03-14 14:53 ` ShengHuo ZHU
2001-03-14 15:57 ` Nevin Kapur
2001-03-14 20:53 ` ShengHuo ZHU
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=m366hcpfvb.fsf@fermat.mts.jhu.edu \
--to=nevin@jhu.edu \
/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).