Problems with new messages after 140/141 update (bitdefender)
Up to V128 I had no problems but since the automatic 140/141 update I have a problem with the body of new mail messages as below. I can read previous messages without any issues. My system is Windows 11 24H2 fully up to date. THunderbird is 141.0 (64bit) RElease UPdate Channel Build 20250721141226. I can access my email at Talktalk via their webmail with no problem at all but through Thunderbird I get this type of message . X-VadeSecure-Status: MC . X-VadeSecure-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdefgddufeektdduucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuqfgiuffgfgdpggftfghnshhusghstghrihgsvgdpgffpggdqvfetnffmvfetnffmnecuuegrihhlohhuthemuceftddunecundfotefknffkpffiucdludejmdenucfjughrpefhvffufffjgghrkfgtsegrtderredttdejnecuhfhrohhmpedfofihucghrghithhrohhsvgdfuceoofihhggrihhtrhhoshgvsegvmhhlrdifrghithhrohhsvgdrtghomheqnecuggftrfgrthhtvghrnhepleffkedvkefhkeefheffgfffgfekueehkeeiteefgfdvvdetgffhgffgffejudevnecuffhomhgrihhnpeifrghithhrohhsvgdrtghomhenucfkphepudelkedrvdeghedrleefrddvudenucevlhhushhtvghrufhiiigvpeekfedtnecurfgrrhgrmhepihhnvghtpeduleekrddvgeehrdelfedrvddupdhhvghlohepmhhtrgegrdgvmhhlrdifrghithhrohhsvgdrtghomhdpmhgrihhlfhhrohhmpegsohhunhgtvgdqudeipgfjvffonfdqhedtfeduvdeiuddqieduleelkedtqdehvddttddtudduvdeiqdelfedusegsohhunhgtvgdrvghmlhdrfigrihhtrhhoshgvrdgtohhmpdhnsggprhgtphhtthhopedupdhmohguvgepshhmthhppdhgvghtqdfurghfvggfnhhsuhgsshgtrhhisggvpdhgvghokffrpehushdpshhpfhepphgrshhspdgukhhimhepphgrshhspdgumhgrrhgtpe
hprghsshdprhgvvhfkrfepmhhtrgegrdgvmhhlrdifrghithhrohhsvgdrtghomhdrpdhlvggrrhhnihhnghepthhruhgv
X-VadeSecure-Score: 17 X-VadeSecure-SID: ee41513a-185b4dfa799deaff X-VadeSecure-Dom: oxcloud-pro-eu-1 Authentication-Results: oxseu-vadesecure.net;
iprev=pass policy.iprev=198.245.93.21; spf=pass (sender IP is 198.245.93.21) smtp.mailfrom=bounce-16_html-5031261-619980-520001126-931@bounce.eml.waitrose.com; dkim=none (message not signed); dmarc=pass action=reject header.from=eml.waitrose.com; arc=none;
X-OX-DMARC: pass (policy=reject) Received-DKIM: Success Received-SPF: Pass Received: from mta4.eml.waitrose.com ([198.245.93.21])
by oxseu2nmtai04p.internal.vadesecure.com with ngmta id ee41513a-185b4dfb300e8b38; Wed, 13 Aug 2025 10:50:21 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; s=200608; d=eml.waitrose.com;
h=From:To:Subject:Date:List-Unsubscribe:List-Unsubscribe-Post:MIME-Version: Reply-To:Message-ID:Content-Type; i=MyWaitrose@eml.waitrose.com; bh=Qrk+tP6/Th9RstefylsTHjBAGDIUNRTrAYCkfLtc38M=; b=WE1rpforjUyxr16PPRudha8LqiSmD7GsDOFhYzt2/L6g8SANQJCWZP6xRf12waPKh4Sz6V35WPih Ue716DftEebtBUhRFOda2LmILu6X2+8jVUMZ8+LQW6RpBq5Gw4/ZBsyyPESM0zBMXsG/xLpRQxCI turi9qN0yV6fmYdxFU0=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; s=fbldkim6; d=s6.y.mc.salesforce.com;
h=From:To:Subject:Date:List-Unsubscribe:MIME-Version:Reply-To:Message-ID: Content-Type; bh=Qrk+tP6/Th9RstefylsTHjBAGDIUNRTrAYCkfLtc38M=; b=iJ8brDdDUkSup+Bc6vSZQz+P0k6lOZi70SDV5Vn/oalGH30v6ZfKqlkzs1tSgP9BOiZUF2hP0Ipx swvZFBASGiPkGp96LX1gMpRbbHa4PuGYYs6BTiDxYAoyJeUzk9JEiji73zQBcQNcVOZC6VPTTmkz pE4LSP+1GMbbGDiaDuS+EJ/XVs6Z2roqSxxNJf34KPiVyJlOZgY3MxfXhCLMEB+Q8mC+JWbZwveD mGDtJanDzTnJn4A3pz0maVPWKaQ8B2DuVmwig3zBWJcJGuAHCxoByX2kG/PdAu0SBzcAqBPdtYDN YVcSx4q6Ic/ooTA/pqlPIsTrvxrQ/9wH16G6Qw==
Received: by mta4.eml.waitrose.com id hjhmuq2fmd4j for <brian.adams@talktalk.net>; Wed, 13 Aug 2025 10:45:12 +0000 (envelope-from <bounce-16_HTML-5031261-619980-520001126-931@bounce.eml.waitrose.com>) From: "My Waitrose" <MyWaitrose@eml.waitrose.com> To: <brian.adams@talktalk.net>
Изменено Wayne Mery
Все ответы (1)
Solution update posted at 8:48 Eastern time (12:48 UTC) Thursday by Alexlandru_BD, an admin at bitdefender, "The developers reverted the changes made in the last signature update and this should do the trick until a permanent fix is deployed. Just click on update in systray and reboot once completed. But keep in mind this change is being rolled out gradually, so it may not reach everyone at the same time.." More details at https://www.reddit.com/r/Thunderbird/comments/1mo693n/comment/n8ammvq/
Для ответа на сообщения вы должны войти в свою учётную запись. Пожалуйста, задайте новый вопрос, если у вас ещё нет учётной записи.