Deploy Junk E-mail Lists Throughout Your Organization

As we know, we can set Outlook's "Safe Senders list", "Block Senders list" and "Safe Recipients list" to help people protect Spam. However, allowing all users to modify their lists is time-consuming and inconvenient. Now, we can use the following steps to deploy such lists throughout your organization (we will use "Safe Sender list" as example).


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.\ServerJunkE-mailSafeSenders.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:



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


This article also applies to Outlook 2007. We can replace Outlk11.ADM with Outlk12.ADM file from "Microsoft Office 2007 Resource Kit".

Comments (17)

  1. Anonymous says:

    Great post, explained really well and I could really understand. Thank you.

  2. Ryan Sadler says:


    If i apply the above solution to all workstations/laptops across the network will end users lose the current entries they have for their Safe Senders, or will the above simply append what is already in place client-side?



  3. Peter Todd says:

    You can specify whether to append or overwrite the safe senders file.

  4. Hugh says:

    Also note is that while Microsoft says the relevant key (JunkMailImportLists) is changed from 1 to 0 by Outlook after import, this does not appear to be true with Outlook 2003 SP2.  It appears to stick at 1, so that effectively it is a mandatory append (provided you specify append).  This should not be a problem as long as your Safe Senders file is on a DFS share (replicated and local to each office) and the file contains only a few entries.  A large file accessed over a WAN link may cause negative performance for Outlook however.

  5. Егорка says:

    Хм… Мне кажется, минусы значительно превосходят плюсы. Думаю, не стоит заморачиваться.

  6. Schindler says:

    How should a large file cause negative performance for Outlook. The file is applied by the group policies – not Outlook…


  7. Tony says:

    <a href=""”>" ></a> [url=][/url] <a href=  ></a>  

  8. Mercedes says:

    <a href=""”>" ></a> [url=][/url] <a href=  ></a>  

  9. thevicmayster says:

    We have tested this on a couple of users and the JunkMailImportLists key does not change from 1 to zero when Outlook is launched. It stays set to 1.

    The email addresses do not appear on the Safe Senders List.

    We have manually run gpupdate, logged off and logged back on, and even rebooted several times.

    We get the same results for both Outlook 2003 and Outlook 2007.

  10. CraigB says:

    What’s the point of using a GPO to avoid sending registry hacks, when you have to do a registry hack to allow the GPO to do what it’s supposed to do anyway?

    I think I’m just going to send an "all users", tell them about the import button, tell them where the list is, and if they care enough to procede all well and good, if not it’s their own problem.

  11. мaлышyля says:

    Спасибо вам огромное за инфу, почитал с интересом

  12. CYStemAdmeen says:

    We have the same problem with thevicmayster’s.

    Outlook 2003 resets the value of JunkMailImportLists to zero. Although our Office 2003 is already in Service Pack 3.

  13. Rob Dunn says:

    Why did I just get a 'Hello World!' script popup when I browsed to this page…?

  14. Dee Ramon says:

    We did this and it works great, however we did notice the registy setting for always trust emails from contacts was also set  – JunkMailTrustContacts  has anyone seen that?

  15. Toly says:

    Microsoft posted an adm file to deploy "JunkMailImportLists" registry key for Outlook 11,12,14 at…/2252421

  16. ladrick says:


    Great post – easy to follow however rather than add a list of addresses is it possible to add an entire domain; in my case my local domain (i.e. We use a software package that emails the users from their own email address… having to maintain a safesenders.txt containing all staff local addresses would be a big pain..


Skip to main content