Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 3D42664FCE5 for ; Wed, 16 Jul 2008 17:35:51 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 54603-08 for ; Wed, 16 Jul 2008 17:35:44 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from momjian.us (momjian.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id 4212364FCE4 for ; Wed, 16 Jul 2008 17:35:47 -0300 (ADT) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id m6GKZjJ26702; Wed, 16 Jul 2008 16:35:45 -0400 (EDT) From: Bruce Momjian Message-Id: <200807162035.m6GKZjJ26702@momjian.us> Subject: Re: Message-ID should surely not be shown as a mailto: URL In-Reply-To: <20080609143417.GA5026@alvh.no-ip.org> To: Alvaro Herrera Date: Wed, 16 Jul 2008 16:35:45 -0400 (EDT) CC: Andrew Sullivan , pgsql-www@postgresql.org X-Mailer: ELM [version 2.4ME+ PL124 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200807/98 X-Sequence-Number: 15528 Alvaro Herrera wrote: > 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 I looked at this for a while and am uncertain how to affect the header display. When I was dealing with this, I considered the message-id to be an identifier, rather than something I wanted displayed in the email header block, so I put it above the header: http://momjian.us/mhonarc/patches_hold/msg00021.html Using these mhonarc.rc lines: Message-ID: $MSGID$ You could even modify this to add a link to show the message by message-id URL. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. +