From: Florian Weimer <fw@deneb.enyo.de>
Subject: Re: using `equal' on email addresses
Date: 03 Feb 2001 19:41:20 +0100 [thread overview]
Message-ID: <8766irtxrj.fsf@deneb.enyo.de> (raw)
In-Reply-To: <m3hf2gdhjt.fsf@multivac.student.cwru.edu>
prj@po.cwru.edu (Paul Jarc) writes:
> Also, to be maximally careful, the domain is everything after the
> *last* "@".
Ugh, does anybody still use RFC 822 source routing? I don't think so,
bang paths and percent hacks might still exist, however.
next prev parent reply other threads:[~2001-02-03 18:41 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 [this message]
2001-02-06 13:27 ` Randal L. Schwartz
2001-02-06 19:58 ` Florian Weimer
2001-02-06 20:14 ` Randal L. Schwartz
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=8766irtxrj.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
/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).