From: merlyn@stonehenge.com (Randal L. Schwartz)
Cc: ding@gnus.org
Subject: Re: using `equal' on email addresses
Date: 06 Feb 2001 12:14:41 -0800 [thread overview]
Message-ID: <m1ofwf4lhq.fsf@halfdome.holdit.com> (raw)
In-Reply-To: <87elxb7fdf.fsf@deneb.enyo.de>
>>>>> "Florian" == Florian Weimer <fw@deneb.enyo.de> writes:
Florian> merlyn@stonehenge.com (Randal L. Schwartz) writes:
Florian> Ugh, does anybody still use RFC 822 source routing? I
Florian> don't think so, bang paths and percent hacks might still
Florian> exist, however.
>>
>> It's not just for "source routing". It's perfectly legal for me to
>> set up <merlyn@news@stonehenge.com> to use for Usenet postings.
Florian> This is not a valid address in RFC 822 syntax, and thus not permitted
Florian> by RFC 1036. You could use "merlyn@news"@stonehenge.com instead.
Oops. :) Now I remember why I didn't do that. Blame the "3 hours
of sleep in 48 hours" for that, please. :)
That's what happens when you spend 10 days at sea in the caribbean
with a bunch of other geeks (www.geekcruises.com)... no sleep. :)
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
next prev parent reply other threads:[~2001-02-06 20:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-30 15:48 NAGY Andras
2001-01-30 16:17 ` ShengHuo ZHU
2001-01-30 16:25 ` Jost.Krieger
2001-01-30 18:24 ` Paul Jarc
2001-02-03 18:41 ` Florian Weimer
2001-02-06 13:27 ` Randal L. Schwartz
2001-02-06 19:58 ` Florian Weimer
2001-02-06 20:14 ` Randal L. Schwartz [this message]
2001-01-31 1:25 ` NAGY Andras
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=m1ofwf4lhq.fsf@halfdome.holdit.com \
--to=merlyn@stonehenge.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).