Hi Thunderbird maintainers! My understanding (by reading some Thunderbird upstream mailing lists) is that 52.8.0 only has part of the EFAIL fixes and the remaining fixes will go into 52.8.1.
So perhaps this bug should not be marked as fixed in 1:52.8.0-1? Or are the remaining problems tracked on another bug report that I could not find? Cheers, -- intrigeri
