outgoing emails after 7.0.1456

[jabrocuk]

Hi, since this upgrade (7.0.1456) I am having probs with outgoing emails (smtp) on windows live mail with a pop3 server - webmail is fine, and I can restore function if I disable "scan outbound messages".  Windows live mail reports:-

Subject: 'xxx xxx xxxx'
Server error: 421 Cannot establish SSL with SMTP server xx.xxx.xxx.xx:465,
SSL_connect error 10054
server: 'smtp.xxxxxxx.com'
Windows live Mail Error ID: 0x800CCC67
Protocol: SMTP
Port: 25
Secure (SSL): No

This has definitely occurred since upgrade 7.0.1456, complete system recovery did not cure problem.  Conventional webmail, and sending from Hotmail addresses, (even when using Windows Live Mail) is ok.  Anyone else had this problem? Any ideas?

[DavidR]

Does this account require you connect using SSL ?

[Miss Cellany]

I am experiencing the same problem using Windows Live Mail with my smtpout accounts:

A time-out occurred while communicating with the server.

Subject 'xxxxxxx'
Server: 'smtpout.secureserver.net'
Windows Live Mail Error ID: 0x800CCC19
Protocol: SMTP
Port: 80
Secure(SSL): No

The problem happened after the last software upgrade; all was well before.  I googled Microsoft support which said it's an anti-virus problem.  Does anyone know how to fix?  Can Avast please address this problem?

[Pondus]

check your account settings
is your smtp port 80?..... if so try 25

[Miss Cellany]

That worked, thank you!

[davidzzzz]

Seems to me that no one has answered the original poster's (jabrocuk) question (which is the same as mine).

One poster (DavidR) asked if the email account used SSL even though the original posting clearly indicated "No."

Another poster (Miss Cellany) diverted the thread with a question that included the wrong Port.  That problem was solved, but not the orignal poster's question.

It boggles my mind that there appears to be no solution to such a basic problem.  Is Avast 7.0.1456 not compatable with Outlook 2010 with no SSL encryption?

[Theo Peterbroers]

Hi davidzzzz,

There are three possible setups wrt mail and SSL:
- no SSL encryption: unsecure against man-in-the-middle attack
- SSL encryption and decryption by your mail client: much better, but mailshield cannot look inside encrypted emails
- SSL encryption and decryption by mailshield: secured against mitm attack, mailshield protects against unwanted content. This requires SSL encryption in your mail client to be off.

One may check the 'SSL accounts' in the 'expert settings' of mailshield, to see if mailshield does provide SSL encryption for the mailaccounts that require it. If not: add the account manually.

Best regards,

[DavidR]

Seems to me that no one has answered the original poster's (jabrocuk) question (which is the same as mine).

One poster (DavidR) asked if the email account used SSL even though the original posting clearly indicated "No."

The question for the OP was still valid even if the error mentions SSL = No, if the account required SSL (via avast redirection) then it would fail to connect.

Another part of the eror message indicates that the attempt to connect was using SSL, so one way or another we need to know if it is an SSL requirement or not:

Server error: 421 Cannot establish SSL with SMTP server xx.xxx.xxx.xx:465,

That would then give us another clue where to look - Unfortunately the OP never responded to any of the questions.

Currently I believe there is a problem with the Outlook Plug-in, not working with that build (it is fixed in the current beta testing (RC build), so the Mail Shield is effectively taking over that task.

Now if yours is exactly the same as the OP, if your account doesn't require SSL, then ensure the Mail Shield, Expert Settings, SSL Accounts, account with problem, it should be set with Protocol=SMTP, Port=25 and Encryption=None, see image.

[davidzzzz]

DavidR,

I am totally confused by all this.

1) The instructions at the top of the Avast Mail Shield SSL accounts page clearly indicate that unencrypted accounts (no SSL) don't have to be listed.  Why are you telling me to list them?

2) When Avast is disabled, port 80 as an output port works.  Port 25 does not.

I have tried every combination of settings and nothing works.   You say that you "believe there is a problem with the Outlook Plug-in, not working with that build."  Does that mean that Avast does not work with Outlook 2010 with unencrypted email accounts?

[DavidR]

I'm not telling you to list them but check and see if that account is listed (?), if it is and it is a Non SSL account you have two choices:
1. Delete the entry.
2. ensure that it uses the correct port and doesn't use encryption as per my previous post.

I would go for the second option as there would be no guarantee that the account might be added again, that way the account with correct setting would be present.

Why are you using port 80 as that is an HTML port and not an email port ?

When you use port 80 the Web Shield would try to redirect that and it would be expecting HTML protocol and my guess that is why the connection sails as the web shield would choke in SMTP protocol when expecting HTML.

What is this email account webmail, e.g. Hotmail/Livemail or other account ?

If it is Hotmail/Livemail then it is possible that it is using the Microsoft Proprietary DeltaSync protocol. But I believe it is the above reason SMTP using port 80 being redirected by the Web Shield. This is a best guess as I now nothing about your email account.

[davidzzzz]

The account is a godaddy account.  It's my own domain.

The reason I'm using Port 80 is because, with Avast disabled, port 80 works and port 25 doesn't.  Do you really think that port 25 is going to work with Avast, when it doesn't work without Avast??!!  In any event, I tried changing both the Outlook setting and the Avast setting you recommended to port 25 and it still doesn't work.

Also, port 80 is the port that godaddy says to use.

[DavidR]

Lets put it this way, port 80 won't work as that will be redirected to the web shield not the mail shield and that is essentially going to fail as the web shield can't handle email protocols or make mail connections.

I can't understand why godaddy say that unless it is for their webmail, viewed through a browser, using non-standard ports for email is going to cause problems.

Lets forget that side just for a minute, when you make a connection with port 25 is this the error that you get (from my Reply #7):
Server error: 421 Cannot establish SSL with SMTP server xx.xxx.xxx.xx:465 (where the xxx stuff is your email server address) ?

If so I suspect that there is something else in your Outlook settings for godaddy, and that may be using secure authentication when logging in/on. That would have the effect of forcing avast to try and connect securely, hence the 465 bit at the end of that error message (this is the secure SMTP port).

[davidzzzz]

I repeat - Do you really think that port 25 is going to work with Avast, when it doesn't work without Avast??!!

[DavidR]

Sorry I have given this my best shot, if you don't want to try it I can't do anything else. I have asked questions but don't get answers that just leaves me guessing.

[davidzzzz]

Try what?  I have tried everything you suggested and nothing has worked so far.

I'm telling you that Outlook doesn't work with port 25.  Even with Avast disabeld.  The error I get is that Outlook cannot connect with the SMTP server.  It times out.

Are you suggesting that we can get Outlook working with Avast on Port 25, even when it doesn't work without Avast?  I have repeatedly asked you this question and you have repeatedly not answered it.

It seems to me that we  FIRST need to get Outlook working on port 25 without Avast.  If Outlook doesn't work on Port 25 without Avast, there's no Avast setting that will make it work.