Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: Problem with dovecot expiry to a different group/imap folder
Date: Thu, 24 Oct 2019 23:05:00 +0200	[thread overview]
Message-ID: <86pnilkg77.fsf@dod.no> (raw)
In-Reply-To: <86tv7xkgns.fsf@dod.no>

>>>>> Steinar Bang <sb@dod.no>:

> I seem to remember that there was an issue with nnimap expiry to a
> different group when the server is dovecot.

> But I can't remember what the issue was (something to do with the date
> of the moved message that would get the date of the move instead of the
> date the original message was received).

This was the issue:
 commit d5427e71da28856c5e43396a37ffd0c906947499
 Author: Lars Magne Ingebrigtsen <larsi@gnus.org>
 Date:   Mon Mar 14 20:23:30 2016 +0100

    Disable MOVE more for Dovecot
    
    * lisp/gnus/nnimap.el (nnimap-process-expiry-targets): Also
    disable MOVE when expirying.
    (nnimap-split-incoming-mail): And when splitting mail.

If I remember correctly this means that instead of using IMAP MOVE,
articles are moved by a COPY (which gives the target message a new date)
followed by a DELETE.

> Is this still an issue? Is there a possibility of getting it fixed?

It would be very niced if this issue is fixed, because it means I can go
back to expiring to an archive folder without having the dates on the
target message broken.p

Thanks!


- Steinar




  reply	other threads:[~2019-10-24 21:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24 20:55 Steinar Bang
2019-10-24 21:05 ` Steinar Bang [this message]
2019-10-24 21:11   ` Steinar Bang
2019-10-24 21:14     ` Steinar Bang
2019-10-24 22:39       ` Eric Abrahamsen
2019-10-25 15:15         ` Steinar Bang

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=86pnilkg77.fsf@dod.no \
    --to=sb@dod.no \
    --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).