Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: davidzzzz on August 21, 2012, 02:44:23 AM

Title: Outlook Won't Send Email After Avast 7.0.1456 Install
Post by: davidzzzz on August 21, 2012, 02:44:23 AM

I'm running Outlook 2010 and Windows 7.  Everything was working fine until I installed Avast 7.0.1456.

I have an email account that uses SSL encryption (yahoo) and another that uses no encryption (godaddy).

The yahoo account receives and sends OK.  The godaddy account receives OK, but doesn't send.

If I disable Avast, everything works fine including the godaddy send.  But when I enable Avast the godaddy account send doesn't work.  The email just sits in the Outbox and Outlook repeatedly tries to send it unsucessfully.

I googled it read everything I could find including changing the Avast mail settings, but no combination I tried seems to work.

Any help would be greatly appreciated.

Title: Re: Outlook Won't Send Email After Avast 7.0.14 Install
Post by: Theo Peterbroers on August 21, 2012, 05:33:16 AM

I see you also posted in another thread.

Most likely, avast mailshield encrypts your outgoing godaddy emails, which it shouldn't do. If so, you can remove your godaddy account from the 'SSL accounts' in 'Expert settings' of mailshield.

Best regards,

Title: Re: Outlook Won't Send Email After Avast 7.0.14 Install
Post by: davidzzzz on August 21, 2012, 01:48:16 PM

Kwartet,

I tried that.  Doesn't fix the problem.

Title: Re: Outlook Won't Send Email After Avast 7.0.14 Install
Post by: avast@@dvantage77.com on August 23, 2012, 12:51:12 AM

What ports are you using?  There was an issue I remember with godaddy that their default port had issues, but other alternate ports worked.

Title: Re: Outlook Won't Send Email After Avast 7.0.14 Install
Post by: davidzzzz on August 23, 2012, 02:21:35 AM

Quote from: avast@ advantage77.com on August 23, 2012, 12:51:12 AM

What ports are you using?  There was an issue I remember with godaddy that their default port had issues, but other alternate ports worked.

Yes, that's correct.  When you go to the godaddy website, there's a document that directs you to use port 80 for outgoing messages and 110 for incoming messages both with no SSL encryption.  But I did some more research and found another godaddy document that has other port options including the standard SSL ports (incoming 995 and outgoing 465).  When I used these ports with SSL incryption, it now works.