From: David Z Maze <dmaze@mit.edu>
Subject: Re: Duplicate suppression, other processing at split time
Date: Mon, 06 Jun 2005 15:54:37 -0400 [thread overview]
Message-ID: <y68zmu3z2f6.fsf@scrubbing-bubbles.mit.edu> (raw)
In-Reply-To: <y68d5r5rhk8.fsf@biohazard-cafe.mit.edu>
David Z Maze <dmaze@mit.edu> writes:
> If I wind up with the same message delivered to me twice, can I cause
> the second message to get dropped at split time?
>
> (Procmail scares me -- I understand what Gnus does, and
> nn*-split-fancy is kind of elegant in its own way -- but I think it is
> an option, if this is something easy to do there.)
It turned out that dup suppression is something explicitly mentioned
in procmailex(5), so I'm doing it (along with adding a Message-Id if
need be) in procmail.
--dzm
prev parent reply other threads:[~2005-06-06 19:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 19:41 David Z Maze
2005-06-01 20:07 ` David Z Maze
2005-06-02 17:46 ` Ted Zlatanov
2005-06-06 19:54 ` David Z Maze [this message]
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=y68zmu3z2f6.fsf@scrubbing-bubbles.mit.edu \
--to=dmaze@mit.edu \
/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).