2020 ndMail Server Refreshes

Follow

Updated:

Improvements and fixes in 2020 refreshes:

Week ending

Description of changes

27 March 2020

Improvements and Features

  • Support for German Datacenter
  • Planned resource increases (scaling) for predictive search service
  • Continued work on upcoming large features

20 March 2020

 

Improvements and Features

  • Planned scalability improvements
  • Continued work on upcoming large features
  • Continued work on German datacenter ndMail services

Issues Resolved

  • Fixed an issue where some new repositories could not create a new Exchange connection for ndMail. 

13 March 2020

Improvements and Features

  • Continued work on upcoming large features. 
  • Continued work on German datacenter ndMail services

6 March 2020

Improvements and Features

  • Continued work on upcoming large features. 

28 February 2020

Improvements and Features

  • Continued work on upcoming large features. 

21 February 2020

Improvements and Features

  • Continued work on upcoming large features. 

14 February 2020

Improvements and Features

  • Scalability changes related to the Global Filing Indicator (GFI) search to accommodate planned growth. 
  • Continued work on upcoming large features.

7 February 2020

Improvements and Features

  • Scalability changes related to the Global Filing Indicator (GFI) service to accommodate planned growth. 
  • Continued work on upcoming large features. 

31 January 2020

Improvements and Features

  • Continued work on upcoming large features.

24 January 2020

Improvements and Features

  • Continued work on upcoming large features.

17 January 2020

Improvements and Features

  • Optimized the GFI process to improve scalability as users ramp up use of ndMail 1.6. 

10 January 2020

Improvements and Features

  • If a user files a message with conversation filing and sets the security to just Me then that location will only be remembered for that conversation for that one user and not other users. 
  • Improved handling of duplicate filing requests such that if a message is filed, we cache the message ID and information about that message for 60 seconds so we can detect any subsequent (duplicate) filing requests and delay them for 60 seconds. This delay allows for the first message to be indexed before the second copy is tried so we can perform a complete deduplication check. 

Back to Top

Was this article helpful?
0 out of 0 found this helpful
Powered by Zendesk