Cannot send emails
Hi,
I've setup Thunderbird (32 bit) on Windows 8.1 client on Hyper-V. This is a setup I've used on 2 other machines with no problems as long as I run the 32-bit version. I currently have a similar Hyper-V setup on my laptop (Windows 11 host/Windows 8.1 client/Thunderbird 32-bit) with no issues.
On this machine (Windows 10 host/Windows 8.1/Thunderbird 32-bit) however, I can receive emails fine but can only send 1 message and then no more. I've followed all of the online suggestions, and I can even ping the smtp.google.com servers and it works fine. Web browsing works fine (upload, download). It also works fine on the Windows 10 host, as there are no problems sending/receiving using Thunderbird from there.
I know this is a little out of normal use, but in my case, I have older 32-bit software that I have to virtualize because the activation servers were shut down last year. So, I run on a 15-use "trial" since I can't activate my "owned" software anymore. When I run out of trial uses, I create a new virtual machine, reload the software, restore my backup file and I'm off and running again.
Anyway, any clues of where to look would be appreciated.
被選擇的解決方法
I wanted to follow up on this and let you know that it's fixed!
Now, it could be one of two things I did over the weekend.
The first is that I was suspecting hardware issue in my computer as this was the only one that this was happening to and because of some BSDs I had experienced last week. So Google said I should run MS memory diagnostics. It showed that the memory was bad. I then rebooted and tested with memtest86 and it couldn't even complete the scan, as there were so many errors. I replaced the ram with some that I had and retested again with no errors.
Then I rebooted the computer and wanted to work on this TB sending problem. So first thing I uninstalled Hyper-V, restarted the host machine, then went back in to reinstall Hyper-V, restarted the host machine again. After windows started, I booted the client machine, started TB and tried forwarding a message to my other Gmail. That worked, so I tried on a few more and it seems to now be acting like my other two computers with this setup. That is flawlessly.
So whether it was the bad RAM that somehow was affecting the Hyper-V install, or it was Hyper-V itself missing some component it needed which the reinstall fixed, I don't know. But thank you for suggesting recreating the profile, because that's really what made me try reinstalling Hyper-V.
從原來的回覆中察看解決方案 👍 0所有回覆 (4)
Assuming you have TB 115 on this setup (latest version for W8.1), what are the gmail settings, and are you using a VPN? Settings should be imap.gmail.com, 993, SSL/TLS, OAuth2, email address; smtp.gmail.com, 465, SSL/TLS, OAuth2, email address. smtp.google.com is not a valid server.
Actually, trying version 99.0b2 (32 bit) right now but had 115 installed before and had similar results. However, when I tried this earlier version, I was able to send 1 email before it stopped sending. On 115 it wouldn't even send one. I apologize for not sending server settings. I've attached them. Since whatever past version of TB, I've just used the auto setup as it's always connected to Google servers with no problems.
Not using a VPN, only Windows Defender on client, and Windows security on host. I tried both "default and external virtual network switches" in Hyper-V. Both allow me to use the host machine's network adapter. So, both settings have full internet access and can receive emails flawlessly. Tried turning off firewalls in both Host and Client.
Interestingly I was able to send 1 test email again after starting the VM session today before it stopped sending again. However, that test took almost 10 minutes to hit my inbox on my other account. I almost want to think it's a Google-side permission that is not allowing me to send. But I allowed TB to connect with Google when I was installing.
I've logged in to the admin console for my Google Workspace account and can't find anything. But I'm no expert when it comes to workspace.
I've no experience with VMs, but I'd try creating a new profile with 115.16.2, to ensure the latest OAuth2 settings, add a personal gmail account, and see if it works. If it does work, add the workspace account and test. If it doesn't work, I think the issue is with gmail and VMs.
The reason for testing in the new profile is to avoid any issues with re-using old profiles that might have been used with various versions.
選擇的解決方法
I wanted to follow up on this and let you know that it's fixed!
Now, it could be one of two things I did over the weekend.
The first is that I was suspecting hardware issue in my computer as this was the only one that this was happening to and because of some BSDs I had experienced last week. So Google said I should run MS memory diagnostics. It showed that the memory was bad. I then rebooted and tested with memtest86 and it couldn't even complete the scan, as there were so many errors. I replaced the ram with some that I had and retested again with no errors.
Then I rebooted the computer and wanted to work on this TB sending problem. So first thing I uninstalled Hyper-V, restarted the host machine, then went back in to reinstall Hyper-V, restarted the host machine again. After windows started, I booted the client machine, started TB and tried forwarding a message to my other Gmail. That worked, so I tried on a few more and it seems to now be acting like my other two computers with this setup. That is flawlessly.
So whether it was the bad RAM that somehow was affecting the Hyper-V install, or it was Hyper-V itself missing some component it needed which the reinstall fixed, I don't know. But thank you for suggesting recreating the profile, because that's really what made me try reinstalling Hyper-V.