From: Michael R Cook <mcook@cognex.com>
Subject: Re: spam filtering on message-id (was: Hmm.. 2 q's)
Date: 21 Jul 1997 11:56:58 -0400 [thread overview]
Message-ID: <r4pvsccsad.fsf@cognex.com> (raw)
In-Reply-To: Ken Raeburn's message of "20 Jul 1997 17:36:06 -0700"
>>>>> "KR" == Ken Raeburn <raeburn@cygnus.com> writes:
KR> So maybe the solution is not to discard, but to bounce, thus pestering
KR> people with broken configs.
Most of the invalid message-ids come via mailing lists.
Bouncing would usually have the affect of getting me
auto-unsubscribed from those lists.
next prev parent reply other threads:[~1997-07-21 15:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-07-13 9:56 Hmm.. 2 q's Markus Stenberg
1997-07-13 12:50 ` Andy Eskilsson
[not found] ` <wkd8ondpwa.fsf@peorth.gweep.net>
1997-07-13 14:56 ` Markus Stenberg
1997-07-14 18:19 ` Scott Blachowicz
1997-07-14 19:01 ` Randal Schwartz
1997-07-19 16:14 ` spam filtering on message-id (was: Hmm.. 2 q's) Michael R Cook
1997-07-21 0:36 ` Ken Raeburn
1997-07-21 15:56 ` Michael R Cook [this message]
1997-07-23 20:06 ` Ken Raeburn
1997-07-14 21:01 ` Hmm.. 2 q's Paul Franklin
1997-07-14 19:53 ` Karl Kleinpaste
1997-07-14 21:41 ` Scott Blachowicz
1997-07-14 21:45 ` Karl Kleinpaste
1997-07-13 17:01 ` Aaron M. Ucko
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=r4pvsccsad.fsf@cognex.com \
--to=mcook@cognex.com \
/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).