From: "Mats Löfdahl" <xyzzy@chello.se>
Subject: Re: Two IMAP problems
Date: Mon, 15 Sep 2003 20:56:26 +0200 [thread overview]
Message-ID: <m3he3dg9t1.fsf@c213-89-193-148.cm-upc.chello.se> (raw)
In-Reply-To: <ilu1xuk35db.fsf@latte.josefsson.org>
Simon Josefsson <jas@extundo.com> writes:
> Mats Löfdahl <xyzzy@chello.se> writes:
>
>> Hm. I guess I'll want to find a way to manipulate the group buffer so
>> something like "imap:" or "xxx:" is substituted for the ugly
>> "nnimap+xxx:INBOX." part.
>
> If you name the secondary method "", it will look like
> nnimap:INBOX.foo. Getting rid of the INBOX part isn't possible, I
> think, unless you configure the server to work differently (it is
> possible in recent Cyrus IMAPD, I believe).
I realize that. I was thinking about how the group is presented in the
*Group* buffer, not what it is actually called on the server.
But that's a really minor thing. And probably not very practical,
since it would make it confusing when gnus asks for a group name as a
target for moving or copying a message.
>>>> The IMAP protocol does not support editing of messages.
>>>
>>> Oh. That's a real drawback, isn't it? Not that I edit the contents
>>> of messages very much. But I often want to repair threads with "T
>>> ^", which does not seem to be possible, then.
>>
>> Hmmm. So the problem is with the IMAP protocoll. Nothing much we can
>> do about that, I guess.
>>
>> But it appears you can move messages between nnimap groups and other
>> mail groups. Wouldn't it be possible to do it in a more roundabout
>> way, so you move the message to be edited to some temporary group on
>> another backend, do the editing, and then move it back. Or maybe do
>> this with copying rather than moving, so it doesn't get lost if there
>> are other problems while you're doing it. Like, copy out of the
>> nnimap, edit, copy back in, then remove original message.
>
> Yup, this would be possible. Not implemented yet though.
After writing my message, I actually thought I remembered a discussion
along those lines a long time ago.
>> [...]
>> I see no error messages and it even says that it's done expunging. But
>> the deleted messages are still there.
>
> Hm, and the B DEL command really sent the delete command to the server
> earlier? If so, it seems weird that the server doesn't says anothing
> more at the EXPUNGE command, it should say which articles was marked
> \Deleted and remove them.
>
>> They are marked "Y" when I enter the group again with "C-u SPC".
>
> Y? If so, then you didn't delete the message, you scored it down.
> Try B DEL on the article instead.
Oh. Right. I've been pressing "d" (It's a "d", so it has to mean
"delete"... :-) and "E". Now that I try B DEL it works.
>> (Don't know what the "NOT SINCE 31-Aug-2003" means. I'd entered that
>> group both yesterday and earlier today.)
>
> I think it means you have article expiring enabled, and that Gnus
> searches for eligible articles to expire.
Can I use the expire features to get the messages deleted properly? I
mean, so that when they expire, it's like if B DEL was pressed.
--
Mats Löfdahl
prev parent reply other threads:[~2003-09-15 18:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3iso5h4jv.fsf@c213-89-193-148.cm-upc.chello.se>
2003-09-07 0:33 ` Simon Josefsson
2003-09-07 9:01 ` Mats Löfdahl
[not found] ` <ilu1xuk35db.fsf@latte.josefsson.org>
2003-09-15 18:56 ` Mats Löfdahl [this message]
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=m3he3dg9t1.fsf@c213-89-193-148.cm-upc.chello.se \
--to=xyzzy@chello.se \
/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).