Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101098
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.15.19 as permitted sender)
To: internals@lists.php.net
References: <CAESVnVovMZAZx4KyvwUjx4bRT6AODHdtZzGZ8nZaCJQUTqDNdQ@mail.gmail.com>
 <CAESVnVrYD7ACfpCBwt-bpJ0146hs8w_EpM43MaL8MSxTBEV7VA@mail.gmail.com>
 <CANt4hZhBimaY8yvv+z6VvSB6f8PQtiN1=dusQjhGPH-gLJ9uWg@mail.gmail.com>
 <CAEU6NAdE3Rpkzo6Mi1YLtQ5ntoyVW07A9LOP_44zCmYrt4Z4rQ@mail.gmail.com>
 <CANt4hZidj5SeVD8O6P3nbH-O8NKLSdm4fqw7AhFdKgVrofBjXA@mail.gmail.com>
 <077d8e99-3aac-c9ca-bce4-aa90c98ed075@heigl.org>
 <1510070893.27420.85.camel@ctankersley.com>
 <CAJd4=YZ2C_JPBU1NO1eOU7JGrJ-wx=665PYr0isOoQb+9T57+Q@mail.gmail.com>
 <CACXBjuiwaEkyjN_3sWgyoM0AJd5BGx-0XDQWXrGqwxRDu_8WJA@mail.gmail.com>
 <CAESVnVp54-3h4KX2Xt_UBMTfeWOboonurJDqyCbWd8cgwAPAwA@mail.gmail.com>
Message-ID: <7b074035-57db-5e36-384e-147ad9d26489@gmx.de>
Date: Wed, 8 Nov 2017 12:59:40 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <CAESVnVp54-3h4KX2Xt_UBMTfeWOboonurJDqyCbWd8cgwAPAwA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Content-Language: de-DE
Subject: Re: [PHP-DEV] Re: PHP's mail servers suck
From: mkliewe@gmx.de (Michael Kliewe)

Am 08.11.2017 um 12:09 schrieb Sara Golemon:
> On Wed, Nov 8, 2017 at 2:51 AM, Rasmus Lerdorf <rasmus@lerdorf.com> 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 changes. If it is just replace ezmlm
>> with Mailman, then you are going to have to make a really really strong
>> case for why you think a sideways migration like that will make any
>> difference. It is also important to understand the difference between the
>> list server and the mail server responsibilities.
> 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 be a shared experience (therefore internals@) or an
> essentially open request for "I'd like to help, but I'll need the
> ability to poke around to figure out wtf is going on".
The problem seems to be the mailing list software, not the mail server.
Mail servers just transfer bytes from A to B.

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-xxxx]), that's why the DKIM signature breaks.
SPF breaks, because Gmail and others don't include the IP address of the
PHP mailing list mailserver in their SPF records. So SPF also fails.

Easiest fix should be:
- Don't touch the email, especially don't change the Subject. Then the
DKIM signature stays valid, and DMARC is happy.

Maybe the better way:
- Change the From:-Header to an email address that php.net owns, and put
the original email address into the displayname. Like:
Michael (mkliewe@gmx.de via PHP-DEV Mailing List)
<members-internals@lists.php.net>
- Remove existing (now broken) DKIM-Signatures, and add php.net own DKIM
signature (alternative: change to X-Original-DKIM-Signature)
- Set the original From: email address into Reply-To: if you want
- Because now it's "your" email, you can change the Subject + content as
you like.

Obviously the mailing list software has to support this procedure.
In MailMan for example you can configure this with some settings:
https://wiki.list.org/DEV/DMARC
For ezmlm there seems to be something in 7.2.0:
https://untroubled.org/ezmlm/archive/7.2.0/CHANGES
 "- Added optional rewritefrom feature to ezmlm-send, automatically
enabled when the sender has a "reject" DMARC policy."

Hope this helps to see, that it has to be fixed in the mailing list
software, not the mailserver.

Michael