If a user is created with more than one first or last name, then the default scheme of generating long form email addresses fails to generate valid emails. Also, if a users name contains characters outside of normal ASCII, these are not either stripped or converted to an ASCII form, resulting in invalid email addressing.
It ought to be simple to handle the spaces that more than one first or last name can create by either substituting periods (.) or underscores (_) for these. Non-ASCII characters are harder to handle in a nice way, but it should be easy enough to remove them when generating the long form address. It is not necessarily pretty, but certainly better than having an invalid address shown. Ideally, you could have a substitution table that the administrator could set up, e.g. ø -> o æ -> ae å -> aa è -> e And so on. Then it is up to people who experience the issue how they want to deal with it. If no substitution table exists for a given character, then remove it. Possibly, you could also have an option for using the e-mail address defined in iManager when iManager integration with GW2014 has been configured. The client who has this issue had defined a valid email in iManager, but it was not imported to GroupWise when connecting the post office via iManager. I have verified that you can enter just one first and last name in iManager and modify the full name to have the rest, but this full name attribute also doesn't make it to GroupWise and so the issue remains.
by: Mike B. | over a year ago | Administration
Comments
Handling of space by removing them from multiple first / last names would be a great start. Adding the 'simplification' of special characters sounds great too!
Thank you for migrating my request, Mike! I hope it gets picked up!
We have the ability in our FirstClass email system to replace spaces with a character. I think exchange can do this too. This reduces our need to setup over rides for everything that has a space in the name.