Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110309
Message-ID: <1213C754-F29A-43D0-AE0D-47218B8C2F83@benramsey.com>
Content-Type: multipart/signed;
	boundary="Apple-Mail=_24322A1D-FE22-4765-BB6F-1B66B52B69C4";
	protocol="application/pgp-signature";
	micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Fri, 29 May 2020 18:19:37 -0500
In-Reply-To: <1ffc26c8-78d3-a8f3-69af-fed44b463f70@thelounge.net>
Cc: PHP Internals List <internals@lists.php.net>
To: Reindl Harald <h.reindl@thelounge.net>
References: <CAJ2zyzPknkB2d-Meim7zqjrUgLUzaq2S7tQFTXPVWYJisE6V6g@mail.gmail.com>
 <CANeKSiS9W3VkfdMCVnBxaUbptBiPT6pzLvf29QaibcB2piohnw@mail.gmail.com>
 <CAJ2zyzMDeizUs+K=nmo3fse=ntUfyp6UEnB_cPeF5vzp5HyGbA@mail.gmail.com>
 <6ECC5663-F3CA-465A-93A5-037122D9B26A@benramsey.com>
 <1ffc26c8-78d3-a8f3-69af-fed44b463f70@thelounge.net>
Subject: Re: [PHP-DEV] Avoid ending up in Spam
From: ben@benramsey.com (Ben Ramsey)

--Apple-Mail=_24322A1D-FE22-4765-BB6F-1B66B52B69C4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

> On May 29, 2020, at 18:01, Reindl Harald <h.reindl@thelounge.net> =
wrote:
>=20
>=20
>=20
> Am 30.05.20 um 00:58 schrieb Ben Ramsey:
>>> On May 29, 2020, at 17:34, Jakob Givoni <jgivoni.php@gmail.com> =
wrote:
>>>=20
>>> On Sat, May 30, 2020 at 12:07 AM Benas IML =
<benas.molis.iml@gmail.com> wrote:
>>>>=20
>>>> Here's a quote from Ben Ramsey that basically sums up the problem:
>>>>=20
>>>>> This appears to be happening due to DMARC rules on the domains of =
the senders.
>>>>> I had the same thing happen to my emails, so I had to relax my =
DMARC rules. If
>>>>> your rules are set too strict, servers see the =46rom address =
coming from a
>>>>> server not authorized by the domain, so it gets quarantined.
>>>>=20
>>>=20
>>> Shouldn't I just be able to add lists.php.net or something to my SPF
>>> record for my domain then?
>>=20
>>=20
>> That might work. I haven=E2=80=99t tried it. I=E2=80=99ll try to look =
into it next week and see what I can figure out.
>=20
> how do you imagine that a SPF for any random domain could affect
> envelope senders ending with "@lists.php.net"?
>=20
> DMARC is not just about SPF
> SPF is not about "=46rom address" in the From-Header


I thought SPF allowed you to specify domains/IPs that are allowed to =
send email =E2=80=9Cfrom=E2=80=9D your domain.

Why wouldn=E2=80=99t something like this help?

    v=3Dspf1 include:_spf.google.com include:lists.php.net ~all

(In this example, assuming one already has an SPF record allowing Google =
Apps to send email for their domain.)

Cheers,
Ben


--Apple-Mail=_24322A1D-FE22-4765-BB6F-1B66B52B69C4
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iHUEAREIAB0WIQToXQMR3fpbrPOmEOewLZeYnIwHGwUCXtGYiQAKCRCwLZeYnIwH
G9g+AP0ULcLCOURl1RQ2RqaFLJxNeU/YCTU6avCQxVya7M703QD7BrMU8rmSRz7S
a5+dwer0WZykvC2yLDLS+S23IE2k15A=
=Iq15
-----END PGP SIGNATURE-----

--Apple-Mail=_24322A1D-FE22-4765-BB6F-1B66B52B69C4--