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.

Scenario
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.

Comments

Popular posts from this blog

Integration with vCloud Director failing after NSXT upgrade to 4.1.2.0 certificate expired

  Issue Clarification: after upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Issue Verification: after Upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Root Cause Identification: >>we confirmed the issue to be related to the below KB NSX alarms indicating certificates have expired or are expiring (94898)   Root Cause Justification:   There are two main factors that can contribute to this behaviour: NSX Managers have many certificates for internal services. In version NSX 3.2.1, Cluster Boot Manager (CBM) service certificates were incorrectly given a validity period of 825 days instead of 100 years. This was corrected to 100 years in NSX 3.2.3. However any environment originally installed on NSX 3.2.1 will have the internal CBM Corfu certs expire after 825 regardless of upgrade to the fixed version or not. On NSX-T 3.2.x interna...

Calculate how much data can be transferred in 24 hours based on link speed in data center

  In case you are planning for migration via DIA or IPVPN link and as example you have 200Mb stable speed so you could calculate using the below formula. (( 200Mb /8)x60x60x24) /1024/1024 = 2TB /per day In case you have different speed you could replace the 200Mb by any rate to calculate as example below. (( 5 00Mb /8)x60x60x24) /1024/1024 =  5.15TB  /per day So approximate each 100Mb would allow around 1TB per day.

Device expanded/shrank messages are reported in the VMkernel log for VMFS-5

    Symptoms A VMFS-5 datastore is no longer visible in vSphere 5 datastores view. A VMFS-5 datastore is no longer mounted in the vSphere 5 datastores view. In the  /var/log/vmkernel.log  file, you see an entry similar to: .. cpu1:44722)WARNING: LVM: 2884: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device shrank (actual size 18424453 blocks, stored size 18424507 blocks) A VMFS-5 datastore is mounted in the vSphere 5 datastores view, but in the  /var/log/vmkernel.log  file you see an entry similar to: .. cpu0:44828)LVM: 2891: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device expanded (actual size 18424506 blocks, stored size 18422953 blocks)   Purpose This article provides steps to correct the VMFS-5 partition table entry using  partedUtil . For more information see  Using the partedUtil command line utility on ESX and ESXi (1036609) .   Cause The device size discrepancy is caused by an incorrect ending sector for the VMFS-5 partition on the ...