DPDK CI discussions
 help / color / mirror / Atom feed
From: Ali Alnubani <alialnu@nvidia.com>
To: Aaron Conole <aconole@redhat.com>,
	"techboard@dpdk.org" <techboard@dpdk.org>,
	Lincoln Lavoie <lylavioe@iol.unh.edu>
Cc: "ci@dpdk.org" <ci@dpdk.org>
Subject: RE: UNH - DMARC issue
Date: Wed, 8 Feb 2023 09:02:09 +0000	[thread overview]
Message-ID: <DM4PR12MB51675EEFBFF96265F24D3448DAD89@DM4PR12MB5167.namprd12.prod.outlook.com> (raw)
In-Reply-To: <f7to7qc164h.fsf@redhat.com>

> -----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

  reply	other threads:[~2023-02-08  9:02 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 [this message]
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
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=DM4PR12MB51675EEFBFF96265F24D3448DAD89@DM4PR12MB5167.namprd12.prod.outlook.com \
    --to=alialnu@nvidia.com \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=lylavioe@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).