Gnus development mailing list
 help / color / mirror / Atom feed
From: Ken Raeburn <raeburn@raeburn.org>
Subject: nnimap and crossposting (Re: Moving from nnml to nnimap...)
Date: Fri, 02 Jan 2004 14:17:58 -0500	[thread overview]
Message-ID: <tx1u13eupll.fsf_-_@raeburn.org> (raw)
In-Reply-To: <tx18ym4wfem.fsf@raeburn.org> (Ken Raeburn's message of "Tue, 25 Nov 2003 12:01:53 -0500")

The silence is deafening....  So, is no one actually using
cross-posting when splitting articles in an nnimap server?

My experimentation so far (playing with imtest, don't have the guest
account and nnimap config set up yet) seems to indicate that the marks
won't be propagated.  If this is the case, I think it would be a good
idea for the documentation to indicate this.

(Actually, seen and expire are the only marks I really care about, if
they're done any differently.)

I wrote, in November:
> I use crossposting a lot in my incoming mail splitting, though.
> I want the messages marked for expiration in all groups at the same
> time it's marked for expiration in one of the other groups.  Do marks
> get propagated for cross-posted articles in nnimap?

Ken



  reply	other threads:[~2004-01-02 19:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-24  0:59 Moving from nnml to nnimap Jinhyok Heo
2003-11-24  1:48 ` Daniel Pittman
2003-11-24 16:24   ` Ted Zlatanov
2003-11-25 17:01     ` Ken Raeburn
2004-01-02 19:17       ` Ken Raeburn [this message]
2004-01-02 21:41         ` nnimap and crossposting (Re: Moving from nnml to nnimap...) Simon Josefsson
2004-01-04  3:28           ` Ken Raeburn
2004-01-04 15:13             ` Simon Josefsson
2004-01-07  1:00               ` Ken Raeburn
2004-01-07  1:29                 ` Simon Josefsson
2004-01-07  1:40                   ` Simon Josefsson
2004-01-13  7:59                   ` Ken Raeburn
2004-01-13  9:06                     ` Simon Josefsson
2004-01-09  9:13                 ` Kai Grossjohann
2004-01-13  8:03                   ` Ken Raeburn

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=tx1u13eupll.fsf_-_@raeburn.org \
    --to=raeburn@raeburn.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).