[Tickets #8837] Re: invalid email address
bugs at horde.org
bugs at horde.org
Mon Feb 1 08:27:22 UTC 2010
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/8837
------------------------------------------------------------------------------
Ticket | 8837
Updated By | rsalmon at mbpgroup.com
Summary | invalid email address
Queue | IMP
Version | Git master
Type | Bug
State | Feedback
Priority | 1. Low
Milestone |
Patch |
Owners | Michael Slusarz
------------------------------------------------------------------------------
rsalmon at mbpgroup.com (2010-02-01 03:27) wrote:
> On line 762 of imp/lib/Compose.php, can you put a print_r($message)
> and post the output. A test for me gives:
Composing as plain text like you, I don't have this issue! Here is
$message when composing as HTML:
Horde_Mime_Part Object
(
[_type:protected] => multipart
[_subtype:protected] => alternative
[_contents:protected] =>
[_transferEncoding:protected] => binary
[_description:protected] =>
[_disposition:protected] => inline
[_dispParams:protected] => Array
(
)
[_contentTypeParams:protected] => Array
(
[boundary] => =_ey9kh8syst4cs8g0044wk88s
)
[_parts:protected] => Array
(
[0] => Horde_Mime_Part Object
(
[_type:protected] => text
[_subtype:protected] => plain
[_contents:protected] => Resource id #35
[_transferEncoding:protected] => binary
[_description:protected] => Plaintext Version
[_disposition:protected] => inline
[_dispParams:protected] => Array
(
)
[_contentTypeParams:protected] => Array
(
[charset] => ISO-8859-1
[format] => flowed
[DelSp] => Yes
)
[_parts:protected] => Array
(
)
[_mimeid:protected] =>
[_eol:protected] =>
[_temp:protected] => Array
(
[toString] =>
[sendTransferEncoding] => Array
(
[1] => 7bit
)
[transferEncodeClose] =>
)
[_metadata:protected] => Array
(
)
[_boundary:protected] =>
[_bytes:protected] =>
[_contentid:protected] =>
[_reindex:protected] =>
[_basepart:protected] =>
[_hdrCharset:protected] =>
)
[1] => Horde_Mime_Part Object
(
[_type:protected] => text
[_subtype:protected] => html
[_contents:protected] => Resource id #38
[_transferEncoding:protected] => binary
[_description:protected] => HTML Version
[_disposition:protected] => inline
[_dispParams:protected] => Array
(
)
[_contentTypeParams:protected] => Array
(
[charset] => ISO-8859-1
)
[_parts:protected] => Array
(
)
[_mimeid:protected] =>
[_eol:protected] =>
[_temp:protected] => Array
(
[toString] =>
[sendTransferEncoding] => Array
(
[1] => 7bit
)
[transferEncodeClose] =>
)
[_metadata:protected] => Array
(
)
[_boundary:protected] =>
[_bytes:protected] =>
[_contentid:protected] =>
[_reindex:protected] =>
[_basepart:protected] =>
[_hdrCharset:protected] =>
)
)
[_mimeid:protected] =>
[_eol:protected] =>
[_temp:protected] => Array
(
[toString] =>
[sendTransferEncoding] => Array
(
[1] => 7bit
)
)
[_metadata:protected] => Array
(
)
[_boundary:protected] => =_ey9kh8syst4cs8g0044wk88s
[_bytes:protected] =>
[_contentid:protected] =>
[_reindex:protected] => 1
[_basepart:protected] => 1
[_hdrCharset:protected] =>
)
charset isn't set in the top object, that's probably why IMP gets
confuse between UTF-8 (probably default value if not set) and
ISO-8859-1 (set when composing)
More information about the bugs
mailing list