After recent avast updates Threatfire has began to flag the email scanner as potentially malicious when I send an email. I am not sure who’s end the fix needs to come from Avast or TF but I thought I would bring it to your attention and see if anyone else is having the problem.
Have you changed TF from the default sensitivity (i.e. 3) ?
Just tried it myself on Vista Home Basic. avast! 4.8.1129, TF set to default. No problems with either Windows Mail (IMAP) or Thunderbird (POP3). Latest iAVS (080729-0) may have solved the problem.
Don’t you mean version 4.8.1229 ?
Yes, 4.8.1229. Thank-you David.
Yes, Threatfire was (and is) set to the default protection level of 3, no changes there. The only thing that had changed (that I am aware of) that started TF flagging Avast’s email scanner was that I had updated Avast.
Today I applied the latest Avast iAVS update (080730-0) and TF still flags the Avast email scanner on my machines which run XP home. For now I have just allowed the process in TF and told it to remember my answer. It doesn’t really solve the root of the problem but it will get me by until either Avast or TF figures out whats going on.
I would say that maybe it could be some glitch on my system except that it does it on both of my computers and on my father’s computers as well.
You have to be aware that after program updates components change and as such would be challenged, so you have to recognise this is normal and allow the changes after a program update.
The same will be true of other programs (after an update) that have an internet interaction or security purpose.
the iAVS updates don’t change the program components only the signature file, so that shouldn’t trigger any fresh threatfire alert.
You say “It doesn’t really solve the root of the problem but it will get me by until either Avast or TF figures out whats going on.” if as I explained a) program changes are likely to be challenged as what threatfire had previously allowed changed and b) after allowing the changed process and remembering the answer there are no further pop-up alerts, then that is as it should be.
So are you saying even after allowing and checking remember my answer the pop-up alerts continue ?
If so that is most certainly a threatfire issue as avast hasn’t changed since the program update that sparked the TF alert.
Or what do you consider the root of the problem is ?
I have updated other applications and Avast previously and it never caused TF to alert due to the changes. On my father’s system he had not updated avast (program) but after doing an iAVS update TF began flagging the email scanner.So to me the problem was that TF didn’t used to alert on avast and now it does. So what changed…I don’t know. It’s no big deal I guess, I was just curious if anyone else was having the same issue and if so knew what had caused it. Oh and no, I do not get the alerts anymore after setting TF to allow and remember.
I think avast and TF are both great products and I appreciate the work personnel from both do.
Thanks for your help.
OK, after applying the latest signature update for Avast and the database update for TF after I arrived home today, I was still having TF flag the Avast scanner. I had not rebooted after the updates at the time as neither program asked for one.
Anyway, I decided to remove the always allow setting in TF that I had set up for the Avast scanner and tried rebooting. Now TF is no longer flagging Avast’s scanner. Very strange stuff, I don’t get it, but hey the two back working as usual alongside each other now.
Thanks again for your consideration of my problem.
Very strange indeed and most certainly a TF issue as essentially even with updates, the Internet Mail (ashMaiSv.exe) functionality (how it intercepts and scans email and sends it on its way) hasn’t changed.