6.0.0-beta1
7/5/25

[#11810] HTML inline format fails
Summary HTML inline format fails
Queue IMP
Queue Version 6.0.2
Type Bug
State Not A Bug
Priority 2. Medium
Owners
Requester watz (at) nerd2nerd (dot) org
Created 12/03/2012 (4597 days ago)
Due
Updated 05/28/2013 (4421 days ago)
Assigned
Resolved 12/04/2012 (4596 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
05/28/2013 09:01:17 PM orlandorozasi (at) gmail (dot) com Comment #4 Reply to this comment
I set to false but its not work..

Appear "null" or blank message


regards
Can't reproduce.

is $conf[['compose']['convert_to_related'] true?  If so, try setting 
to false.
12/04/2012 08:14:13 PM Michael Slusarz State ⇒ Not A Bug
 
12/04/2012 11:10:31 AM watz (at) nerd2nerd (dot) org Comment #3 Reply to this comment
Can't reproduce.

is $conf[['compose']['convert_to_related'] true?  If so, try setting 
to false.
Hi,

it was set to false. I set it to true and it worked. Thanks a lot.

For my understanding, what does this option do exactly?

Greets,

Aleksander Paravac
12/04/2012 03:59:03 AM Michael Slusarz Comment #2 Reply to this comment
Can't reproduce.

is $conf[['compose']['convert_to_related'] true?  If so, try setting to false.
12/03/2012 09:51:28 PM watz (at) nerd2nerd (dot) org Comment #1
Priority ⇒ 2. Medium
Patch ⇒ No
Milestone ⇒
Queue ⇒ IMP
Summary ⇒ HTML inline format fails
Type ⇒ Bug
State ⇒ Unconfirmed
Reply to this comment
Hi,

sending emails via the HTML composer result in emtpy HTML inline 
parts. The strange thing is, that this doesn't happen if you save the 
email in your drafts.

Procedure:

1.) compose email with HTML composer
2.) save email to drafts
You will get something like:

X-IMP-Draft: Yes
Content-Type: multipart/alternative; boundary="=_00ft_elMjhO4ots63x5F1Q2"
MIME-Version: 1.0

This message is in MIME format.

--=_00ft_elMjhO4ots63x5F1Q2
Content-Type: text/plain; charset=UTF-8; format=flowed; DelSp=Yes
Content-Description: Plaintext Message
Content-Disposition: inline

TEST HTML

--=_00ft_elMjhO4ots63x5F1Q2
Content-Type: text/html; charset=UTF-8
Content-Description: HTML Message
Content-Disposition: inline

<body style="font-family:Arial;font-size:14px"><br />
<span style="color:#ff0000;"><strong>TEST 
HTML</strong></span><!--a75c305b1c0a6022--></body>
--=_00ft_elMjhO4ots63x5F1Q2--

Which is correct.

3.) Reopen mail and sent it.
4.) The text/html inline part will be empty, resulting in:

User-Agent: Internet Messaging Program (IMP) H5 (6.0.2)
Content-Type: multipart/alternative; boundary="=_DvErYfWOwRJzeikcfEHklQ1"
MIME-Version: 1.0

This message is in MIME format.

--=_DvErYfWOwRJzeikcfEHklQ1
Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes
Content-Description: Plaintext Message
Content-Disposition: inline

TEST HTML

--=_DvErYfWOwRJzeikcfEHklQ1
Content-Type: text/html; charset=utf-8
Content-Description: HTML Message
Content-Disposition: inline


--=_DvErYfWOwRJzeikcfEHklQ1--

Horde uses directly the SMTP of our postfix.

This was already also in IMP 6.0.0 (Horde Webmail 5.0.0). I updated to 
6.0.2 (Horde Webmail 5.0.2) today and it's still there.

Greets,

Aleksander Paravac

Saved Queries