Has it been determined if this is a Thunderbird 102 bug or some other issue that was exposed with the move to version 102? If anyone has a work around or way to resolve the problem, please post it. Still have this annoying issue after upgrading to 10...
