Sebastian, you'll need some type of server application software to do this.

In ColdFusion, I could write the script to do these tasks in 30 mins.

Do you have a programming guru?

Ron

Hi Ronald,

I used to code in ColdFusion back in the days when it was still Macromedia :)

Well I was thinking about doing something in python with API calls (and maybe IMAP libs if needed). But well, first I have not much time to spend on this and also would need the list of all possible special folders translated names to check the folders against, and I don't have this list.

As the issue was generated by "bogus" translation changes to IMAP in SmarterMail production release I would think that SmarterTools had thought about a solution for their customers that were affected.

For our CEO, I already spend too much time on troubleshooting these IMAP (and other)  issues on many clients and arguing in tickets/community to have these changes reverted, to now spend more time on coding a cleanup script.

At first we bought SmarterMail commercial solution to avoid having to develop our own solution and deeply troubleshoot/fix the problems ourselves, but in the end I've spent more time on bugs reporting/troubleshooting than setting up our own solution based on opensource components and own scripts...

That's why I'm asking if there is a near-ready solution to clean this :)

Kind regards.

Agreed. There isn't just 1 non-english customer with these translation issues. There are likely thousands.

This is, indeed, the responsibility of SmarterTools.

Ron

I would do something like this:

- Get a list of all accounts

loop start

- List mail folders for the account that aren't the official special folders

- Check if the folder name matches a possible translated special folder name (for this I need the whole list of possible translations).

- If it matches, check if it's empty

  * If it's empty remove it

  * If it's not empty, move the content to the user real special folder (need again the list of the possible translation of the folder and what special folder to know where to move the content), then remove it

loop end

But I don't know if all this is possible using the API only. Maybe ST can give some hint about what calls to use for the operations.

Sébastien,

You and others are owed this fix. Also, you are right that this is commercial software and one shouldn't be expected to build a program in order to fix it.

Perhaps SmarterTools would be inclined to build a "mail server translation folder one-time fixer" executable.

Ron

Well I think so too Ronald.

It wouldn't be a big issue if there wasn't a side effect of these duplicate translated folders, but actually most of the people willing to switch back their webmail language from english to their original language are getting an error (because SM says it would conflict with existing folder names).

This create a lot of support requests and THIS is an issue.

Kind regards

Sébastien -

We are currently developing a utility to help resolve the problem you are seeing. As you suggested, it will iterate through each user and merge any potentially conflicting folders.

Hello Andrew,

Thank you for the information, this is great news.

Kind regards,

Sébastien

We have completed development of the clean-up utility for this issue. If you have an open ticket for this issue, our support team will be reaching out to you. If you do not have a ticket and need this utility, please open a ticket.

I like how this was handled.

Jag gillar hur detta hanterades.

Me gusta cómo se manejó esto.

J'aime la façon dont cela a été géré.

Мне нравится, как с этим справились.

我喜歡如何處理。

Ron

Hello,

Just a little update and warning about the cleaning utility provided by ST.

We cloned our SmarterMail server and ran the utility. At first it seemed to be great, but after checking a few "conflict resolved" mailboxes.

It appears that the content of the conflicting/dupe folder, that should be moved to the official folder, for example Brouillons -> Draft, is lost.

The tool says "XX messages moved" but they are not present in the destination folder and the source folder is removed.

I would advise not to run the tool on production servers yet until this is sorted out.

I've updated our related ticket at ST with this information...

Kind regards.