This bug is only fixed in Lightning 2.4 for Thunderbird 22 (and newer), see comments and status fields above.
This bug is only fixed in Lightning 2.4 for Thunderbird 22 (and newer), see comments and status fields above.