IMAP sync issues with 160 when using ESET Smart Security at default email client settings one server out of four
This is mostly informational for the community and a question
Background - I was affected by the missing intermittent mail at version 159. After the release of version 160 my problem persisted. Following the fix I set about more troubleshooting. I Had only issues with one of four email accounts tn TB, one other account is to a different server but has the same setup port 993 SSL/TLS setup. My email provider has great support and indicated many had had issues and the reports of 160 correcting the problem were many.
I found an ESET setting was the culprit, in advanced settings under "email client setup" they have a toggle for "Scan IMAPS mail transport" by default this is on. After switching this off version 160 works perfectly. This function has been in place a while and can confirm it worked OK with version 158.
I do not think its the vendor, as in one of my test I loaded the affected account into Windows 11 Outlook and established instant sync with "Scan IMAPS mail transport" on. The problem only effects TB sync with IMAP on one server.
From ESET's information this function scans the mail in route to the client. It does not affect "other" AV function with mail.
The Question: Should I pursue resolving this with TB? Or is it just a conflict?
Все ответы (1)
Выбранное решение
Update: I found a resolution to this issue by re-installing my ESET product. this was effective on two PS's affected.
ESET support was very interested and were working with me collecting logs. They really cared about the issue even as "Thunderbird" is not officially supported. Very impressive.
After what seemed like endless test and troubleshooting I just got a hunch in re-installing ESET much to my amazement this resolved the presumed conflict. As a note I use mostly default security settings so as to "avoid" making errors to things beyond my understanding.
Hopefully if this issue affects other's its something to try - Bill