9front - general discussion about 9front
 help / color / mirror / Atom feed
From: "Lyndon Nerenberg (VE7TFX/VE6BBM)" <lyndon@orthanc.ca>
To: 9front@9front.org
Subject: Re: [9front] upas/fs: copy messages between IMAP folders
Date: Sat, 29 May 2021 14:41:04 -0700	[thread overview]
Message-ID: <0322c68128a95c7e@orthanc.ca> (raw)
In-Reply-To: <E7A78FE36FDAAE545D7DA7EBEEBD1A0E@gmx.com>

> As a detail,
> IMAP, as a protocol, does not support moving
> messages between folders, so moving has to be
> implemented by first copying the message to the
> target folder and then deleting the original
> message from the source folder.  I chose to
> offload this logic to the mail client, as
> presented in the upas/nedmail patch, which
> could also be adapted to acme's Mail.

The IMAP "move" model has always been 'copy + store +flags \deleted'.
This performs the copy operation internally to the IMAP server, so
no data need go over the wire.  I haven't looked at your patch in
detail, but if you have devolved this to the case where a "copy"
between folders on the same server always involves a round trip
through the MUA, this is a horrible pessimization and the patch
should NOT be incorporated as is.

Doing IMAP "right" isn't always easy, and this is a case where you
have to do the extra work in order to do the correct optimization.
You need to reliably figure out if the source and destination paths
in the "move" correspond to the same server+user.  If they do, use
the IMAP COPY command, otherwise fall back to the MUA loop.

--lyndon

  reply	other threads:[~2021-05-30 22:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-28 15:10 risto.salminen
2021-05-28 15:29 ` Stanley Lieber
2021-05-28 16:26   ` risto.salminen
2021-05-29  3:50     ` Stanley Lieber
2021-05-29  9:44       ` risto.salminen
2021-05-29 21:41         ` Lyndon Nerenberg (VE7TFX/VE6BBM) [this message]
2021-05-31 11:31           ` Risto Salminen
2021-05-31 22:34             ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2021-05-28 22:11 ` kjn
2021-05-31 11:41 ` Risto Salminen
2021-06-09 21:41   ` igor
2021-06-10 11:02     ` Risto Salminen

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=0322c68128a95c7e@orthanc.ca \
    --to=lyndon@orthanc.ca \
    --cc=9front@9front.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).