Gabriele, thank you for reporting this issue. We have been able to replicate the issue and have added this to our bugs list.

THX Robert.

I hope that we can have a fully functional production release soon!

I love your work with SmarterMail!

Even EM Client with EWS support has the same issue with the localized folder name.

Please verify this too.

Hey Gabriele, we did add this as a change item for us to complete.  This will be a bigger fundamental change but one we think it is required and an important change.  We can't complete this quite yet as we're only making performance changes in light of our release that's coming up soon.  However, this will be one of the tasks we work on following the release candidate.

OK , but you know that non English people can't use MAPI (and perhaps EWS) until this is completed, so  this is a show stopping issue for many customers around the world

Same issue even in Outlook connected via IMAP: some folders are translated in Italian (INBOX --> Posta in arrivo), other folders no:

Please be aware that for non-English people (like all our customers!) this is a very big issue!

Hey Gabriele, Tim provided some insight on the non-English folders in this thread, https://portal.smartertools.com/community/a93087/7398-and-7405-issue-importing-pst-file-with-mapi-and-outlook-2016.aspx .

Hi Larry, I read Tim's post and from what I understood he was referring only to the import of PST files through Outlook.

What I indicate above, on the other hand, also refers to any account (even empty like the one of the image I posted) to which you connect, even without importing PST files.

So I say that even those who have no data to import are afflicted by the same problem, and therefore at the moment ALL non-English users have this problem and it needs to be corrected as soon as possible, independently of the PST files.

I don't know if this issue involves also EAS... Can someone test it?

Gabriele, if you configure Outlook to use EAS and then attempt to import a PST you will be given the following error message.  In order to import a PST into Outlook, you need to have MAPI/EWS functionality enabled.

Hi Mark, this is not a post regarding PST import!

I don't want to import PST file in this post.

For issue with PST files there's another post.

This post is for that:

The issue of non-localized folder names is present even in empty new accounts.

You simply create a new account and connect to it with Italian version of Outllook or EM Client (via MAPI, IMAP or EWS):  non-localized folder names are there mixed with others that are localized.

I haven't tried EAS.

In exchange Server I never had this issue AND I am never been requested to change Exchange user language (I use OVH Cloud Exchange).

It automatically use the correct language seamlesly, even if you you have 3 different PC with 3 different language Outlooks connected to the same account (tested with in MAPI connected to OVH Cloud Exchange, never tried IMAP or EWS or EAS)

UPDATE: with latest EM Client 8 and latest SM 7417 the localization of folder names seems to be correct both in IMAP and in EWS

 Unfortunately, the issue remain in Outlook (2016) both in IMAP and MAPI:

News?

Any news on that?

We cannot make our clients use SmarterMail MAPI because of this issue!!!

Any news?

Have the same problem with French version of Outlook. Main folders (Inbox, Drafts, sent items..) are listed in english instead of French.

SM Team : any clue / solution for us?

In april Tim wrote that this problem would be resolved about a month after the release of the final version of MAPI / EWS.

We are now about a month after the release and I would like to have news if we are close to the solution.

News

?

You should maybe open a ticket about it. It seems that ST aren't looking that much at the community recently.

Hey SM team, nothing new about it? 😉

I'm waiting for that...

Untill it's OK, I can't use MAPI.....

Is there a roadmap to solve this issue?

Any news?

We are planning on working on this for the next release. 

Good news!!!

Thanks Derek!

Thank You Derek, Good news, because we can't deploy MAPI until implemented. (French language)

@Derek Curtis when will the new release come out?

It seems that latest build ( yesterday - v.7523 ) doesn't fix this issue... :-(

We need to wait for next one...

Do you think this is the good week to release it?

Next week?

Gabriele: I fully understand that you are waiting/needing the localized/international foldernames support.

But keep in mind: SmarterTools stated that supporting the localized foldernames requires bigger fundamental changes. So perhaps it could even be better to not install such a first public build with this feature right away on your production server.

Let's say I trust Tim enough that they release a working version!

Or at least I hope so ... 😁

I think after so many month, can be a working, production ready, version :-)

Hey all, just wanted to let everyone know that we have been working on getting this completed.  I know we've had a couple of releases without the changes in place but it is coming soon.  We've had to make significant changes to our back-end code to get this working across multiple protocols.  We also want to make sure we have covered various scenarios, not just related to protocols, before we consider this a production ready change.

Thanks for your patience as we continue to work closer to getting it into a release.

Hi Larry, nice to ear that you are working on this!

We (and also all international non-English customers...) really need this to proceed in SmarterMail deploying!

Do you have some ETA?

Hi guys, nothing about it?

It's really important for non-english customers :/

when do you think the non-english folder names will work?

Sorry to bother you again, but this is very needed here, as without it SmarterMail MAPI support is unusable by our clients!!!

There's an ETA to this function?

Some times ago Tim wrote that it will be available a month after the official MAPI release, but now several months passed and we never see that...

It's seems that v. 7565 solves this issue.

Here the changelog:

Can you confirm that?

I'm testing it with MAPI (Outlook 2106)...

It's better than before, but not completely fixed...

This must be "Posta in uscita" ...

Hey, Gabriele

Will you open a support ticket on this? We should be translating "Outbox" so we'll want to check some things to figure out why it isn't. Thanks!

Hi Derek.

I think that the issue is related to previously configured Outlook MAPI accounts.

In this case, Outlook translate all folders except OUTBOX.

If I create a new Outlook MAPI account (same user in SmarterMail), all folders are correctly translated.

Hi Derek and Gabriele,

my account is in MAPI too, it had translated all the folder at the first sync after the updated except the OUTBOX one.

But when I've sent a message, it has translated OUTBOX to POSTA IN USCITA.

You just have to send a message ;)

UPDATE: if you already have a folder with the same name of the translation of one of the "standard folders", it won't make you change language

Example: If you already have a folder named BOZZE (drafts in italian) that it's not the "standard" one, you can't select italian language.

You have to delete / rename it, after it you can switch your language.

Best regards.

Stefano

Gabriele, that's good info. We have something to look at now. And thanks for the info Stefano!

Derek, is it normal that an IMAP account doesn't see the translated folders?

I had to remove and add again an IMAP account for having the folders in italian.

Stefano, I tried tosend a message, but OUTBOX never get translated in my old account...

I create a new Outlook account and there I have "Posta in uscita", but in the old account it remain "OUTBOX"...

Same user same PC, only 2 Outlook separated accounts, one already existent and the other newly created

I don't know why...

Hi Gabriele, have you tested 7573 with IMAP and Outlook, with webmail set in italian?

Thanks ;)

Hi Stefano!

Yes, and it seems to work as it is OK

On my side, I played a bit with Outlook and IMAP. When a special folder has an accent in it, it is duplicated and the wrong one is used.

After doing some tests like changing the language in the webmail for an account and restarting outlook accessing the same mailbox, it ended up creating a huge mess in the folders and finally completly broke the IMAP access with this error in the imap log:

[2020.09.26] 16:08:08.465 [192.168.50.35][39128339] connected at 26.09.2020 16:08:08
[2020.09.26] 16:08:08.481 [192.168.50.35][39128339] command: A1 CAPABILITY
[2020.09.26] 16:08:08.481 [192.168.50.35][39128339] response: * CAPABILITY IMAP4rev1 AUTH=CRAM-MD5 AUTH=PLAIN SASL-IR UIDPLUS QUOTA XLIST CHILDREN ENABLE CONDSTORE IDLE STARTTLS
[2020.09.26] 16:08:08.481 [192.168.50.35][39128339] response: A1 OK CAPABILITY completed
[2020.09.26] 16:08:08.560 [192.168.50.35][39128339] command: A2 STARTTLS
[2020.09.26] 16:08:08.638 [192.168.50.35][39128339] command: A3 CAPABILITY
[2020.09.26] 16:08:08.638 [192.168.50.35][39128339] response: * CAPABILITY IMAP4rev1 AUTH=CRAM-MD5 AUTH=PLAIN SASL-IR UIDPLUS QUOTA XLIST CHILDREN ENABLE CONDSTORE IDLE
[2020.09.26] 16:08:08.638 [192.168.50.35][39128339] response: A3 OK CAPABILITY completed
[2020.09.26] 16:08:08.731 [192.168.50.35][39128339] command: A4 AUTHENTICATE CRAM-MD5
[2020.09.26] 16:08:08.747 [192.168.50.35][39128339] madjik@xxx13.com logged in
[2020.09.26] 16:08:08.763 [192.168.50.35][39128339] command: A5 CAPABILITY
[2020.09.26] 16:08:08.763 [192.168.50.35][39128339] response: * CAPABILITY IMAP4rev1 AUTH=CRAM-MD5 AUTH=PLAIN SASL-IR UIDPLUS QUOTA XLIST CHILDREN ENABLE CONDSTORE IDLE
[2020.09.26] 16:08:08.763 [192.168.50.35][39128339] response: A5 OK CAPABILITY completed
[2020.09.26] 16:08:08.841 [192.168.50.35][39128339] command: A6 XLIST "" "*"
[2020.09.26] 16:08:08.841 [192.168.50.35][39128339] Exception: (PooledTcpItem.cs) Object reference not set to an instance of an object.
[2020.09.26] 16:08:08.841 [192.168.50.35][39128339] StackTrace:    at MailService.TcpServerLib.IMAP.ImapListParser.<>c.<.ctor>b__6_2(db_folder_readonly p)
[2020.09.26]    at System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext()
[2020.09.26]    at MailService.TcpServerLib.IMAP.ImapListParser..ctor(String userName, MailboxManager mm, Boolean subscriptionsOnly)
[2020.09.26]    at MailService.TcpServerLib.IMAP.IMAPSession.XLIST(String tag, String argsText)
[2020.09.26]    at MailService.TcpServerLib.IMAP.IMAPSession.ProcessAsyncCommand(String tag, String command, String argsText)
[2020.09.26]    at MailService.TcpServerLib.IMAP.IMAPSession.ProcessAsyncData(Byte[] memStream)
[2020.09.26]    at MailService.TcpServerLib.Common.PooledTcpItem.ProcessData(Int32 bytes)

The account seems dead.

Sorry but I'm still not conviced that translating the special folders server-side for the IMAP protocol is a good idea. It will only create trouble and we do not need more trouble than we already have...

The physical folder of the user contains now a mixed set of folders in french/english/german

Hello,

Can we have please in the next build, a global server setting where we can enable/disable the special folders translation for IMAP.

Since this was introduced it brought only trouble for our customers and therefore for us.

We don't see any benefit for this feature and it compilcates an already complicated enough service.

Also if customers, after having their client configured are sometimes changing the language in the webmail because they use a computer that has a different default language and by mistake change their webmail language it can mess the configuration of some clients that doesn't automatically re-assign special folders.

I really think that as system admin we should have the choice to enable or disable the translated folders for IMAP so if we want to play it safe can still disable this feature and the others feeling adventurous can enable it.

In our case we need a STABLE service. The benefit from this feature is really not worth the trouble. Even this was almost fixed in new builds there is still issues with some clients (outlook) and probably others that we don't know yet.

Still we're convinced that it's the _mail client_ to translate the name of the folders according to the language set in _the client_, not in the webmail.

Also staying with standard english folder names for these special folders, through IMAP, will avoid issues with folder name encoding and mismatches that brings trouble.

Thank you for your consideration.

Kind regards