Re: Sending using my @debian.org in gmail
- To: firstname.lastname@example.org
- Subject: Re: Sending using my @debian.org in gmail
- From: Thomas Goirand <email@example.com>
- Date: Wed, 5 Dec 2018 14:58:08 +0100
- Message-id: <[🔎] firstname.lastname@example.org>
- In-reply-to: <email@example.com>
- References: <CAPQicOyW3bMxmV2GgdEd3T+rt4g_eCP8Mfrsyxg3K1Dx9en0fg@mail.gmail.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com>
On 11/30/18 6:57 PM, Michael Stone wrote:
> On Fri, Nov 30, 2018 at 12:49:02PM -0500, Alexandre Viau wrote:
>> It is true that others are vulnerable, but this is a choice that Debian
>> makes and it can be fixed. If we wanted, we could largely limit this
>> with more restrictive debian.org DNS records.
> Yes and no. :) There would need to be a concerted push for some time to
> migrate 20+ years of legacy configurations in order for this to not
> break quite a lot.
Absoultely not. Adding some DMARC records in our DNS doesn't break any
server not checking DMARC records.
Thomas Goirand (zigo)