This is an automated email from the ASF dual-hosted git repository.

btellier pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/james-project.git

commit 930fd38717b67f753b96f8b0595e80af7903298a
Author: Benoit Tellier <[email protected]>
AuthorDate: Wed Feb 26 15:08:58 2020 +0700

    JAMES-3074 Changelog & upgrade instructions for JPA & Cassandra as well
---
 CHANGELOG.md            |  2 +-
 upgrade-instructions.md | 18 ++++++++++++++++++
 2 files changed, 19 insertions(+), 1 deletion(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index b846a76..a76e0e8 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -49,7 +49,7 @@ of tasks being currently executed.
 - JAMES-2972 Incorrect attribute name in the mailet configuration thanks to 
jtconsol
 - JAMES-2632 JMAP Draft GetMailboxes performance enhancements when retrieving 
all mailboxes of a user
 - JAMES-2964 Forbid to create User quota/ Domain quota/ Global quota using 
negative number
-- JAMES-3074 Maildir backend generated invalid UidValidity. Read upgrade 
instructions.
+- JAMES-3074 Fixing UidValidity generation, sanitizing of invalid values upon 
reads. Read upgrade instructions.
 
 ### Removed
 - Classes marked as deprecated whose removal was planned after 3.4.0 release 
(See JAMES-2703). This includes:
diff --git a/upgrade-instructions.md b/upgrade-instructions.md
index d37ba88..7b29280 100644
--- a/upgrade-instructions.md
+++ b/upgrade-instructions.md
@@ -28,7 +28,25 @@ Change list:
  - [Hybrid blobStore replaces Union 
blobStore](#hybrid-blobstore-replaces-union-blobstore)
  - [New forbidden set of characters in Usernames local 
part](#new-forbidden-set-of-characters-in-usernames-local-part)
  - [UidValidity and maildir](#uid-validity-and-maildir)
+ - [UidValidity and JPA or Cassandra](#uid-validity-and-jpa-or-cassandra)
  
+### UidValidity and JPA or Cassandra
+
+Date 26/02/2020
+
+SHA-1 XXX
+
+JIRA: https://issues.apache.org/jira/browse/JAMES-3074
+
+Concerned products: JPA mailbox backend, Cassandra mailbox backend
+
+Non-Maildir backends could generate '0' uid validity with a low probability, 
which is invalid regarding RFC-3501. 
+We changed the generation mechanism to use valid UidValidity for newly created 
mailboxes. Regarding persisted mailboxes,
+we regenerate invalid UidValidity upon reads.
+
+While this sanitizing is transparent to the end user and the admin, it might 
lead to rare IMAP client full mailbox
+ resynchronisation. (one chance out of two billions).
+
 ### UidValidity and maildir
 
 Date 26/02/2020


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to