I started a new thread on this issue since mine is WAY down the list and now the topic is “I think I fixed it” rather than it still being a definite issue.
I happen to read a suggestion in this thread by Gandalf1369 helping someone with FileZilla connection issues:
I thought shoot, might as well try it for Outlook. The person could not connect and send files, but if he cut web shield off, he could. That was the same issue for me (and others around here); I could not send emails from Outlook, but if I turned off web shield, I could.
My Outlook sending port to my server is 80. So I did this in avast! Free:
Settings
Troubleshooting
Redirect Settings
Web
Removed 80 from the list of http ports
Immediately tried sending an email from Outlook and it worked. Tried five more times…worked every time. Rebooted the computer…still worked.
Regarding computer and AV stuff, I would categorize myself a tad bit above novice, so for you experts out there…is what I did okay? Am I still being protected by avast! Free regarding emails?
It’s also great to know this ahead of time for FileZilla since I plan on using that as well on this new computer rather than what I have on my old computer.
Am I still being protected by avast! Free regarding emails?
if not you are being protected by Microsoft ...if this is your Hotmail account
Microsoft protect all Hotmail accounts with TrendMicro on the mail servers
I’m pretty sure that by removing 80 from the http ports list you have seriously degraded your computer’s protection when using a web browser. It is my understanding that all web browsers use port 80 when they access the internet. Avast’s Web Shield constantly scans this port and, by doing so, prevents virus and malware from infecting your computer when accessing web pages. I would definitely recommend that you add 80 back into the http ports list.
I realize that this will not help you at all in regards to your Outlook problem. Unfortunately I don’t use Outlook so I can’t offer any help for that. Perhaps if you search the posts here in the forum for other user’s problems with Outlook you might come across a solution that works for you.
Thanks, Gandalf. It was worth giving it a shot. I have sent a ticket in to avast! a few days ago and they responded asking for more information, which I provided. Hopefully, they’ll be able to figure it out. If not, it’s back to an earlier version of avast! free.
From the avast GUI click “Settings” → “Active Protection” → “Web Shield” (click the gear symbol on the right) → then while in the Main Settings window put a check mark in the “Scan traffic from well known browser processes only”.
Hopefully this will allow you to send and receive emails thru Outlook and, at the same time, continue with complete avast! protection while browsing the web.
Gandalf, that seems to have fixed the Outlook problem!! Thank you, thank you!! (Thank you!)
Although I have no idea what “Scan traffic from well known browser processes only” means, as long as I’m still protected and I can send Outlook email (which I depend on heavily in my business), this is FANTASTIC!
“Scan traffic from well known browser processes only” simply means that avast! will only scan the in/out traffic from the most commonly used web browsers, i.e. Internet Explorer, Firefox, Opera, etc., and leave all other processes alone i.e. Outlook, FTP programs, etc. This way you are still fully protected when browsing the web.
Does this mean that emails coming “in” to Outlook are not scanned ?..in other words open to Virus on incoming emails ?
I say this because even with ISP scanners & anti-spammers Avast 8 has caught one or two a month that saved my butt.
I typically never have outbound scanned but inbound is kind of critical IMHO.
Good point. I’m pretty sure that ALL email will still be scanned assuming that you have checked “Scan inbound mail (POP3, IMAP4)” and “Scan outbound mail (SMTP)” in the Mail Shield Settings. Hopefully someone with more knowledge than me will be able to definitively answer you question.
Wow…sure hope someone from Avast chimes in…what it sounds to me (no expert by far)…is that “Scan traffic from well known browser processes only” allows “servers” that are not “major” to come thru un-scanned…seems like a various dangerous option. PamJ, in Avast 2014 is there place to see if emails are scanned ?..as you know I have not made the jump to V9 & in V8 (see pic attached) you can see last email scanned, qty, etc. I thought I read somewhere in V9 this is no longer ?
That thought had occurred to me as well, wondering if mail would be scanned.
I sent myself a couple of emails then checked statistics (see process below) and it seemed they were still being scanned:
Choose Statistics on the left of main avast! Free window.
2 This puts you in a window that on the left says Realtime Data
Under the moving graph of shield activity is a list of the last five or so scans (Last Scanned Items). When I send or receive email, it’s showing up there as being scanned.
Again, I’m assuming this means emails are being scanned properly. Avast, are they?
And what does this change with checking the box “Scan traffic from well known browser processes only” actually do with web browsing, avast? Would love someone from avast! to let us know if this is a safe solution to the Outlook issue. I’m hoping it’s the excellent solution it seems to be.
Attachments so historical data with the mail shield graph and the realtime data showing that an outbox email was scanned with the subject line.
I just tried Gandalf’s fix with Outlook Internet Security, and, it seems to work there, too.
Avast did respond to my ticket, and suggested that I “repair” Avast IS through the uninstall programs tool in Control Panel. Did that this morning, and it had no effect…the issue was still there. I replied to their ticket response with that info.
I’m still interested why the webshield module affects email. When using Outlook, as a POP3/SMTP client, I wouldn’t expect there to be any traffic on port 80 (related to sending email, anyway), and wouldn’t expect a web module to cause any issues. I would expect the mailshield to potentially cause issues (that would only make sense).
Rob, if you haven’t already, I would suggest checking the port your server is using for outgoing email (SMTP). Mine was originally 25, but now it’s 80. And because it’s 80, that might be my issue since that’s also apparently a port for web browsing, or something like that. I had to go to port 80 earlier this year for outgoing mail when 25 stopped working. I’m going to see if I can switch back to 25 and maybe that will clear the problem for me. I still have not received any advice from my ticket, but I’m sure not going through the trouble of a “repair” if I don’t absolutely have to, especially since it didn’t help you any. (Since 80 is one of several ports on servers that can be used for email, it still needs to be addressed by avast.)
You’re right, my outgoing mail port is, indeed, port 80. What kind of cockamamie crap is that!?!? SMTP has been port 25 since, approximately, the beginning of time; while HTTP has been port 80.
Who the hell moves email on port 80!?
Did some double checking…we use GoDaddy to manage our email remotely. I used their auto set up tool when setting up Outlook. A check on their configuration screens shows that they take smtp traffic on port 80, 25, 3535, and 465 (ssl). I switched Outlook to port 25, and it seems to have worked. However, I went and un-checked the “well known browser processes” box, and we’re back to failing to send email.
I thought you were on to something (at least related to why the webshield is preventing email traffic, if the email traffic is on the HTTP port, it would make sense).
Just got another response to my Avast trouble ticket. The suggestion this time is to uninstall Avast (using their uninstaller in Safe mode), then reinstall. I don’t have time to go through all that right now, so, it’ll have to wait for a little bit till I have some time to mess around with it again.
I am no expert but the “web shield” port and email server “port” are not that same thing.
Hopefully Avast Team member will clarify but turning off web shield or disabling port 80 is not a good solution…it opens you up.
Once you have time to do the uninstall, clean re-install perhaps this may work…I doubt it but 100% would try this first.
You can also try Pam’s suggestion of clicking "Settings" → “Active Protection” → “Web Shield” (click the gear symbol on the right) → then while in the Main Settings window put a check mark in the “Scan traffic from well known browser processes only”. Again, not sure how much this opens you up but most definitely less than removing port 80.
Outlook definitely has an issue in current program rev of Avast 9.
yeah…I’ve done the “well known browser processes” check box, and it’s working that way, regardless of which port I tell Outlook to use.
I’m with you on the reinstall…I don’t have a lot of faith in it solving the problem, but, it’s definitely a step to take (especially since Avast Tech support are advising it). If it doesn’t work, hopefully they’ll go to the next step in the problem-solving process. If it does work, well…then, maybe they can fix whatever is changing during the upgrade so future upgraders don’t run into the issue.
Now that I know a bit more (mainly from help here), I agree that removing port 80 in avast! Free under Troubleshooting/web ports is a bad idea. Since the web shield is what seems to be blocking Outlook’s attempts to send email (not the email shield) and when I change Outlook’s outgoing server port FROM 80 back to 25, it then works, I would think it would have to be something related to port 80 and the avast’s web shield configuration. Since port 25 stopped working for me before on my server, it might start suddenly not working again. Avast needs to figure this out.
When I unchecked “well-known browser processes” and change the port back to 25 in Outlook, it works for me (at least for now). I had changed the outgoing email port to 80 in Outlook about six months ago when I couldn’t send mail through Outlook. Working with my host/server, they suggested changing it to one of the other accepted ports, so I chose 80, not knowing it made any difference.
Rob, please post and let us know what happens when you do the reinstall. If I do a reinstall, it’ll probably be back to the previous version of avast! Free ;). At least avast techs have gotten back to you with some suggestions. Not so for me yet.
Oh, Rob, my website host/email etc., is ultimately owned by GoDaddy, even though it has another name. So the same ports are listed for me as outgoing (SMTP) ports as you listed.
Just completed the uninstall/reinstall evolution…and…no difference in operation.
Avast! support recommended using their uninstaller (Avast Clear); and deleting any program files/folders found after that. Then reinstalling the latest version (linked in the email) with default options.
Upon installation, I now have a nifty desktop gadget for Avast that I didn’t have before, but, emails still don’t sent, and still fail with a timeout error. Checking the “well known browser processes” box allows email to be sent per normal.
I’ll respond to my ticket, and see where we go for the next step. Avast! has 20 days till my subscription expires to get this fixed, before I’ll renew my subscription for another year, personally.
I just received a suggestion from avast regarding my ticket.
[i]
"I would recommend you to try the new beta version build.
The new avast! version 2014 R2 BETA1 is currently in Beta testing phase, if you would like to install this version and/or fix any major issue, which is resolved in beta release description, please follow this link."[/i]
A beta version build? What does THAT mean? Isn’t that basically an untested version build? I could end up with more problems than I originally had with this one.
I will say that most of the problems I originally had have resolved. For example, I had no popups or voice regarding virus database updates and some programs I load everyday were being scanned by avast! each time I opened them. These are fixed. But although I have been able to successfully change the Outlook outgoing port to 25 and it works that way for me, it needs to be fixed by avast! to allow the use of 80 when you can’t use anything else.
Rob, I hear you. I’d have to leave too (or go back to an earlier version) if I wasn’t able to change back to port 25. It worked fine for me on version 8 using port 80 for Outlooks outgoing mail, so avast should be able to make it so the current version works as well.
