I have setup Connections Self Registration for a few customers now using a separate Domino address book within an existing Domino Infrastructure and Domino LDAP as the source for the registered users (HCL helped out with my original one of these via support to get this working using this config). All works fine with regard to the registration and Connections which is why I have deployed this out, however it looks like there is an issue with doing this because when a user now tries to email from notes to one of the self registered users it fails.
The reason it fails is that the user doesn't have a mail file set in the address book. Well this is true as it is an external user. When self registration sets up the person documents it sets them up as below which I can see no real control over:
user name: richard.dew_at_bloggs.com/Acme-Ext
MailSystem: Other
Domain:
Other Address:
Internet Address: richard.dew@bloggs.com
So as you can probably see the issue is that it creates the entry as MailSystem Other and Domino is reading the username field and picking up on the /Acme-Ext and it thinks that this is a Domino user and doesn't try to send the mail out over the internet it tries to route it internally and then fails.
If I manually change the MailSystem to other Internet Mail and set the forwarding address to the same as the internet address this obviously then works fine but this is not feasible to have to change this each time as it makes the self registration model obsolete.
Has anyone else setup self registration with Domino and found the same problem or managed to get round this as its starting to cause a real problem.
Hi Richard,
We're taking a look at your question as a team and will get back to you shortly.
Thanks,
Wes
Hi Richard,
Thanks for the question - you could theoretically replicate the behavior completely outside of Connections by manually adding the same style of Person Document into your Domino name and address book. Then it becomes a question of your mail routing setup.
We checked with the Domino mail routing team, and they performed a quick test where only the forwarding address was populated and the internet address was left blank. This allowed mail routing to process. They also provided the following reference on Domino mail routing:
https://help.hcltechsw.com/domino/10.0.1/admin/plan_thedominodirectoryandmailrouting_r.html
From the Connections standpoint, you can configure selfregistration-config.xml to use whatever attribute you want for mail, so it would be possible (though we have not tested this specifically) to use the forwarding address as this target value. However, we're not yet sure of the ramifications of doing so (why would you not have an internet address? Why wouldn't Domino route based on having an internet address? Is there a Domino configuration change that would permit routing based on this alone?) and are not yet making this recommendation. A full investigation and recommendation would require further coordination and input from both Connections and Domino support, and it would be best to do this via a support case. Can you please open a case and refer to this thread?
Thank you,
Michael Montani
HCL Support
Hi Michael,
Thanks for your reply. I know that just adding in the forwarding address actually works for me as I have been doing this manually as a work around for us and our customers and as far as I am aware as long as the internet address field and the forwarding address field have the details then Connections is happy as well.
Please see the reply from Jacques below on how he got round this. I do not know what I need to add to the self-registration.xml file which I am hoping he will provide but it may well be worth adding a note to the Connections documentation that if you don't do this and you set it up using a secondary Domino Address book you need to take these steps into consideration.
Hi Richard,
I have successfully setup the invite application with Domino LDAP using the following settings:
- registering guests users in a separate domino directory and choosing Other Mail System and filling the internet and forwarding adress fileds with the guest mail adress
- configuring the Directory assistance to add the secondary address book
- Configured an additionnal and separate TDI synchonization script for the secondary adress book with specifics guest settings as described in the documentation
At this stage, It will not work. Now you need to create a LDAP configuration document in the secondary address book with the following setting: (sorry it's in french)
I also set the same setting in the LDAP configuration document in the main adresse book
After that It works
Hi Jacques,
Thanks for your reply. I actually have my setup exactly the same as yours the only bit I am missing is this part -
- registering guests users in a separate domino directory and choosing Other Mail System and filling the internet and forwarding address fields with the guest mail address
Everything else works as if I manually add in the forwarding address then it all works fine. Could you provide me with the settings you used to change the self-registration.xml file to fill in the person document fields you have mentioned when a user goes through self registration.
If you could that would be great as this would then fix the problem I have.
Richard,
My self-registration.xml file is a little bit customized, however here is how I set the forwarding address;
<!-- The mail attribute field. The mapping value could be obtained from the `<TDISOL>map_dbrepos_from_source.properties` file -->
<key>mail</key>
<value>${form:r_mail}</value>
<validator name="mailUnique" type="unique"/>
</attribute>
<attribute>
<!-- to set forwarding address -->
<key>mailaddress</key>
<value>${form:r_mail}</value>
<validator name="mailUnique" type="unique"/>
</attribute>
Thanks Jacques,
Works perfectly and allows me to understand the customisation a bit better which is brilliant.
