Bill Cole kirjoitti 23.9.2019 20:11:
On 23 Sep 2019, at 11:43, Jari Fredriksson wrote:
Bill Cole kirjoitti 23.9.2019 18:26:
On 23 Sep 2019, at 1:00, Jari Fredriksson wrote:
Hello again.
I have a problem that arises after my mail server has been up for
maybe two days. Suddenly all DKIM-verifications in SpamAssassin says
DKIM_INVALID while those look valid to be when looking to mail
source code. It works again correctly after I reboot the machine.
This starter as it is when I upgraded from Debian Stretch to Buster,
I think.
Sample: https://pastebin.com/cZKSTZVC
The signature on that message does not verify according to the
dkimverify.pl from Mail::DKIM or the dkimverify from the Python
'dkimpy' package. Using the --debug-canonicalization option of
dkimverify.pl shows that the 'bh' field matches, so the problem is in
the headers.
In short: it's probably not your problem *in this case*
One side-note on this: In reviewing this I see that the first case is
labeled as multipart/alternative but it contains only an unterminated
text/plain part, so it seems to have been truncated, which is not
consistent with the fact that dkimverify.pl comes up with the same
body hash, so I'm questioning everything now...
Yes I attached only the headers of the mail, not the body as I
considered it to be wasteful. Maybe a bad decision... Such happens.
Thank You very much for your comments!
--
ja...@iki.fi
