From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: 9front@9front.org
Subject: Re: [9front] rewrite rules -- explanations?
Date: Sun, 04 Oct 2020 16:55:00 -0700 [thread overview]
Message-ID: <3f41f20d22b7fb10@orthanc.ca> (raw)
In-Reply-To: <763FCEEB41D2EEBA2CDB9E95648C5D01@eigenstate.org>
> The following two don't make much sense to me: What generates
> chains of '@'s, and why do we convert to them before converting
> to '!'? Is this something old email servers used to generate?
> Is it still relevant?
>
> # convert source domain address to a chain a@b@c@d...
> @([^@!,]*):([^!@]*)@([^!]*) alias \2@\3@\1
> @([^@!]*),@([^!@,]*):([^!@]*)@([^!]*) alias @\1:\3@\4@\2
>
> # convert a chain a@b@c@d... to ...d!c!b!a
> ([^@]+)@([^@]+)@(.+) alias \2!\1@\3
> ([^@]+)@([^@]+) alias \2!\1
"Source routed" RFC822 addresses have been dead for decades. Time to
blow that cruft out of the water.
prev parent reply other threads:[~2020-10-04 23:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 23:35 ori
2020-10-04 23:55 ` Lyndon Nerenberg [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=3f41f20d22b7fb10@orthanc.ca \
--to=lyndon@orthanc.ca \
--cc=9front@9front.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).