Avast checks one outgoing email but not another

[glnz]

My outgoing email on verizon.net is checked by Avast.  The recipient sees the "Virus-free" logo at the bottom.
 
But it seems my outgoing email on a different email domain hosted on Network Solutions is NOT checked by Avast - there is no "Virus-free" logo at the bottom.

The good verizon.net email requires an SSL connection for the incoming (POP3) and outgoing (SMTP) and uses incoming port 995 and outgoing port 465.

The bad Network Solutions email does NOT require an SSL connection, it is also POP3 and SMTP, and it uses incoming port 110 and outgoing port 2525.

Attached is a jpg showing my Avast Redirect settings.  It shows secure ports 995 for POP and 465 for SMTP, so the verizon.net email is good.

Avast Redirect shows (unsecure) ports 110 for POP and 25,587 for SMTP, so I am missing 2525 for the Network Solutions outgoing.

HOWEVER, when I added ,2525 to SMTP a month ago, my email stopped working correctly - I was not connecting correctly to email servers.

My email app is Outlook Express 6 on Win XP SP3 (still getting updates through the POS hack).

What do you think?  Why does adding ,2525 cause problems?  And if I could add it, would it cause Avast to start checking outgoing emails on the Network Solutions-hosted domain?

Thanks.

[Pondus]

But it seems my outgoing email on a different email domain hosted on Network Solutions is NOT checked by Avast - there is no "Virus-free" logo at the bottom.

It could be that avast check but dont add the message?


This may work to find out: 
Right click avast tray icon and pause avast shields, then download a Eicar test file  http://www.eicar.org/85-0-Download.html
create a mail and add the file as attachment, turn on avast shields ... wait a minute to be sure all is started .... now send mail, any detection?

you may try this with both mail accounts

[glnz]

Pondus - thanks for suggestion.  I ran your test a few times, and it PROVES that Avast does NOT scan my outgoing email via my second email account through Network Solutions.  (It DOES scan outgoing through my verizon.net email account and stopped the outgoing email.)

So the problem persists.  HOW DO I GET AVAST TO SCAN MY NON-SSL OUTGOING EMAIL THROUGH MY NETWORK SOLUTIONS EMAIL ACCOUNT?

[Pondus]

even if avast dont scan your mail accounts are most likely protected as most mail providers have spam/virus filter on the mail server

The mail you where able to send out, did it arrive at the reciveing end with attachment or was it stopped on the way?

you can test mail security here:
http://www.aleph-tec.com/eicar/
http://www.emailsecuritycheck.net/


Maybe somone form avast will reply here with info about your issue

[glnz]

Pondus - again you are right.  My tests per your suggestion also show that the two email providers did NOT on send the "infected" email to their destinations (me).

However, Avast needs to fix or explain.  Avast is promising to scan outgoing email and is failing.  And my UNscanned outgoing emails are the easier of the email accounts two because it is NOT connected with SSL.

AVAST - please read my first post and advise. 

[DavidR]

First finding any help setup info on Network Solutions is terrible, finding a needle in a haystack could well be easier. I found this - http://www.networksolutions.com/support/pop-imap-settings/

The standard port for SMTP is 25, not 2525 (not sure if that has an impact), but it also mentions that you can use port 587 instead of port 2525 for the Outgoing Server Port = 2525 or 587. I would give 587 a try and see if that works.

[glnz]

DavidR - Agree with you re Network Solutions.

However, we switched outgoing to 2525 some time ago at Network Solutions' own request.

The issue remains - why won't Avast permit me to add ,2525 and then scan?

[Eddy]

If Network Solutions support port 25, give that a try and see if it makes a difference.

[glnz]

DavidR and Eddy - in my OE6, in the Account settings for the Network Solutions email, I just switched the SMTP port from 2525 to 587, and Avast now scanned my first outgoing email correctly.

But I have reason to believe this will cause a problem after a while -- Network Solutions asked us to move to 2525 some time ago.  The issue remains why Avast won't accept ,2525 as noted in my first post above.

Thanks.

[Pondus]

Port 25  >>  The Spam Superhighway  >>  http://www.slate.com/articles/news_and_politics/explainer/2008/07/the_spam_superhighway.html

[Eddy]

Time for avast to explain if port 2525 is scanned or not.

[Pondus]

In Network Solutions guide here they say 2525 or 587 so i would try 587
http://www.networksolutions.com/support/step-by-step-pop-setup-instructions/

[DavidR]

In Network Solutions guide here they say 2525 or 587 so i would try 587
http://www.networksolutions.com/support/step-by-step-pop-setup-instructions/

Yes, same information, but a different location to the one I found.

Network Solutions, make it sort of clear that if your ISP needs to use 587 then OK.

@ glnz
Given what Network Solutions say about changing to 587 if required and 587 is an email port that avast definitely monitors/redirects I don't believe it should be an issue in the medium term. I would have thought if there would be an issue it really should have failed right off.

[bob3160]

587 - 2525
One works the other doesn't. Seems like a simple choice to me.

[glnz]

DavidR and Bob - As I wrote a little earlier today, I have now switched my Network Solutions NON-SSL outgoing SMTP from 2525 to 587.

But, once again, Avast promises certain features and doesn't deliver (although it certainly delivers endless popups and installations we don't want).  Avast is unable to scan 2525, which port was previously directed by Network Solutions.  Why not?