This week has been released another version of midpoints Let’s Encrypt 4 Domino v2.2.0 .
This versions includes an updated LetsEncrypt agent. Let’s Encrypt introduced a change for there API, which requires an update on our side. You will have to upgrade to v2.2.0 until November 2019 to keep LE4D working.
Can a user find out which version of Verse On-Premises is used to access their mail database in a browser? Yes, but it’s not quite user friendly. Someone would look for it somewhere in “About”, but you need to click a little more.
I have therefore created a new post in the Product Ideas Forum for which you can also vote LINK
I found it in the HCL knowledge database:
To determine which version of the Verse On-Premises is being used, you can examine the “build-number” in Verse. The “build-number” tag is an identifier that is unique to each Verse On-Premises version.
To view the “build-number” number you should:
Open Verse in your browser and right click on mouse to select the option: “Inspect”
Go to the “Console” tab and find the line that includes the word “Current Build”.
Use the table below to determine which Verse On-Premise version is currently in use.
Verse On-premises version
16838-458 *Note this is the same as 1.0.5 as the client code has not been updated*
Traveler 10.0.1 FP2 installation package is available on Flexnet. HCL Traveler Documentation – LINK
What’s new in 10.0.1.2?
Updated APNS p12 certificates to replace the files shipped with IBM Traveler 10.0.0 (expire on October 14, 2019). These new certificates expire on June 07, 2020.
Knowledge Base – Customer Support
If a Mail-In Database name has a slash in it, the name returned from the lookup includes CN=, OU=, O=, etc.. Trim these identifiers before returning the lookup result to the client for a more human friendly display.
If a Group name has a slash in it, the name returned from the lookup includes CN=, OU=, O=, etc.. Trim these identifiers before returning the lookup result to the client for a more human friendly display.
Update device security record modification time when device approval action is executed so that the security record is returned by API searches for recently changed security records
Unable to open email attachments in Apple mail client or Verse mobile client for certain type of attachments (example, xlsx file types)
Timing gap between stale connection cleanup and connection registration can cause “Traveler did not respond” errors in the console. The gap is small such that this error is rare, so most “Traveler did not respond” errors are caused by some other reason.
Traveler hang due to MISC threads all being orphaned when S/MIME is enabled for large non-S/MIME messages.
Red status due to User null on thread Alarm-XXXX has been running for XX minutes
EMails restored from archive via iNotes do not sync to device
Improve banned document handling for calendar events
Improve mail streaming performance when MIME-version header missing
Add configuration option, NTS_CALENDAR_INITIAL_GHOST_NOTES_ICS, to prevent ghosting and avoid replication issues for notices created by opening .ics email attachments.
Windows 10.x installer doesn’t remove uninstall entry for 9.x or earlier
Attachments are stripped from plain text mails sent from IMSMO clients
Content Adapter Exception processing Event with Body of type=Text
A draft mail created on Verse iOS defaults to $KeepPrivate=1 when synchronized with the user’s mail file
Allow login name checks to be case insensitive so that user renames that only change the case of some letters also work properly.
Prevent objects over MaxObjSize from syncing on every subsequent sync until deleted, moved to a non-syncing folder or filtered out
tell traveler version reports “running on a VM” when running on real hardware
Improve error handling when schema level is unknown
Performance: avoid reading attachments multiple times during MIME message processing
DB Schema change: Increase the width of the Traveler database’s Exchange ActiveSync version column used to store the protocol version when the device is not security compliant
Update APNS p12 files that expire in October 2019
Pushstatus APIs added in V10.0 are now reported in the output from api/traveler
Although already mentioned, I add this important information to my website. Starting with HCL Verse 10.0.7 for iOS (when it is available), the application is now transferred to an HCL Technologies Apple account and is signed by an HCL-owned certificate.
Expect the following changes:
The Verse application is being rebranded to HCL Verse. Not all references to IBM have been removed in this release.
The Verse application will no longer be able to access any data that the previous IBM signed versions had stored on the keychain. Therefore, you will be prompted for your password after you upgrade to 10.0.7 and launch the application for the first time. If you choose to remove an existing version and then install 10.0.7, then the user will be required to reconfigure the client. This is not a change in behavior. However, for reasons stated below, we recommend you upgrade over your previous version of the Verse application. Note that the same applies when upgrading from the IBM ToDos application to the HCL ToDos application (when available).
The device ID generated by iOS will change (clients managed by IBM Maas360 and MobileIron are not affected). Moving to the HCL account caused a change in the development team ID for the IBM Verse application. This team ID is input to the Apple API that the application uses to generate a unique device ID. The result is a different device ID which will be used when communicating with the Traveler server (in the form HCL_IOS_xxxxxxxxxx). After installing 10.0.7, the client application will look like a new device to the Traveler server. You can see your new device ID on the About screen under Verse settings, the user’s Traveler home screen or in the Traveler Administration view.
A new device ID will have the following effects:
After you install 10.0.7 (either new or as an upgrade), the device will re-sync because Traveler treats the device as a new device because of the device ID change. You will see all mail in the all folders disappear and then start to re-populate. There is no way to avoid this re-sync, so plan accordingly.
A new profile document will be created for the new device ID (HCL_IOS_xxxxxxxxxx) by the Traveler server. This means all your preferences (things like days to sync, signature, etc) will be set to the defaults. However, if you take the recommended approach of upgrading (installing 10.0.7 over the top of a previous version), the Verse application will recognize the previous install and push all of your local preferences up to the server so that the new profile document is populated with your device preferences rather than the defaults.
If device approval is enabled on the Traveler server, the IBM Verse client may need to be re-approved depending upon the automatic approval settings.
The old device id (IBM_IOS_xxxxxxxxxx) will appear in the user’s device list until it is either reaped by the Traveler Server due to inactivity or deleted by the Administrator
The user may see duplicate notifications on the device for a period of time, typically 24 hours from the upgrade, because both the old and new device IDs are active on the server. There is no way for the new application to tell the server to stop sending notifications for the old device ID. After that period, the Traveler server will mark the old device as offline and stop sending notifications to the old device ID.
IBM Verse for Android is not affected by this change.
You may not see the option to open an archive database after upgrading to Verse On-Premises 1.0.8.
If you have a “simple” solution where you have a manually created archive DB of your mail (without applying the policy), you probably won’t see this new option to open it to the VOP as described here LINK.
I solved this issue with HCL support and this is a bug on which request VERSE-57616 was created.
There will be a VOP 1.0.8a deliverable in the coming weeks that will include the fix for this issue.
The bug is due to the fact that the code was expecting there to be an Archive Settings policy document assigned to the user. If there was no archive Setting policy document assigned to the user, VOP would not show any archives. You can work around this issue by assigning an Archive Settings policy document to the user.
The beginning of September is really hectic. HCL is rolling out news with us starting with Beta V11, FP3 for V10.0.1, Verse On-Premises 1.0.8 and Domino App Dev Pack 1.0.2.
In addition, we are still faced with various problems related to the products transer from IBM to HCL.
The positive thing about all of this is that something is happening and HCL has been keeping the promised deadlines and news ahead of time. We are still waiting for the Beta Nomad for Android. But I think we have enough toys.
FP3 for Notes / Domino 10.0.1 is available. Starting with IBM Notes/Domino 10.0.1 Fix Pack 3, downloads are now available from HCL. FP will no longer be found on IBM FixCentral. Here is a detailed description: LINK
SPR# DLIMBDWQXW – Fixed a problem where the Notes client would hang on exit when Replication on exit was enabled. This regression was introduced in 9.0.1 FP10.
SPR# JALAB6SRRH – If EnableThreeClicks ini is set to 1, user will be required to enter three clicks for opening attachments and URLs, as mandated by the EU. This option is off by default.
SPR# VRARB6GJCZ – Fixed a problem in the Notes client where Widgets would not work. This regression was introduced in 10.0.1 FP10.
SPR# ZNDNBC8H3E – Fixed a Notes client crash on Windows 10 V1809 whenever the user tried to remotely connect to their machine via Remote Desktop Protocol.
SPR# DOKEATLHV9 – Prior to this fix, the failover error “Remote system no longer responding” was shown on send-mail action when the primary server was down.This is specific to SCN.
SPR# SSARBD4J84 – Fixed a problem in the Notes client where, if the Notes preference Open each document in new window has been set, the first window opened cannot be closed. This regression was introduced in 9.0.1 FP10.
SPR# KSOAB5MM66 – Fixed a problem with the Notes calendar where setting the body text to any proportionally spaced font then reopening the saved calendar entry would result in the body text having been changed toDefault Monospace font. This regression was introduced in 10.0.
SPR# SMEAB94AYW – Fixed a problem where the Notes client would hang when using a particular widget.
SPR# RGANBBABED – Fixed a problem in Xpages in the Mac Client where an error 500 page was being displayed when trying to launch an Xpage app. This regression was introduced in 10.0.1.
SPR# RPAIBC5J2Y – Fixed a problem in the Notes client where certain SMIME messages would crashing when being opened
SPR# SSPLBCSJ2B – Mac client now has an updated version of the JVM – 1.8 (IBM) SR5 FP30
SPR# AGUD87CN4P – Fixed a problem where the LotusScript Split function would produce incorrect results if the delimiter contained two of the same character.
SPR# JCORBDBPYA – LotusScript JSONElement.value property truncates the LotusScript string when the value is greater than 64K. Fix provides for complete return of a JSONElement value string.
SPR# JCUSB9JL8B – DQL: Fixed a problem where DQL did not recognize a query that contained DBCS characters.
SPR# RDOLB9734S – Fixed a problem in Domino Designer where editing and saving LotusScript agents in would sometimes hangs when “Run in background client thread” was enabled.
SPR# TOCLBC7MGL – Fixed a problem in Domino Designer where Xpages would no longer work after opening/closing a form if LibreOffice (v6.2) was installed. This regression was introduced in 10.0.
SPR# GFALBCFAK3 – Fixed a problem with DAOS resync where deletion and copy style compact were not possible after DAOS resync due to an error “File is in use by another program”.
SPR# GRHEBBCS5X – Fixed a problem where Symmetrical cluster created a folder when doing a repair even if the directory in the path was a directory link
SPR# KKHOBCGF8H – Fixed a problem where, when creating new replicas (where the target replica is a stub), if a corrupt folder note exists in the source database, replication might retry replicating the corrupt folder note and not complete. This regression was introduced in 10.0.
SPR# MNAA9K9ANA – Fixed a problem where Xpages documents would not show an inserted image if an attachment had been uploaded to the document. The MIME data type was not getting set to Content-Type:multipart/related
SPR# MSKABBZH3L – Fixed a problem where Adminp was failing trying to create replicas of large databases (250gb) on large disks (2TB). It would incorrectly state there was insufficient space. The workaround is to create the replica directly in the UI and not use adminp. This issue has been corrected. This regression was introduced in 10.0
SPR# PLYSBCPKCP – Fixed a problem in the Domino SMTP server where a non-ascii internet message address phrase lost its encoding when being stored in a Notes item. This regressoin was introduced in 9.0.1 FP10.
SPR# RPAIBA9JUZ– Fixed a problem in QVault tool where too much logging information was being output by default. Logging now requires notes.in DEBUG_IDV_QVAULT=1 to be set.
SPR# SAZR9REQ9R – Fixed an intermittant crash on Domino server making outbound LDAP search requests. This is most likely due to an edge case network error condition.
SPR# STAAB6A5GX – Fixed a problem in the Domino server where the Tika java process was not being shutdown when the update task was restarted.
SPR# DVDIASU9A3 – Fixed a problem in the HTML Parser where the router would sometimes hang while processing styles.
SPR# JPAIB6ZLKG – Fixed a problem with the Domino server where the Java Tika process was not terminating cleanly on Domino server shutdown on non windows platforms
SPR# PKURBBX6QK – Fixed a problem where ampersands contained in an LDAP filter attribute value were inadvertently being escaped in filters which were not being sent to IBM Directory Server LDAP. This fix causes the ampersand to be escaped only in filter attribute values being sent to an IBM Directory Server. This regression was introduced in 9.0.1 FP8.
SPR# RSTNB6GC7D – Fixed a problem where dbmt did not terminate when running with -range option and loaded at server startup. This was causing dbmt to not process databases when the next time the specified range came around.
SPR# MSAHBC92RS – iNotes: Fixed a problem in iNotes where, using IE, the Notes ID management dialog box became blank after the internet certificate was imported.
SPR# SLODAN59R7 – iNotes: Fixed a problem where hyper links in the mail body were truncated if the URL had spaces. This regression was introduced in 10.0.
SPR# TPONBBYCME – iNotes: Fixed a problem where the mail body contents in bidirection environment didn’t appear in the correct direction.
SPR# RMTGB7NEX2 – iNotes – Fixed a problem that hyper links in mail body did not work if the URL had spaces – the spaces were truncated. This regression was introduced in 10.0.
The Product Ideas Forum for Domino, Notes, Verse, Sametime, Connections has been available for a long time. This is the place where you can submit your product ideas and enhancement request. You can participation by voting on, commenting on, and creating new ideas.All new ideas are evaluated by HCL Product Management & Engineering teams. Some user ideas have already been included in the new versions, some are in the solution.
So you can be co-creator or visionary of new functionalities, new versions. You may be part of the new #dominoforever era.