Thunderbird incorrectly places emails in junk folder
Thunderbird keeps sending an email to my Spam folder. I have repeatedly marked the email as "Not junk" and returned it to my inbox but it is almost immediately sent back to the Spam folder. This has been happening for over a month now and it is quite inconvenient because the address is for incoming payments by a company I sell to quite frequently so I do not want their communications consigned to Spam. How do I stop Thunderbird incorrectly targeting this email address?
चुने गए समाधान
Diddydean said
...but it is almost immediately sent back to the Spam folder...
That tells me you are using IMAP and the server keeps marking the message as spam. After all, Thunderbird only does so when receiving the message, so unmarking should "educate" Thunderbird and not send it back to a folder called Spam, which it doesn’t contain either (it’s a server folder). Also, you can check Thunderbird’s Junk log if applicable using the Tools menu (press Alt when needed) > Security panel > Junk tab - Show log button.
Try "teaching" webmail / your ISP’s spam filter about the message not being spam - you may need to set up a filter rule if you want to fully trust it.
संदर्भ में यह जवाब पढ़ें 👍 0All Replies (2)
चयनित समाधान
Diddydean said
...but it is almost immediately sent back to the Spam folder...
That tells me you are using IMAP and the server keeps marking the message as spam. After all, Thunderbird only does so when receiving the message, so unmarking should "educate" Thunderbird and not send it back to a folder called Spam, which it doesn’t contain either (it’s a server folder). Also, you can check Thunderbird’s Junk log if applicable using the Tools menu (press Alt when needed) > Security panel > Junk tab - Show log button.
Try "teaching" webmail / your ISP’s spam filter about the message not being spam - you may need to set up a filter rule if you want to fully trust it.
Many thanks for responding, I appreciate it. In the event I used quite a crude fix: I deleted the Spam folder and created a new one. That seems to have broken the path and solved the problem. Not quite as sophisticated as yours but it seems to have worked. But if it returns again, I'll try your method.