Skip to main content

Class Question: Can the administrator determine the contents of the “Safe Sender” list?

This answer comes from the Microsoft Supportability e-newsletter: http://blogs.technet.com/asiasupp/default.aspx?p=3

1. Create a share folder on server, say Junk E-mail, and give everyone read permission. Create a text file name SafeSender.txt. Input email addresses into file (one address one line).
2. Install "Microsoft Office 2003 Resource Kit" on the Domain Controller.
3. Start Active Directory Users and Computers (ADUC), Right Click on the OU in which users account is present, Go To "Properties", Click on "Group Policy" tab.
4. Select the Policy in effect, click on "Edit". It will open "Group Policy Object Editor". Right click on "Administrative Templates" under "User Configuration" -> All Tasks -> "Add/Remove Templates" -> Click on "Add" -> Select "Outlk11.ADM" and click "Open" -> Click "Close".
5. Expand "Microsoft Office Outlook 2003" under "Administrative Templates" -> Expand "Tools Options" -> Expand "Preferences" -> Click on "Junk E-mail".
6. In the right pane double click on "Specify path to Safe Senders list".
7. Click on "Enabled" and under "Specify full path and filename to Safe Senders list" type UNC path of SafeSender.txt file (e.g.\\Server\JunkE-mail\SafeSenders.txt).
8. Double Click "Overwrite/Append Junk Email Import List" to configure if you want to keep user's own list.
9. Click on OK. Close "Group Policy Object Editor". Click OK again. Close Active Directory Users and Computers.
10. Log on to client machine and edit the following registry entry:

HKey_Current_User\Software\Microsoft\Office\11.0\Outlook\Options\Mail
DWORD = JunkMailImportLists
Value = 1

Note: This registry key should be deployed to the client machines for successfully deploying the Safe Senders List. We can use Group policy again to deploy this key. The value of this registry key will turn back to zero after Outlook applies the safe sender list from group policy. So if you need to modify the list, please change the value to 1 again.

11. Log off from the client machine and log on again.
12. Launch Outlook. Now you can see the email addresses in the Safe Sender list.

NOTE: The same procedure described above can be used to specify "Safe Recipients" and "Blocked Senders" list.

We also can use the Custom Installation Wizard or the Custom Maintenance Wizard to deploy such lists. Please refer to the following article for more information.

How to use the Custom Installation Wizard or the Custom Maintenance Wizard to customize user profiles to load default junk e-mail filter lists in Outlook 2003
http://support.microsoft.com/?id=927470



Class: Information Worker: Outlook 2007 Power User*
Date: November 12, 2008
Location: Indiana State University
*The Information Worker series is available through LanTech Training in Indianapolis. Please visit their website for more information

Comments

Popular posts from this blog

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...