Skip to main content

Whaddya know how to create a Mailing Distribution List in MS Exchange Server 2007?

Ok you're the Network Administrator in your company and they had asked you to create a Mailing Distribution List. For example a mailing list for your HelpDesk support, let's call it as HelpDesk @ Well, as Network Administrator/Email Administrator you suppose to know it. This is just another technical how to references to guide other Network or Email Administrator out there.

In this example, we are using MS Exchange Server 2007. I need to point this out because the management console is different between MS Exchange Server 2003 and 2007.

Ok, let's begin. Fire up (I mean double click on)  your Exchange Management Console.
  • In Recipient Configuration, select Distribution Group.
  • Right click on Distribution Group to create New Distribution Group.
  • Select New Group, click Next
  • Select Group Type as Distribution
  • Type the Name and Alias e.g. HelpDesk, click Next to complete.
  • Add the user(s) to be member of this distribution list
  • Send a test message and you're done.
Well not yet! By default, MS Exchange Server 2007 policy is requiring that all senders are authenticated. In this case, when someone from outside send you a message. They will receive an email from the Postmaster regarding undeliverable due to Exchange policy.

But if you're senders are all within your organization. It is safe (highly recommended) to requires all senders are authenticated.

How do you disable "Requires that all senders are authenticated" for this specific Mailing Distribution List?

Let's go back to the Exchange Management Console, select the Distribution Group e.g. HelpDesk, click on Properties.
  • In HelpDesk properties, click on Mail Flow Settings tab.
  • Select Message Delivery Restrictions, then click Properties
  • In Message Delivery Restrictions, uncheck "Requires that all senders are authenticated".
  • Click OK to apply your changes.
Now test sending email to your HelpDesk distribution list from your outside email such as Gmail, MSN or Yahoo. This should work now.

SECURITY REMINDER: When you disabled "Requires that all senders are authenticated" you will receive email from outside of your company including unsolicited emails or SPAM. This is only applicable if you have a number of consultants working for your company. 

As IT Security person, I don't recommend disabling this feature. I want all exchange users to properly authenticated before they can use the service. As always, consider other best alternative.

Share your thought, post your comments or join me at community.


Popular posts from this blog

Alternative Social Networks

If you are planning to create your social network e.g. similar to Facebook. Here's a short list of alternative software's:

Open Source and Free​ - Wordpress (Open Source and Free) - (Open Source and Free)Commercial Social Networks software ($299 Stand Alone, $29/mo Cloud) (run with Joomla, need to know CMS) (very expensive, $399 for Standard) (from free to Commercial, I left my networks and they are selling it (I used this before, it's hard to maintain. I moved to NING but left too after it was sold to another company) (I don't recommend using this service, it's hard to export your data when it's time to move)Something to check when selecting your next soc…

Example of Out of Office Reply for Terminated Employee

This is a sample message that I used for terminated employees, unless HR staff specified a different message.
=== Example for KING.NET Employee === John Doe (employee or consultant) is no longer with KING.NET effective June 1, 2008 (termination date). For matters relating to "Project Name here" please direct your concerns to John Smith at (Manager or Supervisor). For all other matters, please direct your email to Mary Smith HR at
Please call our main office 703-345-6789 if you have other concerns.
Thank you.
=== end of message ===

Frequent Account Lockout in Active Directory

I have a user in Windows Pro 7, and Windows Server 2003 environment that is frequently account locked out. I tried many different scenarios to resolve this account lockout issue, from resetting his password, changing a new password, remove and re-join the domain, rebooting the workstation and active directory servers.

I tried to use the command prompt utility to run "rundll32.exe keymgrdll, KRShowKeyMgr" (case sensitive) to delete the account in Windows 7 password cache, and still no luck.

Still searching for answer ... Let me know if you encounter a similar issue in Windows Pro 7 and Windows Server 2003.

Continue reading updated post here: