Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: info-gnus-english@gnu.org
Subject: Re: gnus INBOX housekeeping, kept (copies of) mail lying around
Date: Thu, 07 Jan 2016 22:03:08 +0800	[thread overview]
Message-ID: <87lh817ahv.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87h9ipbvkk.fsf@hillenius.net>

Gijs Hillenius <gijs@hillenius.net> writes:

> [...] hope snipping this much is ok..
>
>>>
>>> If my Gnus (5.13, part of Debian's Emacs) copies messages back into
>>> the INBOX, does fancy-split set the delete/expunge IMAP flag to
>>> these?
>>>
>>> Because, if it does not flag them for deletion, would that perhaps
>>> explain why the nightly Cyrus pruning does not do anything? Cyrus is
>>> set to remove from disk all messages that have been flagged for
>>> deletion for 3 days.
>>
>> No, no flags are set. From IMAP's point of view, splitting is simply a
>> MOVE operation. Sorry, I misspoke earlier when I said the messages
>> were *copied* back into the same group. They're actually MOVEd. That
>> means there's only ever one copy of the message, but it gets a new
>> UUID number each time.
>>
>> No new flags are set at all.
>
> So, these message come back int the INBOX, but are not shown anymore by
> Gnus. They are also not marked as deletable and that would explain why
> Cyrus does not remove them from disk, yes?

Right. Once they are given the Seen flag, that flag sticks with them
even if they are moved around (including "moved" into the same group
they were already in). That Seen flag means Gnus won't show them to you
again.

I think the distinction here is between message deletion, and adding the
"Deleted" flag. Deletion occurs as part of the move process (the message
is in one instant removed from one group and added to another). If
you're MOVEing to the same group, the message is deleted from that
group, then added back to that group. But it keeps its old flags, and no
other flags are put on it (there's nothing in the splitting process that
would add a Deleted flag), so Cyrus doesn't see any reason why it should
garbage-collect the message at the end of the day.

Hope that makes sense.

E



  reply	other threads:[~2016-01-07 14:03 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-05 11:04 Gijs Hillenius
2016-01-05 11:17 ` Eric Abrahamsen
2016-01-05 11:26 ` CHENG Gao
2016-01-05 12:38 ` Gijs Hillenius
2016-01-05 12:54   ` Eric Abrahamsen
     [not found]   ` <mailman.1737.1451998456.843.info-gnus-english@gnu.org>
2016-01-05 13:07     ` Gijs Hillenius
2016-01-05 13:24       ` Eric Abrahamsen
     [not found]       ` <mailman.1740.1452000295.843.info-gnus-english@gnu.org>
2016-01-05 14:16         ` Gijs Hillenius
2016-01-05 14:48           ` Gijs Hillenius
2016-01-05 15:11             ` Eric Abrahamsen
     [not found]             ` <mailman.1745.1452006719.843.info-gnus-english@gnu.org>
2016-01-07  7:28               ` Gijs Hillenius
2016-01-07  8:54                 ` Eric Abrahamsen
     [not found]                 ` <mailman.1877.1452156877.843.info-gnus-english@gnu.org>
2016-01-07  9:14                   ` Gijs Hillenius
2016-01-07 14:03                     ` Eric Abrahamsen [this message]
     [not found]                     ` <mailman.1882.1452175419.843.info-gnus-english@gnu.org>
2016-01-08  7:54                       ` is this a bug in gnus v5.13? " Gijs Hillenius
2016-01-08 10:33                         ` Eric Abrahamsen
     [not found]                         ` <mailman.1947.1452249217.843.info-gnus-english@gnu.org>
2016-01-08 11:27                           ` Gijs Hillenius
2016-01-09  4:02                             ` Eric Abrahamsen
2016-01-09  9:44                               ` Adam Sjøgren
2016-01-11  6:56                                 ` Eric Abrahamsen
2016-01-11  9:28                                   ` Adam Sjøgren
     [not found]                               ` <mailman.2029.1452332680.843.info-gnus-english@gnu.org>
2016-01-11  9:29                                 ` Gijs Hillenius
2016-01-11  9:33                                   ` Adam Sjøgren
2016-01-11  9:40                                   ` Eric Abrahamsen
     [not found]                                   ` <mailman.2130.1452505220.843.info-gnus-english@gnu.org>
2016-01-11 11:34                                     ` Gijs Hillenius
2016-01-11 11:48                                       ` Adam Sjøgren
     [not found]                                       ` <mailman.2136.1452512951.843.info-gnus-english@gnu.org>
2016-01-11 12:54                                         ` Gijs Hillenius
2016-01-11 13:18                                         ` Gijs Hillenius
2016-01-11 15:47                                           ` Adam Sjøgren
     [not found]                                           ` <mailman.2152.1452527287.843.info-gnus-english@gnu.org>
2016-01-18  8:08                                             ` FIXED " Gijs Hillenius

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=87lh817ahv.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=info-gnus-english@gnu.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).