Fix Mailbox does not exist error in Microsoft Teams

If you’re using Microsoft Teams, then maybe you have come across a particular error in recent times. It’s nothing out of the ordinary, but annoying nonetheless. The issue we are talking about here is when the mailbox in Microsoft Teams is empty. You may see an error message – Mailbox does not exist.

An empty mailbox, or one that doesn’t exist, would be a surprise to anyone that had content within it before this problem. The big question right now is what caused this to happen, and whether or not if there is a way to fix it once and for all. Now, we can’t say for certain what caused the mailbox to go empty, but we can say the problem can be solved.

Mailbox does not exist error in Microsoft Teams

From what we have gathered, the mailbox does not exist error tends to happen when Microsoft Exchange is in use. Yes, many users of Microsoft Teams take big advantage of Exchange, which should come as no surprise to anyone at this point.

OK, so let’s look into how we can solve the no mailbox error, and hopefully, it will never show its ugly head ever again

Microsoft Teams – Mailbox does not exist

Fixing this problem is super easy, at least from our point of view, so don’t be discouraged because we will make it easy to understand.

  1. Check the O-auth setting
  2. Verify that Exchange Online can successfully connect

1] Check the O-auth setting

The first thing you’ll need to do is run the Test-OAuthConnectivity tool to see if things are working as they should. The idea here is to make sure your organization can successfully connect to Exchange Online because this is a very important aspect.

To get this done, please launch Windows PowerShell by right-clicking on the Start menu button, then select Windows PowerShell from the menu. We suggest choosing the admin version for a better chance of this working.

After launching the tool, please copy and paste the following into PowerShell then hit the Enter key on your keyboard:

Test-OAuthConnectivity -Service EWS -TargetUri -Mailbox <On-Premises Mailbox> -Verbose | Format-List

2] Verify that Exchange Online can successfully connect

The next step, then, is to test if the connection is working, and yes, the task is easy to accomplish. You see, simply follow the steps above to launch Windows PowerShell, then copy and paste the following, and as usual, hit the Enter key:

Test-OAuthConnectivity -Service EWS -TargetUri <external hostname authority of your Exchange On-Premises deployment>/metadata/json/1 -Mailbox <Exchange Online Mailbox> -Verbose | Format-List

That should get the job done, 100 percent. So, go ahead and check the mailbox to see if its back to its regular setting.

All the best.

Changing System Admin Email Address for Salesforce Securlet Connection

I need a solution


Can I please get some advice. My organisation is going through a major change and we will be changing our email domain for user and shared mailbox.

We currently have configured Salesforce Securlet connection using a shared mailbox. Since this shared mailbox domain will be changed, we will need to reflect this change in CASB.

My questions if someone could help me:-

  • Is there a way for me to change the email address/CloudSoc username?
  • If no.
    • Then it seem like I will need to set-up a new CloudSoc account? then update the email on Salesforce side.
    • If so will the API connection break?
    • we will require to re-create Salesforce Securlet connections again?
    • Will there be any option to somehow have some continuity to the Securlet data? Prior and After the change? 




Sizing Tool for Messaging Gateway Virtual Appliance

I need a solution

Hi everyone,

How do we size Messaging Gateway based on the number of users and mailbox for Virtual Appliance?

As I know Symantec has a sizing tool but I can’t seem to find it anywhere. (including the partnernet etc)

Please advise if anyone has it?

I need it for a hyper-v environment. The article I checked does not state how many users/mailbox it can support based on the requirement given.

Thank you.



Unable to see O365 device in XMM

Recalculating Active Sync Partnership

There is the possibility that even though users have devices synchronizing with their mailbox, that the HasActiveSyncPartnership attribute is not set. This Microsoft KB article provides further details:

In a nutshell you must run the following command to correct all mailboxes in Exchange.

Get-CASMailbox * -RecalculateHasActiveSyncDevicePartnership

Advise customer to check that their data is incorrect and to follow the KB article.


NMM Exchange – GLR Database with parameter IsExcludedFromProvisioning=False

Article Number: 502821 Article Version: 3 Article Type: Break Fix


For GLR (Ganular Level Restore) DB in Exchange 2010, the “IsExcludedFromProvisioning” is set to FALSE

This “IsExcludedFromProvisioning” is an Exchange parameter to determine whether new mailboxes will be created in this Exchange DB automatically due to load balancing.

New in Exchange 2010 and carried into Exchange 2013 is a feature called Automatic Mailbox Provisioning. This feature automatically load balances the creation of new mailboxes across all available databases when a creation of a new mailbox account occurs. It’s no longer mandatory to specify what database mailbox should reside on as Exchange uses a mailbox provisioning agent to take the decision for you on what mailbox database the mailbox creation will be created on.

It is recommended that all large Exchange deployments utilise the Automatic Mailbox Provisioning system to randomly distribute mailboxes between mailbox databases. If you place users in particular mailbox databases based on items such as a department, in the event issues occur with a specific mailbox database and the database will not mount, an entire department within a company will be out of production for a period of time. If mailboxes are randomly distributed between multiple databases, in the event a database goes offline, it will still effect the company however the impact will be less saver as all departments within your company will still be operational.

Automatic Mailbox Provisioning system distributes mailboxes randomly amongst databases but in case we want to exclude a mailbox database from having additional mailboxes provisioned such as a mailbox database which is dedicated to holding Archive mailboxes, Microsoft has included two attributes which can be configured against a Mailbox Database for this purpose called “IsExcludedFromProvisioning” and “IsSuspendedFromProvisioning“.

IsExcludedFromProvisioning <$true | $false>

The IsExcludedFromProvisioning parameter specifies that this database is permanently not considered by the mailbox provisioning load balancer.

If the IsExcludedFromProvisioning parameter is enabled, new mailboxes aren’t added automatically to this database.

You can manually add a mailbox if your role permits.

IsSuspendedFromProvisioning <$true | $false>

The IsSuspendedFromProvisioning parameter specifies that this database is temporarily not considered by the mailbox provisioning load balancer.

The reason they are two attributes is for environments which have multiple admins as a mechanism to indicate which provisioning suspensions are permanent, and which are temporary so that other admins know if they are allowed to unsuspend a mailbox database from provisioning. Thus, in a multi-admin environment, if one admin configures either setting, the intent should be clear to the other admins (and therefore, they won’t remove a permanent suspension as a result of knowing that intent).

This is Exchange parameter and need Exchange admin to configure it according to mailbox creation load balancing among Exchange Databases


Re: Best practice question: How are you dealing with old shortcuts in mailboxes?


As number of years a user will continue to stay with organisation grows, their mailbox size will grow as well. For an example I am with current organisation for close to 13 years and my mailbox is close to 7GB after shortcutting and emails older than 6 years are cleaned up from my mailbox by IT though.

I can share what I have seen, basically you covered the points already.

1. Inform users how large number of items in their mailbox would impact performance of Outlook.

2. Educate users to export to PST (if your organisation allows).

3. You already have shortcutting in place yet it cannot keep on bring the size of mailbox down if number of items in mailbox continue to grow (like my mailbox).

4. Inform users couple of months beforehand that emails other than __ years will be deleted from their mailbox. You may have to send reminders few times.

5. Finally if you see mailboxes still large then as you mentioned run delete activity to get rid of old email as per your business policy requirements and suggest users to use search site.

Best regards,

Rajan Katwal


Recovering Exchange Data with NMM 9

This article will cover restore options for Exchange in NMM 9. The demo in the article is with NMM and Exchange 2013 DAG. NMM 9 offers the choice of using ItemPoint to perform mailbox/item level recovery. ItemPoint is the preferred method of GLR in NMM 9. However traditional GLR (Granular Level Restore) using NMM GUI is available for Exchange 2013 and Exchange 2010. For Exchange 2016 ItemPoint is the only method of GLR .

If you choose to use ItemPoint for mailbox/mail item recovery, then traditional GLR from NMM GUI is not available. So you can either use ItemPoint or traditional GLR restore but not both on a given host. This choice is made during NMM 9 install. Additionally if there is a requirement to restore backups done with NMM 8, then during install of NMM 9, select the option ‘Restore of NMM 8.2.x and earlier backups(VSS workflow)’

Below is the screen shot of the NMM 9 install process that shows the selection to restore backups from previous version and selecting ‘Exchange Granular Recovery’ (ItemPoint) as the preferred method of GLR.


Note, when you select to ‘Restore of NMM 8.2.x and earlier backups(VSS workflow)’, the install process installs the binaries for NMM 8.2.4, that will be used for the restore. The binaries are stored in the default folder:

C:Program FilesEMC NetWorkernsrrpvnmm

RPVNMM stands for ‘Restore Previous Version of NMM’

There is also a selection added in the ‘EMC Networker’ Program Group, under ‘NetWorker Tools’ for the Restore GUI that will read older backups done with NMM 8.2.x. The program name is ‘Restore previous NMM release backups’


In addition, the install also contains the binary ‘nsrsnap_vss_ssrecover’ that allows for flat file restore of the NMM 8 backups, if required.

On a Exchange host where ItemPoint was chosen for GLR, there are 2 restore choices available. ‘Database Recovery’ and ‘Granular Level Recover’. Note there is no ‘RDB data recover’. If you are used to seeing this option with previous versions of NMM, then note that ItemPoint restore is not handled through RDB, hence the choice of ‘RDB data recover’ is not available.

1. Database Recovery


Database Recovery provides the following options:

a. Overwrite the Database, if there is a need to recover the database to itself (overwriting it). Select the desired database and then click ‘Recover’. You will see the message window below advising to set the property ‘This database can be overwritten by a Restore’ of the database.


This can be done either using the PowerShell command as mentioned in the message window or using ECP / EAC GUI as below:


****Note this is a destructive action. Make sure this is the correct choice before you proceed. NMM does not let you set the ‘This database can be overwritten by a restore’ property from the NMM GUI, to ensure there is no accidental overwrites.

Once the property ‘This database can be overwritten by a restore’ is set, then NMM GUI allows you to proceed with restore. Click ‘recover…’ and then ‘Recover options…’ Under ‘Exchange’ tab there are certain choices to make that will determine how the ‘recover’ is done within Exchange


Below is a brief explanation of these choices:

‘Include Existing logs (Roll-forward Recovery)’. This option is useful if the database and logs were on separate volumes and the volume containing logs is still available, or even if both DB and logs are on the same volume and only the ‘edb’ file is corrupt and the logs are good, then you can do the restore of the backup and then perform a roll forward recovery using the logs on the disk. This will bring the database to the most recent state with minimum or no data loss.

‘Include only logs from this restore (Point-in-time recovery)’. Select this option when point in time restore is required, i.e the database will be recovered to the time of the last backup.

‘Put database online after restore’. By default the restore process will replay the logs and put the database online after restore. If this is not required, then click on this option again to deselect it and select ‘Do not replay the transaction logs’. If ‘Do not replay the transaction logs’ is selected then the logs are restored, but they will need to be manually replayed using ‘eseutil’

‘Deleted Database Target’, This is used if a flat file restore of database is required. This option bypasses VSS method of restore and simply restored the ‘edb’ and ‘logs’ as files to the target directory. Further processing is required to mount the database.

For Database Restore of a database that’s replicated in a DAG configuration, you first have to suspend the replication, otherwise the following error is seen in the Monitor tab:

The client name used NMMHOST2. The Exchange Server version used is Exchange 2013.

145369:nsrnmmrc: Initialization success — Exchange shell successfully initialized. Required for Exchange.

MailboxStore [DB01] is in replicated state, please suspend the replication on all DAG nodes and perform restore after that.

Also note that this restore can only be performed on the node that holds the active copy of the database.

2. GLR restore with ItemPoint:

Before trying GLR restore with ItemPoint, some preparatory steps have to be taken to meet all pre-requisites:

  1. Install 32 bit Outlook 2010/2013 on the server from where the restore will be performed. Outlook 2016 is currently not supported.

Microsoft does not recommend (or support) Outlook Installation on Exchange Server. Prior to NMM 9.2, ItemPoint could only be used on the Exchange server, which means outlook had to be installed on the Exchange server. However NMM 9.2 and greater allows ItemPoint GLR from a non-Exchange server (Proxy).

2. Ensure the user performing restore has send-as, receive-as permissions on the mailbox server to allow for browsing and restoring the mailboxes. Also make this user a member of the ‘Exchange Organization Management’ security group.

Also ItemPoint needs additional permission assignments to the user performing restore to allow for browsing and recovering mail items from any mailbox

Get-mailboxdatabase -identity db01 | add-adpermission -user nmm_svc -accessrights genericall

Get-mailbox | add-mailboxpermission -user nmm_svc -AccessRights FullAccess -InheritanceType All

For further information on this topic refer to ItemPoint documentation.

To perform ItemPoint GLR from a non-Exchange server ensure the following pre-requisites are met:

  1. The non-Exchange server would need to have same OS as the production Exchange server. You may be able to get away using a different OS on this host. Using the same OS will eliminate any complications. Check ItemPoint documentation on support for different OS.
  2. Install and configure a 32-bit Outlook 2010 or 32-bit Outlook 2013. Note outlook and MAPI/CDO [Messaging API and Collaboration Data Objects] software cannot co-exist on a host. If MAPI/CDO software is installed, uninstall it before installing outlook
  3. Install Networker client 9.2.x & NMM 9.2.x. For this article I’m using NMM
  4. Create a client resource for this host on the Networker server.


5. Grant remote access permissions to the user performing restore from this host. There are 2 ways to do this. Either add this user to a user group that has remote access privilege or add this user to the ‘remote access’ attribute of the DAG client resource.

Method 1: Adding the user performing the restore to the ‘Remote Access’ attribute of the client resource.


Method 2: Add the user to a user group that has ‘remote access’ privilege.


Once the above pre-requisites have been met, you are ready to perform GLR using itempoint.

To start the recovery, from NMM restore host, launch the NMM GUI as ‘administrator’. Then select the client from the drop down and then select ‘Exchange Recover Session’ => ‘Granular Level Recover’


Note this restore is being performed from a host that does not have Exchange server installed and as such NMM provides only the GLR option for restore. Since Exchange is not installed, Database Recovery or Restore to RDB cannot be performed.

From the browse window, select the desired client, browse time and database for restore and right click:


From the right click menu either choose ‘mount backup’ or ‘mount backup and run ItemPoint’. If you select ‘Mount backup’ then NMM will mount the backup and then you have to manually launch ItemPoint to restore from the mount points. ‘Mount backup and run ItemPoint’ is preferable as NMM GUI mounts the backup and then starts ItemPoint and auto fills the path for edb and log files:


Click ‘Finish’ and ItemPoint starts processing the log files and edb file:


Once the log and edb file is processed, ItemPoint GUI shows the content of the source database that was mounted. The next step is to open a target. This can be an Exchange server or a PST file. Here we open a target Exchange server, as we want to restore to a mailbox to the target server.


When you click ‘Open Target Exchange server’, you get the following choices. In ‘Select Target’ either choose to connect to a single mailbox or ‘All Mailboxes’. You would choose ‘All Mailboxes’ if you want to restore data to different mailboxes. Click ‘Next’


ItemPoint shows the number of mailboxes in the Target. Review and click ‘Close’



This output shows copy of mailbox ‘nmm_svc’ to the mailbox ‘blee’


If you need to restore a mailbox or mailbox items to a PST file, right click the mailbox / mail items and select ‘Export…’


(Only for Exchange server 2010 and Exchange Server 2013. With Exchange Server 2016 ItemPoint is the only choice for GLR)

If ItemPoint will not be used for GLR, then you can fall back on traditional GLR with NMM GUI. The recovery process here is very similar to the GLR in NMM 8, except that NMM uses ‘block based backup’ mechanism to mount the backup. In NMM 8, NwFS (Networker virtual file system) was used to perform the virtual mount of the backup.

Following are the pre-requisites for successful GLR using NMM GUI.

  1. Install “Messaging API and Collaboration Data Objects 1.2.1” on the Exchange server where the restore will be performed. Version 6.5.8353 is recommended
  2. The service account used with NMM, should have ‘send-as, receive-as’ rights on the Exchange Server
  3. The service account used with NMM should have a mailbox located on a database that’s mounted on the same version of Exchange server. If the environment has both Exchange Server 2010 and Exchange Server 2013, then the service account mailbox should be on a Exchange 2013 server if the GLR is being performed for Exchange Server 2013. If the GLR is being performed for Exchange server 2010, then the service account mailbox should be on a Exchange Server 2010.
  4. The service account used with NMM should be a member of the Exchange Organization Management security group.
  5. If restore to PST is required, then the service account needs to have the additional ‘Mailbox Import Export’ role

Once the above pre-requisites are met, you are ready to perform GLR restore with NMM.

  1. Start the NMM GUI as ‘administrator’.
  2. Select the correct client from the ‘client’ drop down. Change ‘Recover Browse Time’ if required.
  3. Click ‘Recover’ -> Exchange 2013 Recover Session -> Granular Level Recover


4. Select the desired database. Then click ‘Recover…’


5. Click ‘Recover Options…’ if you want to modify the recovery behavior.

    1. Under General Tab, set the diagnostic level. This normally would be used by support to troubleshoot a restore failure


b. Under ‘Exchange’ tab below are the options. The defaults are fine for GLR restore.


6. Click start recover


7. Once the restore completes, the following message window is seen:


Review the monitor window for logging of the restore:


8. Click on the ‘recover’ tab to browse the GLR database and expand to the desired mailbox.


9. Select the mailbox or mailbox items


10. If recovering the mailbox/mailbox items back to the original mailbox choose ‘Recover..’ If recovering to another mailbox choose ‘Advanced Recover..’

Here I’m recovering to the original mailbox, so I choose ‘Recover..’. The ‘monitor’ window shows the messages for the restore.


When the recover completes, you can login to the mailbox to confirm the recover was successful. The recovered items are placed under a folder ‘Recovered Items …’ as seen below


This completes GLR using NMM GUI.

Recovery from backups done with previous version

If there is a requirement to restore from backups done with NMM 8.2.x, and during install the choice ‘Restore of NMM 8.2.x and earlier backups(VSS workflow)’ was made, then NMM will install the software required to perform this restore.

Note this software is installed in “C:Program FilesEMC NetWorkernsrrpvnmm”.

NMM 9 GUI cannot be used to recover backups performed with NMM 8. To launch the NMM 8 GUI, from program group ‘EMC NetWorker -> NetWorker Tools -> ‘Restore previous NMM release backups’. Start this GUI as ‘administrator’


Check recovering Exchange backups in NMM 8 for details on recovery with NMM 8.


Recovering ‘Deleted Mailbox’ with NMM

Recovering ‘Deleted Mailbox’ with NMM

This article covers the scenario of recovering a ‘deleted’ mailbox from NMM. The procedure documented in this article applies both to NMM 8 and NMM 9. Exchange server 2010 is used in this demo.

Before I cover this procedure in NMM, below is background on how the need for this restore may arise.

In Exchange 2010 a user mailbox can either be ‘Removed’ or ‘Disabled’.


Difference between ‘Remove’ and Disable’ mailbox choice in EMC:

Disable: Will remove the Exchange attributes from the user account but will leave the user account in Active Directory. The mailbox for the user will still exists on the mailbox database and it gets purged when the retention time elapses (default of 30 days)

Remove: Remove will remove both the user mailbox and user account from Active directory. The mailbox will still be there on the mailbox database till the retention time has elapses.

If the mailbox was either ‘deleted’ or ‘removed’ (for some reason, like employee leaving a company), there may be a need to restore this mailbox in future. If the deleted mailbox retention time has not expired, it could be recovered as below:

  1. If the mailbox was ‘Disabled’. This mailbox will show in the ‘Exchange Management Console’ under ‘Disconnected Mailbox’ as shown below:



b. To recover this mailbox, Right click the mailbox and select ‘Connect…’


c. Select ‘User Mailbox’ , then ‘Next’


d. Click ‘Browse’ Under ‘matching user’ and then select the user to connect this mailbox to


e. Provide the ‘Alias’, then select ‘next’


f. Review Summary and select ‘Connect’


g. Review and select ‘Finish’. This will ‘reconnect’ the disconnected mailbox to the user in Active directory.

2. If the mailbox was ‘removed’ and is still within the retention period, create a new ‘user’ in Active Directory with the same name as the original user and then follow the above steps to ‘connect’ the user to the mailbox on the database.

The following exchange shell command is useful to get a list of ‘Disabled’ or ‘Removed’ mailbox users that are still within the retention period:

Get-MailboxDatabase | Get-MailboxStatistics | where {$_.DisconnectReason -ne $null} | ft displayname,database,disconnectreason,*guid*,*server* -auto

DisplayName Database DisconnectReason MailboxGuid ServerName OriginatingServer

———– ——– —————- ———– ———- —————–

charlu carydb3 Disabled 3f91bda9-453c-4752-8b88-423d2f4ccc53 APPHOST1 apphost1.spring.local

Once the retention period expires and the mailbox is purged from the database, it will not show up in the above output.

Once the mailbox data is purged from the mailbox database, if a restore is required after the retention period, then you would need to depend on your backups for restore.

Restoring a deleted mailbox using NMM:

I have used NMM 8.2.4 to demo this procedure. It likely will work as is, with NMM 8.2.3 or NMM 8.2.2. Also the same procedure applies to NMM 9. The first step in performing mailbox restore of mailbox (deleted or otherwise) is to perform GLR or restore to RDB. Refer to the post

  1. Once the initial phase of GLR or RDB restore is complete, the mailboxes can be browsed from NMM GUI:


2. When you click the ‘deleted’ mailbox it generates this error message (shown below). Note, because there is no user associated with this mailbox or the associated user has its mailbox properties removed, MAPI is not able to show the contents of this mailbox. You can only recover the ‘Entire’ mailbox and not individual folders or mail items within it.


3. Acknowledge the message window by click ‘ok’. When you switch to the ‘Monitor’ tab, you will notice the same message there:

Selecting Exchange RDB view

Mailbox SystemMailbox{18d1f726-3cd7-48cd-8983-12ec40779e8b} is a ArbitrationMailbox and is not browsable nor can it be recovered.

Error getting item list: Error browsing folders — Failed to fetch mailbox items. Please see libmapibrowse.raw for more information. [exch_get_mbx_list].

Error browsing folders — Failed to fetch mailbox items. Please see libmapibrowse.raw for more information. [exch_get_mbx_list].

4. Select the mailbox for ‘restore’. Once you select the mailbox for restore, there are 2 types of restores that can be done:

  1. Restore the mailbox to itself

If you want to restore the mailbox to itself, create the mailbox with the same name (you would do this before you do the restore with NMM. You can do this with Exchange Management Console or Exchange powershell and then come back to the NMM GUI and select ‘Recover..’ as shown below:

(Note: If you have disabled the mailbox, connect the mailbox shown under ‘Disconnected Mailbox in EMC to the original user. If the mailbox was removed, then connect, under ‘Disconnected mailbox’ to a new mailbox and a new AD user with the same name. If the mailbox was deleted from the database, due expiry of retention time or the mailbox was manually deleted from the database, using the ‘remove-storemailbox’, then create a new user and new mailbox with the same name and proceed with the restore. In all variations of deletions, the mailbox can be restored to the original mailbox name)


b. Restore the mailbox to another mailbox. (Alternate mailbox)

To restore this mailbox to another mailbox, you would choose ‘Advance Recover..’. Then in the ‘Select Alternate Mailbox User’ box, specify the user to which you want to restore to and click ‘Search’ to locate the user. Then select this user and click ‘Next’


Here we are performing the restore to an alternate mailbox ‘Andy’ and ‘Start Restore’


5. When the restore is complete, switch to the ‘Monitor’ tab to check on the progress.


6. Verify the restore by logging into the mailbox of the target user, in our case ‘Andy’ :


Restore using Exchange PowerShell:

This mailbox restore can also be done using Exchange Powershell:

  1. First get the GLR database name:



b. Issue the new-mailboxrestorerequest command:

new-mailboxrestorerequest -sourcedatabase GLR20180516163434 -sourcestoremailbox “charlu” -targetmailbox “Andy” -TargetRootFolder Restore201805161717 –AllowLegacyDNMismatch



This article covered the procedure involved in restoring a deleted mailbox from NMM 8.2.4 backups. The procedure also applies to NMM 9. Key point to remember is that the deleted mailbox cannot be browsed for individual mail items recovery from the NMM GUI. The entire mailbox can be recovered from NMM GUI or using powershell. Powershell command can be further refined to recover individual folders within the mailbox if desired.


7022961: Forward Copy Rule Using NGW-Variable

This document (7022961) is provided subject to the disclaimer at the end of this document.


GroupWise Mailbox Management


A rule needs to be created that will contain the from address for every user in the system, and forward to a specific folder or address. How can this be done in bulk using GroupWise Mailbox Management?


GroupWise Mailbox Management (GWMM) utilizes the NGW Variable in order to populate fields in the rules, as well as the signatures, so that the administrators do not have to create a rule for every user. Using the variables, and the copy feature in GWMM can save a lot of time and effort. The steps are outlined below to copy a rule and forward it to a different e-mail address, or other action.

1) Create a Forward Rule for a user. In the condition set it to From | Contains | and then input the NGW Variable Email Address: [[NGW-EmailAddress]]
2) Define the action and save the Rule.
3) Launch GroupWise Mailbox Management and select the user that the rule was created, and click on rules
4) Copy the rule to the users.
Note: There is a known issue where the display name will be incorrect, showing the rule creator. The NGW-EmailAddress, however, will have changed to the correct user in the from field. The rule itself will work in GroupWise, and display properly for the users


This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.