From: steve@miranova.com (Steven L. Baur)
Subject: Re: Getting new mail with nnml
Date: 04 Nov 1995 19:43:39 -0800 [thread overview]
Message-ID: <m2u44ju3o4.fsf@diana.miranova.com> (raw)
In-Reply-To: steve@miranova.com's message of 04 Nov 1995 17:41:41 -0800
Let me rephrase that ...
I just wrote:
>Another problem which manifests itself similarly is Gnus will bogusly
>match a shorter nnml folder name to a spool file (in case 2 above) but
>get it correct for cases 1 & 3. Eg. I have a nnml folder named
^^^ ^^ ^^^^^^^ ^^^ ^^^^^ ^ ^
(Initial startup, and one group at a time).
>gnus-list which is intended to have messages inserted *manually only*
>to it. I have another nnml folder dgnus-list which is intended to be
>filled by mail split by procmail from ~/spool/dgnus-list.spool. When
>I do M-2 g all of the dgnus-list.spool gets put into nnml:gnus-list.
This is only true with Gnus 5.0. Sgnus does not handle *any* batch
mail splitting correctly (with my settings).
--
steve@miranova.com baur
next prev parent reply other threads:[~1995-11-05 3:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-05 0:25 Sean Lynch
1995-11-05 1:41 ` Steven L. Baur
1995-11-05 3:43 ` Steven L. Baur [this message]
1995-11-06 13:33 ` Lars Magne Ingebrigtsen
1995-11-07 18:46 ` Sean Lynch
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=m2u44ju3o4.fsf@diana.miranova.com \
--to=steve@miranova.com \
/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).