From: Chris Richards <cjr@netpliance.net>
Cc: Chris Richards <cjr@netpliance.net>, ding@gnus.org
Subject: Re: Sorting not Sorting
Date: 29 Feb 2000 08:00:41 -0600 [thread overview]
Message-ID: <6ed7pgun06.fsf@sloth.netpliance.net> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "28 Feb 2000 22:20:48 +0100"
Howdy.
Here is an update. See below for a few comments.
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> What happens if you do `B q' on a mail which was incorrectly put in
> nnml:mbox?
They report that they should go to the split mailbox. The third broken
rule (word@ address) split correctly last night. However, the other
two did not.
> What happens if you set mail-source-delete-incoming to nil, then let
> mail accumulate, then fetch it, then `G f' the corresponding
> ~/Mail/Incoming* file, look for a mail which was incorrectly put in
> nnml:mbox, do `B q' and `B r' there?
I'll try this today.
Cheers,
cjr
prev parent reply other threads:[~2000-02-29 14:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-28 3:59 Chris Richards
2000-02-28 9:32 ` Kai Großjohann
2000-02-28 18:28 ` Chris Richards
2000-02-28 21:20 ` Kai Großjohann
2000-02-29 14:00 ` Chris Richards [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=6ed7pgun06.fsf@sloth.netpliance.net \
--to=cjr@netpliance.net \
--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).