Gnus development mailing list
 help / color / mirror / Atom feed
From: "Ted Zlatanov" <tzz@lifelogs.com>
Subject: Re: nnimap: editing articles
Date: 8 Feb 2006 15:11:49 -0500	[thread overview]
Message-ID: <4nslqt8vay.fsf@lifelogs.com> (raw)
In-Reply-To: <v9ek2fm1b7.fsf_-_@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Tue, 07 Feb 2006 20:11:24 +0100")

On  7 Feb 2006, reinersteib+gmane@imap.cc wrote:

On Tue, Feb 07 2006, Uwe Brauer wrote:
>
>> Well and it does not work, because when I save, and reenter the buffer
>> the editing result is not there anymore. How should the editing
>> solution work?
>
> Article editing isn't implemented in the nnimap back end.  I'm not
> sure if the protocol (IMAP) allows it.  Simon?

IMAP does not allow editing, you have to delete and store the new
article, AFAIK (from reading the rev4 RFC).

> IIRC someone suggested to move the article to a local group, edit it
> and move it back to IMAP might be a workaround.  Thunderbird 1.5
> supports deleting and detaching (stripping) attachments which works
> also on IMAP.  I just tried it and it seems to me, they do something
> similar.  At least when looking at the "modified" article with Gnus, I
> saw an `N' (`gnus-recent-mark') and the article number is different.

Right.  So basically, implementing labels is easier with flags than
with IMAP editing, and much faster.

IMAP flags can be any atom name, which means it can not contain:

( ) { % * " \ ]
space
control characters
characters with the high bit (8-bit characters)

I would stick to a-zA-Z0-9_.- as the character set...  It's probably
safer to avoid the other characters such as @ or = IMO.

A custom flag "MyFlag" can be set like this:

APPEND "Inbox" (\Seen MyFlag) [etc...]

I used a message by Mark Crispin to get this information:
http://groups.google.com/group/comp.mail.imap/msg/ab2bab9722a80272?dmode=source&hl=en

I propose that for backends that can't support flags, e.g. nntp or
nnrss, we use the gnus-registry (if installed) to track the flags by
message-ID as a fallback.

Ted



  reply	other threads:[~2006-02-08 20:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-06 11:22 set labels in nnml or nnfolder groups Uwe Brauer
2006-02-06 13:22 ` Reiner Steib
2006-02-06 14:37   ` Uwe Brauer
2006-02-06 15:09   ` mozilla (was: set labels in nnml or nnfolder groups) Uwe Brauer
2006-02-06 19:06     ` mozilla Ted Zlatanov
2006-02-07 12:25       ` mozilla Uwe Brauer
2006-02-07 15:41         ` mozilla Ted Zlatanov
2006-02-07 17:54           ` mozilla Uwe Brauer
2006-02-07 19:11             ` nnimap: editing articles (was: mozilla) Reiner Steib
2006-02-08 20:11               ` Ted Zlatanov [this message]
2006-02-09 15:23                 ` nnimap: editing articles Reiner Steib
2006-02-11 22:01               ` Simon Josefsson
2006-02-13 19:24                 ` Ted Zlatanov
2006-02-13 20:06                   ` Simon Josefsson
2006-02-13 22:22                   ` Steven E. Harris
2006-02-07 12:27       ` mozilla Uwe Brauer

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=4nslqt8vay.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    /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).