Andrew Cooper <andrew.cooper3@citrix.com> writes: [Summary of an IRC debugging session, as requested] b4 DKIM checks on my own patches fail. It worked fine for Konstantin, and it turns out to be because of differing TXT record visibility inside and outside of the corporate notwork. ~Andrew (via https://msgid.link/16beccd0-db0b-4c9c-a4d1-fcf43f98959c@citrix.com)
Konstantin Ryabitsev <konstantin@linuxfoundation.org> writes: On Wed, Mar 06, 2024 at 05:04:51PM +0000, Andrew Cooper wrote: > [Summary of an IRC debugging session, as requested] > > b4 DKIM checks on my own patches fail. > > It worked fine for Konstantin, and it turns out to be because of > differing TXT record visibility inside and outside of the corporate notwork. Right, one option we can consider is specifying an external DNS server to use for DKIM lookups. I'll have to check if dkimpy supports this, though. bugbot assign to me (via https://msgid.link/20240306-chirpy-dugong-of-enhancement-cfdfad@lemur)
Konstantin Ryabitsev writes in commit 1457bc615a8ff06afba252a15480b61dd7cfef60: main: add ability to specify DNS resolvers for DKIM Sometimes it is useful to be able to specify alternative resolvers to use for DKIM lookups, for example when you're on an internal network that uses split-horizon DNS. You can now override the resolvers to use, but please check that you're actually able to query them. Reported-by: Andrew Cooper <andrew.cooper3@citrix.com> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=218567 Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org> (via https://git.kernel.org/pub/scm/utils/b4/b4.git/commit/?id=1457bc615a8f)