EWS: The SMTP address has no mailbox associated with it.

Question

Hi,

When I check for existence of a folder in a shared mailbox at an Exchange 2013 server by using the following method:

    private void CreateEwsFolder(string sMailFolder, EwsFolderId oEwsSharedFolderId)
    {
        bool bRootFolder = true;
        EwsFolderInfo oEwsFolderInfo = null;
        EwsFolderId oEwsFolderId = null;

        try
        {
            foreach (string sFolder in sMailFolder.Split('/'))
            {
                if (bRootFolder == true)
                {
                    bRootFolder = false;

                    if (oEws.FolderExists((oEwsSharedFolderId == null ? EwsFolderId.Root : oEwsSharedFolderId), sFolder) == false)
                    {
                        oEws.CreateFolder((oEwsSharedFolderId == null ? EwsFolderId.Root : oEwsSharedFolderId), sFolder);
                    }

                    oEwsFolderInfo = oEws.FindFolder((oEwsSharedFolderId == null ? EwsFolderId.Root : oEwsSharedFolderId), sFolder);
                    oEwsFolderId = oEwsFolderInfo.Id;
                }
                else
                {
                    if (oEws.FolderExists(oEwsFolderId, sFolder) == false)
                    {
                        oEws.CreateFolder(oEwsFolderId, sFolder);
                    }

                    oEwsFolderInfo = oEws.FindFolder(oEwsFolderId, sFolder);
                    oEwsFolderId = oEwsFolderInfo.Id;
                }
            }
        }
        catch (Exception ex)
        {
            oLog.Write(oResourceManager.GetString("ErrorCreateEwsFolder") + sMailFolder + Environment.NewLine + ex.Message, Log.Type.Warning, true);
        }
    }

I get the following error in the log:

Ews(45)[4] EWS: FolderExists failed: Rebex.Net.EwsException: The SMTP address has no mailbox associated with it. (ErrorNonExistentMailbox).

Is there a possible solution for this?

The version of RebEx I use is 2016R2.1.

Regards,
Chris Witterholt.

Answer 1

Hi,

it seems it is a bug in your Exchange 2013 server, please see this Microsoft's support page. Installing the update mentioned in the link should solve the issue.