virus in eml file detect only with manual scan and not real time scan, Why ?

[hellboy755]

dear @harlan4096 

your answer is good

but imagine when you have share folder that all users save their eml file in that folder, when mcafee install, eml file scan and when virus found inside it, clean and delete

but when kaspersky install, can not scan and users can send eml file with virus in it so easy

why ?

this is not good, i want my system resource is used very high, i have not problem with that, but kaspersky scan all file, not selected by itself

my boss like mcafee and i love kaspersky, but in this situation i lose this game because kaspersky not scan all file and my boss winner, WHHHHHHHY ?

this is so bad

[harlan4096]

The file type eml is just an exported content of an email message, usually users don’t export messages and send the eml file, except for specific situations…  anyway as I already said: setting Kaspersky Selective Scan to High Security Level will scan and detect malicious threats inside, if You open it Kaspersky (in Defaults Settings) will detect it, if You try to send it via email again Kaspersky (in Defaults Settings) will detect it and again if You try to send it via a browser, Kaspersky (in Defaults Settings) will detect it… so Kaspersky can detect eml with different layers of protection…

 

Agree that Kaspersky does not scan an eml directly in real-time protection but it is not necessary, since it is not a direct executable type, that eml remains harmless unless You manually open it, and in the other cases if You try to open or send it We know Kaspersky will detect it in Defaults Settings… so as I said, it is enough safe behaviour for me, anyway contact to Kaspersky Support for an extra information :)

[hellboy755]

I am not convinced

so its name must not all files

its name must specific file

[hellboy755]

i send my question to support team

and this is their answer

 

“Thank you for your patience. We have just received a response from our experts. This behavior has been tested, and we registered it as a bug. As soon as we receive a response from our developers, we will notify you. Please wait.”