I’m finding it really annyoing now when my friend tries to send me e-mails from CNET.com and these messages are being reported as suspicious…all the time.
What is it about this message that I can’t post that’s suspicious? ???
What she is doing my friend is she’s going to CNET.com to measure her bandwidth, then copying the whole page by selecting the ENTIRE HTML content select, copy and sending it to me VIA e-mail in it’s entire HTML format. paste
LOL, she does this to rub in my face how much FASTER her Rogers Cable is compared to my DSL line. : ;D
When Avast E-mail scanner scans the message…it warns me of it being suspicious. :-\
sighs… Okay… It’s NOT THAT BIG A DEAL guys, I know. But why does avast not like CNET’s ITAG headers in e-mails sent to my POP8 address?
I like how Avast is being EXTRA pre-cautious…but these e-mails hold no threat as they come from CNET.com’s speed testing site.
I deleted the messages…just in case and scanned my system to be sure, and returned NEGATIVE results. I deleted the e-mail too. I know they are not infected with anything.
I don’t even understand what IFRAME TAGs are?
All you need to do to verify the same FALSE ALERT is to go to CNET.com, run a bandwidth test…and when the results page appears… copy, then paste and send the ENTIRE message in it’s true HTML form to somebody who runs Avast4Home with the e-mail scanner.
The suspicious alert will appear.
Is it something that I need to do… or is it something Avast will look into so that the alert does not need to happen?
Just wanted to post my findings on something I have no clue about.
heh! I must admit, I have no idea what IFRAME TAGS are?? :-[
Kindest Regards,
~Steele Wolf~