The most common solution to these grievances is a shared mailbox with a have server reply using a specific message rule underneath it.
Note: There is another way, that does not involve creating a new shared mailbox. It requires using a third-party solution such as CodeTwo Exchange Rules Pro. I discuss it in this section of the article.
Set up an auto reply for a distribution group
Follow the steps below to set up the whole mechanism:
- Save the distribution group’s most essential properties:
LegacyExchangeDN (attribute used in Outlook’s and OWA’s auto-complete cache to route messages). You can get it by running one of the below scripts (depending on the type of the group):
Get-DistributionGroup “<distribution group’s id>” | Select LegacyExchangeDN
Get-DynamicDistributionGroup “<dynamic distribution group’s id>” | Select LegacyExchangeDN
List of members – To export the list to a CSV file run:
Get-DistributionGroupMember “<distribution group’s id>” -ResultSize Unlimited | Select alias | Export-CSV -Path “<target CSV file path>”
To export members of a dynamic distribution group use the second script from the top provided in this article. As well as any other properties you may want to. For example, you can easily export your dynamic distribution group’s primary properties by running the following cmdlet:
Get-DynamicDistributionGroup “<dynamic distribution group’s id>” | select name,includedrecipients,recipientfilter | Export-Csv "<target CSV file path>" - Delete the distribution group.
- Create a new shared mailbox using the deleted distribution group’s SMTP address and grant yourself full access permissions to the mailbox.
- Update the shared mailbox’s LegacyExchangeDN with the saved distribution group’s LegacyExchangeDN (as I mentioned earlier, this is necessary because of Outlook and OWA routing). You can easily do this via ADUC, by editing the LegacyExchangeDN entry in Attribute Editor.
- Create a clone of the old distribution group using a new SMTP address (unless you want to abandon distribution groups altogether in this case and use e.g. a transport rule or Outlook rule which sends copies of emails to ex-members of the group).
- Create an Outlook profile for the shared mailbox. To do this go to Control Panel > Mail > Show Profiles…. Choose the Prompt for a profile to be used, click Add….
- Provide a name for the new profile, click OK, and complete the account creation wizard (leaving the password boxes empty).
- Run Outlook in the shared mailbox’s profile.
At this point you could set up a standard Automatic Reply for the mailbox. However, this would limit the number of automatic responses to only one per sender (see this Microsoft article for details). Also, when sending messages to the shared mailbox, users would keep seeing an “Automatic reply” MailTip suggesting that the shared mailbox “recipient” is absent. That’s why, you may want to set up the auto-response by using Outlook rules. To do so: - Go to File > Manage Rules & Alerts >New Rule…
- In the Rules Wizard, select Apply rule on messages I receive and click Next.
- Configure the rule’s conditions to suit your needs or leave the conditions empty to apply the rule to all messages received by the shared mailbox. Click Next.
- In the actions’ configuration step, select the below and click Next.
- Have server reply using a specific message and create the message template that will be used as the auto-reply (the template can include attachments).
Note: Regardless of how you fill out the TO, CC and BCC fields, the whole template will be sent to the original sender. - An action that will send the message to the new distribution group (e.g. forward it to or redirect it to).
- Have server reply using a specific message and create the message template that will be used as the auto-reply (the template can include attachments).
- Configure exceptions or leave this step blank and click Next.
- Complete the last step and click Finish.
- Test the setup by sending an email to the shared mailbox’s address.
Autoreply for a distribution group using CodeTwo Exchange Rules Pro
To set up an auto-reply mechanism for a distribution group using CodeTwo Exchange Rules Pro, follow these steps:
- Create a new rule in CodeTwo Exchange Rules Pro.
- Configure at least one condition, so that the rule will catch emails sent to the distribution group. For example, Recipient > matches AD user > <your distribution group>.
- Configure an Auto respond action.
- Save changes.
To test this functionality, download a free 30-day trial of CodeTwo Exchange Rules Pro from this page.
Learn more about CodeTwo Exchange Rules Pro
Further reading
Recommended articles
Migrating Exchange data to the cloud is not rocket science – explore your options and launch the migration stress-free. As you may already know, Exchange Server 2016 and 2019 have reached end of life and are no longer officially supported by Microsoft. If your organization still uses either of these platforms to manage email, contacts, calendars, and tasks, keep in mind that: Your environment may become vulnerable to newly discovered security threats – Microsoft will no longer provide security updates for Exchange 2016 and 2019 (unless you’ve enrolled in the Extended Security Update program, which ends in October 2026). Your emails may get blocked – Microsoft has started to throttle and block emails sent from unsupported Exchange Server versions to Exchange Online (as I covered in this article). That said, migrating to a supported platform is now the only viable long-term option for keeping your organization’s email environment secure, supported, and fully operational. If your organization wants or needs to keep things on‑premises (and continue using Microsoft’s solutions for that), upgrading to Exchange Server Subscription Edition (SE) is the only path forward. But given Microsoft’s clear preference for its cloud services – evident in the faster rollout of new features and the many security capabilities available exclusively in Microsoft 365 (Office 365) – now is a great time to leave your on‑prem environment behind and migrate to Exchange Online as part of Microsoft 365. While switching over to a new platform might seem like a rough ride, I’ll show you some easy ways to follow when migrating mailboxes from Exchange Server 2016/2019 to Microsoft 365. How to prepare for email migration to Microsoft 365 Before you start the migration process, you need to make sure your environment is ready for the move. For this purpose, you can use this guide in the Microsoft 365 admin center – it will help you connect your organization to Microsoft 365 and integrate your existing user accounts with Microsoft Entra ID. Microsoft also recommends completing the steps below: Set up an SPF record to determine valid email sources for your organization’s Microsoft 365 domain. Set up the Exchange Online Protection service as a means of protection against spam and malware. If you’re behind on updates, make sure to install the latest Cumulative Update (CU). And here is my quick, less obvious Microsoft 365 migration checklist: Verify if your software will work in Microsoft 365 (especially when it comes to server software). Microsoft 365 migration might be the time you learn that there is crucial legacy software that half the company uses and which is hard to replace. Encourage the whole company to clean up projects. It’s much easier to do this before the migration and start fresh. Gather as much information about your on‑premises environment as possible. For example, you might need to recreate access roles and permissions from scratch in the cloud or set up mail flow rules. Without prior research, it will be much more difficult. Verify if you need to migrate service accounts. There can be a lot of them on‑premises and in most cases, you won’t need them after the move. Review mailbox size limits in Exchange Online before migration to see which licenses you’ll need and whic
Microsoft retired the Search-Mailbox cmdlet – now what? Discover how to use New-ComplianceSearch, its key advantages and how to make the switch seamlessly.
One of many features of the PowerShell command line tool is its ability to connect with and manage the Exchange Server remotely. The procedure described below applies to the classic on-prem Exchange server and to the Microsoft 365/Exchange Online version.
CodeTwo sp. z o.o. sp. k. is a controller of your personal data.
See our Privacy Policy to learn more.