Hello and thank you, also sorry for the inconvenience, ok seems a bit complex, I’m getting the folder name from this method (another sdk):
It automatically decodes international folder names presented in UTF-7 Modified encoding (see IMAP4 protocol specification in RFC3501 for details on UTF-7 Modified encoding). However, the original name (not decoded from UTF-7 Modified) is still available via RawName property.
Do you think this is causing the problem? passing UTF-7 Modified encoding name to Aspose AddSubFolder method?
Does AddSubFolder method need UTF-8 encoded etc?
Hello and thanks, but, objection; let’s argue on the behavior!
This is not quite right considering this specific overload’s goal: to make folder hierarchy!
Almost anywhere in Windows/FTP SDKs I’ve seen that if:
exists or not, adding:
Will make the inner folder anyway, if outer folder exists, will be made inside, otherwise both will be made!
When Folder1 exists, a request to make Folder1\Folder2 should not return “Folder already exists” error, IMO.
If you think it’s wise to your logic, you may consider it as an improvement!
My case: I am sending AddSubFolder requests inside a loop of reading remote imap server.
A bit complex to gain control over it, so I will check the target pst folder existence:
So regardless of your decision, please help me make wih the general idea of an algorithm of a function to get the PersonalStorage and full folder path (to be created inside Pst) and make it anyway.
Here’s my sample, which is of course is a terrible way to go, that’s why I asked your kind help for an efficient algorithm, anyway, it also shows that I could make 2 folders in the root with the same name but different cases!