From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: nnmaildir & expiry (again..)
Date: Fri, 24 Sep 2004 10:06:54 -0400 [thread overview]
Message-ID: <m3mzzf4v6z.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <86hdq06f2i.fsf@ID-110038.user.uni-berlin.de> =?iso-8859-1?Q?=28Rapha=EBl?= Berbain's message of "Tue, 21 Sep 2004 12:00:07 +0200")
raphael.berbain@free.fr (Raphaël Berbain) wrote:
> The problem is, after being expired the article appears unread again
> in the target group.
If you want all the articles in the target group to be marked as read,
you could set (always-marks . ['(read)]) in the group parameters.
> What should be the right behavior ?
Copying all the marks (except 'expire) from the original article would
probably be good. I'll have a look at that.
> Regardless of this, I think both backends should behave in the same
> way.
Yes, the backend interface ought to be redesigned to put less (i.e.,
no) policy decisions in the backends. But that's a big job.
paul
next prev parent reply other threads:[~2004-09-24 14:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-21 10:00 Raphaël Berbain
2004-09-24 14:06 ` Paul Jarc [this message]
2004-09-26 10:52 ` Raphaël Berbain
2004-09-27 15:16 ` Paul Jarc
2004-09-28 16:51 ` Raphaël Berbain
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=m3mzzf4v6z.fsf@multivac.cwru.edu \
--to=prj@po.cwru.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).