Overview of Microsoft Outlook Mail Security features

It's unfortunate that malware is delivered by mail. Malicious code that is attached to message information can contain worms or viruses. Once a computer is infected with malicious code, the use of frequent messaging systems will allow malware to spread quickly.

What are we going to do about such a problem? The user proposes more advanced personalization features so that Microsoft will include them in Microsoft Office as part of the system. The first real headache is that the mail virus is created and propagated by using the Office macro language. Recently, a large number of malicious software has shifted the "position", using Microsoft IE browser vulnerabilities to attack.

With Microsoft Outlook and other Office apps in mind, there are plenty of advantages to Microsoft's Windows operating system, but some malicious users use these features incorrectly, without distinguishing them from other techniques.

It is also not a good way to completely reject all scripts and executable forms of operations. The ideal solution is to remind users not to open those suspicious attachments. Let's say that the user will follow the method you have given before, we can understand better.

Even if you still can't rule out the problem, stop the attack. Fortunately, the combination of Microsoft Outlook email security features and the Administrator's ability to comprehend can at least be applied,

A review of Microsoft Outlook Mail Security features

There is often a contradiction between ease of use and security, especially in the description of the security features in the update introduction interface for Microsoft Outlook 98 and Outlook 2000 when it comes to a security update. (Updated features have been created to Outlook2002 and Microsoft Office Outlook 2003)

The purpose of the update is to add features to Outlook to limit the message-carrying malware spread. This must strictly restrict user access to some types of attachments like executable files and VB script files. In addition, when external programs (including from Microsoft itself and Third-party software) attempt to access identified properties and methods, the security update warns Outlook to warn users, which is more influential in some corporate environments than in the case of an add-on security shift. Fortunately, the system administrator is able to personalize the parts that need to be updated through a Microsoft Exchange Server 2003 public folder, and the end-user can personalize the attachments that are stored on the system without the administrator's control.

Five major changes to Microsoft Outlook security

Security update (This is what I'm going to talk about, although it has been included in the current version of Outlook) includes five major changes:

Enhanced attachment security. Outlook is completely disabled for the following file types. Includes:. exe knowable files, PIF program information files, and screensaver files. The system administrator can then specify a different set of file types that are less restricted, so that the files cannot be opened directly, but can be saved to disk.

More control for the user. This user-defined feature allows you to control process access to the Address book, as well as Outlook's send mail functionality.

Support for code and Component Object mode (COM) Add-ins (Add-ins) that are provided for Outlook by the Exchange System administrator should be safe. Note that this feature can only be applied in Outlook 2002 and Outlook 2003 and not in the security update for Outlook 2000 and Outlook 98. These restrictions can only be applied to COM add-ins, not to programs that use the Datagram Delivery application interface (MAPI) or Collaboration Data Objects (CDO).

Security zone changes. You can run a change to the default security zone on Outlook.

Code changes. The encoding of an unpublished or detached Outlook form will not work unless the Exchange system administrator has specified permission.