From: Anthony Sorace <a@9srv.net>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] moving 9fans to new server, but still 9fans@9fans.net
Date: Thu, 24 Oct 2019 11:24:58 -0400 [thread overview]
Message-ID: <877B8319-F21F-4975-AAC6-8D49B9FC34B9@9srv.net> (raw)
In-Reply-To: <2b0db54f-65f8-4bca-bc98-94408eb2f299@www.fastmail.com>
Archived-At is from RFC 5064.
https://tools.ietf.org/html/rfc5064
The weird "=?UTF-8?B?" is an "Encoded Word", per RFC 2047. Email headers are defined to be 7-bit ASCII (yes, still); 2047 provides a way to encode other characters in email headers. Mind you, it looks like all the actual Archived-At links Topicbox would fit in 7-bit ASCII anyway and it'd be nice if they reserved the Encoded Word for when they needed it, but whatever; email is a mess and this is nice to have.
https://tools.ietf.org/html/rfc2047
Anthony
> On Oct 23, 2019, at 10:45 , Calvin Morrison <calvin@fastmailteam.com> wrote:
>
> On Wed, Oct 23, 2019, at 8:03 AM, hiro wrote:
>> this is the case on any other mailing lists or only a topicbox-internal
>> standard...
>
> Quite right. RFC2369 describes most of the standard headers you'll be used to. However, I'm not aware of a permalink to web archives for each individual post.
>
> https://tools.ietf.org/html/rfc2369
>
> Cheers,
> Calvin
>
> ------------------------------------------
> 9fans: 9fans
> Permalink: https://9fans.topicbox.com/groups/9fans/T73a7388a716e3644-Me389cd73535c82b4365703bb
> Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2019-10-24 15:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 16:57 Russ Cox
2019-10-11 17:04 ` Russ Cox
2019-10-11 17:34 ` Russ Cox
2019-10-11 17:38 ` [9fans] " Don Bailey
2019-10-11 17:40 ` Calvin Morrison
2019-10-11 17:47 ` Rodrigo G. López
2019-10-11 19:14 ` hiro
2019-10-12 4:30 ` Lucio De Re
2019-10-14 9:12 ` Anthony Martin
2019-10-14 15:56 ` Aram Hăvărneanu
2019-10-14 18:52 ` Darren Wise
2019-10-19 18:07 ` Ethan Gardener
2019-10-23 7:38 ` Anthony Martin
2019-10-23 8:03 ` hiro
2019-10-23 14:45 ` Calvin Morrison
2019-10-24 15:24 ` Anthony Sorace [this message]
2019-10-23 10:24 ` Ethan Gardener
2019-10-14 9:07 ` Anthony Martin
2019-10-14 11:21 ` Anthony Martin
2019-10-14 14:12 ` [9fans] " James A. Robinson
2019-10-14 20:36 ` Skip Tavakkolian
2019-10-14 20:58 ` [9fans] " Federico Benavento
2019-10-24 9:44 ` Fazlul Shahriar
2019-10-24 10:48 vp
2019-10-24 16:22 vp
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=877B8319-F21F-4975-AAC6-8D49B9FC34B9@9srv.net \
--to=a@9srv.net \
--cc=9fans@9fans.net \
/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).