Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101103
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain phpgangsta.de designates 84.200.8.31 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>
 <7b074035-57db-5e36-384e-147ad9d26489@gmx.de>
 <67f497ca-7704-2328-0319-83efb23a57bc@rhsoft.net>
 <aecfc016-aca3-bc6a-b43e-beb872e4c3e0@gmx.de>
 <bcec944f-27f3-d5e4-87f3-906e22070c30@rhsoft.net>
Message-ID: <d8809878-586c-b3a7-0094-e6276766f48b@phpgangsta.de>
Date: Wed, 8 Nov 2017 13:52:59 +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: <bcec944f-27f3-d5e4-87f3-906e22070c30@rhsoft.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Content-Language: de-DE
Subject: Re: [PHP-DEV] Re: PHP's mail servers suck
From: info@phpgangsta.de (Michael Kliewe)

Am 08.11.2017 um 13:40 schrieb lists@rhsoft.net:
>
>
> Am 08.11.2017 um 13:36 schrieb Michael Kliewe:
>> Am 08.11.2017 um 13:27 schrieb lists@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-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.
>>>
>>> nonsense - a mailing list does not forward with the original envelope
>>>
>>> Return-Path: internals-return-101098-lists=rhsoft.net@lists.php.net
>>> Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=76.75.200.58
>>>
>> nonsense. Read about DMARC alignment
>> I was talking about the From: header. I just wanted to explain a bit,
>> not in every detail (DMARC alignment for example).
>>
>> No need to be rude
>
> the from header has no business with SPF - period
> DMARC is a different story
>
Maybe you should try to say it better, instead of just saying it's wrong.

From DMARCs view, the "SPF part" has to be a successful SPF check (which
checks the envelope from), AND the From: header has to be aligned to the
envelope from. That's where From: header and SPF come together, and need
to be aligned.

Yes, you were right, it does not fail because the basic SPF check fails,
but because the alignment fails, and then the "SPF-part of DMARC" fails...

Anyway, DMARC fails because SPF(including alignment) and DKIM both fail.