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:
The actual mhonarc call is in this script:
The mhonarc documentation:
Oh, FWIW, the Message-ID URLs (which are just hard links actually) are
created by this script:
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.
In response to
pgsql-www by date
|Next:||From: Tom Lane||Date: 2008-06-09 14:38:49|
|Subject: Re: Message-ID should surely not be shown as a mailto: URL |
|Previous:||From: Andrew Sullivan||Date: 2008-06-09 13:55:04|
|Subject: Re: Message-ID should surely not be shown as a mailto:URL|
pgsql-hackers by date
|Next:||From: Simon Riggs||Date: 2008-06-09 14:36:07|
|Subject: Re: Strange issue with GiST index scan taking far toolong|
|Previous:||From: A. Kretschmer||Date: 2008-06-09 14:24:08|
|Subject: Re: Strange issue with GiST index scan taking far too long|