Gnus development mailing list
 help / color / mirror / Atom feed
From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Re: nnimap article editing
Date: Thu, 09 Oct 2008 13:52:02 +0200	[thread overview]
Message-ID: <kz8wsy2dgd.fsf@kafka.physik3.gwdg.de> (raw)
In-Reply-To: <muxbpxuvzlt.fsf@uzeb.lrde.epita.fr> (Didier Verna's message of "Thu, 09 Oct 2008 12:20:46 +0200")

Didier Verna <didier@xemacs.org> writes:
>nnimap doesn't support article editing

Yes, because the IMAP protocol doesn't allow it.

> So am I correct in assuming that we could implement nnimap article
> editing by simply downloading the article, editing it, destroying the
> old version and uploading the new one ?

That's how other mail clients do it, e.g. for removing attachments from
articles to save space on the server. The problem with this approach is
that the edited article gets a new UID from the server (and hence a new
article number in Gnus), which can lead to problems regarding sorting,
caching, calculation of article numbers, etc.

-David



  reply	other threads:[~2008-10-09 11:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-09 10:20 Didier Verna
2008-10-09 11:52 ` David Engster [this message]
2008-10-09 13:44   ` Ted Zlatanov
2008-10-09 14:58     ` David Engster
2008-10-09 17:21       ` Ted Zlatanov
2008-10-09 17:36     ` Reiner Steib
2008-10-09 19:04       ` Ted Zlatanov
2008-10-09 20:02         ` Christoph Conrad
2008-10-09 20:25           ` Ted Zlatanov
2008-10-09 21:23             ` Christoph Conrad
2008-10-09 20:45         ` Reiner Steib
2008-10-10 13:07           ` Ted Zlatanov
2008-10-10 18:14             ` Reiner Steib
2008-10-13 13:21               ` Ted Zlatanov
2008-11-03 15:25               ` Gnus CVS checkins (was: nnimap article editing) Ted Zlatanov
2008-11-03 20:19                 ` Gnus CVS checkins Reiner Steib
2008-11-03 20:46                   ` Ted Zlatanov

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=kz8wsy2dgd.fsf@kafka.physik3.gwdg.de \
    --to=deng@randomsample.de \
    --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).