Re: new ietf mail archive? permanent urls?

<> Mon, 21 March 2016 11:48 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 813AD12D756 for <>; Mon, 21 Mar 2016 04:48:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id vxi7Yt10S3Xp for <>; Mon, 21 Mar 2016 04:48:12 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6673F12D746 for <>; Mon, 21 Mar 2016 04:48:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=s2048; t=1458560887; bh=+DTkerUKPNr8WKz6BTV3GUtR4P/pQD8jD/qzMZhbIAg=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=dn8J72tj9kk4O2uG3U6mt1iB+LYVWNKlx0M27wefYW9c+e1sxj1A5vRR3hfx3l/ktY0uVAtOVaZE5MwzQ99ryixAfNz1A7NRqQ6CvN+HkFwpoV34hOE4TGT1vRC51FwGlsGkb6wrfNV+jB4qoxCcKLhMzE6Dv3q+csbdOqMD3UxypGaxpCOTNfGKkn41hhEWRaSVZgm5qwYXxMTMlvGOjb+dkm+pY2eSVRGZ0GZyHc+RsEI+8ljxH/QdDSxzy03un31btfTh5BoiNd1NbhoLTppXPCO0jZoBoKER0C6axnjlIoT2tBYcP3UDQD17eR+8oM7raMaNgNE7v5799NuLnw==
Received: from [] by with NNFMP; 21 Mar 2016 11:48:07 -0000
Received: from [] by with NNFMP; 21 Mar 2016 11:48:07 -0000
Received: from [] by with NNFMP; 21 Mar 2016 11:48:07 -0000
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: 2HPuflwVM1ml__iPL96njYXOF_lfmgwaU3XJvLOgHleqJjpNx2tefQrFSlmAydG tzktmCrUnolunoqGq3Ldhn1HeqB.17Pyb3V4f7Q1DV_W_bxyWPPWmq_oelR8ZxK_Nucbi9WlENHz tRjvs7H7s.fYiwgwk6PCuH22_bhfMQAbu23A2ZtUrzAwKrTOhdCd18.oKbez7Dq0Q8grUUHQVL.q mPeHNOpAhkIt32TRoYDVMnlsJWKtiyUEhRyk23E8LyGdQlKU1ftn515sYIqhVZvN9_NRvr5ChzbQ H1NTL.pe8wFLTLkuE87IDZTstUU4JMcUhiDd_QKUOmNe68Pa5cN5P_ztdi6k5ivUtvnVpT_6dlW_ OA9kAO0Njxx32JEVlEdhwIZwaUJjDfffbzf__Xx.FXQ6f05gXojbzyWtkSm92LEbKOohunpH9BG3 cyzwDSqqpgaydFph.bV_uGtz7uJLRrkqPNdwRzQJCH7ymsMXVltX14eB.m9KusENzrx_dkG.2UTC mviB.MxZErPxcJdQPyYNM5Gigmx3P6vlwOG8xKocb
Received: by; Mon, 21 Mar 2016 11:48:07 +0000
Date: Mon, 21 Mar 2016 11:48:06 +0000
To: Henrik Levkowetz <>, IETF Discussion <>
Message-ID: <>
In-Reply-To: <>
References: <>
Subject: Re: new ietf mail archive? permanent urls?
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: <>
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 21 Mar 2016 11:48:13 -0000

Hi Henrik,

I'd be good with list/YYYY/MM/DD/identifier-hash (per Wordpress
and in line with ISO8601 - none of that US MM/DD/YY funny stuff)
added into the urls, allowing mails to be retrieved either with
or without the date. (I presume the list id is optional as well
but't work as I might expect.


can return all emails to that list on that date, so much the better:
gives the entire month, etc.

should return the same thing.

Lloyd Wood 

----- Original Message -----
From: Henrik Levkowetz <>
To:; IETF Discussion <>
Sent: Monday, 21 March 2016, 21:03
Subject: Re: new ietf mail archive? permanent urls?

Hi Lloyd,

On 2016-03-20 12:42, wrote:
> okay, I've finally belatedly noticed the new ietf mail archive.
> (because I have a life these days.)
> Is e.g.
> a permanent url? If not, should it be?

Yes, it is.  If you go and look at the message headers, you'll notice
that there's even an Archived-At: header field which has that permanent
url as its value.

> (It's occasionally
> useful to refer to emails directly, and cite text with urls, but
> that doesn't look like a good choice. I mean, no date in url?
> as a hint?)

Good point. I think it would be rather easy to add a date hint to the
permanent URL, even if I think we'd still be using just the list and
hash to identify and pull out the message at the server end.  The list
is already in the URL (in the case of the URL above, the list identifier
is the '/ietf/' part).