Adding an apostrophe as part of a Display Name attribute on an Exchange mailbox in SolidCP 1.4.9 reveals the character encoding, and then re-encodes the ampersand on subsequent updates to the mailbox. Steps to replicate:
1. Create a mailbox with an apostrophe in the First or Last Name (such as O'Connor).
2. Update the mailbox in some way. We disabled the user.
3. Return to the Mailbox list view and edit the settings of the mailbox again
4. The apostrophe shows as an encoded character in the name
5. Make another change to the mailbox and save.
6. Return to the Mailbox list view and edit the settings of the mailbox again
7. The original apostrophe now shows as encoded, along with the ampersand used to encode the original apostrophe.
8. You can continue this loop ad nauseum, and it will continue to encode the ampersands from the previous encodings..
You can erase the encoding and return it to just a regular apostrophe. However, you would have to remember to do that every time you make a change to that mailbox. The attached file is what it looks like after the second mailbox update (step 6 above).
Notice that the original apostrophe is now encoded, along with the ampersand used to encode the initial apostrophe. You’ve correctly identified that this loop can continue indefinitely, re-encoding ampersands from previous encodings. To revert to a regular apostrophe, manually erase the encoding each time you make changes to that mailbox.
Thanks Robert. I'm aware I can simply erase the old encodings to return to the original display name. However, this is a rough corner for customers and wanted to report it for a fix, rather than a workaround.
Hello,
It sounds like a frustrating encoding issue. Here’s a concise summary of the steps to replicate the problem:
Create a mailbox with an apostrophe in the name (e.g., O'Connor).
Update the mailbox (e.g., disable the user).
Edit the mailbox settings again; the apostrophe appears encoded.
Make another change and save; the apostrophe and previous encoding (ampersand) both appear encoded.
This loop continues with each update.
To avoid this, you might need to manually correct the encoding after each update.
Best Regards,
James Henry
Hello,
I think this should be fixed in the 1.5.0 release coming up on 02-12-2025 with the "[Exchange] Display name frontend validator" fixes. (the fix is currently available in the github source code).
Regards,
Marco Tiggelaar
