Is EMON necessary for scanning emails in Outlook 2003?

Is EMON necessary for scanning emails in Outlook 2003? Doesn't IMON do the job just as good? I do have both enabled but if IMON is enough maybe I could disable EMON?

 

This is the information from the NOD32 site:

 

Ok, thanks. I do have Outlook 2003 so I guess it's safe to disable EMON.

 

I think so...

Regards

 

The website still shows that but I think that piece of info is outdated. Here is the info on the EMON scanner (and more) included with 2.50. (Hopefully someone from eset can give us the definitive answer.)

 

I wouldn't, I'd leave it there to do its job. If you are not seeing any issues why would you take down a portion of your defences?

Cheers

 

Correct, HAN!

Thanks for the upgrade info...

ESET should take more attention to this things, and have their website always updated correctly...

 

Entered inquiry to Eset based on
http://www.nod32.com/scriptless/products/nt.htm
and got back further below.

When got first email, did come across
http://nod32.com/products/nt.htm
which is different from
http://www.nod32.com/scriptless/products/nt.htm
re EMon and Outlook 2003.

---------------------------------------------------------------




Bill wrote:
Hello Eset Tech Support,


Have not attempted to try, as per

http://www.nod32.com/scriptless/products/nt.htm :


EMON (Email MONitor), a complementary resident module, scans e-mails incoming via MAPI interface. MAPI interface is used e.g. in the following e-mail clients: Microsoft Outlook 95, 97, 2000 (not Outlook Express) in the Corporate mode and in MS Exchange. MS Outlook 2002(Office XP) and Outlook 2003 are not suported in the current version of EMON. MAPI interface is used also when receiving e-mails from the Microsoft Exchange Mail Server via the Exchange protocol.

[Bolding done by me from cut, paste from referred-to Eset, Nod32 webpage.]


So, question:

1. If Windows XP SP2
2. If Microsoft Office Professional 2003
3. If Outlook 2003
4. If current version of Windows XP Nod32

Can I activate and use Emon for IMAP given above 1., 2., 3., 4. conditions?

Here, specifically inquiring about IMAP protocol also, which did not inquire about before (as stated currently not supported anyway).

So now, besides inquiring about statement above, also inquiring about use with IMAP protocol

in Microsoft Office Professional 2003 Outlook using Windows XP SP2.


Much thanks for the info,
Bll

p.s. If can use Emon per above, perhaps referred to webpage needs updating?

-------------------------------------------------------------------------


@bill wrote:

Short description: Emon Outlook 2003

Comment: Is there a timetable for Emon to support Outlook 2003?

If so, when approx.?

Much thanks,
Bill

billaku

Please don't post Eset support emails in public. See the link.

https://www.wilderssecurity.com/showpost.php?p=581616&postcount=3

 

What mode are you using Outlook 2K3 in? With an Exchange Server? Then yes, EMON will do its job because of the MAPI protocol, and IMON won't be used because as far as e-mail clients are concerned, IMON is only checking ports 25 and 110.

IMON is only used in accordance with Outlook for POP3/SMTP Internet mail..such as if you set Outlook up with your ISPs mail servers. In this case, EMON is not being used....it's sniffing a different protocol.

 

Not sure about 'MAPI'. Using an email service that has IMAP on a Cyrus Server. I access by DSL from my stand-alone computer.

Using Outlook 2003 with IMAP SSL Port 993 and SMTP SSL Port 465
is Nod32 doing anything for me as implied it is during the setup
when I chose to activate EMON for Outlook?

Or given my use of Outlook 2003, would it be IMON monitoring the ports 993 (and 465)??

Or neither?


edit: Did just try sending email from one account to another - same email service and:


Sent email
_____________ NOD32 EMON 1.1257 (20051016) information _____________

This message was checked by NOD32 antivirus system
http://www.eset.com


Received email
_____________ NOD32 EMON 1.1257 (20051016) information _____________

This message was checked by NOD32 antivirus system
http://www.eset.com



_____________ NOD32 EMON 1.1257 (20051016) information _____________

This message was checked by NOD32 antivirus system
http://www.eset.com


So, now see the 'NOD32 EMON 1.1257 (20051016) information'


Question answered by trial - just doubtful due to not understanding, still, IMON, EMON, IMAP
- but appears it is EMON with IMAP SSL Port 993, SMTP SSL Port 465, Outlook 2003, Cyrus server, DSL access.

 

IMON does not scan IMAP at all (only POP3 and HTTP). If you want to scan your IMAP e-mail, you need to leave EMON enabled.

Much of the confusion over the term MAPI is Microsoft's fault, in my opinion. Microsoft uses "MAPI" to mean three different things. The definition of MAPI that applies to EMON is this one: http://support.microsoft.com/default.aspx?scid=kb;en-us;200018

MAPI gives EMON the ability to scan within individual e-mail messages, and also to manipulate the messages themselves... delete attachments, delete messages, move messages to other folders. Since EMON can scan the Outlook e-mail messages using MAPI, this means that it does not matter what e-mail protocol is used (POP3, IMAP, Exchange Server...). EMON will scan the e-mail after it has reached Outlook.

In contrast, IMON can scan only the POP3 data stream as it comes in from the internet, before it reaches the e-mail client.

 

EMON scans and catches stuff on my POP accounts. I have IMON turned off for email too.

 

Yeah, http://www.nod32.com/scriptless/products/nt.htm still incorrect re


"... MS Outlook 2002(Office XP) and Outlook 2003 are not suported in the current version of EMON."


As EMON does now support Outlook 2003.