Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More
Open

Probleme bei Umstellung von POP auf IMAP

Thunderbird Junk email and spam
rudolf.weinzierl-landshut
rudolf.weinzierl-landshut

Subject: Thunderbird 152 – IMAP Junk messages are not automatically moved to Spam (T-Online IMAP) I am using Thunderbird 152 on Windows 11 with a Deutsche Telekom (T-Online) IMAP account. Problem When I manually mark a message as Junk (toolbar button, context menu or Junk column), the message briefly disappears from the Inbox and immediately reappears. It is marked as Junk, but it is not moved to the Spam folder. If I disable the option "Move new junk messages to:", the message remains in the Inbox and is marked as Junk, without the brief disappearance. Manual Move to → Spam always works correctly. Environment • Windows 11 • Thunderbird 152 • T-Online IMAP • ESET Internet Security • Only one Spam folder exists on the T-Online server. Troubleshooting already performed • Created a completely new IMAP account. • Verified Junk settings. • Verified the Spam folder path: imap://...@secureimap.t-online.de/Spam • Manual move to Spam works correctly. • Rebuilt the folder cache. • Recreated folderTree/folder cache files. • Performed IMAP resynchronization. • Tested with ESET mail protection enabled and disabled (no change). • Checked profile configuration. • Verified that the IMAP server directory setting does not change the behaviour. Additional observation The profile contains two IMAP cache directories: • secureimap.t-online.de • secureimap.t-online-1.de The current IMAP directory does not contain local Spam/Junk cache files, while the old "-1" directory still contains: • Spam • Spam.msf • Junk • Junk.msf Thunderbird also displays a greyed-out, inaccessible Spam/Junk folder which cannot be selected, subscribed or removed. Question Is this a known issue in Thunderbird 152 related to IMAP Junk handling or old IMAP cache migration after changing an account from POP to IMAP? If not, which log or additional information would help identify the cause?

PS: The POP account worked correctly before the migration to IMAP. The problem started only after switching from POP to IMAP. Rudolf.weinzierl-landshut@t-online.de

Subject: Thunderbird 152 – IMAP Junk messages are not automatically moved to Spam (T-Online IMAP) I am using Thunderbird 152 on Windows 11 with a Deutsche Telekom (T-Online) IMAP account. Problem When I manually mark a message as Junk (toolbar button, context menu or Junk column), the message briefly disappears from the Inbox and immediately reappears. It is marked as Junk, but it is not moved to the Spam folder. If I disable the option "Move new junk messages to:", the message remains in the Inbox and is marked as Junk, without the brief disappearance. Manual Move to → Spam always works correctly. Environment • Windows 11 • Thunderbird 152 • T-Online IMAP • ESET Internet Security • Only one Spam folder exists on the T-Online server. Troubleshooting already performed • Created a completely new IMAP account. • Verified Junk settings. • Verified the Spam folder path: imap://...@secureimap.t-online.de/Spam • Manual move to Spam works correctly. • Rebuilt the folder cache. • Recreated folderTree/folder cache files. • Performed IMAP resynchronization. • Tested with ESET mail protection enabled and disabled (no change). • Checked profile configuration. • Verified that the IMAP server directory setting does not change the behaviour. Additional observation The profile contains two IMAP cache directories: • secureimap.t-online.de • secureimap.t-online-1.de The current IMAP directory does not contain local Spam/Junk cache files, while the old "-1" directory still contains: • Spam • Spam.msf • Junk • Junk.msf Thunderbird also displays a greyed-out, inaccessible Spam/Junk folder which cannot be selected, subscribed or removed. Question Is this a known issue in Thunderbird 152 related to IMAP Junk handling or old IMAP cache migration after changing an account from POP to IMAP? If not, which log or additional information would help identify the cause? PS: The POP account worked correctly before the migration to IMAP. The problem started only after switching from POP to IMAP. Rudolf.weinzierl-landshut@t-online.de

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.