Outlook and Nod32

[Antarctica]

I am using Outlook Express, without any problems I have to say. Yet I am getting this annoying message evry time I am making a scan with NOD.

"Either there is no default mail client or the current mail client cannot fulfill the message request. Please run Microsoft Outlook and set it as the default mail client"

I don't want to have Outlook as my default mail client! Is there anything to do to fix that?

Thank you.

This is from the FAQ's.............guess they forgot to put in this feature for the "upcoming major environment release". If it's there, I don't know where it's at.......
----------------------------------------------------

Suggested solutions:

If you are using Microsoft Outlook for receiving emails and it is not set up as default mail client, You can set it up as default mail client in this way:
In the Internet Explorer>Tools>Internet Options>Programs>E-mail - change to Microsoft Outlook (if applicable).
If you have Microsoft Outlook installed and don't use it:
Consider uninstalling Microsoft Outlook.
In the upcoming major environment release, NOD32 will have a checkbox that will prevent it from accessing MAPI32.DLL.

[Antarctica]

Thank yo GuruGuy for the answer, it's appreciate.

[anders]

If you disable "Use MAPI interface" in the settings for the scanner, that prompt shouldn't appear.

Best regards,
Anders

[Antarctica]

That's solved my problem anders. Thank you so much, I am quite
happy!

[Blackspear]

Anders/Jan Does this have any other effect on Nod (unticking "Use MAPI Interface") and if not, why is it a default setting?

Cheers

[Marcos]

As the only result of unticking this option, MAPI32.dll will not be loaded at NOD32 Scanner startup so your Personal folders (pst files) cannot be scanned.

[anders]

If you have a MAPI-client (Outlook) using the MAPI-interface will provide scanning of the mail databases. Of course, you are always protected by Amon, but it's "nice" to scan the Outlook databases, and not only scan incoming mail, or attachments that are executed.

If you get the warning message (I think it appears when Outlook is installed, but not the default mail client), just unselect that option.

For people that use Outlook as their default mail client, it provides an "extra scanning feature".. For people that doesn't have Outlook installed, it does nothing.. and if you have Outlook installed, but not as your default mail client, you might get the warning.

I don't think that THAT many have Outlook installed, but "not using it" (as default), so.. I think it's a good default setting. If you have it installed, but not using it.. why not uninstall it?

Best regards,
Anders

Anders,

The MAPI setting makes the Outlook Inbox and Personal Folders available as scanning targets inside the scanner, but I couldn't find any setting or combination of settings that allowed for "internal" scanning of Outlook *.pst (database) files that aren't connected to Outlook as the current Inbox (for example an old *.pst file or a *.pst file from another PC stored on disk).

Paolo seemed to "confirm" that NOD32 could not scan inside *.pst files not connected to Outlook as the Inbox (see thread on the "Shell Power For NOD 2.0" for more details of our exchange).

While I couldn't get *.pst files to be internally scanned, I could scan Outlook Express files (*.dbx) internally just as a *.zip file would be.

Is this correct and was there any intention for being able to scan *.pst files internally if not currently connected to Outlook as the Inbox?

Thank you.

[anders]

[citat]Is this correct and was there any intention for being able to scan *.pst files internally if not currently connected to Outlook as the Inbox?[/citat]

As far as I know there has been no such intention, and I do not know if Eset plans to implement it. Personally, I don't think it's that important.

For Esets view/comments, ask Jan (PM him to get his attention or something

Best regards,
Anders

[jan]

Hi,

>Paolo seemed to "confirm" that NOD32 could not scan inside *.pst files not connected to Outlook as the Inbox

This is correct.

Rgds.,

jan