My provider (fastmail.com) recently started enforcing the use of app passwords, and at the same time switched to new server names. I made the changes easily. I'm sending messages with no trouble.
But I'm seeing in the logs (TB and FM) that TB is logging in as IMAP, but apparently never attempting to retrieve mail.
I quit and restarted TB, no change. I inserted the app password in both parts of the server config instead of marking the SMTP side "same as IMAP", no change.
I enabled protocol logging for both SMTP and IMAP. The SMTP log was created and looks appropriate. The IMAP log has not been created despite explicit "get new mail" commands. This is what leads me to believe that TB isn't even trying to retrieve mail.
I'm still using TB 10.5.3 due to all the complaints here about conversation view. It seems those complaints have mostly been resolved, so if needed, I'll upgrade. In fact, if no other solution is found, I suppose that's the next thing I'll try.
Edward
But I'm seeing in the logs (TB and FM) that TB is logging in as IMAP, but apparently never attempting to retrieve mail.
I quit and restarted TB, no change. I inserted the app password in both parts of the server config instead of marking the SMTP side "same as IMAP", no change.
I enabled protocol logging for both SMTP and IMAP. The SMTP log was created and looks appropriate. The IMAP log has not been created despite explicit "get new mail" commands. This is what leads me to believe that TB isn't even trying to retrieve mail.
I'm still using TB 10.5.3 due to all the complaints here about conversation view. It seems those complaints have mostly been resolved, so if needed, I'll upgrade. In fact, if no other solution is found, I suppose that's the next thing I'll try.
Edward
Edited: - 18 October 2024 17:58:21