On Beta channel (60.0b1) SMTP no longer works for any of my email accounts
I use Thunderbird to control several different email accounts - they are all in fact using the gmail servers even though they are not all gmail.com addresses. I use SMTP protocol. Up until this beta release (60.0b1 32-bit) this procedure has been working satisfactorily for several years. Now any attempt to collect email does one of two things. It either hangs saying it is connecting or it bring up a dialog saying "connection to server pop.googlemail.com was reset" It does not collect any mail
I have tried reverting to non-beta (reinstall from the site) = no difference, still doesn't work I have checked firewall - seems OK However I do think it is partly machine or Windows based
Note: this machine is a 64bit running Win 10 (64 bit) professional Another machine - 32 bit running Win10 (32 bit) professional is still working (it is running current release Thunderbird (52.4.0 32-bit) and this is working successfully on the same accounts
bonnyjars
Ọ̀nà àbáyọ tí a yàn
So does it work when you turn off the email scanner in AVG?
Ka ìdáhùn ni ìṣètò kíkà 👍 1All Replies (5)
Thanks, but I was never intentionally involved with IMAP - all my emails are POP SMTP - I found stuff online about changing port numbers which also had no effect
I currently think that the problem is with AVG (I use pro) - it looks to me as though gmail may have changed their server ID so the firewall part of AVG no-longer recognises pop.googlemail.com- so I am off to investigate that
Ọ̀nà àbáyọ Tí a Yàn
So does it work when you turn off the email scanner in AVG?
smtp has nothing to do with imap and pop. Tha t is, it doesn't matter if you are imap or pop. :)
I didn't think of turning off the email scanner in AVG but what I did was to check the firewall reference ids and took out the one I thought was the googlemail one and thus forced it to ask for confirmation next time I connected - it is now fine The interesting thing is that both Mozilla and AVG are 32-bit apps running on a 64bit machine and OS (Win 10 pro 64 bit) meanwhile over on another machine which is 32-bit and running Win10 pro 32-bit there was no problem -FYI I keep that setup to run some legacy software that will not run in a 64bit environment - it happily runs in an NTVDM environment
Meanwhile, thanks to everyone who suggested answers - it now is all OK