fighting for truth, justice, and a kick-butt lotus notes experience.

HCL Traveler 14.0 released

 Dezember 8 2023 09:11:18 AM
HCL Traveler 14.0 is a feature release, that includes new features and bug fixes for the Traveler server.

Traveler 14.0 can be used to install a new Traveler environment or update an existing Traveler environment running Domino 9.0.1.x, or Domino 12.0.x without requiring a Domino upgrade
.

(Although it is always recommended to keep Domino at the latest level.)


Database Schema


Traveler 14.0 does include a database schema update to Database Schema Level 20230417.


Updated APNS Certificate for iOS


The download package includes an updated APNS certifiacte valid until November 14, 2024.

For older Traveler versions, you can download and update the APNS certificate manually. Take a look at  
https://my.hcltechsw.com/downloads/domino/traveler/14.0 where you can find a Traveler_APNS_Prod.zip file.

New Features


Clear the sync anchors for a device from the Traveler home page

If enabled by the administrator, the Traveler home page provides a set of commands that the user can execute for the user or the user's devices.
New to this release is the option to clear the sync anchors for a user's device(s). This is a light weight option to trigger a device to resync the data (mail, calendar, etc).

Verifying the Traveler mail file replica list

Traveler maintains a list of mail file replicas in the Traveler database.
This list is dynamically built from the information in the cluster directory and, in the case that the mail file algorithm requires mail files to be local (e.g. NTS_MAIL_SERVERS_ALGORITHM=LOCALONLY), mail files detected on the traveler servers.
A new form of the Bind command, verifyLocalOnly has been added to verify the accuracy of the list of replicas for a user (or all users) and ensure that users are bound to a traveler server with a mail file replica.

Security improvements to the Traveler home page

Inline CSS styles and JavaScript were removed from the Traveler home page to support a more secure Content-Security-Policy header.
Environments with an existing Content-Security-Policy header set for the Traveler home page should remove the 'unsafe-inline' values of the style-src and script-src policy directives and set them to 'self' instead.

Fix List

KB0103688

Smart Forward/Reply: Rich Text mail attachment for Forward/Reply without attachments has image and broken content
 

KB0104294
Unable to deselect devices in Device Security view in web-based administration (lotustraveler.nsf)

KB0104467
User locale based values such as date formats may be incorrect if the HTTP Accept-Language header name is not exactly Accept-Language

KB0106643
Message with non existent product name in Czech

KB0107519
Traveler replica information is missing or incorrect; bind verifyLocalOnly enhancements

KB0108246
Smart Reply or Smart Forward to a mail with Content-Disposition header on the original mail causes SMTP error

KB0105587

Do not assume a Traveler server has a local mail replica if the Traveler server is unreachable


Details:
https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0103462


Kommentare

1Dominique Perarnaud  12/08/2023 10:26:49 PM  HCL Traveler 14.0 released

These APNS .p12 certificates expire on November 14, 2024.

2Detlev Poettgen  12/09/2023 4:10:38 PM  HCL Traveler 14.0 released

Thank you Dominique,

I corrected the expire date.

  •  
  • Hinweis zum Datenschutz und Datennutzung:
    Bitte lesen Sie unseren Hinweis zum Datenschutz bevor Sie hier einen Kommentar erstellen.
    Zur Erstellung eines Kommentar werden folgende Daten benötigt:
    - Name
    - Mailadresse
    Der Name kann auch ein Nickname/Pseudonym sein und wird hier auf diesem Blog zu Ihrem Kommentar angezeigt. Die Email-Adresse dient im Fall einer inhaltlichen Unklarheit Ihres Kommentars für persönliche Rückfragen durch mich, Detlev Pöttgen.
    Sowohl Ihr Name als auch Ihre Mailadresse werden nicht für andere Zwecke (Stichwort: Werbung) verwendet und auch nicht an Dritte übermittelt.
    Ihr Kommentar inkl. Ihrer übermittelten Kontaktdaten kann jederzeit auf Ihren Wunsch hin wieder gelöscht werden. Senden Sie in diesem Fall bitte eine Mail an blog(a)poettgen(punkt)eu

  • Note on data protection and data usage:
    Please read our Notes on Data Protection before posting a comment here.
    The following data is required to create a comment:
    - Name
    - Mail address
    The name can also be a nickname/pseudonym and will be displayed here on this blog with your comment. The email address will be used for personal questions by me, Detlev Pöttgen, in the event that the content of your comment is unclear.
    Neither your name nor your e-mail address will be used for any other purposes (like advertising) and will not be passed on to third parties.
    Your comment including your transmitted contact data can be deleted at any time on your request. In this case please send an email to blog(a)poettgen(dot)eu

Archive