On Wed, Feb 21, 2024 at 7:59 PM Larry Garfield wrote:
>
> Hello again, fine Internalians.
>
> After much on-again/off-again work, Ilija and I are back with a more polished
> property access hooks/interface properties RFC. It’s 99% unchanged from last
> summer; the PR is now essentially complete
On Wed, 21 Feb 2024 at 18:56, Larry Garfield wrote:
> Hello again, fine Internalians.
>
> After much on-again/off-again work, Ilija and I are back with a more
> polished property access hooks/interface properties RFC. It’s 99%
> unchanged from last summer; the PR is now essentially complete and
On Thu, Feb 22, 2024 at 8:25 AM tag Knife wrote:
> A few things i was interested to get the idea around.
> Was it thought about for the set{} for it to return the value to set the
> property to
> instead implicitly setting its own field?
>
> eg
>
> ```
> public string $name {
> set {
>
I have noticed quite a number of emails appearing on externals but not
appearing in my inbox. I randomly get an email saying:
Hi, this is the Mlmmj program managing the
mailing list.
Some messages to you could not be delivered. If you're seeing this
message it means things are back to normal, an
> If I'm using gmail and not getting emails, how many other people are
> also not getting emails on this list?
Same here.
On 22 February 2024 08:52:49 GMT-05:00, Robert Landers
wrote:
>I have noticed quite a number of emails appearing on externals but not
>appearing in my inbox. I randomly get an email saying:
>
>Hi, this is the Mlmmj program managing the
>mailing list.
>
>Some messages to you could not be delivere
I had an email to the list bounce due to SpamCop adding a sizeable portion of
Outlook's IP space into a block (as they've been erroneously doing for 25 years
now). Emailed syst...@php.net about it, never heard back. I'm also receiving
next-to-no list traffic and receiving similar bounce message
> Gmail is rejecting emails after we moved the servers without telling us why,
> in
> enough detail to do anything about it.
It's not just gmail.
-Jeff
> If I'm using gmail and not getting emails, how many other people are
> also not getting emails on this list?
>
Same here, with both gmail and zoho mail.
Personally I would switch to github issues and discussions, even ignoring all
the deliverability issues which I had even before the switch to
Am 22.02.2024 um 15:14 schrieb Jeffrey Dafoe:
Gmail is rejecting emails after we moved the servers without telling us why, in
enough detail to do anything about it.
It's not just gmail.
I guess it's because of a wrong setting in the mailinglist server.
The content of the original email is cha
On Thu, 22 Feb 2024 at 14:12, Derick Rethans wrote:
> On 22 February 2024 08:52:49 GMT-05:00, Robert Landers <
> landers.rob...@gmail.com> wrote:
> >I have noticed quite a number of emails appearing on externals but not
> >appearing in my inbox. I randomly get an email saying:
> >
> >Hi, this is
On Thu, Feb 22, 2024 at 09:05:22AM -0500, Derick Rethans wrote:
> Gmail is rejecting emails after we moved the servers without telling us why,
> in enough detail to do anything about it.
I run other mail lists and have had similar problems with gmail recently.
The problem seems to be SPF. This
On Thu, 2024-02-22 at 10:29 -05:00, Alain D D Williams
wrote:
> On Thu, Feb 22, 2024 at 09:05:22AM -0500, Derick Rethans wrote:
>
>> Gmail is rejecting emails after we moved the servers without telling us why,
>> in enough detail to do anything about it.
>
> I run other mail lists and have had s
On Thu, 22 Feb 2024, Alain D D Williams wrote:
On Thu, Feb 22, 2024 at 09:05:22AM -0500, Derick Rethans wrote:
Gmail is rejecting emails after we moved the servers without telling us why, in
enough detail to do anything about it.
I run other mail lists and have had similar problems with gma
On Thu, 22 Feb 2024, mjec wrote:
On Thu, 2024-02-22 at 10:29 -05:00, Alain D D Williams
wrote:
On Thu, Feb 22, 2024 at 09:05:22AM -0500, Derick Rethans wrote:
Gmail is rejecting emails after we moved the servers without telling
us why, in enough detail to do anything about it.
I run other
On Thu, Feb 22, 2024 at 04:46:04PM +, Derick Rethans wrote:
> > Make the From: address internals@lists.php.net
>
> We don't want to change the From address, as that means that replies go to
> the list, rather than the original sender. We never had to do any of that
> before.
I understand tha
On 22 February 2024 17:49:10 CET, Derick Rethans wrote:
> On Thu, 22 Feb 2024, mjec wrote:
>
> > On Thu, 2024-02-22 at 10:29 -05:00, Alain D D Williams
> > wrote:
> >> On Thu, Feb 22, 2024 at 09:05:22AM -0500, Derick Rethans wrote:
> >>
> >>> Gmail is rejecting emails after we moved the server
Hi
On 2/22/24 16:29, Alain D D Williams wrote:
• SPF for lists.php.net is "v=spf1 a mx a:osu1php.osuosl.org. ip4:45.112.84.5
ip6:2a02:cb43:8000::1102"
Change to "v=spf1 a mx -all"
•• If you make the MX change that I suggest then the
following are redundant: ip4:45.112.84.5 ip6:2a02:cb43:8000::
Hi
On 2/22/24 15:44, Michael Kliewe wrote:
1. Don't change the content or the DKIM-signed headers of the email (do
not prepend something in the subject). Then the original DKIM signature
stays valid and the From:-header can stay untouched
Strong +1 for that one. I've suggested the same in the
On Thu, Feb 22, 2024 at 07:45:41PM +0100, Tim Düsterhus wrote:
> Hi
>
> On 2/22/24 16:29, Alain D D Williams wrote:
> > • SPF for lists.php.net is "v=spf1 a mx a:osu1php.osuosl.org.
> > ip4:45.112.84.5 ip6:2a02:cb43:8000::1102"
> > Change to "v=spf1 a mx -all"
> >
> > •• If you make the MX chang
Hi
(Robert, Ondrej, please apologize the duplicate mail, the list rejected
my first attempt, because the previously used alias tim@ is no longer
accepted as a valid sender, I'll need to update my subscription)
On 2/20/24 14:21, Robert Landers wrote:
I'd love to see all array_* functions acce
Hi
On 2/22/24 00:02, Matthew Weier O'Phinney wrote:
Once again in reading the proposal, the first thing I'm struck by are the
magic "$field" and "$value" variables inside accessors. The first time they
are used, they're used without explanation, and they're jarring.
[…]
Second: you don't have
Hi
1. I believe there is an error in the "Final Hooks" section:
> // But this is NOT allowed, because beforeSet is final in the parent.
I believe it should be s/beforeSet/set/.
2. In the same section this sentence is probably grammatically incorrect.
> Declaring hooks final on a property that
Hello internals,
I updated the RFC to encompass all the feedback:
https://wiki.php.net/rfc/deprecate-implicitly-nullable-types
Let me know if there are any final remarks before we start the vote sometime
next week.
Best regards,
Gina P. Banyard
On Wed, Feb 21, 2024, at 11:02 PM, Matthew Weier O'Phinney wrote:
> On Wed, Feb 21, 2024 at 12:57 PM Larry Garfield
> wrote:
>> After much on-again/off-again work, Ilija and I are back with a more
>> polished property access hooks/interface properties RFC. It’s 99% unchanged
>> from last summe
25 matches
Mail list logo
