In the meantime I have switched to Leap 42.1 and noticed that with initially the same Thunderbird version this bug did not exist in Leap. So this bug seems to be 13.2 specific.