Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Brent Busby <brent@jfi.uchicago.edu>
Cc: ding@gnus.org
Subject: Re: X-Gnus-Article-Number cleanup
Date: Thu, 28 Jan 2021 06:03:02 +0100	[thread overview]
Message-ID: <87wnvx4prt.fsf@gnus.org> (raw)
In-Reply-To: <8xxr1m7iccn.fsf@jfi.uchicago.edu> (Brent Busby's message of "Tue, 26 Jan 2021 16:04:40 -0600")

Brent Busby <brent@jfi.uchicago.edu> writes:

> I've been trying to figure out what to do to repair mailboxes like this
> so Gnus will see all of them again.  Using sed to completely get rid of
> all X-Gnus-Article-Number and/or Xref lines and then doing meta-g on the
> group seems to work, but also seems a little brutal.  All of this makes
> it very hazardous to move messages around between mailboxes, especially
> if copying into an existing nnfolder, even within Gnus, with no
> involvement from any other mailreaders.  It becomes necessary to do
> header cleanup afterward to make all messages visible again.
>
> What do you think would be the recommended way to hammer a mailbox's
> Gnus metadata back into shape in situations like these?

That sounds like a good way to do it, but it'd be nice if we could
figure out what's going wrong instead.  I'm assuming you're using
nnfolder?  And you say that `B c'-ing an article to one of these groups
doesn't result in the message getting the X-Gnus-Article-Number header?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no


  reply	other threads:[~2021-01-28  5:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-26 22:04 Brent Busby
2021-01-28  5:03 ` Lars Ingebrigtsen [this message]
2021-01-28 16:49   ` Brent Busby
2021-02-01  8:58     ` Lars Ingebrigtsen
2021-02-01 15:23       ` Brent Busby

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=87wnvx4prt.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=brent@jfi.uchicago.edu \
    --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).