From: Steinar Bang <sb@metis.no>
Subject: Re: New feature request: "faked" identity, and supercede
Date: 09 Nov 1996 19:35:32 +0100 [thread overview]
Message-ID: <wh918bce17.fsf@norne.metis.no> (raw)
In-Reply-To: David Moore's message of 09 Nov 1996 09:33:01 -0800
>>>>> David Moore <dmoore@UCSD.EDU>:
> This is a good plan, we can also suggest that all email forgers
> use 'metis.no' as a hostname when forging. :) The current trend of
> spammers is to use valid hostnames, except ones they don't have accounts
> on. So it wouldn't help much there.
I wasn't thinking of stopping spammers. I was just trying to put some
obstacles in the way of "humorous" cow-orkers sending email to
all@metis.no as elvis@heaven.com or somesuch.
"Let them eat Netscape"
-- Marie Antoinette
> I guess I could see someone wanting their mail reader to check the
> addresses of incoming messages for host validity, something called
> similar to mc-verify. You might want to go further and have your
> 'forgery-verify' routine look at the insertion points (received
> from, or path headers) compared with the addresses. But this seems
> like a lot of work, and the heuristics might be wrong often?
Nah! Overkill.
next prev parent reply other threads:[~1996-11-09 18:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-10-29 17:45 Steinar Bang
1996-10-29 22:30 ` Edward J. Sabol
1996-10-29 22:47 ` Lars Magne Ingebrigtsen
1996-11-05 21:16 ` Lars Magne Ingebrigtsen
1996-11-06 7:30 ` Steinar Bang
1996-11-06 8:58 ` Lars Magne Ingebrigtsen
1996-11-06 11:37 ` Steinar Bang
1996-11-06 22:00 ` Lars Magne Ingebrigtsen
1996-11-07 8:01 ` Steinar Bang
1996-11-09 4:51 ` Lars Magne Ingebrigtsen
1996-11-09 15:13 ` Steinar Bang
1996-11-09 17:33 ` David Moore
1996-11-09 18:35 ` Steinar Bang [this message]
1996-11-09 20:24 ` Hrvoje Niksic
1996-11-10 6:45 ` Steven L Baur
1996-11-06 19:04 ` Sten Drescher
1996-11-08 19:05 ` Steinar Bang
1996-11-08 20:50 ` Steven L Baur
1996-11-09 21:36 ` Mark Eichin
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=wh918bce17.fsf@norne.metis.no \
--to=sb@metis.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).