From tgl@sss.pgh.pa.us Sun May 24 10:44:37 2026 Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id A4E412E019B for ; Mon, 9 Jun 2008 04:29:55 -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 92830-05 for ; Mon, 9 Jun 2008 04:29:31 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by developer.postgresql.org (Postfix) with ESMTP id F26B72E027E for ; Mon, 9 Jun 2008 03:30:56 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m596Uthr005609 for ; Mon, 9 Jun 2008 02:30:55 -0400 (EDT) To: pgsql-www@postgreSQL.org Subject: Message-ID should surely not be shown as a mailto: URL Date: Mon, 09 Jun 2008 02:30:55 -0400 Message-ID: <5608.1212993055@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/47 X-Sequence-Number: 15274 So looking at page source for, eg, http://archives.postgresql.org/pgsql-hackers/2008-06/msg00338.php I see
  • From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • To: pgsql-hackers(at)postgresql(dot)org
  • Subject: Re: We have a launch abort ... PG update releases will be delayed
  • Date: Sat, 07 Jun 2008 11:45:56 -0400
  • Message-id: <20506(dot)1212853556(at)sss(dot)pgh(dot)pa(dot)us>
    • This seems outright silly. In the first place, I do not see the value of displaying mailto: URLs containing intentionally-broken addresses. In the second, even if the domain names were fixed, there is no way on god's green earth that mailto: a Message-ID is going to work. Hm, I wonder if sloppiness of this sort accounts for the remarkable prevalence in my mail logs of spam-sign like this: Jun 9 00:44:06 sss2 sm-mta[4062]: m594i5Ns004062: <19570.1142971720@sss.pgh.pa.us>... User unknown I don't pretend to know what is the approved way to deal with these issues, but *this* can't be best practice. regards, tom lane From ajs@commandprompt.com Sun May 24 10:44:37 2026 Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id D11F12E00CF for ; Mon, 9 Jun 2008 11:15:29 -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 35253-03-4 for ; Mon, 9 Jun 2008 11:14:43 -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 8660F2E00F2 for ; Mon, 9 Jun 2008 10:55:09 -0300 (ADT) Received: from commandprompt.com (227-54-222-209.mycybernet.net [209.222.54.227]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m59DuevE024049 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 9 Jun 2008 06:56:43 -0700 Date: Mon, 9 Jun 2008 09:55:04 -0400 From: Andrew Sullivan To: pgsql-www@postgresql.org Subject: Re: Message-ID should surely not be shown as a mailto: URL Message-ID: <20080609135503.GB83012@commandprompt.com> References: <5608.1212993055@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5608.1212993055@sss.pgh.pa.us> User-Agent: Mutt/1.5.17 (2007-11-01) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Mon, 09 Jun 2008 06:56:44 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/50 X-Sequence-Number: 15277 On Mon, Jun 09, 2008 at 02:30:55AM -0400, Tom Lane wrote: > > Hm, I wonder if sloppiness of this sort accounts for the remarkable > prevalence in my mail logs of spam-sign like this: > > Jun 9 00:44:06 sss2 sm-mta[4062]: m594i5Ns004062: <19570.1142971720@sss.pgh.pa.us>... User unknown Good bet. > 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. A -- Andrew Sullivan ajs@commandprompt.com +1 503 667 4564 x104 http://www.commandprompt.com/ From alvherre@commandprompt.com Sun May 24 10:44:37 2026 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. From tgl@sss.pgh.pa.us Sun May 24 10:44:37 2026 Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id E00432E0032 for ; Mon, 9 Jun 2008 11:39:05 -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 59408-09 for ; Mon, 9 Jun 2008 11:38:47 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by developer.postgresql.org (Postfix) with ESMTP id 44F7F2E0039 for ; Mon, 9 Jun 2008 11:38:53 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m59EcolG019074; Mon, 9 Jun 2008 10:38:50 -0400 (EDT) To: Andrew Sullivan cc: pgsql-www@postgresql.org Subject: Re: Message-ID should surely not be shown as a mailto: URL In-reply-to: <20080609135503.GB83012@commandprompt.com> References: <5608.1212993055@sss.pgh.pa.us> <20080609135503.GB83012@commandprompt.com> Comments: In-reply-to Andrew Sullivan message dated "Mon, 09 Jun 2008 09:55:04 -0400" Date: Mon, 09 Jun 2008 10:38:49 -0400 Message-ID: <19073.1213022329@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/52 X-Sequence-Number: 15279 Andrew Sullivan writes: > 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. What I'm complaining about is the logical disconnect involved in sticking a mailto: onto an address that you have carefully made unusable for sending mail to. I don't have a problem with munging all of them, just leave off the mailto decoration. regards, tom lane From bruce@momjian.us Sun May 24 10:44:37 2026 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. + From bruce@momjian.us Sun May 24 10:44:37 2026 Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id CE3B364FCFA for ; Tue, 11 Nov 2008 00:12:46 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 85718-06 for ; Tue, 11 Nov 2008 00:12:44 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from momjian.us (momjian.us [70.90.9.53]) by mail.postgresql.org (Postfix) with ESMTP id CDC3364FCD8 for ; Tue, 11 Nov 2008 00:12:43 -0400 (AST) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id mAB4CjI27298; Mon, 10 Nov 2008 23:12:45 -0500 (EST) From: Bruce Momjian Message-Id: <200811110412.mAB4CjI27298@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: Mon, 10 Nov 2008 23:12:45 -0500 (EST) 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-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200811/44 X-Sequence-Number: 16091 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 Have you tried adding this to your mhonarc.rc file? In fact looking at: https://pgweb.postgresql.org/browser/trunk/archives/bin/resource-common I see the use of MAILTO even though the comment doesn't match: 25 It seems logical seeing as we are already using: -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + From alvherre@commandprompt.com Sun May 24 10:44:37 2026 Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 24D0B65016A for ; Tue, 11 Nov 2008 10:23:15 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 37226-03 for ; Tue, 11 Nov 2008 10:23:07 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by mail.postgresql.org (Postfix) with ESMTP id B7F7364FEF7 for ; Tue, 11 Nov 2008 10:23:06 -0400 (AST) Received: from perhan.alvh.no-ip.org (200-126-101-5.bk7-dsl.surnet.cl [200.126.101.5]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id mABERKrC026484 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Nov 2008 06:27:23 -0800 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 1B2BF47CC0; Tue, 11 Nov 2008 11:22:51 -0300 (CLST) Date: Tue, 11 Nov 2008 11:22:51 -0300 From: Alvaro Herrera To: Bruce Momjian Cc: Andrew Sullivan , pgsql-www@postgresql.org Subject: Re: Message-ID should surely not be shown as a mailto: URL Message-ID: <20081111142251.GF4272@alvh.no-ip.org> References: <20080609143417.GA5026@alvh.no-ip.org> <200811110412.mAB4CjI27298@momjian.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200811110412.mAB4CjI27298@momjian.us> 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]); Tue, 11 Nov 2008 06:27:23 -0800 (PST) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200811/46 X-Sequence-Number: 16093 Bruce Momjian wrote: > Have you tried adding this to your mhonarc.rc file? > > Hmm, no, I just added it and the archive is being reprocessed. The mailto: links have now been removed; for example see http://archives.postgresql.org/pgsql-committers/2008-11/msg00111.php (Mhonarc is still running) > I see the use of MAILTO even though the comment doesn't match: > > > 25 Ugh. I assume Marc took the original config file and switched the setting without even looking at the comment. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. From alvherre@commandprompt.com Sun May 24 10:44:37 2026 Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 14DF9650578; Tue, 11 Nov 2008 21:11:14 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 09912-01-3; Tue, 11 Nov 2008 21:11:09 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by mail.postgresql.org (Postfix) with ESMTP id CDA76650555; Tue, 11 Nov 2008 21:10:46 -0400 (AST) Received: from perhan.alvh.no-ip.org (200-126-101-5.bk7-dsl.surnet.cl [200.126.101.5]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id mAC1EvNd019429 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Nov 2008 17:15:00 -0800 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id E803447CC0; Tue, 11 Nov 2008 22:10:26 -0300 (CLST) Date: Tue, 11 Nov 2008 22:10:26 -0300 From: Alvaro Herrera To: Bruce Momjian Cc: Andrew Sullivan , pgsql-www@postgresql.org, Pg Hackers Subject: Re: Message-ID should surely not be shown as a mailto: URL Message-ID: <20081112011026.GT4272@alvh.no-ip.org> References: <20080609143417.GA5026@alvh.no-ip.org> <200811110412.mAB4CjI27298@momjian.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200811110412.mAB4CjI27298@momjian.us> 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]); Tue, 11 Nov 2008 17:15:01 -0800 (PST) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200811/52 X-Sequence-Number: 16099 Okay, so Bruce got in Perl hacking mode today and wrote a script to munge the message-ids. If you look at our archives you'll notice that on each message the Message-Id header is now a proper link to the message itself using the message-id-style URL, and it is no longer munged by the "no spam" Mhonarc mode. (Well, actually it is, and it's de-munged by Bruce's script later on. We'll be fixing that too hopefully!) Thanks Bruce! -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support