Here’s the current status. I think I’ve done everything you have suggested.
OK, that looks right based on the description of your mail server, but of course it doesn’t pick up your mail. So let’s take Avast! out of the path. The attachment shows how the settings/troubleshooting/redirect settings should look now. If you remove the “110” so that line is blank, Avast! will not look at that port at all and you should be directly connected to your mail server if TB is configured correctly.
BTW, I see we haven’t asked some of the routine questions. What firewall are you using? What AV were you using before you downloaded avast? How did you remove it? Did your mail work OK with an earlier version of Avast!?
My reply to your questions: I’m using ZoneAlarm firewall. My previous AV was AVG Antivirus. Removal was a problem. After I ran the uninstall, some pieces were left on my computer. AVG recommended a utility that I downloaded from their site that cleaned out the rest. I have never had a previous version of Avast.
Did AVG have you run one of the programs at http://www.avg.com/us-en/download-tools ? IIRC, AVG also has a mail scanner which can sometimes interfere. If not, or you don’t remember, go ahead and run the appropriate removal tool. There have also been some conflicts with ZA, but usually not the free version-is that what you are running?
Yes, I tried the 32-bit remover, the first one on that AVG page, and nothing happened. The second one, 64-bit, did the trick. Do suggest I run it again? I don’t think any AVG stuff is still running on my computer.
I’m running ZA Free Firewall.
Go ahead and run it again and reboot. Then try the removal of the “110” so we can get your mail working again with Avast! bypassed but still installed. We may also need to uninstall Avast! with their tool at http://files.avast.com/files/eng/aswclear6.exe and reinstall that, but ???
I see a lot of conflicting information on the net about how yahoo.verizon is supposed to work, both from Thunderbird and from Verizon. So if bypassing Avast! and using port 110/none doesn’t work there are other alternatives to try:
- Change the TB settings to SSL/995
- Change the TB settings to TLS/995
Once you can successively connect with Avast! installed but bypassed, we can figure out how to insert it into the path.
OK, I ran the AVG uninstall utility again, though I don’t think anything happened. I rebooted and removed 110 from the Avast page. Now I am able to download messages to yahoo.verizon.net (for the first time in days). So far, so good. But I understand that Avast now isn’t monitoring my email. I think this answers your last message also.
Sounds good, even though we are back at the beginning. 
Now do 2 things:
- remove the entry from the SSL accounts table for yahoo.verizon.net completely
- add port 110 back to the redirect ports for Avast!
and we can see if avast! is smart enough to do the reconfiguration by itself.
I don’t think it is smart enough. I did the two things you said, then directed an e-mail to the Verizon account. I got the familiar Alert error message and no downloaded message. For what it’s worth, no entry magically appeared on the SSL accounts table.
OK, looks like the proxy is not working properly. settings to try with the SSL table.
- verizon.net pop3 110 none
- incoming.yahoo.verizon.net pop3 110 none
- yahoo.verizon.net pop3 110 none
and if none of those work I think Avast! will need to take a look at it. Or maybe another verizon.yahoo user will show up. ???
Nope, no luck with any of them.
Have you done an Avast! uninstall with their uninstaller yet, along with a reinstall? That is about the only simple thing left to try. And use the ssl settings with the yahoo.verizon line removed.
I did the reinstallation. For some strange reason, the d_mn thing is working now.
While installing I got a long avast information message about one removing SSL/TLS from one of my e-mail accounts. Too bad I didn’t understand it the first time.
Many thanks. Your patience has been remarkable.
Congratulations. Possibly the rerun of the AVG removal actually helped but still left installation problems with Avast! As far as the SSL/TLS message, you get that if you try to use TLS/SSL directly in the TB settings instead of letting Avast! do it after scanning in the SSL table. But this account doesn’t use it. In general, all of your TB accounts should be set to 110/none with Avast! and the ones that actually use SSL/TLS show up in the SSL table as port 995. Let us know if you have other problems.
Thanks for your input sded.