The third and final component of the patch is a configuration change to Outlook's Security Zone settings. As Tom explains in Part 1 of his series, Microsoft's recent Outlook security update, designed to limit the damage caused by the recent rash of worm viruses, was controversial before it hit the streets. Those who worked with the pre-release code complained that the patch broke more than it fixed and its implementation was a disaster. In Part 4, Tom gives you some valuable recommendations. Worm viruses replicate by accessing elements of Outlook's Object Model, which in simple terms is a hierarchical structure of functions that one program can use to accomplish some action within another.
Recent permutations are deadlier still.
They email themselves to all contacts in the user's Address Book and busily start destroying local system files. This process has the potential to repeat itself on the system of each contact foolish enough to open the same infected file. If any such access is detected, a warning dialog appears as shown in Figure 1. In other words, if you bought Office for its seamless integration with sibling components, you are in for some surprises. Others report being prompted with the dialog shown in Figure 1 for every merge record.