Avast Email Alerts via SSL/TLS on 587

I found the thread on setting up email alerts. Very straightforward.

Now I need to expand that to allow me to send an alert to port 587 over SSL/TLS.

In the admin section for email configuration, I see where I can set ‘Encrypted’ to True. I’m looking for the same feature in the ‘Group-Expert settings’ config.

The reason for this: when my users roam out of the network, I still want them to send in alerts of virus detection. Most ISP block port 25. Thus I need to use 587 to get around that issue as well as forcing encrypted transmission (just in case they are on public wifi).

Along with these settings:
avastcfg://avast5/Common/NetAlert SMTP:yourname@domain.com
avastcfg://avast5/Communication/SMTPFrom from_address@domain.com
avastcfg://avast5/Communication/SMTPPort 587
avastcfg://avast5/Communication/SMTPServer yoursmtpserver.domain.com

I am trying to use
avastcfg://avast5/Communication/SMTPUserName
avastcfg://avast5/Communication/SMTPUserPassword
avastcfg://avast5/Communication/SMTPAuth Tried 1,2,3 hoping one of these would be for encryption)

I have yet to get this working… Anyone else have success?

avastcfg://avast5/Communication/SMTPAuth 1=on, 0=off

most tricky will be the
avastcfg://avast5/Communication/SMTPUserPassword

I’d recomend to “set up” it in an avast client manually then open avast5.ini and copy the password fro [Communication] section

Can you elaborate on why the password is ‘tricky’? Is it hashed or something? I would have assumed that since this field can be edited by an admin, the admin would just provide the password for the account… no?

Checking a wireshark trace on the client after EICAR was detected shows the attempt to send mail, however, the server responds with ‘client not authenticated’.

Also, I have no avast5.ini on my client systems. I don’t see where this could be set manually anyway. Could you provide a walkthrough.

While using the name and password method on port 587, I discovered that doing an AVAST ‘repair’ solved all my e-mail alert issues. I can offer no explanation as to why, but now it works the way I expected it to work in the first place. Both the AVAST test as well as an EICAR virus test work fine.