From: Per Abrahamsen <abraham@dina.kvl.dk>
Cc: ding@ifi.uio.no
Subject: Re: Gnus5, procmail, and reading mail lists.
Date: Tue, 14 Nov 1995 14:04:48 +0100 [thread overview]
Message-ID: <199511141304.OAA20140@ssv4.dina.kvl.dk> (raw)
In-Reply-To: steve@miranova.com's message of 13 Nov 1995 17:43:31 -0800
>>>>> "SLB" == Steven L Baur <steve@miranova.com> writes:
SLB> Exactly. You end up with two messages with identical message-ids
SLB> going into the same nnml folder, one of which is now in a Gnus black
SLB> hole, and cannot be referenced reasonably, or two identical messages
SLB> going into the hyperarchive.
If you use procmail, I suggest using the following code to sort out
duplicates (stolen from someone on the procmail list):
#####################
# Prevent dubplicates
:0
{
:0 Whc: .msgid.lock # w produces (non-fatal) error msg
| formail -D 8192 .msgid.cache
:0 a
mail/duplicate/.
}
next prev parent reply other threads:[~1995-11-14 13:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-14 1:43 Steven L. Baur
1995-11-14 13:04 ` Per Abrahamsen [this message]
1995-11-15 2:42 ` Steven L. Baur
1995-11-14 16:27 ` Joe Hildebrand
1995-11-14 17:22 ` Scott Blachowicz
1995-11-14 21:35 ` Joe Hildebrand
1995-11-15 6:58 ` Sudish Joseph
1995-11-15 18:46 ` Scott Blachowicz
1995-11-15 4:37 ` Sudish Joseph
1995-11-15 14:32 ` Per Abrahamsen
1995-11-15 15:50 ` Kai Grossjohann
1995-11-15 16:13 ` Per Abrahamsen
1995-11-15 17:50 ` Steven L. Baur
1995-11-17 21:18 ` Jason L Tibbitts III
1995-11-17 21:40 ` Joe Hildebrand
-- strict thread matches above, loose matches on Subject: below --
1995-11-14 1:55 Steven L. Baur
1995-11-13 22:21 Steven L. Baur
1995-11-13 20:33 Steven L. Baur
1995-11-13 22:43 ` Joe Hildebrand
1995-11-14 19:52 ` Edward J. Sabol
1995-11-13 17:48 Mark Borges
1995-11-13 20:16 ` Joe Hildebrand
1995-11-14 0:24 ` Mark Borges
1995-11-15 6:19 ` Mark Borges
1995-11-15 8:17 ` Steven L. Baur
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=199511141304.OAA20140@ssv4.dina.kvl.dk \
--to=abraham@dina.kvl.dk \
--cc=ding@ifi.uio.no \
/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).