Bug 782878 - Broken non-basic-latin imap folder handling
Summary: Broken non-basic-latin imap folder handling
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-18 19:14 UTC by Nicolas Mailhot
Modified: 2012-01-19 08:11 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-19 08:11:23 UTC
Type: ---


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 668247 0 None None None Never

Description Nicolas Mailhot 2012-01-18 19:14:38 UTC
Description of problem:

evolution has stopped processing imap folders with non-basic-latin names

For example when I try to check my 'Sent' folder (Éléments envoyés in French) evo freezes and displays a yellow bar stating :

Erreur durant Actualisation du dossier « Éléments envoyés ».
Dossier non trouvé : Ãléments envoyés

(can not refresh folder « xxx ». Folder not found yyy)

With another folder called “Dépenses” I have the same error:

Erreur durant Actualisation du dossier « Perso/Dépenses ».
Dossier non trouvé : Perso/Dépenses

This is typical UTF-x mangling

This setup has been working for years and the same folders export fine on the local webmail

Version-Release number of selected component (if applicable):
evolution-3.3.4-1.fc17.x86_64 using imapx backend

imap server:
dovecot-2.1-0.3.rc1.fc17.x86_64
dovecot-pigeonhole-2.1-0.3.rc1.fc17.x86_64

Comment 1 Milan Crha 2012-01-19 08:11:23 UTC
Thanks for a bug report. I moved this upstream as [1]. Please see [1] for any further updates. If possible, please CC yourself there, in case upstream developers will have additional questions.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=668247


Note You need to log in before you can comment on or make changes to this bug.