iOS New Calendar Appointments Not Parsing Names to Emails Correctly

Mindwatering Incorporated

Author: Tripp W Black

Created: 11/26 at 10:41 PM

 

Category:
Domino Server Issues Troubleshooting
Traveler

Issue:
Emails on iOS devices suddenly stopped working after reboot.
Other than mail template updates, no changes have been made in months since Traveler upgraded from a R12 point release to the latest R12 point release to also get the APN apple certificates.
We are currently running: 11/26/2025 11:02:43 PM Traveler: Traveler 14.0.0.2 Build 202502121820_30

Symptoms:
The calendar invite email is seen in the Sent folder, but the emails have incorrectly translated to Notes name addresses. However, the iOS client isn't sending/performing the new API request to send the mail message.
Worse, the current user is no longer the chair and had no control in the Notes client to manage the calendar entry except as a participant.
Worse, the iOS device when deleting, doesn't remove the calendar entry from the calendar in the Notes client.

It appears the issue should be related to the last Traveler patch.

Example:
Principal should be: Tom Testor/MWNet
Principal value is incorrectly: "CN=Tom Testor/O=MWNet"<CN=Tom%20Testor/O=MWNet>
INETPrincipal is also incorrectly: "CN=Tom Testor/O=MWNet"<CN=Tom%20Testor/O=MWNet>

This is what is causing the owner/chair to be just a participant instead.


Solution:
Even though we migrated from HCL Traveler 11.0.1 to 12.0, and later, 12.0.2 over several iterations, we didn't think the following notes.ini would matter but we tried it set to default:
NTS_AS_SEND_NOTICES_FROM_MAIL_SERVER=false
... and then tried it again, not to default (true, to do the old way through the mail server) ...
NTS_AS_SEND_NOTICES_FROM_MAIL_SERVER=false

After restarting HCL Traveler service, this did actually cause the invitations to route through the mail server, but then the current user doesn't receive the mail invitation at all. It dies in the router as being an invalid Notes Name/email address - which it is very invalid. We also had failed transfers for the invitees as well.

After further fruitless testing, we returned and noticed another entry was not the default value. The notes.ini below was set to false. So we set the entry below to true, and set the notes.ini above back to its default value, as well.
NTS_ADDRESSCACHE_ENABLED_DEVICE_2_SERVER=true

To sum up, the follow values restored the Traveler server's functionality again:
NTS_ADDRESSCACHE_ENABLED_DEVICE_2_SERVER=true
NTS_AS_SEND_NOTICES_FROM_MAIL_SERVER=false




previous page

×