You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Gabriele Bulfon gbulfon@sonicle.com reported this issue on the mailing list:
I found a problem while scanning the imap tree through our java web app, behaving differently from a 2.4.12 to a 3.0.2 upgraded.
Looking at the protocol I find these differences:
==2.4.12==
. LIST "" "Other Users"
* LIST (\Noselect \HasChildren) "/" "Other Users"
. OK Completed (0.000 secs 192 calls)
==3.0.2==
. LIST "" "Other Users"
. OK Completed (0.000 secs)
So, what happens is that while the java code is checking existence of a folder in the tree, on 3.0.2 it receives an error.
Systems are same, replicated, but one upgraded to 3.0.2, so imap base and configuration is the same, but for the 3.0.2 trimmings.
The text was updated successfully, but these errors were encountered:
Gabriele Bulfon gbulfon@sonicle.com reported this issue on the mailing list:
The text was updated successfully, but these errors were encountered: