From: Justin Sheehy <justin@linus.mitre.org>
Subject: Re: Forging my return address with gnus
Date: 16 Jun 1998 14:54:29 -0400 [thread overview]
Message-ID: <glmium1dvoa.fsf@caffeine.mitre.org> (raw)
In-Reply-To: <4y90mxqjsu.fsf@sgichr.sib.hl.no>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 536 bytes --]
"Christian Nybø" <chr@mediascience.no> writes:
> 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?
No, not at all. There's nothing wrong with that.
The person who asked the question that I was responding to was asking
how to insert ".spam." or somesuch thing into their address.
If your address is valid and will be delivered to you, then there is
definitely no problem.
--
Justin Sheehy
In a cloud bones of steel.
prev parent reply other threads:[~1998-06-16 18:54 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ø"
1998-06-16 18:54 ` Justin Sheehy [this message]
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=glmium1dvoa.fsf@caffeine.mitre.org \
--to=justin@linus.mitre.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).