From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: widening in nnml split does not work
Date: Sat, 25 Jan 2003 19:46:34 -0500 [thread overview]
Message-ID: <m3n0lozqj9.fsf@heechee.beld.net> (raw)
In-Reply-To: <84wukslxld.fsf@lucy.is.informatik.uni-duisburg.de> (kai.grossjohann@uni-duisburg.de's message of "Sat, 25 Jan 2003 22:37:50 +0100")
On Sat, 25 Jan 2003, kai.grossjohann@uni-duisburg.de wrote:
> Well, nnmaildir is a mail backend which presumably supports
> splitting. But it is not based on nnmail.
I see. There's no nnmaildir-split-fancy either, since the incoming
mail is already split usually with maildir. So I won't worry about it
until users ask for fancy splitting for nnmaildir.
Ted
next prev parent reply other threads:[~2003-01-26 0:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-25 6:41 Ted Zlatanov
2003-01-25 10:24 ` Kai Großjohann
2003-01-25 12:35 ` Ted Zlatanov
2003-01-25 13:14 ` Kai Großjohann
2003-01-25 14:48 ` Simon Josefsson
2003-01-25 15:14 ` Kai Großjohann
2003-01-25 15:29 ` Ted Zlatanov
2003-01-25 15:41 ` Simon Josefsson
2003-01-25 16:18 ` Ted Zlatanov
2003-01-25 21:37 ` Kai Großjohann
2003-01-26 0:46 ` Ted Zlatanov [this message]
2003-01-25 21:36 ` Kai Großjohann
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=m3n0lozqj9.fsf@heechee.beld.net \
--to=tzz@lifelogs.com \
--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).