Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 426542E0035 for ; Mon, 9 Jun 2008 11:34:41 -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 56946-01 for ; Mon, 9 Jun 2008 11:34:18 -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 697A32E0032 for ; Mon, 9 Jun 2008 11:34:24 -0300 (ADT) Received: from perhan.alvh.no-ip.org (190-95-19-91.bk17-dsl.surnet.cl [190.95.19.91]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m59EZs80025789 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 9 Jun 2008 07:35:57 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id B13A847C7C; Mon, 9 Jun 2008 10:34:17 -0400 (CLT) Date: Mon, 9 Jun 2008 10:34:17 -0400 From: Alvaro Herrera To: Andrew Sullivan Cc: pgsql-www@postgresql.org Subject: Re: Message-ID should surely not be shown as a mailto: URL Message-ID: <20080609143417.GA5026@alvh.no-ip.org> References: <5608.1212993055@sss.pgh.pa.us> <20080609135503.GB83012@commandprompt.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080609135503.GB83012@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]); Mon, 09 Jun 2008 07:35:58 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/51 X-Sequence-Number: 15278 Andrew Sullivan wrote: > On Mon, Jun 09, 2008 at 02:30:55AM -0400, Tom Lane wrote: > > I don't pretend to know what is the approved way to deal with these > > issues, but *this* can't be best practice. > > Obviously, someone is looking for something that _looks_ like a mail > address, attempting to munge it, and on the way through, changing it > to a mailto: link. I think some parsing of the RFC2821/2822 headers > is needed first, so that one doesn't do this for things like the > message id. Mhonarc does this mangling. I tried to stop it but couldn't find the way. I didn't investigate it too closely though, so most likely there is a way to make it work. If anyone wants to spend some time on it, feel free to send patches. Our resource files are here: https://pgweb.postgresql.org/browser/trunk/archives/bin/resource-current https://pgweb.postgresql.org/browser/trunk/archives/bin/resource-common https://pgweb.postgresql.org/browser/trunk/archives/bin/resource-utf8 The actual mhonarc call is in this script: https://pgweb.postgresql.org/browser/trunk/archives/bin/mk-mhonarc The mhonarc documentation: http://www.mhonarc.org/MHonArc/doc/mhonarc.html Oh, FWIW, the Message-ID URLs (which are just hard links actually) are created by this script: https://pgweb.postgresql.org/browser/trunk/archives/bin/createmsgid.pl It has a couple of holes (i.e. there are certain types of Message-Ids for which it doesn't work), so patches are welcome too. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.