1310 |
 | 9.0 |
| |
7 |
|  |
52 |
 | 8.5.3 FP6 |
| |
82 |
|  |
86 |
 | 8.5.3 FP4 |
| |
180 |
|  |
127 |
 | 8.5.3 FP2 |
| |
132 |
|  |
1264 |
 | 8.5.3 |
| |
149 |
|  |
241 |
 | 8.5.2 FP3 |
| |
142 |
|  |
172 |
 | 8.5.2 FP1 |
| |
1944 |
|  |
131 |
 | 8.5.1 FP5 |
| |
142 |
|  |
2 |
|
 | Attachments |
| |
3 |
|
|  |
2 |
|
 | Calendaring & Scheduling |
| |
2 |
|
|  |
10 |
|
 | Client UI |
| |
2 |
|
|  |
4 |
|
 | Contacts |
| |
11 |
|
|  |
| | | | MKHS83ZLSK | This fix addresses a problem where moving a document to a different folder in an IMAP enabled database could corrupt that document. |  |
 |  |  |  | MVEO7P7K6Y | Panic VARRAY element index is too large. Caused by an update to the database. The code that finds the bucket containing the varray is using the... |  |
| | | | BYAU7WELLK | Fixed a potential memory leak on BLK_NIF_POOL which happens over the course of about 2 weeks. Restarting the server weekly will prevent the block... |  |
 |  |  |  | SWAS85BJXX | Slow response at high number of reader threads to a single database. 2 API's (NSFDbGetNoteInfoByUNID and NSFDBGetMultNoteInfoByUNID) are at times... |  |
| | | | WSCN83SP44 | Log file full due to an error opening a database not found in dbdirman. When this condition occurs, we are unable to write in memory information to... |  |
 |  |  |  | SWAS7QBN8N | Addresses a server crash with panic string of 0x203a2010 with archive transaction logging enabled. |  |