Mostly just got looking for assurance rather than a problem fix.
I recently signed up for a new e-mail mail account which I read through Thunderbird. I had to change to port 587 in order to send mail.
Avast! scans my incoming mail on port 110.
I have done a search and I understand that avast! will not check mail sent through port 587. I also understand that I can download Stunnel to work around this issue but I have decided not to.
My question is mostly about the port 587 itself. Since avast! is not scanning it, can I be confident in using this port to send my mail? And also, I trust that Standard Shield would pick up any problems with mail sent through this port?
Port 587 is generally used for secure email SMTP connections (SSL/TLS) and the only thing that it would protect is your privacy. avast! doesn’t scan it because it can’t it is encrypted and that is the whole idea of secure email to stop nosey people and programs peeking into it.
So you need the third party application to act as an interface to allow avast to scan it before it is encrypted and sent. However, if you ensure any attachments, etc. that you are going to send are clean then not scanning outbound email using port 587 shouldn’t be a problem.
Just leave the avast outbound scan enabled it will ignore the 587 port and monitor port 25 in case something else might try to send spam/infected emails if for some reason you picked up a trojan mass e-mailer.
