DPDK CI discussions
 help / color / mirror / Atom feed
From: Ali Alnubani <alialnu@nvidia.com>
To: Lincoln Lavoie <lylavoie@iol.unh.edu>
Cc: Aaron Conole <aconole@redhat.com>,
	"techboard@dpdk.org" <techboard@dpdk.org>,
	"ci@dpdk.org" <ci@dpdk.org>
Subject: RE: UNH - DMARC issue
Date: Wed, 1 Mar 2023 19:52:18 +0000	[thread overview]
Message-ID: <DM4PR12MB51673CD9B8BD695FCE0E9ACDDAAD9@DM4PR12MB5167.namprd12.prod.outlook.com> (raw)
In-Reply-To: <DM4PR12MB5167955788AF99D1AF5D1E92DAAD9@DM4PR12MB5167.namprd12.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 5603 bytes --]

Hello,

After further investigation, I see now that some reports have broken DKIM signatures because Mailman (or the email libraries it uses) are folding their long subject headers into multiple lines, probably to conform with internet standards. There isn’t a configuration to control this per list in Mailman though, so I might have to look into patching it. Will update hopefully by end of next week.

Can you keep the emails in plaintext format? They are more readable now in https://inbox.dpdk.org/test-report/ as the body is no longer being encoded.

Regards,
Ali

From: Ali Alnubani <alialnu@nvidia.com>
Sent: Wednesday, March 1, 2023 3:10 PM
To: Lincoln Lavoie <lylavoie@iol.unh.edu>
Cc: Aaron Conole <aconole@redhat.com>; techboard@dpdk.org; ci@dpdk.org
Subject: RE: UNH - DMARC issue

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<mailto:lylavoie@iol.unh.edu>>
Sent: Tuesday, February 28, 2023 10:57 PM
To: Ali Alnubani <alialnu@nvidia.com<mailto:alialnu@nvidia.com>>
Cc: Aaron Conole <aconole@redhat.com<mailto:aconole@redhat.com>>; techboard@dpdk.org<mailto:techboard@dpdk.org>; ci@dpdk.org<mailto: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<mailto: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<mailto:lylavoie@iol.unh.edu>>
Sent: Wednesday, February 8, 2023 5:37 PM
To: Ali Alnubani <alialnu@nvidia.com<mailto:alialnu@nvidia.com>>
Cc: Aaron Conole <aconole@redhat.com<mailto:aconole@redhat.com>>; techboard@dpdk.org<mailto:techboard@dpdk.org>; Lincoln Lavoie <lylavioe@iol.unh.edu<mailto:lylavioe@iol.unh.edu>>; ci@dpdk.org<mailto: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<mailto:alialnu@nvidia.com>> wrote:
> -----Original Message-----
> From: Aaron Conole <aconole@redhat.com<mailto:aconole@redhat.com>>
> Sent: Thursday, February 2, 2023 4:42 PM
> To: techboard@dpdk.org<mailto:techboard@dpdk.org>
> Cc: Lincoln Lavoie <lylavioe@iol.unh.edu<mailto:lylavioe@iol.unh.edu>>; ci@dpdk.org<mailto: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
lylavoie@iol.unh.edu<mailto:lylavoie@iol.unh.edu>
https://www.iol.unh.edu
+1-603-674-2755 (m)
[https://ci3.googleusercontent.com/mail-sig/AIorK4xlKa1qM3IJKocZErE7ywuQuw_cfMEDW_tlU6Dw8dHUTWPjdawcJawE6HcYf7_JfXJnr9fvVJI]<https://www.iol.unh.edu/>


--
Lincoln Lavoie
Principal Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
lylavoie@iol.unh.edu<mailto:lylavoie@iol.unh.edu>
https://www.iol.unh.edu
+1-603-674-2755 (m)
[https://ci3.googleusercontent.com/mail-sig/AIorK4xlKa1qM3IJKocZErE7ywuQuw_cfMEDW_tlU6Dw8dHUTWPjdawcJawE6HcYf7_JfXJnr9fvVJI]<https://www.iol.unh.edu/>

[-- Attachment #2: Type: text/html, Size: 17440 bytes --]

  reply	other threads:[~2023-03-01 19:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-02 14:42 Aaron Conole
2023-02-08  9:02 ` Ali Alnubani
2023-02-08 15:36   ` Lincoln Lavoie
2023-02-08 16:19     ` Ali Alnubani
2023-02-28 20:56       ` Lincoln Lavoie
2023-03-01 13:10         ` Ali Alnubani
2023-03-01 19:52           ` Ali Alnubani [this message]
2023-03-01 20:21             ` Thomas Monjalon
2023-03-01 20:35               ` Lincoln Lavoie
2023-03-02 10:42                 ` Ali Alnubani
2023-05-18 21:07                   ` Patrick Robb
2023-05-22 13:43                     ` Patrick Robb
2023-05-22 18:45                       ` Patrick Robb
2023-05-23  6:46                         ` Ali Alnubani

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DM4PR12MB51673CD9B8BD695FCE0E9ACDDAAD9@DM4PR12MB5167.namprd12.prod.outlook.com \
    --to=alialnu@nvidia.com \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=lylavoie@iol.unh.edu \
    --cc=techboard@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).