On Wed, Nov 8, 2017 at 9:56 AM, Rasmus Lerdorf wrote:
> It isn't super-helpful to publicly shame our active volunteers.
>
There are many not-super-helpful things here, for example:
Ignoring an inability to subscribe to the mailing list for YEARS isn't
super helpful.
Preventing project discussion
It isn't super-helpful to publicly shame our active volunteers.
On Wed, Nov 8, 2017 at 3:33 PM, Sara Golemon wrote:
> On Wed, Nov 8, 2017 at 9:11 AM, Rasmus Lerdorf wrote:
> > So please report that directly to systems@ (that's what it is there
> for) and
> > cc sascha@ specifically since he mai
On Wed, Nov 8, 2017 at 9:11 AM, Rasmus Lerdorf wrote:
> So please report that directly to systems@ (that's what it is there for) and
> cc sascha@ specifically since he maintains php-smtp2. And php-smtp2 has been
> around less than a year, so if you haven't reported it since the changeover
> they p
So please report that directly to systems@ (that's what it is there for)
and cc sascha@ specifically since he maintains php-smtp2. And php-smtp2 has
been around less than a year, so if you haven't reported it since the
changeover they probably never saw a report.
-Rasmus
On Wed, Nov 8, 2017 at 3:
On Wed, Nov 8, 2017 at 8:03 AM, Rasmus Lerdorf wrote:
> Our smtp servers are actually quite well maintained by Sascha and company.
>
This is a response from the mail server, with no mailing list software involved.
This is a regular response covering years.
This is response which has been reported
On Wed, Nov 8, 2017 at 8:03 AM, Rasmus Lerdorf wrote:
> I am sure Sascha and his team would love to see concrete examples
> (as in with full headers) of any messages rejected at the smtp level.
>
Next time I get one Rasmus I'll be happy to forward it on. This is
definitely new news that someon
> Without any generally available information about the existing email
> infrastructure, it's hard to make targeted comments about how to fix
> what is obviously broken with this system which literally nobody with
> the ability to fix cares about. That means a either a conversation
> (which should
Am 08.11.2017 um 13:40 schrieb li...@rhsoft.net:
>
>
> Am 08.11.2017 um 13:36 schrieb Michael Kliewe:
>> Am 08.11.2017 um 13:27 schrieb li...@rhsoft.net:
>>>
>>> Am 08.11.2017 um 12:59 schrieb Michael Kliewe:
The PHP mailing list software is not configured DMARC compliant. DMARC
means, ei
Am 08.11.2017 um 13:36 schrieb Michael Kliewe:
Am 08.11.2017 um 13:27 schrieb li...@rhsoft.net:
Am 08.11.2017 um 12:59 schrieb Michael Kliewe:
The PHP mailing list software is not configured DMARC compliant. DMARC
means, either SPF or DKIM has to be valid. The PHP mailing list changes
the Su
On Wed, Nov 8, 2017 at 6:59 AM, Michael Kliewe wrote:
> Am 08.11.2017 um 12:09 schrieb Sara Golemon:
>> On Wed, Nov 8, 2017 at 2:51 AM, Rasmus Lerdorf wrote:
>>> So please send your volunteer requests there, but not just a generic offer
>>> to help. Please include a concrete description of what y
Am 08.11.2017 um 13:27 schrieb li...@rhsoft.net:
>
>
> Am 08.11.2017 um 12:59 schrieb Michael Kliewe:
>> The PHP mailing list software is not configured DMARC compliant. DMARC
>> means, either SPF or DKIM has to be valid. The PHP mailing list changes
>> the Subject (it adds [PHP-]), that's why
Am 08.11.2017 um 12:59 schrieb Michael Kliewe:
The PHP mailing list software is not configured DMARC compliant. DMARC
means, either SPF or DKIM has to be valid. The PHP mailing list changes
the Subject (it adds [PHP-]), that's why the DKIM signature breaks.
SPF breaks, because Gmail and oth
Am 08.11.2017 um 12:09 schrieb Sara Golemon:
> On Wed, Nov 8, 2017 at 2:51 AM, Rasmus Lerdorf wrote:
>> So please send your volunteer requests there, but not just a generic offer
>> to help. Please include a concrete description of what you plan on doing.
>> As in which software or configuration c
On Wed, Nov 8, 2017 at 2:51 AM, Rasmus Lerdorf wrote:
> On Tue, Nov 7, 2017 at 5:44 PM, Pedro Magalhães wrote:
>
>> I'm not sure if the people who have access to the machines follow this
>> mailing list as well, so I would suggest reaching out directly to the
>> people listed as having access to
On Tue, Nov 7, 2017 at 5:44 PM, Pedro Magalhães wrote:
> I'm not sure if the people who have access to the machines follow this
> mailing list as well, so I would suggest reaching out directly to the
> people listed as having access to the mailing lists machine (you can find
> that list here: htt
On 7 Nov 2017 16:40, "Eli White" wrote:
On Tue, Nov 7, 2017 at 9:07 AM, Peter Lind wrote:
> Might be worth noting that fixing the mailing lists does not amount to
> taking on the php.net mail servers. The two are separate - just in case
> someone should be up for one, but not both tasks.
>
In
I'm not sure if the people who have access to the machines follow this
mailing list as well, so I would suggest reaching out directly to the
people listed as having access to the mailing lists machine (you can find
that list here: https://wiki.php.net/systems/pb1).
Also, there seems to be a system
On Tue, 2017-11-07 at 16:54 +0100, Andreas Heigl wrote:
> Am 07.11.17 um 16:40 schrieb Eli White:
> > On Tue, Nov 7, 2017 at 9:07 AM, Peter Lind
> > wrote:
> >
> > > Might be worth noting that fixing the mailing lists does not
> > > amount to
> > > taking on the php.net mail servers. The two are
Am 07.11.17 um 16:40 schrieb Eli White:
> On Tue, Nov 7, 2017 at 9:07 AM, Peter Lind wrote:
>
>> Might be worth noting that fixing the mailing lists does not amount to
>> taking on the php.net mail servers. The two are separate - just in case
>> someone should be up for one, but not both tasks.
>
On Tue, Nov 7, 2017 at 9:07 AM, Peter Lind wrote:
> Might be worth noting that fixing the mailing lists does not amount to
> taking on the php.net mail servers. The two are separate - just in case
> someone should be up for one, but not both tasks.
>
In this case I believe that they are one and
Might be worth noting that fixing the mailing lists does not amount to
taking on the php.net mail servers. The two are separate - just in case
someone should be up for one, but not both tasks.
On 7 November 2017 at 14:48, Eli White wrote:
> Just chiming in that I have constantly had issues (sinc
Hey all.
Am 07.11.17 um 14:48 schrieb Eli White:
> Just chiming in that I have constantly had issues (since you asked for
> hands), get emails denied (let's see if this one goes through), and
> semi-constant threads of being auto-removed because of bounces that have
> nothing to do with me (see ab
Just chiming in that I have constantly had issues (since you asked for
hands), get emails denied (let's see if this one goes through), and
semi-constant threads of being auto-removed because of bounces that have
nothing to do with me (see above gmail discussion).
Yeah, it sucks. And it's been bro
Biweekly reminder that PHP mail servers suck.
On Wed, Oct 25, 2017 at 10:30 AM, Sara Golemon wrote:
> 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
24 matches
Mail list logo
