Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: AlexFeren on February 27, 2009, 01:59:40 PM

Title: non-english (Japanese) email subject causes Virus warning
Post by: AlexFeren on February 27, 2009, 01:59:40 PM
Hello,
using Home v4.8.
When wife sends/receives email with non-english (Japanese) subject (email's body's irrelevant, and no attachments) she gets a warning that there's a possibility of virus.
Is this a known fault? (I can't find any mention of this in Knowledge Base.)
Alex
Title: Re: non-english (Japanese) email subject causes Virus warning
Post by: igor on February 27, 2009, 05:08:19 PM
Any particular subject, or it doesn't matter?
What exactly does the warning say?
Title: Re: non-english (Japanese) email subject causes Virus warning
Post by: AlexFeren on March 01, 2009, 09:18:17 AM
Igor,
thanks for asking. Attached is the warning (minus identify of Sender). Forgot to mention, we're talking about Outlook 2007 using Hotmail account.
Alex
Title: Re: non-english (Japanese) email subject causes Virus warning
Post by: Iso-G on March 01, 2009, 04:05:04 PM
There is no problem with Japanese emails, though I have used avast! 4 since 2003.
Quote
Attached is the warning
Dose the subject include sequence whitespaces ?
I hope the explanation of "Heuristic Page" in the avast's help.chm helps you.
Title: Re: non-english (Japanese) email subject causes Virus warning
Post by: AlexFeren on March 02, 2009, 11:15:00 AM
Dose the subject include sequence whitespaces ?
I hope the explanation of "Heuristic Page" in the avast's help.chm helps you.
The title includes all Japanese characters. Obviously it seems Avast can't handle the Japanese character-set and and interprets these characters in Subject as suspicious.
As per original post, the above warning appears on all emails with Subject in Japanese.
Title: Re: non-english (Japanese) email subject causes Virus warning
Post by: RejZoR on March 02, 2009, 12:28:25 PM
Looks like Internet mail provider isn't UNICODE and treats so many ???? as possibly malicious mail. Could be something else though...
Title: Re: non-english (Japanese) email subject causes Virus warning
Post by: Lisandro on March 02, 2009, 01:39:42 PM
Obviously it seems Avast can't handle the Japanese character-set and and interprets these characters in Subject as suspicious.
I don't think so. If this is the case, we won't have Japanese users, Arabian ones, etc.
The character set is not the problem.
Anyway, you can change heuristic options in the email providers to relax the detection.
Title: Re: non-english (Japanese) email subject causes Virus warning
Post by: igor on March 03, 2009, 02:23:19 PM
What have you set in Control Panel / Regional and Language Options / Advanced / Language for non-Unicode programs?
If there isn't Japanese there, does it help if you set so?
Title: Re: non-english (Japanese) email subject causes Virus warning
Post by: AlexFeren on March 04, 2009, 02:37:29 PM
Email provider is Hotmail and it certainly does handle Japanese (both Subject and content). Email client is Outlook 2007 and it definately does handle Japanese (both Subject and content).
Wife's account is set (Region) for both English and Japanese via Vista's IME (ie. language toolbar).
There shouldn't be a need for me to relax any kind of security feature, quite the opposite, I want all the protection Avast can provide.
Obviously Avast's Outlook plugin has a problem with Japanese character set, non-English HTTP email (as provided by Hotmail), or both.
Title: Re: non-english (Japanese) email subject causes Virus warning
Post by: igor on March 04, 2009, 02:51:38 PM
What have you set in Control Panel / Regional and Language Options / Advanced / Language for non-Unicode programs?
If there isn't Japanese there, does it help if you set so?
Title: Re: non-english (Japanese) email subject causes Virus warning
Post by: AlexFeren on March 04, 2009, 03:04:14 PM
What have you set in Control Panel / Regional and Language Options / Advanced / Language for non-Unicode programs?
If there isn't Japanese there, does it help if you set so?
Control Panel / Regional and Language Options / Administrative / Language for non-Unicode programs is set to English which is what most of us would set it to for programs that don't support Unicode.

Did additional testing. If there's at least one English character (I tested at beginning and then at end) in the Subject, the Avast's Outlook plugin doesn't produce the warning. Further evidence that Avast doesn't understand Japanese Subjects.
Title: Re: non-english (Japanese) email subject causes Virus warning
Post by: igor on March 04, 2009, 03:06:57 PM
If the language for non-Unicode programs is set to English, then of course it doesn't understand the characters (being an Ansi program at the moment) - all characters get converted to question marks by the system.

Which, however, doesn't explain why it should consider the subject suspicious...
Title: Re: non-english (Japanese) email subject causes Virus warning
Post by: AlexFeren on March 04, 2009, 03:11:05 PM
If the language for non-Unicode programs is set to English, then of course it doesn't understand the characters (being an Ansi program at the moment) - all characters get converted to question marks by the system.
That Windows' setting is specifically for non-Unicode programs. I have looked at Avast's manual and it doesn't mention Unicode. However, given that Avast is distributed for customers around the world and given that it's a modern program, I assumed it was. So, it's not? Rather disappointing.
Title: Re: non-english (Japanese) email subject causes Virus warning
Post by: igor on March 04, 2009, 03:20:45 PM
Some of its parts (drivers and the surrounding areas) are, some parts (most of the GUI) are not. So, it basically requires having the "correct" language (for non-Unicode programs) set, if everything should work 100%.
Of course, that's a problem if you work with multiple languages (with different encodings), or if there are multiple users on the computer, each using a different language.

Seing the code for the subject check, I can understand the problem... however, it's not clear what to do about it. The subject check may have some sense a couple of years ago, but it's mostly useless today - so the best thing to do is to remove this check/option alltogether, which will most likely happen in avast! 5.0 (even though it will be fully Unicode).
You can safely disable the "Subject structure check" on the customization page of e-mail heuristics, you really won't miss anything.
Title: Re: non-english (Japanese) email subject causes Virus warning
Post by: AlexFeren on March 04, 2009, 03:22:47 PM
Igor. Thanks. /Alex
Title: Re: non-english (Japanese) email subject causes Virus warning
Post by: byronomo on February 17, 2010, 02:58:48 AM
I'm having the same problem (e-mails from wife and others have Japanese subject line) but my "check subject" box is unchecked.  I am using Avast 4.8 home edition. 

Is there any solution for this problem?

Title: Re: non-english (Japanese) email subject causes Virus warning
Post by: byronomo on March 05, 2010, 06:17:46 PM
Can someone please, please offer a solution for this??

Title: Re: non-english (Japanese) email subject causes Virus warning
Post by: byronomo on March 13, 2010, 10:39:51 PM
Are there any moderators or Avast programmers that are aware of this issue?
Title: Re: non-english (Japanese) email subject causes Virus warning
Post by: byronomo on March 16, 2010, 11:22:55 PM
Funny how people posting in Chinese get more responses than I can by posting in English....strange, no?

Title: Re: non-english (Japanese) email subject causes Virus warning
Post by: igor on March 17, 2010, 12:23:11 AM
I'm not aware of such issue.
In any case, I don't think it's very likely that there will be another avast! 4.x program update within the next few months - so I'd suggest to update to avast! 5.0 first, and see if the problem is still present.
Title: Re: non-english (Japanese) email subject causes Virus warning
Post by: byronomo on April 05, 2010, 10:50:43 AM
Thank you very much for your response. Upgrading to version 5 has fixed this problem.