[Phpgroupware-tracker] [bugs #4489] UTF7-Support in Anglemail does not work

[Dr. Christian Böttger]

This mail is an automated notification from the bugs tracker
 of the project: phpGroupWare.

/**************************************************************************/
[bugs #4489] Latest Modifications:

Changes by: 
                Dr. Christian Böttger <address@hidden>
'Date: 
                Wed 04/21/04 at 07:58 (Europe/Berlin)

            What     | Removed                   | Added
---------------------------------------------------------------------------
         Assigned to | None                      | angles







/**************************************************************************/
[bugs #4489] Full Item Snapshot:

URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=4489>
Project: phpGroupWare
Submitted by: 0
On: Sat 07/26/03 at 13:41

Category:  email
Item Group:  0.9.14.004/5/6 release
Severity:  5 - Average
Priority:  5 - Normal
Resolution:  None
Assigned to:  angles
Status:  Open
Component Version:  None
Platform Version:  GNU/Linux - RedHat/Fedora
Reproducibility:  Every Time


Summary:  UTF7-Support in Anglemail does not work

Original Submission:  I am using PHPGw email application to acess a Exchange 
5.5 server via IMAP. Folder names use international characters. With UTF7 
support disabled (settings) the folders show up with the special characters 
showing as &...- as expected, e.g. "Gel&APY-schte Objekte" but apart from this 
folder functionality (browsing, moving, deleting) does work.

With UTF7 support enabled the folder names are cut after the ampersand 
character (e.g. "Gel&APY-schte Objekte" shows up as "Gel") and folder functions 
stop working. With utf7_debug enabled the debugging code shows up that the cut 
takes place before the names are actually utf7_decode()-ed. When calling 
imap_utf7_decode() called manually in a short test script names translate 
correctly, so it seems what exchange 5.5 sents us is correct (always expect 
Exchange does not implement protocols correctly, but obviously it's ok this 
time :-)).











For detailed info, follow this link:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=4489>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/