When doing this fast and the contact search job didn't even have
time to start, this saves running a whole search for nothing.

The Interface::BodyPartMemento(s) were not deleted.

Since they are deleted when switching messages, this is no severe
leak, it just showed up in a unittest.

CCBUG: 363586

Sorry for breaking the string freeze, but this is quite visible.
The new string landed as part of bugfix: please don't consider
bugfixes as automatically grants for new strings, especially
during the freeze, without *at least* a notification to the
i18n mailing list.

CCMAIL: kde-i18n-doc@kde.org
CCMAIL: sknauss@kde.org

The plugins are still not aware of the new API so we need to use the
QueueHtmlWriter.

alternative parts can also have a calender element, so we want to render
that.

BUG: 362958

Typing a filter and then clicking back into the messagelist (to be able to use
Left/Right or Del shortcuts for instance) only worked when clicking on a
*different* current item (because slotSelectionChanged ends up calling setFocus).
Clicking on the existing current item had no effect.

The simplest fix is to just use ClickFocus as focus policy, but
of course tabbing should work too, so rather StrongFocus, which is
actually the default, so just removing the line is best.

In kdepim4 the default focus policy was used too, c626f4cb added this
NoFocus line by error: it doesn't actually fix the dual-color-issue for
selected messagelist items.

MUAs sometimes fail to set the correct character encoding.
If the set us-ascii, we can help a little bit by setting it to utf-8.
Because utf-8 is a superset of us-ascii we do not break anything.

BUG: 248058
FIXED-IN: 5.4.0

ObjectTreeParser knows best, when we need to set plaintextcontent.