Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id EFC3A2E0042 for ; Wed, 18 Jun 2008 11:01:56 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 93218-07 for ; Wed, 18 Jun 2008 11:01:40 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by developer.postgresql.org (Postfix) with ESMTP id 55ED12E0037 for ; Wed, 18 Jun 2008 11:01:45 -0300 (ADT) Received: from perhan.alvh.no-ip.org (190-95-24-79.bk17-dsl.surnet.cl [190.95.24.79]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m5IE3QDL026398 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 18 Jun 2008 07:03:29 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id AC58347C7C; Wed, 18 Jun 2008 10:01:36 -0400 (CLT) Date: Wed, 18 Jun 2008 10:01:36 -0400 From: Alvaro Herrera To: Andrew Sullivan Cc: pgsql-www@postgresql.org Subject: Re: Archived-At message header Message-ID: <20080618140136.GB5077@alvh.no-ip.org> References: <20080618135104.GC433@commandprompt.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080618135104.GC433@commandprompt.com> User-Agent: Mutt/1.5.18 (2008-05-17) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Wed, 18 Jun 2008 07:03:30 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/156 X-Sequence-Number: 15383 Andrew Sullivan wrote: > Hi, > > What are the chances that, if we're going to fix the problem of > archive boundaries at month end, we can do it with > http://www.ietf.org/rfc/rfc5064.txt? I just learned about this > header, and it sure seems like it'd be useful. It would be neat, but I'm not sure it can be done, because the WWW archives are handled very far away from where the message is distributed. Hmm, but 3.2 talks about using Message-Id for generating URLs that will work permanently. Interesting. There's even software for managing it. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.