This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal


Oct 6, 2017, 2:22 PM
33 Posts

Invitation Field "ChairDomain"

  • Category: Calendar
  • Platform: Windows
  • Release: 9.0.1
  • Role: Administrator
  • Tags:
  • Replies: 4

Hello,

Can anybody explain, when and why the field ChairDomain is calculated in an invitation? Does it have a maximum length?

I have a case, in which the field "Chairdomain" is calculated but cut off after 32bytes. This results in delivery failures, when an attendee tries to accept the invitation. (no route found to %destroyed domainname%)

I was not able to reproduce the error in a test environment. The field is not even calculated - let alone cut off. Both domains (chairs and attendees) are connected via notes over several hops (adjacent domains).

Regards,

Manuel

Oct 7, 2017, 2:37 AM
34 Posts
Some answers and 2 questions
ChairDomain is not really used by the Notes C&S code.  It is primarily used in the template for display purposes although the core code will give preference to it over the FromDomain if it is there.

The maximum length a Domino Domain name can be is 32 characters so the max length we allow in the ChairDomain is 32.  There were a couple cases where the code was not handling 32 character domain names properly and truncated the values to 31 characters.  This has been fixed in recent builds.  The issue and fix info can be found under SPR SOKEAHZS6T.  

If you are calculating the value for ChairDomain and it is over 32 characters then you need to adjust your formula to give you shorter domain names.

If you are simply going between adjacent domains, why fake out a ChairDomain at all?  Why not simply use normal mail routing items like FromDomain?

Bruce
IBM
Oct 9, 2017, 3:49 PM
33 Posts
We did not change it AFAIK

Hi Bruce,

Thank you for your thoughts.

The field does contain the first two hops (of four) of the routing path. With this it is quite easy to get over 32bytes. We do not use the Chairdomain field for the response by choice. There are no changes to the code. I cannot find any reference to the field within the Databases code. I thought that must be hardcoded to Notes or Domino.

Currently the sender has an non-adjacent domain doc with target: "*" - Next Domain: %NextDomain% and the %NextDomain% "should" have another adjacent and so forth. But for testing purposes I asked the admin of the source domain to create an non-adjacent domain for "My" Domain like this: Target: %MyDomain% - Next Domain: %NextDomain% this does not change anything - it still creates a defective ChairDomain field.

Today I asked the admin to send a test invitation to me appending the complete routing path to my address: Manuel Nientit/MyOrg@MyDomain@MiddleDomain@MiddleDomain@NextDomain and it worked (of course) without chairdomain field.

So the "ChairDomain" field is  created when the path is not the to field. But still: the path has been found.

FromDomain does not exist...?? I am lost.

Thanks a lot,

Manuel

Oct 9, 2017, 4:19 PM
326 Posts
Changes

Was the Domino server upgraded?  Maybe revert back to what code you had and see if that fixes the issue? Is it possible to have  connections docs to every domain rather than routing through other domains?

Oct 16, 2017, 7:13 AM
33 Posts
Little influence

Hi,

The sender and we are in an association of companies and are connected via an IT-Service-Provider for most of them. I do have little influence on the way servers are configured and updated.

I am working with the senders admin to test some things and maybe we could change the configuration if we knew how to do that. But that is about it.

Thanks anyway,

Manuel


This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal