Who is this article for?

 Mail Manager users encountering the challenge described

 Various levels of access may be needed to check/update such configuration settings

This article covers a number of possible causes and solutions for SharePoint connectivity challenges from MailManager, including those that could cause auto-discovered locations from not being updated or appearing at all.

Intermittent connectivity

If users are seeing intermittent connectivity challenges such as sometimes it not reaching certain SharePoint locations, sometimes not accessing shared config folder files or other similar type symptoms.

This could relate to certain implementations of IPv6. If IPv6 could be disabled on the router or network there so that only IPv4 is in use and then this be run to see if this resolves this, to rule out if this.

Locations not appearing

Possible reasons include:

Wrong login

The user is logging in with the wrong SharePoint credentials or with details for the wrong SharePoint tenant (address).
This will most likely appear as a 403 forbidden error from SharePoint in the Mail Manager session log or filing activity screen.

The easiest way to resolve this is to go to: windows settings > accounts > work or school access
Then disconnect the rogue account. Then reset your Mail Manager to SharePoint login as detailed here.

Shared configuration not loading

Is the Shared configuration folder appearing in for the user under Tools > User Preferences > Filing?
Can the user access that location in browser?

Root site not accessible

The user needs to be able to access the root site of the SharePoint tenant at https://tenant.sharepoint.com/ where tenant, is your SharePoint tenant name.

Search disabled

It is possible to disable searching the site files in the advanced settings of a SharePoint site. This needs to be enabled for Mail Manager's auto-discovery to work. This might be indicative by the number of (matching) sites it indicates as finding in the logs when investigated. This can also be done on a document library level too and could cause a similar outcome too.

Path doesn't match the auto-discovery syntax

Have files/folders been moved?
Has an error crept into this file during an edit?
Remember the site name has to match the actual name, not the name that appears in the url.

Unable to access mmcollection file

If there is a manual mmcollection file located on a SharePoint server, this needs to be added as per Adding a filing location to fix an error that it is unable to access the .mmcollection file when you select the collection, provided it is not just an access issue to the file itself.