The following issue has been set as RELATED TO issue 0000538. 
====================================================================== 
http://www.dbmail.org/mantis/view.php?id=548 
====================================================================== 
Reported By:                idk
Assigned To:                
====================================================================== 
Project:                    DBMail
Issue ID:                   548
Category:                   IMAP daemon
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     new
target:                      
====================================================================== 
Date Submitted:             22-Mar-07 11:23 CET
Last Modified:              22-Mar-07 14:42 CET
====================================================================== 
Summary:                    WISH: Better parsing 8bit header characters
Description: 
In mail header values there are valid only 7bit characters, so accents
should be escaped. But... Seldom I got message from buggy mail client
which ignore this rule.

MSOE's message list has invalid subject (it seems like UTF8 encodings but
displayed by single byte), but opened message has Subject header displayed
correctly (parsed from headers part of message). So I think it has a
solution.

MSOE under Windows (CZE) has default code page 1250, so this is one option
MSOE interpreted Subject from all message content "correctly", other one is
fetching of Content-Type header value (see Additional Information).

The second option should be applicable for DBMail, I mean.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0000538 incorrect field cache values for messag...
====================================================================== 

---------------------------------------------------------------------- 
 paul - 22-Mar-07 14:42  
---------------------------------------------------------------------- 
This is exactly how it's done at the moment. 

If a header is 8bit the header string is converted to utf8.
If the content-type header contains a charset specification dbmail will
try to convert from the specified charset to utf8
Else dbmail will fall back to the charset specified in the
DEFAULT_MSG_ENCODING config value and try to convert the string to utf8,
assuming the header was encoded in that charset.
If both fail dbmail will replace all 8 bit characters with '?'. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
22-Mar-07 11:23 idk            New Issue                                    
22-Mar-07 14:42 paul           Note Added: 0001935                          
22-Mar-07 14:42 paul           Relationship added       related to 0000538  
======================================================================

_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev

Reply via email to