User’s Receive a Message Stating that “User” Has Forwarded Your Meeting Request to Additional Recipients



I recently ran into a problem where some user’s were beginning to receive email messages from Exchange, informing them that their Meeting Request’s were being forwarded to additional recipients.  The issue popped up during a migration from Exchange 2003 to Exchange 2007:

ScreenHunter_01 May. 20 15.46

So, easy fix right, it has to do with the Mailbox Calendar Setting option “RemoveForwardedMeetingNotifications”, second from the bottom in this screenshot.  You can check this status by running the command

Get-MailboxCalendarSettings user | fl

ScreenHunter_06 May. 20 16.13

So, here it’s false, we want to change it to true.  Do that by running the following command. 

Set-MailboxCalendarSettings user –RemoveForwardedMeetingNotificiations:$true

ScreenHunter_03 May. 20 15.53

Bam, problem fixed right?  Well, in this case, no.  The user was still receiving them.

Well, I started digging a little more.  Here is the basic background.  An admin was scheduling appointment’s for her boss, and the boss was receiving these messages.  She would either create the invitation on behalf of the boss, and invite attendees, in which case the forwarded emails would come, or edit a pre-existing appointment, in which case they would also be sent out.  Needless to say, the boss wanted it fixed!

We had recently moved her mailbox to Exchange 2007, which is when the issue began.  We investigated the issue a little further.  Turns out, she had been given access to the boss’s calendar by the boss right clicking his calendar and changing the share permissions. 

We created a test situation, Paul Ponzeka’s mailbox on Exchange 07, just like the admin, and Adam Smith’s mailbox on an Exchange 03 server, just like the boss’s.  We assigned permissions for Adam Smith’s calendar to Paul Ponzeka by changing the share permissions on the calendar.  Using Paul Ponzeka’s outlook, we opened Adam Smith’s calendar, and created a meeting invite.  Sure enough, we received the following email in Adam Smith’s Mailbox:

ScreenHunter_04 May. 20 16.00

So we have duplicated the issue.  Next, on Adam Smith’s Outlook, we added Paul Ponzeka as a delegate, but just gave him access to the calendar and the same permissions he had before:

ScreenHunter_05 May. 20 16.02

So, now we have the permissions the same, but the user is a delegate.  Again, on Paul Ponzeka’s Outlook, we create a meeting request in Adam Smith’s calendar, NO MESSAGE!  We tested the rest of the ways the admin was creating invites, all resolved.

It seems there is a bug that causes these messages, unless the user is a delegate.  It also seems like the “Remove Forwarded Meeting Notifications” setting in powershell, only applies if the user is a delegate.

Just for thoroughness, we tested with both the “boss’s” mailbox, and the “admin’s” mailbox on an Exchange 2007 server, and the exact same behavior was exhibited.  It seems it doesn’t matter where the boss’s mailbox is, 2003 or 2007.  In this example, the organization was running Exchange Server 2007 SP1 with Rollup 7.


  1. dan

    for exchange 2010 use this command

    set-calenderproccessing -identity “user” -removeForwardedMeetingNotifications-$true

  2. Is there any way to prevent those notifications from being generated in the first place?
    Setting MeetingForwardNotificationEnabled on all RemoteDomain objects does not seem to work.

  3. Greenius

    In reply to Dan –
    ‘set-calendarprocessing -identity “user” -removeForwardedMeetingNotifications:$true’
    That’s calendar with an ‘A’, processing with one ‘C’ and a colon ‘:’ before $true, not a dash ‘-‘
    Not being picky, honest. It just won’t even run unless it’s corrected.
    BTW, just heard back from the User that it fixed the issue :¬)

  4. martin

    The Forward message is generated locally and can be seen in the outbox Folder.
    Is there no possibility for a user to prevent creating the Forward messabe on the local pc (Outlook 2013) ?
    Not every user has access to the Outlook Server Shell. In toher words the above is just a admin-solution and not a user-solution.

    Thanks in advance for your help!

  5. Jimbo

    Just a note: For Exchange 2016 / Office 365, the command is now this…


Comments are closed.