Upon trying to add more than one e-mail alias to a Public Folder, CloudPanel encounters an issue with the second (or all additional) adresses.
Error: “The address ‘smtp: sample@domain.tld’ is invalid: Specified argument was out of the range of valid values. Parameter name: The address ‘ sample@domain.tld’ is not a valid SMTP address.”
When trying to grant send-as-permissions to a Public Folder, CloudPanel presents the following error message:
The best overloaded method match for ‘CloudPanel.Exchange.Exch2010.Add_SendAsPermissions(string, string)’ has some invalid arguments
KMI Support 2020-05-15 08:47
@kevinkleinjung Kevin, thank you for the feedback! I will take a look and see if I can get this produced and resolved. We are releasing a new update next week and will get this fixed by then. I will let you know of my findings today.
KMI Support 2020-05-15 08:56
@kevinkleinjung Kevin, can you hold shift and refresh the page? I’m wondering for the email alias if it is old javascript cached because I wasn’t able to reproduce that one.
Hello again,
as for our X500-address problem, your solution of escaping the , with a \ somewhat works, but not exactly in the way it’s supposed to.
We’re currently migrating a company to us for hosting and intend on managing them with CloudPanel, meaning we don’t really have the luxury of tampering with the LEDNs, and since Exchange internally communicates with LEDNs rather than SMTPs, adding the \ to an address falsifies the X500-address in Exchange.
While it does work and allows us to add additional aliases again, using the \ to escape commas in addresses communicates the \ into the X500 address in Exchange, thus falsifying it.
Another issue with this method is that either Exchange or CloudPanel remove EVERYTHING following the \, also impacting the X500-address.
(Ex. X500:/o=hv/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=85638c236f4e41e4aa72e990aedXXXXX–User\, ~Test~
the part highlighted with ~ does not show up in neither CloudPanel nor Exchange).
Thank you for your continued support and communication!
Best regards,
Kevin
KMI Support 2020-05-31 09:48
@kevinkleinjung I see the problem. The issue is the token delimiter is a comma which means it should cut off there. We would need to make the token delimiter a semicolon to resolve this. Let me test that and I can send you a javascript file for now to fix this.
KevinKleinjung Topic starter
2020-06-10 02:06
Hi,
any news about?
Or can you tell me the js file that is responsible for, then I would take a look at it on my own if possible.
Kind regards,
Kevin
KMI Support 2020-06-10 06:55
@kevinkleinjung It is more than just a JS file we found. We are working on an update but it will be a few days.
KevinKleinjung Topic starter
2020-06-10 07:09
Ah okay, thank you for the update.
Stay safe and kind regards,
Kevin
Hi Jacob,
it can’t be an clientside cache issue because this occurs at a customers computer who has logged in the first time after our last update.
I think we are talking about the first issue?
Was it maybe fixed undocumentated between 3.2.318.0 and 3.2.320.0?
Kind regards,
Kevin
KMI Support 2020-05-16 07:54
@kevinkleinjung I checked and don’t see anything. I did find another unrelated issue that we are going to work on and I will continue trying to reproduce this. If I don’t find anything by EOD Monday, we may need to do a screen sharing.
Hello, Jacob,
did you find anything else last week? Otherwise we can watch it remotely via TeamViewer.
Kind regards,
Kevin
KMI Support 2020-05-26 07:04
@kevinkleinjung We have a new update we are releasing tonight. I would like you to install it tomorrow and see if it resolves your issue.
KevinKleinjung Topic starter
2020-05-27 00:59
Hi Jacob ,
is the update already released? Didn’t found smth. new at the download-section.
Kind regards,
Kevin
KMI Support 2020-05-27 10:08
@kevinkleinjung Please check the downloads now. I just published it. Let me know if that works and if it doesn’t I can do a screen sharing with you.
Hi Jacob,
THANK YOU AGAIN!
The problems I have descriped are resolved! ?
One additional issue is open but I haven’t reported yet. If an user-mailbox is having an X500-Adress (because the user is migrated) and the X500-Adress contains an comma, we are not able to modify / update the user via the CloudPanel.
We are getting the message: “<part after the comma> is not a valid email-address”. Is there a workaround?
Pseudonomized Example:
X500:/o=hv/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=b820770339bf4f08b0f6a1614fXXXX-Doe, John
Error Message: John is not a valid email address.
Would be great if we can get a workaround or solution for this also, it’s the only known (by us and our customers) remaining issue so far.
Thank you in advance and kind regards,
Kevin
KMI Support 2020-05-28 06:52
@kevinkleinjung That is the exact error you are getting? That sounds like a message coming from Exchange not and CloudPanel but CloudPanel could be passing it incorrectly. Are you able to add that address in ECP and it works fine?
KMI Support 2020-05-28 06:53
@kevinkleinjung Actually I think you have to escape the comma with a \. So it would be Doe\, John. Give that a try and see if it works. (Exchange thing, not CloudPanel thing)
