Re: Overeager spam fighting for link?
| От | Magnus Hagander |
|---|---|
| Тема | Re: Overeager spam fighting for link? |
| Дата | |
| Msg-id | CABUevEwqRdWBaio-LFH654P+rPQ1jtxXwatR9wjuc0mNmR50Zw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Overeager spam fighting for link? (Greg Sabino Mullane <htamfids@gmail.com>) |
| Список | pgsql-www |
On Tue, Feb 18, 2025 at 3:28 PM Greg Sabino Mullane <htamfids@gmail.com> wrote:
I came across this page today:Subject: Re: redacting password in SQL statement in server logThe 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@gmail.com becomes alice(at)gmail(dot)com
The regexp used is this:
_re_mail = re.compile(r'(/m(essage-id)?/)?[^()<>@,;:\/\s"\'&|]+@[^()<>@,;:\/\s"\'&|]+')
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.
В списке pgsql-www по дате отправления: