I spoke too soon when I said it was working fine in another post. Everything seemed to set up fine, but when I open Thunderbird it’s not showing me my mail.
AFAIK I followed all of the instructions I saw. In Thunderbird I turned “connection security” off. The incoming server is imap.aim.com, and outgoing smtp.aim.com. Using port 587. This all jives with what it says to do in AIM Mail under “IMAP setup information” for mail clients.
In the Avast Mail Shield under SSL accounts my settings are: Host Name - aol.com, Protocol - IMAP, Port - 587, Encryption - SSL
I’ve set Thunderbird as both “Email Client” and “Outbound” as application rules in Comodo Firewall. Both with the same results.
It says “connected to imap.aol.com” in the lower left in Thunderbird when I try to look at my inbox. The message stays there for a long time, then eventually goes away and nothing happens.
Please help me out here. I’d like to be able to take advantage of this Mail Shield.
Somebody should make AIM Mail aware of that tidbit then, because it’s the port they tell you to use.
What then is the right port? Even when I had it set to 143 (the default in Thunderbird), and likewise in the Mail Shield… the results were still the same.
Okay, I’m making “progress” here. Now I can get into my inbox. I realize now the diff. in the Thunderbird settings between incoming and outgoing. I now have the encryption disabled for both, as well as authentication. For the incoming (IMAP) I’m using port 143. Outgoing (SMTP) port 587 (there was my original dilemma). Now I have 2 rules in the Mail Shield. One for incoming (IMAP): Port - 143, SSL. And outgoing (SMTP): Port - 587, TLS.
The problem is now that I cannot send mail. When I try to I get this message: “An error occurred sending mail: The mail server sent an incorrect greeting: Cannot establish SSL with SMTP server 205.188.186.167:587,SSL_connect error 5.” And then a 2’nd message after I click out of that one: “Sending of message failed. Please verify that your Mail & Newsgroups accounts settings are correct and try again.”
You probably still need to authenticate smtp with name and password-are you doing that? And if 587 fails, go ahead and try 465 again. There is no special IMAP outbound, it is all SMTP.
I got it working now, but to do so I had to disable encryption “none” for SMTP protocol under “SSL Accounts” in my Mail Shield settings. I had it set up for TLS previously. Is it normal to have to disable this for it to work? Or am I curing the disease by killing the patient in this case?
I have SSL encryption enabled for the incoming (IMAP) protocol. And I’m using ports 143 (IMAP) and 587 (SMTP). I did change them to 993 & 465 to experiment, to no avail. I reckoned that only applies if you’re using the encryption in the mail client, which you can’t do if you want the Mail Shield to work?
I got rid of my last email account (GMail) to eliminate less useful services. I like AIM Mail much better, and they in fact do support SSL/TSL. When you set up an account and go into the settings it breaks everything down there, including which port(s) to use for SMTP, what type of encryption to use (SSL-IMAP/TSL-SMTP). After Googling around my situation is hardly unique. People have had these issues with various web email/clients combos & the Mail Shield. Many have pointed out my exact scenario (can receive but not send mail). So by simple deduction it can’t just be AIM Mail that’s at fault here. It may be a combo of all 3, who knows.
In any event I’m not going to waste any more time on this. I just wanted to see if I could get the outbound scanning working with encryption enabled, but it’s really not important to me. I know what’s on my computer and I know what I’m sending people. It’s up to them to scan their own emails. The inbound scanning and encryption is working just fine, and that’s all I need. In the end I either had to disable the SMTP encryption to get the scanning to work, or vice versa (disable the scanning to get it encrypted). Either way that’s like curing the disease by killing the patient.
