Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122494
Feedback-ID: id5114917:Fastmail
User-Agent: Cyrus-JMAP/3.11.0-alpha0-153-g7e3bb84806-fm-20240215.007-g7e3bb848
Precedence: bulk
MIME-Version: 1.0
Message-ID: <17d50791-190d-4f74-9478-030a84ae9545@app.fastmail.com>
In-Reply-To: <112488a9-aaa6-4d85-9056-a4581a3cda21@app.fastmail.com>
References: <112488a9-aaa6-4d85-9056-a4581a3cda21@app.fastmail.com>
Date: Mon, 26 Feb 2024 11:03:05 +0000
To: internals@lists.php.net
Cc: "Rob Landers" <rob@bottled.codes>
Subject: Re: [PHP-DEV] is this thing on?
Content-Type: text/plain
From: imsop.php@rwec.co.uk ("Rowan Tommins [IMSoP]")

On Sun, 25 Feb 2024, at 20:02, Rob Landers wrote:
> Before I get to the meat of this email, first of all, IMHO, anyone should be able to email the list, even if they are not a 
> member of the list. I've had to email ubuntu lists about bugs before and I really have no desire to join those lists, but
> I was always able to just send the email to the list just fine.

The biggest problem with an open list is how to manage spam - if you don't catch the spam on the list server, it not only ends up in hundreds of inboxes, but in multiple archives and mirrors of the list. I don't know how the lists you mentioned handle that.

This has also come up in the past regarding moving from e-mail to $currently_fashionable_technology - having some barrier to entry is actually quite useful, since we want people to put some effort into their contributions beyond "me too" or "I had this crazy idea in the pub".

Note that this is exactly why bugs.php.net was abandoned: there was too much spam and low-quality content.


> Now for the issue:
> 
> gmail is failing to send emails to the list (hence why it has probably been a bit quite around here). Here is the error:
> 
> The response from the remote server was:
> 451 4.3.0 : Temporary lookup failure

People are aware of this issue, and looking into it. In case you missed the previous thread, two things have unfortunately happened at once:

- The mailing list was moved to a new server
- GMail rolled out a much tighter set of anti-spam rules

It's not immediately clear which of these is responsible for the 451 errors, but as I say, people are working on it.


> Now, to go figure out how to unsubscribe this email from the list...

Exactly the same way you subscribed, I believe: via the web form, or using +unsubscribe in the to address.

Regards,
-- 
Rowan Tommins
[IMSoP]