In the course of #32501, it turned out that some of the method signatures in the AbstractMessagingTemplate hierarchy (and the corresponding interfaces) do not consistently declare nullable headers/postProcessor arguments and throws MessagingException. This is worth revising in 6.2.9.