Re: Overeager spam fighting for link?

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
Cc: pgsql-www(at)postgresql(dot)org
Subject: Re: Overeager spam fighting for link?
Date: 2025-02-19 19:20:23
Message-ID: CABUevEwqRdWBaio-LFH654P+rPQ1jtxXwatR9wjuc0mNmR50Zw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

On Tue, Feb 18, 2025 at 3:28 PM Greg Sabino Mullane <htamfids(at)gmail(dot)com>
wrote:

> I came across this page today:
>
> Subject: Re: redacting password in SQL statement in server log
>
>
> https://www.postgresql.org/message-id/20220724114449.qqjbwgmpcgn66yhy%40jrouhaud
>
> The spam filtering[1] that occurs for the header information appears to
> have been applied to the bottom link as well - making it 404. Not sure
> where that is getting applied, but doing a "raw source" and checking my
> original inbox seems to indicate the link at the bottom of the email was
> sent unobscured.
>
> [1] In which alice(at)gmail(dot)com becomes alice(at)gmail(dot)com
>
>
The regexp used is this:
_re_mail =
re.compile(r'(/m(essage-id)?/)?[^()<>@,;:\/\s"\'&|]+(at)[^()<>@,;:\/\s"\'&|]+')

Per:
https://github.com/postgres/pgarchives/blob/master/django/archives/mailarchives/templatetags/pgfilters.py#L31

The comment indicates it's trying to special case these links already, but
clearly it's failing. I think maybe because it's not considering the /flat/
part of the URL. I haven't got time to test it out properly right this
moment, but I think that might be it.

--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>

In response to

Browse pgsql-www by date

  From Date Subject
Next Message Federico Campoli 2025-02-20 16:47:26 problem when requesting a new git repository
Previous Message Maciek Sakrejda 2025-02-19 18:05:21 Broken layout: CommitFest Add Review Form (still)