Gnus development mailing list
 help / color / mirror / Atom feed
From: David Moore <dmoore@UCSD.EDU>
Subject: Re: New feature request: "faked" identity, and supercede
Date: 09 Nov 1996 09:33:01 -0800	[thread overview]
Message-ID: <rvram3b2cy.fsf@sdnp5.ucsd.edu> (raw)
In-Reply-To: Steinar Bang's message of 09 Nov 1996 16:13:15 +0100

Steinar Bang <sb@metis.no> writes:
> You can add another thing to this list:
>  it might be a good idea to quietly override a custom email address
>  for a domain that doesn't have an MX record, or an A record, in DNS
> 
> Leave this fact out of the documentation, and out of the elisp
> comments (maybe...).  If someone wants to override this they'll have
> to work at it, which would redirect email forger wannabess to Netscape
> or something.

	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.  Now it might be useful to check
something like this just so it can _tell_ the user that they have their
return address configured incorrectly.

	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?

-- 
David Moore <dmoore@ucsd.edu>       | Computer Systems Lab      __o
UCSD Dept. Computer Science - 0114  | Work: (619) 534-8604    _ \<,_
La Jolla, CA 92093-0114             | Fax:  (619) 534-1445   (_)/ (_)
<URL:http://oj.egbt.org/dmoore/>    | Solo Furnace Creek 508 -- 1996!


  reply	other threads:[~1996-11-09 17:33 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 [this message]
1996-11-09 18:35                   ` Steinar Bang
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=rvram3b2cy.fsf@sdnp5.ucsd.edu \
    --to=dmoore@ucsd.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).