From: Scott Blachowicz <scott@statsci.com>
Cc: "(ding)" <ding@gnus.org>
Subject: Re: Hmm.. 2 q's
Date: Mon, 14 Jul 1997 11:19:13 -0700 [thread overview]
Message-ID: <199707141819.LAA13825@knife.statsci.com> (raw)
In-Reply-To: Your message of "13 Jul 1997 09:48:21 -0400." <wkd8ondpwa.fsf@peorth.gweep.net>
Stainless Steel Rat <ratinox@peorth.gweep.net> wrote:
> Bad idea: there is no requirement that a Message-ID string contain a domain
> name. The only significant requirement is that every Message-ID be unique,
Are there requirements on the message-id as far as legal characters &
such? (e.g. maybe there should be precisely one @ character?) I've been
doing some filtering on message-id's in my mailagent rules:
Message-ID: /\<[^\@]*\>/, /\@.*\@/, /\S.*\</, /\>.*\S/, /^[^<]*$/, /^[^>]*$/ {
# Spam
ANNOTATE X-trashed-by bogus-message-id;
SAVE +trash; ABORT -t;
};
which matches:
1) no @ between the <...>.
2) 2 @'s
3) junk before a <
4) junk after a >
5) no <
6) no >
and picks up a few matches, but I've also gotten some hits on match #2 for
non-spam email, so I'm not so sure.
Scott Blachowicz Ph: 206/283-8802x240 Mathsoft (Data Analysis Products Div)
1700 Westlake Ave N #500
scott@statsci.com Seattle, WA USA 98109
Scott.Blachowicz@seaslug.org
next prev parent reply other threads:[~1997-07-14 18:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-07-13 9:56 Markus Stenberg
1997-07-13 12:50 ` Andy Eskilsson
1997-07-13 17:01 ` Aaron M. Ucko
[not found] ` <wkd8ondpwa.fsf@peorth.gweep.net>
1997-07-13 14:56 ` Markus Stenberg
1997-07-14 18:19 ` Scott Blachowicz [this message]
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
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
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=199707141819.LAA13825@knife.statsci.com \
--to=scott@statsci.com \
--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).