Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: Chuck Lever <chucklever@gmail.com>
To: users@linux.kernel.org, tools@linux.kernel.org
Subject: Most of my "b4 am" runs fail the DKIM test
Date: Wed, 2 Aug 2023 09:53:10 -0400	[thread overview]
Message-ID: <CAFMMQGt=-0HRpmb+fD0e_LVeZ_TPr-8QEPnorAkffrVOowb4dQ@mail.gmail.com> (raw)

I recently started seeing this quite a bit:

  ✗ [PATCH v4 1/2] SUNRPC: add verbose parameter to __svc_print_addr()
  ✗ [PATCH v4 2/2] NFSD: add rpc_status entry in nfsd debug filesystem
  ---
  ✗ BADSIG: DKIM/kernel.org

In fact, even my own patches (sent via the kernel.org SMTP relay) fail
this check.

What am I doing wrong?


-- 
"We cannot take our next breath without the exhale."
 -- Ellen Scott Grable

             reply	other threads:[~2023-08-02 13:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02 13:53 Chuck Lever [this message]
2023-08-02 14:11 ` Most of my "b4 am" runs fail the DKIM test Konstantin Ryabitsev
2023-08-02 14:57   ` Chuck Lever
2023-08-02 15:54     ` Konstantin Ryabitsev
2023-08-02 18:46       ` Chuck Lever

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='CAFMMQGt=-0HRpmb+fD0e_LVeZ_TPr-8QEPnorAkffrVOowb4dQ@mail.gmail.com' \
    --to=chucklever@gmail.com \
    --cc=tools@linux.kernel.org \
    --cc=users@linux.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).