#dominoforever | Product Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Disallow special characters for Group Name

When using special characters like Pound/Hash (#) Plus (+) Equal(=) As because they are known to cause problems in group names. Add input validation to disallow this characters.

It is mentioned here:

https://help.hcltechsw.com/domino/12.0.0/admin/conf_creatingagroup_t.html?hl=creating%2Cgroup


But since there was a case where mails where routed incorrectly (automatically) by the system since (nested) groups contained Pound/Hash(#) characters in their name. Main-Group name e.g. #Group1 contained nested sub-groups e.g. #NestedGroup#12, #NesteGroup#22, etc. and one of those nested Groups was non-existent, the mailrouter automatically chose the first group the the "#" character in the name and forwarded the emails automatically to those members.

Luckily the information was not sensitive...


  • Guest
  • Mar 1 2022
  • Under Consideration
  • Attach files
  • Guest commented
    9 Mar 09:58am

    I agree with the previous comment: It's the router's behaviour that needs to be fixed. Removing the ability to use special characters in group names would break many existing Domino installations.

  • Guest commented
    2 Mar 02:21pm

    Thanks for providing an example. Its the behaviour of the router that is wrong in this instance, not the use of # for group names (which are great for seperating users from groups in name picking dialogues). The behaviour of picking something that sounds like a name also appears in the mail client but the user can correct or remove the offending name at that time of sending. Maybe the router behaviour should be, if I cant get a direct fix on any of the names either a) discard them or b) NDR the whole message or c) a combo of the above, mail to the matched names and NDRs for the unmatched names.