Hi Lincoln,

 

Thank you for taking the time to make the change.

Unfortunately, however, I see that even some of the plaintext ones are still failing DMARC. This is an example if you want to check from your client:

https://inbox.dpdk.org/test-report/20230301075112.591AB601B1@dpdk-ubuntu.dpdklab.iol.unh.edu/

 

I’m checking if there is something I missed.

 

Regards,
Ali

 

From: Lincoln Lavoie <lylavoie@iol.unh.edu>
Sent: Tuesday, February 28, 2023 10:57 PM
To: Ali Alnubani <alialnu@nvidia.com>
Cc: Aaron Conole <aconole@redhat.com>; techboard@dpdk.org; ci@dpdk.org
Subject: Re: UNH - DMARC issue

 

Hi Ali,

 

We deployed the change to only plaintext emails last week.  Can you confirm if this improves things from your side for the DMARC results.  I am also also our IT admin to pull the reports for the past couple of days to see if failures are still being reported to us.

 

Cheers,

Lincoln

 

On Wed, Feb 8, 2023 at 11:20 AM Ali Alnubani <alialnu@nvidia.com> wrote:

> Just to make sure, your example is one that failed, correct?

 

Correct, the copy I got failed DKIM and DMARC authentication.

 

> Changing the content / format type will need a little more investigation, just to make sure the change wouldn't break other emails being sent. Does the message content type impact the DMARC evaluation?  I thought it was more about headers, routing, and approved mail hosts, etc. 

 

Non plaintext emails are more likely to be mangled by Mailman, breaking DKIM signature verification, and DMARC as a result.

 

Regards,
Ali

 

From: Lincoln Lavoie <lylavoie@iol.unh.edu>
Sent: Wednesday, February 8, 2023 5:37 PM
To: Ali Alnubani <alialnu@nvidia.com>
Cc: Aaron Conole <aconole@redhat.com>; techboard@dpdk.org; Lincoln Lavoie <lylavioe@iol.unh.edu>; ci@dpdk.org
Subject: Re: UNH - DMARC issue

 

HI Ali,

 

The To / Cc fields all look identical to what was sent / logged on our internal list.  I've attached the raw stuff email. Just to make sure, your example is one that failed, correct?

 

Changing the content / format type will need a little more investigation, just to make sure the change wouldn't break other emails being sent. Does the message content type impact the DMARC evaluation?  I thought it was more about headers, routing, and approved mail hosts, etc.  

 

Cheers,
Lincoln

 

On Wed, Feb 8, 2023 at 4:02 AM Ali Alnubani <alialnu@nvidia.com> wrote:

> -----Original Message-----
> From: Aaron Conole <aconole@redhat.com>
> Sent: Thursday, February 2, 2023 4:42 PM
> To: techboard@dpdk.org
> Cc: Lincoln Lavoie <lylavioe@iol.unh.edu>; ci@dpdk.org
> Subject: UNH - DMARC issue
>
> Hi all,
>
> UNH reported that their IT will be turning on DMARC enforcement "soon."
> I'm not sure when that will exactly take place, but as part of that,
> they found there was an issue with the DPDK mailing lists doing some
> header rewriting which will break email bounces via the mailing list to
> the lab.
>
> I think Ali is currently investigating, but I'm sending the email here
> to make sure you're aware.
>
> -Aaron

Hello, and apologies for the delay,

I can confirm that DMARC is failing for some of the reports, but I don't see obvious mangling to the headers or bodies of these emails.

Can you please help verify that the list of recipients in To and Cc isn't being mangled for the reports failing DMARC? Example:
https://inbox.dpdk.org/test-report/20230208081905.C6CB9600AB@dpdk-ubuntu.dpdklab.iol.unh.edu/

Would it also be possible to switch the format/content-type of these emails from html to text/plain as way to try and mitigate this?

Thanks,
Ali


 

--

Lincoln Lavoie

Principal Engineer, Broadband Technologies

21 Madbury Rd., Ste. 100, Durham, NH 03824

+1-603-674-2755 (m)


 

--

Lincoln Lavoie

Principal Engineer, Broadband Technologies

21 Madbury Rd., Ste. 100, Durham, NH 03824

+1-603-674-2755 (m)