On 07/24/2015 01:46 AM, Neil Bothwick wrote: > On Thu, 23 Jul 2015 16:27:33 -0700, walt wrote: > >> Anyway, claws-mail (for normal behavior) apparently *requires* me to >> switch email accounts from a drop-down menu (Configuration::Change- >> current-account) before trying to read or send email. > > Are you saying that Message>Receive>Get from all accounts doesn't do what > it says? I normally only use one account for reading so wouldn't have > noticed this.
Hm. I've never done that til now so I don't know what to expect, but I just tried it while sniffing for internet traffic and saw absolutely zero. So I suppose the answer is yes, it doesn't do what it says. However, after being confused for days about this whole subject I'm beginning to suspect that both of my hypotheses are correct: claws-mail does indeed require me to change email accounts from the drop-down menu for proper operation, *and* google is paranoid enough to change behavior every time I access their email servers using a different client. To wit: claws-mail induced the long latency for my ISP's mail server unless I first switched to that account using the menu. I can reproduce this behavior consistently. But: gmail changes from zero-latency to long-latency in a (weasel words) fairly consistent way every time I switch mail clients, including when I use their own (carefully-targeted-ad-plagued-https-everywhere-browser-based) email solution. The gmail latency returns to zero after a period of time that I haven't pinned down yet through experiment, but is roughly 24 hours. I really sorta expected the google police to knock on my door after I tried to log in to my gmail account from a Windows 10 instance running in virtualbox. But they only sent an email telling they had protected my account by denying my login attempt. Very lenient, I think.
