From: Aaron Conole <aconole@redhat.com>
To: techboard@dpdk.org
Cc: Lincoln Lavoie <lylavioe@iol.unh.edu>, ci@dpdk.org
Subject: UNH - DMARC issue
Date: Thu, 02 Feb 2023 09:42:06 -0500 [thread overview]
Message-ID: <f7to7qc164h.fsf@redhat.com> (raw)
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
next reply other threads:[~2023-02-02 14:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 14:42 Aaron Conole [this message]
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
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=f7to7qc164h.fsf@redhat.com \
--to=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).