Skip to main content

Distribution Groups - Automatic Replies from the Group

 Groups - Automatic Replies from the Group

This is not recommended as it'll be a structure mess.

You may want a reply to come from a distribution list - perhaps to acknowledge that the email message has been received. However a distribution list cannot do automatic replies as there is no account or folder for the reply to be attached to within Exchange.
You can get around this by using a public folder. However doing so means that you have to change things around a little.

The public folder is the "list" and the distribution list used to send email to the users is actually hidden.
Create and Configure the Public Folder
First you need to create the public folder that will be the initial recipient of the email messages.

  1. Create a public folder using Outlook with the name that you want for the distribution list. Ensure that it is of type "Mail and Post items".
  2. Go in to Exchange System Manager, Folders, Public Folders and find the folder that you have just created. Right click on it in the LEFT column and choose "Mail Enable".

    For Exchange 2007, you will need to mail enable the folder using Exchange Management Shell:

    enable-mailpublicfolder -identity "\test\moderated folder" - note the \ at the start and that it is the full path to the folder enclosed in quotes.

    To confirm that it was mail enabled correctly, run get-publicfolder -identity "\test\moderated folder" | fl
  3. Wait a moment for Exchange to process the request, then right click on the folder and choose Properties.
    You should now have the additional Exchange tabs.
  4. Click on the tab "email addresses" and check the email address that has been given to the folder is the one that you want email messages sent to. If the email address is already in use by a list, then you will have to remove the email address from that list so that it can be placed on to this public folder.
    You should probably also disable the option. "Automatically update email addresses based on recipient policy".

Create the Distribution List
Next you need to create the distribution list that will actually control the distribution of the email messages.

  1. Create the distribution list in the usual way using ADUC on the Exchange server (Exchange 2003) or Exchange Management Console. Make sure that you give the list an email address so that Exchange can use it. You may not want to add all the users to it at this point until you have tested it.
    You may want to name this folder something similar to the actual list address that you want to use, so that you know what it is being used for. Also make use of the Description and Notes to record its use.
    If you have a list already - then you can adapt that.
  2. Go back to the Public folder properties in ESM (Exchange 2003) or the Public Folder Console (Exchange 2007), click on the tab "Member of" and add the folder to the distribution list.
    (While you can add the public folder using "members" on the Properties of list, in practise it is easier to add the list to the properties of the folder on the "Member of" tab).

Configuring the Response and Email Management
Now that the list and folder are created, now it is time to setup the management of the inbound messages.

  1. Back to Outlook...
    Right click on the public folder and choose Properties. Click on the tab "Administration". On that screen is "Folder Assistant".
    This is where you set the rules.
  2. First rule to set is the auto reply. Use a template etc etc - pretty self explanatory.
  3. Second rule is the forward to send it to the distribution list.
  4. Test by sending an email to the public folder address.

    Now you can secure the folder and list.
  5. On the public folder, in Outlook, click on the tab "permissions" and set the following:
    • Ensure that someone is the folder owner. Use the "Email Admins Group".
    • Set "Default" to none.
    • Leave "Anonymous" as contributor.
    • Finally add the distribution list with suitable permissions - reviewer will be fine.
  6. Back to the distribution list - choose "Exchange Advanced" and hide from the address lists. This means that the public folder is the only thing that shows in the Global Address List.

Net result...

  • auto reply from an email address
  • distribution list for easy management
  • the public folder keeps a copy of every message that is sent to the list
  • being a member of the distribution list lets you in to the public folder
  • however no one can delete items from the list.
  • if you have users who need to review the emails that are sent to that list, but not receive every message (such as a manager) just add them to the public folder permissions - again setting permissions as required.


Popular posts from this blog

Recreating a missing VMFS datastore partition in VMware vSphere 5.x and 6.x

    Symptoms A datastore has become inaccessible. A VMFS partition table is missing.   Purpose The partition table is required only during a rescan. This means that the datastore may become inaccessible on a host during a rescan if the VMFS partition was deleted after the last rescan. The partition table is physically located on the LUN, so all vSphere hosts that have access to this LUN can see the change has taken place. However, only the hosts that do a rescan will be affected.   This article provides information on: Determining whether this is the same problem Resolving the problem   Cause This issue occurs because the VMFS partition can be deleted by deleting the datastore from the vSphere Client. This is prevented by the software, if the datastore is in use. It can also happen if a physical server has access to the LUN on the SAN and does an install, for example.   Resolution To resolve this issue: Run the  partedUtil  command on the host with the issues and verify if your output

ما هى ال FSMO Roles

  بأختصار ال FSMO Roles هى اختصار ل Flexible Single Operation Master و هى عباره عن 5 Roles فى ال Active Directory و هما بينقسموا لقسمين A - Forest Roles 1- Schema Master Role و هى ال Role اللى بتتحكم فى ال schema و بيكون فى Schema Master Role واحد فى ال Forest بيكون موجود على Domain Controller و بيتم التحكم فيها من خلال ال Active Directory Schema Snap in in MMC بس بعد ما يتعمل Schema Register بواسطه الامر التالى من ال Cmd regsvr32 schmmgmt.dll 2-Domin Naming Master و هى ال Role المسئوله عن تسميه ال Domains و بتتأكد ان مفيش 2 Domain ليهم نفس الاسم فى ال Forest و بيتم التحكم فيها من خلال ال Active Directory Domains & Trusts B- Domain Roles 1-PDC Emulator و هى ال Role اللى بتتحكم فى ال Password change فى ال domain و بتتحكم فى ال time synchronization و هى تعتبر المكان الافتراضى لل GPO's و هى تعتبر Domain Role مش زى الاتنين الاولانيين و بيتم التحكم فيها من خلال ال Active directory Users & Computers عن طريق عمل كليك يمين على اسم الدومين و نختار operations master فى تاب ال PDC Emu

Unlock the VMware VM vmdk file

  Unlock the VMware VM vmdk file Kill -9 PID Sometimes a file or set of files in a VMFS become locked and any attempts to edit them or delete will give a device or resource busy error, even though the vm associated with the files is not running. If the vm is running then you would need to stop the vm to manipulate the files. If you know that the vm is stopped then you need to find the ESX server that has the files locked and then stop the process that is locking the file(s). 1. Logon to the ESX host where the VM was last known to be running. 2.  vmkfstools -D /vmfs/volumes/path/to/file  to dump information on the file into /var/log/vmkernel 3.  less /var/log/vmkernel  and scroll to the bottom, you will see output like below: a. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)FS3: 130: <START vmware-16.log> b. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)Lock [type 10c00001 offset 30439424 v 21, hb offset 4154368 c. Nov 29 15:49:17 vm22 vmkernel: gen 664