I recently switched both my home machines and my business machines over to Avast. While very happy with the product, I noticed that the “Avast email signature” was not being added to out going emails using M365/Exchange or IMAP accounts with non-standard IMAP/SMTP ports. One might ask why I care about the signature… well I don’t really but it sparked my interest. I found that the signature was being added for IMAP/SMTP accounts that use standard ports but was not for those accounts using non-standard.
After a bit of investigation, I realized that it’s very likely none of my business emails are being checked by Avast and the same for my personal accounts which use special ports.
It would be great if I could customize the ports Avast Core Shield/Email scanner checks in order to achieve full functionality for email accounts on non-standard ports.
Well, now I’m even more confused. It does look like the right ports are already there. So what I can’t figure out is why the signature doesn’t automatically append on some accounts but does on others. Is there an answer for that somewhere that I have not found?
Unfortunately I don’t use Outlook nor Office 365 for my e-mail so I can’t test it for myself.
According to Google, Outlook / Microsoft 365 combination may use MAPI for communication instead of IMAP/POP3/SMTP.
And I’m not sure Mail shield supports MAPI in this case.
If you can see e-mail header sent/received from/to your client, it should have strings like these when scanned.
Do you have the latest AV 20.10 installed?
Could you please clarify for which email provider it works/not work?
What ports are you using?
Are all emails are sent via Outlook Microsoft 365 standalone email client or via webmail?
The account which the Avast signature is not being applied to is a business email. We use Microsoft/Office 365 and the outlook desktop application. The ports are default – we have not changed them. All emails are sent through the Outlook application installed on the PCs.
I do see the AV header is added to emails but the avast signature is not appended to outgoing messages.
I have also now just confirmed the same happens for @outlook.com for mail sent via the Outlook desktop application. It still looks like the headers are being added to outgoing/incoming messages but the Avast signature is not added to outgoing emails.
Yes, I am sure that our business accounts are setup as Exchange accounts through Microsoft 365. As for the @outlook.com account, I do believe that it is also an exchange account. However, when I checked via another email application (Thunderbird), the ports were 993 and 587. Both of which are already setup in Avast – but still no outbound signature.
Your screenshot is from Avast Free and the one in the article is from Avast Premium Security. They are slightly different but the repair button is still there for both. I can ask the team to look into. Thank you
but it sparked my interest. I found that the signature was being added for IMAP/SMTP accounts that use standard ports but was not for those accounts using non-standard.
