Last Update: 2022-06-21
CVSS:5.4
CVSS:4.3
CVSS:5.4
CVSS:8.2
There is no control whether a password has been stored when the option “using password” is activated.Now “Using password” can only be used if a password has also been stored.
Missing folder data because of insufficient permissions.This has been solved by checking if event is in all public appointments folder. This way we can make some assumptions even without full folder data.
User needs at least read permission to download a folder.Solution: Make sure read permission is properly checked.
Failed upload of inline images was no longer propagated to TinyMCE.This has been fixed by propagating and catching failed upload again.
Missing error handling when creating composition spaces.This has been solved by implementing general error handling for creating new composition spaces.
Mismatch in order of displayed contact fields.This has been fixed by moving fields to match edit form.
No possibility to circumvent Dovecot issue failing to server “PREVIEW” capability.This has been solved by introducing property “com.openexchange.imap.preferredPreviewMode” for IMAP connector to specify preferred preview mode. See SCR-1087.
Wrong detection of standard SSL protocols.This has been solved by orderly detecting (and using) standard SSL protocols.
With introduction of clean-up framework tasks get executed per database schema. Thus the start and end information are unnecessarily printed per database schema.This has been fixed by restoring previous behavior to log those info only once at start and termination of that task for all database schemas.
Wrong folder traversal on data export of contacts.This has been solved by orderly considering subfolders on export.
Log level ERROR used for CATEGORY_CONFLICT exceptions.Now using log level DEBUG for CATEGORY_CONFLICT exceptions.
The dependencies must have changed and Jolokia support was not part of the DCS anymore.This has been solved by adding explicit Jolokia support into the DCS build.gradle / pom.xml.
Improvement: Do not complain when client tries to delete a non-existing attachment.
File storage account will be accidentally removed locally once a single (sub) folder of an external account gets removed.This has been solved by adding check to remove file account only when root folder get’s deleted.
Was caused by a missing gt call.This has been fixed by adding the missing gt call.
String was not recognized as translatable string.This has been fixed by adding gt calls to boot/i18n.
In case client-passed token does not match the one currently associated with requested composition space while trying to perform an update ends in an infinite retry loop.This has been solved by using dedicated error code in case client-passed token does not match the one currently associated with requested composition space.
Missing recurrence identifier in change exception set of stored recurrence master event.Solution: Orderly incorporate intermediate results when handling calendar resource updates, also consider change exception instances when building recurrence set during update.
USM combines original mail and forward text into a new mail which is sent in base64 format. This seems to be invalid and is rejected by the backend. ICS attachments are filtered by USM if the mime-header content-type contains application/ics or text/calendar.This has been solved by sending combined mail in text format. Create correct mail with hierarchical multipart. ICS attachments will be filtered only if corresponding calendar objects exist.
This functionality was disabled during a restructuring.now it has been adjusted accordingly.
Resizing an email attachment could cause individual attachments to be duplicated.The process has been revised so that resizing an image attachment cannot be interpreted as a new attachment.
User were listed twice.This has been solved by avoiding listing of duplicate users.
There was a typo in bot the documentation as well as in the implementation.Fixed the typo in both places.
Uploaded attachments were spooled to local temporary file while unnecessarily holding lock on affected composition space. This holds that lock for too long.Solution: Spool attachment to local temporary file w/o acquiring lock. However, actually adding the attachment to the draft mail is required to be performed mutually exclusive.
Cached data providing the draft mail identifier might be outdated.Cached data providing the draft mail identifier might be outdated.Perform look-up of draft mail by composition space identifier in case there is no draft mail for cached information.Unfortunately, based on the information provided, it was not possible to understand why all of a sudden the associated draft mail of a composition space cannot be found based on the information managed in memory. Therefore, in such a case, an attempt is now made to find the associated mail by a look-up per composition space identifier. If that also fails, the draft mail must have actually been deleted.
Checked local state for possible too many composition spaces which might not be up to date.This has been solved by always checking content of standard drafts folder on mail server to reliably test for too many composition spaces.
Length of VARCHAR columns in generic_use_count table too big to be used for a PRIMARY KEY or UNIQUE KEY.This has been solved by shrinking VARCHAR columns in generic_use_count table to proper size to be used for a PRIMARY KEY or UNIQUE KEY.
Subfolder flag for Shared files folder was always set.This has been solved by adding proper subfolder detection for ‘Shared Files’ folder.
LibreOffice is having a problem with the default property in styles, regardless of the value LO interprets it as default = “true”. There should only be one default paragraph style in a document. LO thinks that there are twice and lets the latter win. So In this case the correct paragraph style “Normal” is overwritten by the paragraph style “ListParagraph”.Solution: We will no longer write the property “default” in styles when its value is “false”, this is also valid. The bugfix only works for newly created documents and documents that are saved again in our editor.
Was caused by glitches in the manual creation of these templates.This has been solved by fixing the Inconsistency.
Feature toggle was checked to late in code.This has been solved by moving feature check to an earlier point.
Missing max-width and default line/word break behavior.This has been fixed by adding Max width and set proper line break behavior. This makes ellipsis work as intended.
Missing organizer caused js error in UI.This has been solved by making UI more robust so it doesn’t break if an appointment has no organizer.
DELETE statement not matching targeted distribution list entry under certain circumstances.This has been fixed by correctly deleting/updating distribution list members by parent contact identifier.
Wrong slicing of sorted message set.Solution: Fixed slicing of sorted message set.
Slow upload leads to timeouts.Solution: Do not let upload time out since not measurable whether there is slow connection bandwidth or poor performing file storage end-point.
Dav does not call the session hit that the MW does. As a result, the check for multifactor is missed.This has been solved by adding additional check for multifactor in DAV servlet. Should simply reject if found. There is no way to authenticate multifactor in DAV. Application passwords should be used.
Content-Length of last chunk wrong in case requested range is greater than actual file length.Solution: Correctly set content-length header if client-requested range is beyond file length.
Broken folder references in stored distribution list members lead to runtime exception in custom address book plugin.Solution: Unmangle folder id in distribution list members prior passing down to contacts access, skip invalid references when post-processing loaded distribution list members.
Chrome removed U2F support.Utilize webauthn U2F mechanisms to support the logins in Chrome.
Misleading error description for hidden subfolder.This has been solved by returning dedicated errors for the scenario, pointing to the folder causing the error (if visible for the user).
Applied regular expression leading to excessive resource consumption. Too heavyweight logic to convert HTML to plain text.This has been fixed by avoiding using regular expression to split HTML content to lines and fixed possible NPE when querying available composition spaces. Improved html-to-text conversion to be faster and use less memory.
It’s not yet implemented to share all folders except folders without access rights.Now showing “Ignore Warnings” Dialog to share only folders with access right and send ‘ignoreWarnings=true’ to the MW.
Was unsupported.Solution: ‘apps’ can now be hidden via jslob setting “io.ox/onboarding//hidden/apps”, syncapp is hidden by default.
There was no need to URL-encode the URL in the previous OX versions because the token was not base64 encoded.When using the io.ox/core/tk/iframe with the option acquireToken, the token is sent without being URL-encoded. Now it will be URL-encoded.
This wasn´t considered yet.This has been solved by extending the regex.
Wrong check if given sender address is possibly associated with an external account.This has been solved by a proper check if given sender address is possibly associated with an external account.
Max. number of composition spaces not orderly considered when opening a new one.This has been solved by Considering max. number of composition spaces when opening a new one.
Parse errors if a MIME message contains a corrupt Content-Type string.This has been fixed by sanitizing Content-Type string in case a corrupt one is present in MIME message or one of its parts.
Missing help text for dynamic options.This has been fixed by adding a help text for dynamic options.
Update of DAV:displayname property permitted through CalDAV for default Birthdays calendar.Treat DAV:displayname property as protected for Birthdays calendar, and indicate forbidden property updates via DAV:cannot-modify-protected-property precondition.
Errors while trying to resume a previously paused data export.Solution: Handle possible connect failure while exporting mails. Avoid pausing running data export tasks. Let started ones complete and avoid unnecessarily stopping data export tasks in case a continuous timeframe is configured, e.g. “com.openexchange.gdpr.dataexport.schedule=Mon-Sun”.
Plain connection established although SSL connection expected.Solution: Orderly signal whether a direct SSL connection should be established or not.
InputStream.available() might not indicate available content.Solution: Probe for next byte instead of relying on InputStream.available().
This is a bit of a design problem. The settings dialog suggests only one date format, but UI is using 2 formats. A long (with leading zeros) and a short format (without leading zeros). Since there is only one format to choose from we are always wrong one way or the other.Solution: If a user explicitly sets a specific format (customized locale data) we overwrite both, the long and short format with the chosen format. If the user uses the language specific default we use long and short format as before.
Wrong action type leads to creating a copy instead of editing the draft.This has been solved by changing the type from ‘copy’ to ‘edit’.
No sufficient checks for quicklauncher app availability.This has been solved by hiding unavailable apps in quicklauncher and config dialog. Apps that have upsell enabled are considered available. Guests do not have upsell so they will not see upsell enabled apps they lack the capabilities for.
Missing organizer caused js error in UI.Solution: Make UI more robust so it doesn’t break if an appointment has no organizer.
Editing an image with the createImageBitmap function within a worker in Chrome Browser version = 77 leads to incorrect results.Solution: For Chrome Browser version = 77, the editing process with createImageBitmap is no longer performed in the worker.
Client-wise specified expiration date got adjusted by user’s time zone.Now passing client-wise specified expiration date as-is (assume GMT+0) and do not adjust by user’s time zone to solve this issue.
Different mail address in FROM header and mail text.This has been solved by respecting the property com.openexchange.notification.fromSource and use the default sender address in mail text, too.
This has been solved by fixing a typo in Czech .po file.
CVSS:8.2
The first fix was only for form login.Now this has also been fixed for token login.
Retry mechanism circumvented through introduction of client tokens for any reason.This has been solved by re-enabling retry mechanism.
Was caused by too strict permission check when processing CANCEL messages.Solution: Require delete permissions for targeted user attendee when applying CANCEL messages.
Was caused by sporadicaly timeouts when obtaining a connection to the storage.Solution: Retry establishing a connection to file storage in case caught exception indicates a timeout while connecting to an HTTP server or waiting for an available connection from connection pool.
CVSS:3.1
CVSS:3.1
CVSS:3.1
CVSS:3.1
CVSS:5.3
CVSS:3.1
CVSS:3.1
CVSS:3.1
CVSS:3.1
CVSS:3.1
CVSS:3.1
CVSS:3.1
CVSS:3.1
CVSS:3.1
CVSS:3.1
CVSS:3.1
CVSS:3.1
CVSS:3.1
CVSS:3.1
CVSS:3.1
Unnecessary double capability check, which broke upsell configuration.This has been solved by just checking for one capability for each entry.
Wrong calculation of end time slot (was not based of endtime, but starttime and length).This has been solved by fixing calculation of endtime slot so the slot that contains the end time is included correctly.
Fixes translation.
Rampup extensions trying to fetch data without session requiring multifactor.This has been fixed by exiting the rampup stage early if multifactor is required after login.
UI does not have a way to display cancelled appointments.Mark cancelled appointments by striked through text, grey color and an info message in the detail view.
It was not possible to receive notifications for external mail accounts.This has been solved by implementing check for external inboxes. Note: This is done via periodic requests and not via sockets, since there is no MW support for this. Implemented a feature switch for this so the current behavior does not change for customers that don’t want this.io.ox/mail//notificationsForExternalInboxes default is false.
Was caused by an obsolete ui artefact.This has been fixed by removing whole part on accounts settings pane.
Addressbookpicker parameters were changed to expect an object but UI only sends a boolean.Send full option object so only the global addressbook is shown again.
Moment renamed en-SG to en-sg.This has been solved by updating the locale lookup table to new filename.
This has been solved by adding specific mapping for fr_CA when loading help.
CSS selector for steps was too generic.This has been fixed by using id selectors for wizard steps.
Feature handles SSO case not as good as it could be.Moved all relevant parts into extensions.
This was caused by immediate loading of drafts on mobile.This has been solved by introducing lazyload for mobile devices.
Since the redesign the default was set to author right for folders and viewer rights for files.Solution: Changed it to default to viewer rights in all cases.
Missing max length attribute in text field, missing meaningfull error message.Add max length of 65535 characters. Add better error message.
When redrawing the default configuration was used all the time.This has been fixed by only using default configuration when no download is pending. Show requested modules instead.
UI did not check for error codes and kept requesting long running jobs.This has been fixed by removing jobs from queue for error code JOB-0002 so they are not requested anymore.
Was caused by a missing check for capabilites carddav / caldav.This has been fixed by hiding toggle buttons when carddav or caldav is missing.
This was caused by missing check for ‘permissions’ of folders ‘supported_capabilites’ property.This has been solved by adding missing check.
Class ‘mail-detail-content’ was added to body element while plain text mails still add a wrapping DIV with that class name beneath the body element.This has been fixed by adjusting selector to allow adding ‘Show entire message’ button again.
Was caused by missing differentiation between success and error state.This has been solved by idling dialog only when error was returned.
The launcher drop-down moved to the left edge of the top bar and received its own section name in CSS.This has been solved by adding the new section to the others where topbarHover is applied.
Multiple clicks on close button were possible.This has been solved by disabling buttons in window header when app is closing.
Flex shrink was behaving strangely for small devices.This has been resolved by removing shrink for some components.
Feature checks were not sufficient.Federated sharing text now also checks if filestorage_xox or filestorage_xctx capabilities are present. Onboarding wizard now checks for capability client-onboarding and if the setting for the new wizard is actually enabled (io.ox/core//onboardingWizard).
The error was handled twice although it occurs only once.The double handling of the error is unnecessary. The error is now displayed in the tab only and this can be closed with “close”.
Missing customization for what’s new feature list.This has been solved by adding extension point to customize this list.
Was caused by wrong references.This has been fixed by using right references.
Onboarding-hint-popover is shown automatically and visual anchor is hidden behind “whats new”.This has been solved by using Stage instead of Extension to show popover and ensuring popover does not “collide” with other steps visually.
Missing style for drive download button.This has been solved by adding correct style to drive download button.
Missing differentiation between user and contact.This has been fixed by differentiating between user and contact mapping.
Missing QR code support for eas.This has been solved by adding QR code support and MWB-1179.
Browser have different focus styles.This has been fixed by adding consistent focus style for all browsers.
Was caused by wrong capability check for drive apps.This has been fixed by adding capability check for drive capability to disable drive menu options.
Timeout was introduced with an old Bugfix.Differentiate between compose and settings-pane as caller. Compose still uses default timeout (15s) when calling snippets getAll. Settings pane does not use any timeout when calling snippets getAll.
Wrong parameter within the translation made the warning hard to read.Fixed parameters within Spanish translations.
Wrapping of elements were disabled.This has been fixed by simply wrapping actions in toolbar if not enough space is available.
Appointments were drawn before the ‘injectVirtualCalendarFolder’ was called.Now register change listeners for appointments with incomplete folder data to solve this.
Was caused by wrong calculation of offset.This has been fixed by adjusting offset calculation.
This has been solved by fixing a typo.
Warning was not added to baton and therefore not processed.Warning gets added to baton now.
Wording and button position not clear enough.Moved button “Save and apply rule” to the alternative position. Improved wording.
Missing convert of ‘\n’ to ‘br‘ when HTML is preferred mode for mails.This has been solved by adding missing convert of ‘\n’ to ‘br‘.
The file attachment sizes was not orderly advertised with the first request for forwarded mails. File attachment sizes was always rendered if a size is returned in the response.Solution: Orderly advertise size of attachments with first request for forwarded mails and only render file sizes that are larger than 0 B, otherwise don’t render them at all.
Capabilities were not used correctly, selectors were no longer valid and tour accidentally opened the chat app.This has been solved by adjusting selectors and capabilities and no longer open the chat app.
Wrong dirty check caused request that was not needed.This has been solved by fixing wrong dirty check.
The local time zone was used to render the timestamp in the filter rule.This has been solved by now using UTC for rendering.
Wrong selection of day with certain (work)week settings.This has been fixed by removing basic setting dependent .startOf(‘week’) and replace with startOf(‘isoWeek’) in addition to a small adjustment for choosing the correct day.
Focus was not set to list after action.This has been fixed by setting focus to next list item after action.
Button was drawn but not visible.This has been fixed by triggering ‘complete’ to adjust height again.
Settings were not updated and may contain old account name.This has been solved by updating settings correctly.
Event listerners were still listening on an old collection.This has been fixed by adjusting event listeners after folder rename.
Single and double clicks on the same element were competing and led to inconsistent behavior.This has been fixed by treating double clicks as single clicks on list elements in list layouts.
Timing issue with extension point and DOM events.This has been solved by explicitly updating token field view after all extensions have been executed.
Buttons were not enabled after dialog gets idle.This has been solved by setting dialog to idle also when cropped image can’t be loaded.
ForwardUnquoted was not recognized by plaintext editor.This has been solved by adding forwardUnquoted detection for plaintext editor.
Very old implementation of tokenlogin mech hard wired into autologin code.Refactor tokenlogin to be a dedicated login plugin which is running independend of and before the autologin plugin.
Option button was drawn in any cases (not checking any conditions).Remove option completely if user is not allowed to apply changes and remove option completely if user is not allowed to apply changes.
When loading the Mail Compose dialog in the mobile view it is possible that the mail quota has not been updated yet and therefore the default value is stored. This leads to the assumption that the mail quota has been reached.The method with which the mail quota is evaluated has been adjusted to solve this issue.
Move field telephone_company “up” to match edit form.
In rare cases when adding the start hours for “only working hours” mode can lead to wrong calculations due to different offset values.Mind the offset and add it if necessary to solve this issue.
Input not wide enough.Decrease spaces between inputs to make them wider.
Check doesn’t check for number of apps.
GET/POST generally added a ‘?’ to the requesting URL.This has been solved by removing needless ‘?’ for GET/POST requests when no url params a set.
Configured value for special “all messages” folder (through property “com.openexchange.find.basic.mail.allMessagesFolder”) is not a fully-qualified mail folder identifier. UI had a 300ms delay before disabling the select button in the folder picker. This allowed picking invalid folders.Don’t expect fully-qualified mail folder identifiers when performing a mail search. Remove 300ms delay in UI and implement failsave for invalid folders, so invalid folders should no longer be selectable.
Inconsistencies left over after last refactoring, typo in “Confirm new Password”.This has been solved by cleaning up behavior of labels and placeholders to be consistent with the username field, fixed “Password” -> “password”.
Added missing check for guest folder id (16).
Failed virtual folder “request” caused error and error handler failed as ‘error’ and ‘options’ were undefined.This has been solved by adding fallback for ‘error’ and ‘options’.
Feature were accidentally removed during refactoring.This has been solved by adding feature again.
Rights changed to viewer for guests without notice.Now give a notice to user when rights are changed.
Wrong data from external calendar source taken over as-is.This has been fixed by adjusting bogus all-day dates prior to storing event data from subscriptions.
A broken image link leads to failure of send/transport attempt.Solution: Don’t let failed image URI resolution prevent from sending a mail.
Whitespaces and tel schema in URLs aren’t detected and thus URL checks might be bypassed.Remove whitespaces and handle URLs correctly. Add the tel scheme to com.openexchange.html.sanitizer.allowedUrlSchemes.
Existent data export tasks silently deleted if associated user/context do no more exist.This has been fixed by not deleting such “orphaned” data export tasks when invoking listdataexports command-line tool.
Was caused by possible long-running Matcher.find() invocation.This has been fixed by adding fast plausibility check & introduced a timeout-aware matcher alternative that respects a passed timeout whenever matching the input sequence or finding a certain sub-sequence is requested to avoid possibly long-running matcher invocations.
Context names are checked case-insensitive for equality when attempting to change a context’s name and thus changing to the same context name, but different cases were considered as a no-op.This has been solved by checking case-sensitive for equal context names when attempting to change a context’s name.
No response status distinction for read-only operations in If-None-Match/If-Match checks.This has been solved by using HTTP 304 response during If-Match/If-None-Match checks for GET and HEAD.
Missing special handling for error codes that advertise actual transport succeeded, but append to standard sent folder failed.This has been fixed by adding special handling for error codes that advertise actual transport succeeded, but append to standard sent folder failed.
Wrong value inserted into guestCreatedBy field of guest users under certain circumstances.Ensure to reassign guestCreatedBy field to context admin during user deletion if no destination user specified.
Different generation of fallback attachment filename extension.This has been solved by using the common method to yield fall-back name with a reasonable file extension.
Unexpected trigger of update task for a schema that is currently checked for possible expired composition spaces.Skip clean-up of expired composition spaces for those schemas that are currently updated or need an update to solve this.
Sender’s full name for introduction in drive mail notifications escaped twice.This has been fixed by escaping sender’s full name for introduction in drive mail notifications only once.
Equal exceptions chained multiple times.This has been solved by avoiding chaining equal exceptions multiple times.
Inconsistent translation of ‘notes’.This has been fixed by adjusting translations.
Possible concurrent modification of storage objects is quitted with “HTTP/1.1 423 Locked” status response leading to abortion of request processing.This has been fixed by introducing retry mechanism with exponential back-off in case Sproxyd service quits request with “HTTP/1.1 423 Locked”.
Too many occurrences of low-level HTTP end-point pools for initialized Sproxyd clients.This has been fixed by adding cache for low-level Sproxyd HTTP end-point pools.
Intermediate clean-up task unexpectedly dropped file storage resources.This has been solved by not running clean-up task when there are currently running data export tasks.
One optimization was done: Resume reading an S3 object’s content when HTTP connection gets unexpectedly closed due to premature EOF (actually read bytes do not match advertised content length)
Clean-up task does only work for active users since a session is needed. Those belonging to inactive ones are not considered and might therefore remain.This has been solved by refactoring clean-up task for expired composition spaces to have a global task considering any open composition space.
The copy require was missing from the FILEINTO action command, hence the MailFilterService was generating the wrong require directive for the sieve script. The issue lies within the MailFilterService.getFilterRule when the method reconstructs the Rule object from the sieve script, i.e. the copy require is not added as an optional require.This has been solved by including the copy as an optional require for the FILEINTO action command.
Possible premature end of stream when reading a Scality object’s content.Gracefully deal with possible premature end of stream when reading a Scality object’s content.
RPM post installation script do not have information about the version from or to that is currently upgraded during post installation script execution. Therefore we have not been able in the past to write good post installation scripts that run only once. Today we have that and we can easily fix this issue.Run that part of the post installation script only once for each deployment.
try restarting transaction”.Follow the suggestion from MySQL server and repeat the user-copy execution in case an SQL transaction timeout is encountered.
Used same PayloadIdentifier for different users leading to profiles overwriting each other.Use unique PayloadIdentifier to avoid profiles for different users overwriting each other.
Possible “Missing attachment identifier in mail part” error when parsing draft mail.This has been fixed by avoiding “Missing attachment identifier in mail part” error.
Reset of participant status behaves differently then removing and adding of the same participant.When participant status is reset also remove hidden flag, so event is displayed for the attendee again (internal attendee). Also, send “invitation” notification (internal attendee) or iTIP (external attendee) mail to attendee with reset status.
Domains were applied to the existing rule object instead of the updated one.This has been fixed by applying domain checks to the updated rule.
Extensive logging of error afflicted file-storage accounts when performing a drive search.Adjusted log level of user-specific errors to “debug”.
Accessing a file during storage move signals file-not-found error although file list has been retrieved from storage itself.Pass an appropriate file-not-found handler if file listing was retrieved from storage, but accessing a file fails due to absence. This allows to perform checkconsistency to repair that.
E-Mail addresses without top-level domain part in address’ host-name part are considered as valid.Added new config option “com.openexchange.mail.checkTopLevelDomainOnAddressValidation” to enable top-level domain validation on E-Mail address validity check. By default that option is disabled to not mess-up existent installations.
oxsysreport does not consider Image-Converter configuration files.Let oxsysreport also collect Image-Converter configuration files.
Unclear requirement to run ‘deleteinvisible’ after downgrade, problem in database statement during downgrade.Added hint to ‘deleteinvisible’ in changeuser documentation, corrected SQL statement for folder deletions after downgrade.
Message’s delivery-status was not displayed.Now display message’s delivery-status.
Missing attendee data raised an exception when collecting deletions for userized result.Missing attendee data raised an exception when collecting deletions for userized result.
Password change not forwarded to cross-context database.Align guest reference in cross-context database after setting new password in “reset” dialog to solve this issue.
The alias is still supported but there was an issue with the implementation. For each soap alias a new servlet was created and registered but only the first one was filled with data.Instead of creating new servlets for each alias I registered the same servlet for each alias.
RestrictedAction.Type was missing from the getAttachmentAction.This has been solved by adding missing action type.
Final draft messages are not stored in appropriate account’s standard drafts folder.Final draft messages are now orderly stored in appropriate account’s standard drafts folder. Please note that storing intermediate draft messages associated with an alive/intact composition space are intentionally stored in primary account’s standard folder.See also: https://documentation.open-xchange.com/7.10.5/middleware/mail/mail_compose/01_drafts.html#mail-storage-utilization
com.openexchange.report.appsuite.storage.ContextLoader.getAllContextIdsInSameSchema(int, Connection) returns an empty abstract list if a schema has no results for contexts (see table context_server2db_pool).This has been solved by returning new ArrayList<> instead of Collections.emptyList().
Problems in the network stack of the underlying Hazelcast framework caused increased memory consumption and GC activities, eventually leading to nodes becoming unresponsive.Upgraded Hazelcast library to v5.0 where these kind of problems are mitigated according to Hazelcast.Introduced a new package open-xchange-hazelcast5-community which could be installed instead of open-xchange-hazelcast-community.
Repeatedly loading of resource files for JavaMail providers and address map.Solution: Cache loaded resource files for JavaMail providers and address map (reset cache on reloadconfiguration).
Multi-mime-encoded header value wasn’t properly decoded.Now properly decode a multi-mime-encoded header value.
Behaviour of the ApachePostRequestBuilder changed during lib upgrade.Restore old behaviour.
Broken encoding for standard google account nam ein slovak.This has been solved by using UTF-8 encoding instead if ISO-8859-1 encoding for the display name when creating the callback URL for Google.
Missing option to automatically convert login info to lower-case.This has been fixed by introducing boolean property “com.openexchange.authentication.imap.autoLowerCase” (default is false) to specify that login info is supposed to be automatically converted to lower-case when attempting to authenticate against IMAP server.
Folder of external accounts are not supposed being translated, but external account’s Inbox folder was.Avoid translate name for an external account’s Inbox folder.
In case a calendar user appears multiple times in the attendee lineup, a folder existence check may fail due to selecting the false one.This has been solved by considering further alternatives when checking if event is rendered in folder or not.
Generated SAML id is a simple UUID with possible digits, but SAML ID must not start with a digit.This has been solved by prepending a single character “a” to the ID.
Optimization: Avoid using regular expression to split HTML content to lines and fixed possible NPE when querying available composition spaces.
The exception’s display message was exposing internal Cassandra infrastructure information.Adjusted the exception’s display message to hide that information.
EAS support was missing.This has been solved by adding EAS support.
Userization of delete exception dates not working properly for event series in public folders.Solution: Don’t userize change- and delete exception dates for events in public folders.
Possible failed CREATE commands silently swallowed.Orderly advertise possible failed commands to client while considering possible IMAP response codes (like “[LIMIT]“).
Misleading documentation.Added a note to the documentation that explains that the image is not supported in the core UI.
Used always com.openexchange.x as a payload identifier.Use the reversed domain as the payload identifier.
Found paths in IMAP-IDLE backed push implementation for which notifications are published w/o providing basic message info (like subject).Always provide basic message info when publishing notification to solve this.
“<>” was not detected as empty address header.Better detection for missing or empty address headers.
Wrong package in mail authenticity config documentation.This has been solved by using correct package in mail authenticity config documentation.
Missing safety checks prior folder display name template replacements.Solution: Additional safety checks prior folder display name template replacements, added logging if replacements are unavailable.
Possible null dereference when dropping a standard mail folder.Fixed possible null dereference when dropping a standard mail folder.
All-day appointments were not considered during recurrence id normalization.This has been solved by considering all-day appointments.
A very old bug still causes problems, so a security mechanism in the code doesn’t work as expected.Re-enable a self-healing mechanism of fix for bug 19128 and adjusted the code to avoid bug 55703.
Moby naming shipped with v4.x introduces human-friendly names for the Hazelcast instances to be shown in e.g. the Hazelcast Management Center and cluster statistics. It is enabled by default.Disable moby naming when programmatically compiling the Hazelcast configuration.
Static build URL used HTTP and not HTTPS.This has been fixed by preferring HTTPS URL and only retry with HTTP if the forceSecure flag is set (over HTTP API). Also, log a warning if HTTP is used.
Was caused by a NPE while sorting display names.This has been fixed by adding null guard and by preventing null values.
Was caused by broken update task dependencies.Has been solved by fixing update task dependencies.
Incompatible timezone identifier gets cached along with overridden instances, which causes problems when re-loading the data from the cache.Normalize recurrence identifiers prior processing events from external iCalendar source to solve this.
Content-dependent identifier for onboarding profile names were accidentally cropped.This has been fixed by re-adding content-dependent part to profile display name.
Priority not kept when restoring a compose window from formerly saved draft message.This has been solved by keeping priority when editing draft messages.
Filenames containing dashes confused the fulltext index tokenizer.Solution: OX Drive searches for files with “exact-match”, ignore fulltext index for those requests.
Remaining whitespace in tokenized query after non-word characters have been replaced.This has been solved by trimming pattern after replacing non-word characters in client-supplied token.
Wrong sequence number chosen while trying to apply attributes to shared Drive mail attachments.Fixed applying attributes to shared Drive mail attachments.
Listener could not be registered on a certain since there is already such a listener available in cluster, but registration at Dovecot side might no more be active.This has been solved by ensuring registration is set at Dovecot side when there is already a Dovecot-Push listener available in cluster.
Insufficient PROPFIND handling when querying files: Detection of whether the returned resource is a collection or not was done by checking for a trailing “/” character.Added “resourcetype” prop to the PROFIND query which will return whether the resource is a collection or not.
Iteration of checked event series begins too late.This has been solved by considering duration when initialize recurrence iterator for conflicting series events in checked period.
Too low settings for HTTP connection pools for both - auto-config server and ISPDB end-point.This has been solved by increasing settings for HTTP connection pool of both - auto-config server and ISPDB end-point - while lowering values for read and connect timeout.
Generic error returned when vCards exceed the maximum size during bulk import.This has been solved by explicitly handling too large vCard during bulk import requests.
SMTP host information advertised as “None” in case SMTP authentication is disabled through configuration.Now do not advertise SMTP host information as “None” in case SMTP authentication is disabled through configuration.
Possible java.lang.StringIndexOutOfBoundsException when trying to decode subject string obtained from ENVELOPE fetch item.Fixed possible java.lang.StringIndexOutOfBoundsException when trying to decode subject string obtained from ENVELOPE fetch item.
No fallback access used when collecting pending alarm triggers from disabled accounts.This has been solved by using fallback access when collecting pending alarm triggers from disabled accounts.
Missing section highlighting that a data export is a background task and should be handled as such.Added a section highlighting that a data export is a background task and should be handled as such.
Missing log message for failed authentication attempts against primary mail/transport server.This has been solved by adding logging failed authentication attempts against primary mail/transport server.
Premature cancellation of HTTP request leading to HTTP connection shutdown.Avoid premature cancellation of HTTP request leading to HTTP connection shutdown.
Lock entry not cleansed from database in case temporary database outage/inaccessibility occurs.This has been solved by enhancing acquired lock by a time stamp that gets periodically touched (every minute). Consider lock as expired if not touch for more than 5 minutes.
From address determined by examining user’s primary mail account data.Solution: Orderly pre-select user’s default send address when composing new mails.
Guest user handling was not perfect.This has been solved by improving guest user handling:1. When a guest user inserts a mention into a comment, the follwing text appears in the bottom of the comment: “You added people to this comment. Attention: Due to missing permissions no email will be sent!”2. When the guest user sends the comment, the dialog with the information, that no mail be sent, does not appear anymore.
Inserting PRIMARY keys more than once during IC server job proccessing gives DB server exceptions in some timing dependent cases. Inserting PRIMARY keys more than once during IC server job proccessing gives DB server exceptions in some timing dependent cases.Solution: Preventing mutliple access to PRIMARY DB keys fixes the problem with IC server DB communication. Replacing the emulated file storage update call (setFileLength(0)/appendToFile) with sequences of createNewFile/updateDB entry in every case within the IC server code base fixes the inconsistent SproxyD adapter behavior.
Missing sizing information on related Ox provided IC documentation pages.This has been solved by adding sizing section to IC documentation.
Creating the missing settings entry “portal//recents” deletes the existing settings entry “portal//fulltour/shown” causing the tour to start again.Now, when starting a portal app, the missing property “portal//recents” will explicitly be created in frontend code and sent to server.
Images with quite unusual width/height aspect rations (3.8 h/w / 0.26 w/h in this case) get too much distorted when scaled into a target rectangle so that e.g. text rendering within the target image gets distorted/unreadable after processing. Checking aspect ratios for source and target images for unusual ratios above 21:9 (2.33) when scale type CONTAIN is requested and w/h aspect ratios of source and target image differ significantly (e.g. source w/h > 1.0, target w/h < 1.0 and vice versa).Prevent scale processing of images completely in those cases so that as much source image information as possible gets transferred to the requester/browser as possible. This significantly improves readability of e.g. text like content in such images delivered to the frontend .
After configuring test system appropriately, exception logging (with appropriate description now) could be reproduced when viewing mail attachment documents. Instead of using a different algorithm to determine document URL, the standard file based approach was used that finally led to the exception logging without causing further harm.Solution: 1.) Removing newline within log output to log root cause of exception. 2.) Using different approach for mail attachments to determine document URL to be used in RE rendering stage for e.g. file fields. Schema used in mail attachment case is now: file:///Mail/filename
Exiting loop for tool bar expansion too early. After unhiding and unshrinking, but before maximizing the groups.This has been solved by not leaving toolbar expansion process always after unshrinking. Only, if this is required.
The filter cannot evaluate type ‘auto’ for text colors in shapes (Presentation and Spreadsheet, ooxml).Instead of sending ‘auto’ when the user selects ‘Auto’ as a text color, the best text color is evaluated corresponding to the shape background. This calculated color is sent to the filter.
When an image is inserted via the buttons in template drawings, the mousedown happens on the content root node, but the mouseup does not. But these events are registered for an optional scrolling. Therefore the scroll position was not correctly adapted, when the user changes the slide using the slide pane and does not click at least once into the document after inserting the image.Now checking the target nodes for mousedown and mouseup events that are required for scrolling.
Document was not flushed before the copy was created in Drive. Flushing causes to save all pending changes which, in Spreadsheet, includes to commit the cell edit mode.Flush document before starting to copy the file in Drive for user actions “Save As” and “Save As Template” tto solve this issue.
Templates contained more than 5 different languages on XML level.Fixed on XML level, replaced all (western) lang attrs to be only en-US for EN templates, de-DE for DE templates.
The files are not visible because it’s not possible to open the attachements in documents. Hide the attachments folder to not confuse the user
Global templates are not helpful with com.openexchange.capability.alone = true.With com.openexchange.capability.alone = true, global templates in office settings are not displayed anymore for users and also not for admin user.
Print as PDF did only work for Office files and PDF files. Enabled that images can be printed via “Print as PDF” too. Plain .txt files are enabled now, too for “Print as PDF”, which was also not possible before.
The whole list is loaded for a Viewer deeplink. For such big folders, the data can get very big (for 60k files it can be about 30mb). Even the transfer via a typical DSL connection can take a big amount of time. The next reason is that the viewer creates boilerplates for each item that is passed to the Viewer carousel. This adds a additional slowdown.When using a Drive Viewer deeplink (url pasted in the tab), now the Drive list for this folder is used. Instead of loading the whole file list for that folder with a new request. One further advantage is that the order in the Drive list and the Viewer carousel is the same (below the pagination limit). When the to be viewed file is outside of the pagination limit of the Drive list, this single file is added to the viewer carousel in addition.
PDFTool does not return at all with some rare, yet unknown PDF documents.Now we introduced a maximum runtime for each call to the PDFTool (similar to watchdog for RE processes), returning an error after the configured jobExecution timeout time and responding to the appropriate request in time.