Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100951
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAESVnVovMZAZx4KyvwUjx4bRT6AODHdtZzGZ8nZaCJQUTqDNdQ@mail.gmail.com>
References: <CAESVnVovMZAZx4KyvwUjx4bRT6AODHdtZzGZ8nZaCJQUTqDNdQ@mail.gmail.com>
Date: Thu, 26 Oct 2017 10:23:34 +0300
Message-ID: <CAEbg-4Yzoa6Qjbu1vxBQ1sX-L9Xf4NFZafytC9qexN7TedmkEQ@mail.gmail.com>
To: Sara Golemon <pollita@php.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="94eb2c07414a3020ee055c6e0faa"
Subject: Re: [PHP-DEV] PHP's mail servers suck
From: lisachenko.it@gmail.com (Alexander Lisachenko)

--94eb2c07414a3020ee055c6e0faa
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi, internals!

Just quick idea: what about moving from old-school mailing list with
unclear subscription logic and ugly interface to the RFC project on GitHub?
Maybe https://github.com/php/rfc or similar.
There are cases when language developers actively use GitHub for
maintaining RFC-s, label them and review directly in github issues. For
example, https://github.com/rust-lang/rfcs

Organizing internals in this way could give a chance for community to grow,
because everyone knows how to raise an issue on GitHub and how to
contribute to the documentation/RFC.

GitHub also provides flexible way to subscribe to repo/issues/summons.
Maybe it's a good time to move internals to the public open-source system?

Best regards, Alexander

2017-10-26 1:28 GMT+03:00 Tom Samplonius <tom@samplonius.org>:

>
> > On Oct 25, 2017, at 2:17 PM, Aidan Woods <aidantwoods@gmail.com> wrote:
> >
> >> anyways, don't reject mailing-list messages
> >
> > I don't reject the messages, Google rejects the messages because of
> failed
> > DMARC requirements. See support[.]google[.]com/mail/answer/2451690
> >
> > The error occurs when the php mailing list attempts to forward messages
> > from a domain which has a (likey strict) DMARC policy, and sends emails
> as
> > if it was the sender from the domain holding that policy.
> >
> > In any case, despite failed delivery due to the policy being an issue =
=E2=80=93
> it
> > would be great if I wouldn't be unsubscribed from the mailing list
> because
> > of an error that has nothing to do with me =F0=9F=A4=B7=E2=80=8D=E2=99=
=82=EF=B8=8F
>
>   I=E2=80=99m using GSuite for email, and I=E2=80=99ve never received a w=
arning from the
> php.net mail system that mail was bouncing anytime in the past two years,
> nor have I been automatically unsubscribed.
>
>   That said, email is a lot harder than it looks.
>
>
> Tom



2017-10-25 17:30 GMT+03:00 Sara Golemon <pollita@php.net>:

> Quick show of hands: Who's had a "looks like spam" bounce from php.net
> mail servers in the past... lets say the past month.
> Or how about the fact that new users tend to have a very hard time
> even subscribing to this list?
> This isn't directed at any one person because AFAICT, the maintainer
> of those systems is "nobody".
> Is it time to pick someone to actually maintain that pile of mierde?
> Maybe replace the pieces that haven't worked since the 90s?
>
> Fed up with something this basic not working,
> -Sara
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--94eb2c07414a3020ee055c6e0faa--