[Tickets #8837] Re: invalid email address

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/8837
------------------------------------------------------------------------------
  Ticket             | 8837
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | invalid email address
  Queue              | IMP
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2010-01-30 12:28) wrote:

> The body is fine. The issue is with the header.

Incorrect.  If a specific header encoding is not defined for a message  
part, we use the charset defined for the body.  We don't define a  
charset for the headers in IMP, so the charset of the body is the  
important factor here.

On line 762 of imp/lib/Compose.php, can you put a print_r($message)  
and post the output.  A test for me gives:

Horde_Mime_Part Object
(
     [_type:protected] => text
     [_subtype:protected] => plain
     [_contents:protected] => Resource id #22
     [_transferEncoding:protected] => binary
     [_description:protected] =>
     [_disposition:protected] => inline
     [_dispParams:protected] => Array
         (
         )

     [_contentTypeParams:protected] => Array
         (
             [charset] => UTF-8
             [format] => flowed
             [DelSp] => Yes
         )

     [_parts:protected] => Array
         (
         )

     [_mimeid:protected] =>
     [_eol:protected] =>

     [_temp:protected] => Array
         (
         )

     [_metadata:protected] => Array
         (
         )

     [_boundary:protected] =>
     [_bytes:protected] =>
     [_contentid:protected] =>
     [_reindex:protected] =>
     [_basepart:protected] => 1
     [_hdrCharset:protected] =>
)

As expected, _hdrCharset is empty and charset is set to the sending  
charset value (in this case, UTF-8).