From: Hanak David <dhanak@inf.bme.hu>
Subject: Re: Duplicate messages
Date: Tue, 02 Sep 2003 21:32:36 +0200 [thread overview]
Message-ID: <m24qzv3s17.fsf@maui.hanak.hu> (raw)
In-Reply-To: <x34vfsbaz4a.fsf@bbrcu1.slac.stanford.edu>
On Tue, 02 Sep 2003, Philip Clark wrote:
> This only seems to work for incoming email ie. it saves the headers in
> .nnmail-cache to do it. I need to do it for exist mail folders. Any ideas?
Right. That's a tough one. I can't think of any direct methods, but I
have two workarounds in mind.
1. You could write a summary sort function that orders articles by their
Message-IDs. Then you could detect duplicates by skimming the summary
list looking for equally long articles one after another, checking
matches more carefully. Still a lot of work if you have many articles.
2. Remove the .nnmail-cache file, then respool all mails (at least those
where the duplicates appear), then filter the newly created
.nnmail-cache with sort | uniq -d. The ones listed will be hopefully
duplicates. Finally you can match the duplicate Message-IDs to article
numbers, and voila. Now that I think of it, it is quite complicated
this way, too.
I hope that helped.
David
parent reply other threads:[~2003-09-02 19:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <x34vfsbaz4a.fsf@bbrcu1.slac.stanford.edu>]
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=m24qzv3s17.fsf@maui.hanak.hu \
--to=dhanak@inf.bme.hu \
/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).