From: Petr Vorel <pvorel@suse.cz>
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2] cve/icmp_rate_limit01: Lower icmp_msgs_per_sec for debug kernel reliability
Date: Tue, 28 Jul 2026 23:09:11 +0200 [thread overview]
Message-ID: <20260728210911.GC114518@pevik> (raw)
In-Reply-To: <CAASaF6xWz9LxH-=wUveuSt0UBmUs9L7Os1OdWQ5VdpSy3UUTkg@mail.gmail.com>
> On Tue, Jul 28, 2026 at 3:16 PM Petr Vorel <pvorel@suse.cz> wrote:
> > Hi Brian,
> > > Hi Petr,
> > > Happy to contribute!
> > We are happy to get new contributors :).
> > > Thank you for letting me know, that is strange. On my system it's
> > > configured correctly. Digging a little deeper, I think it might be a
> > > corporate smtp issue.
> > FYI it's mangled "From:" mail header [1]: "From: Brian Grech via ltp
> > <ltp@lists.linux.it>". It's probably DMARC + Mailman related.
> > BTW I thought it should not be on redhat.com side, because Jan Stancek does not
> > have that problem, but actually he does have that problem as well [3] "From: Jan
> > Stancek via ltp <ltp@lists.linux.it>". It's just he probably does merge these
> > patches directly without first downloading them from the mailing list.
> > Anyway, very minor problem, but it'd be nice to get it fixed. Our list has
> > setup: from_is_list = no. I suppose this is correct (looking at the docs [4] and
> > also check other projects setup [5]).
> Can you see also these two in our config?
> dmarc_moderation_action = Accept
We have dmarc_moderation_action = Munge From (in privacy/sender/dmarc_moderation_action)
> dmarc_quarantine_moderation_action = No
We have dmarc_quarantine_moderation_action = yes
dmarc_none_moderation_action = No
Too late to read the docs, I'll do it tomorrow.
Kind regards,
Petr
> > Kind regards,
> > Petr
> > [1] https://lore.kernel.org/ltp/20260722212646.2340340-1-bgrech@redhat.com/raw
> > [2] https://wiki.list.org/DEV/DMARC
> > [3] https://lore.kernel.org/ltp/08c85cf64d703dfaba31398ab9d9b480488fe338.1747227481.git.jstancek@redhat.com/raw
> > [4] https://list.org/mailman-admin.txt
> > [5] https://sourceware.org/pipermail/binutils/2023-October/129852.html
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-07-28 21:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 18:14 [LTP] [PATCH] cve/icmp_rate_limit01: Lower icmp_msgs_per_sec for debug kernel reliability Brian Grech via ltp
2026-07-22 19:20 ` [LTP] " linuxtestproject.agent
2026-07-22 21:26 ` [LTP] [PATCH v2] " Brian Grech via ltp
2026-07-22 23:05 ` [LTP] " linuxtestproject.agent
2026-07-27 8:22 ` [LTP] [PATCH v2] " Petr Vorel
2026-07-27 18:44 ` Brian Grech via ltp
2026-07-28 13:16 ` Petr Vorel
2026-07-28 13:26 ` Jan Stancek via ltp
2026-07-28 21:04 ` Petr Vorel
2026-07-28 13:49 ` Jan Stancek via ltp
2026-07-28 21:09 ` Petr Vorel [this message]
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=20260728210911.GC114518@pevik \
--to=pvorel@suse.cz \
--cc=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/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