Gnus development mailing list
 help / color / mirror / Atom feed
From: "\"Christian Nybø\"" <chr@mediascience.no>
Subject: Re: Forging my return address with gnus
Date: 16 Jun 1998 20:32:33 +0200	[thread overview]
Message-ID: <4y90mxqjsu.fsf@sgichr.sib.hl.no> (raw)
In-Reply-To: Justin Sheehy's message of "16 Jun 1998 13:52:21 -0400"

Justin Sheehy <justin@linus.mitre.org> writes:

> chr@mediascience.no (Christian Nybø) writes:
> 
> > Justin Sheehy <justin@linus.mitre.org> writes:
> > 
> > > Forging your address is never a good idea.
> 
> > Does that apply to forging in general, or forging as a spam-protection 
> > scheme?  The last I agree with, but I find it comfortable to use my
> > usual email addresses even if I'm in a different domain.
> 
> I guess I don't know what you mean by a "different domain".

Domain as in domain name.  If I'm sending from a machine whose FDQN
has little to do with the domain at which I receive mail. 

> Sending email or news messages with an invalid address, as the
> original poster was preparing to do, is always wrong.

Yup, no problem with that.  

Will this qualify as forging my address: 
	my home box is known as sgichr.sib.hl.no.  Still, I wish to
	send and receive mail as chr@mediascience.no.

Is there anything wrong with setting message-user-mail-address to
chr@mediascience.no, even if I don't use the MTA at mediascience.no
when sending mail?
-- 
chr


  parent reply	other threads:[~1998-06-16 18:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3emwqu8dx.fsf@colony-4426.demon.co.uk>
     [not found] ` <glm90mxe685.fsf@caffeine.mitre.org>
1998-06-16 17:05   ` Christian Nybø
1998-06-16 17:52     ` Justin Sheehy
1998-06-16 18:19       ` Alan Shutko
1998-06-16 18:32       ` "Christian Nybø" [this message]
1998-06-16 18:54         ` Justin Sheehy

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=4y90mxqjsu.fsf@sgichr.sib.hl.no \
    --to=chr@mediascience.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).