Tickets :: Comment on [#2422] IMP namespace support

* Your Email Address
* Spam protection	Enter the letters below: .__. __.. . .. . \| \|(__ \| \| \|\|_/ \|__\.__)\|/\\|\__\|\| \
Comment	> Response to Vilius (9/8/05): > > Not sure what you mean by 'not converted'. The actual preference > values stored in the prefs backend will not be touched. Instead, IMP > automagically adds personal namespace information (if needed) when > retrieving and strips this information (if needed) when storing. The > current code works for me in all the test cases I can figure out and > on two different configurations of the default namespace (a blank > namespace and the 'INBOX.' namespace) so if this is still not working > for you (or anyone else) you are going to have to start helping debug > since there is no more code that needs to be added, only bugfixing at > this point. > > > > As to your second point - you need to read the rest of the thread. > This is the expected (and cleaner) behavior. Short explanation: > namespaces are not something the end user should be concerned with. > Therefore, we should always show personal namespaces in the same > location (rather than showing these folders under INBOX on one server > and on the same level as INBOX on another).
Attachment
Watch this ticket