647210 - Message filter /Rules : Auto reply with html signature doesn't forward the picture included in the signature

Status: NEW

(Thunderbird :: Toolbars and Tabs, defect)

Description

[rdm]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.2.16) Gecko/20110319 Firefox/3.6.16 ( .NET CLR 3.5.30729; .NET4.0E)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9

-Use a text/html template, and the html signature set in the corresponding account parameters, with rules to automaticaly answer back any incoming mail 
-If the signature embeds a picture, be it local or on a server, the picture is not properly sent.
- In fact, the sent answer starts with: " This is a multi-part message in MIME format. --------------010406090004040806070208 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit "

- The end of the answers ends with some hash, in this style : " --------------010406090004040806070208 Content-Type: image/jpeg; name="customLogo.gif" Content-Transfer-Encoding: base64 Content-ID: Content-Disposition: inline; filename="customLogo.gif" /9j/4AAQSkZJRgABAQAAAQABAAD/2w........(looooooooong hash).....(end=)MU4ehjzDYLnlfLEZe4V62v02+mnWI0NDTBTjJLPsiZdHoaGipr/2Q== --------------010406090004040806070208-- 

- The picture is not joined, but it's place is reserved.

- Going to see at the html composing the answer, the source of the picture is "src="cid:[e-mail]", despite a valid http adress for it was correctly given as src in the html that composes the signature
-The same when pointing the picture "src=" to a local picture

- When looking at the html from the code that makes the answer before it is sent, the reference to the picture is sytematically changed for an inner deep folder from the main thunderbird's user folder...


Reproducible: Always

Steps to Reproduce:
1.make a rule to send a signed answer to incoming mails, with a classic html moz-signature which includes a picture, whatever its location 

2.Observe the html which makes the answer before it's sent : the picture's src= from the moz-signature is never the one that was programmed in the moz-signature

3.See the unexpected result in the answered mail after it has reached its target e-mail adress.


Actual Results:  
The signature issued from the moz-signature used through a filter/rule programmed to answer incoming mails is displayed strangely, compared to classic sent mails'signature 

Expected Results:  
The result shouldn't be different than when just using signatures in a sent mail

Comment 1

[Joe Sabash [:JoeS1]]

Would you mind sharing your code for the sig

Does it work properly as a regular sig rather that a filter response.

If your intention is to retain a remote location for the image, you might try this

<img moz-do-not-send="true" src="xxxxx"

Comment 2

[rdm]

Thx Joe. Will have to try as  soon as I'm back at work on Monday (and for sharing the sig also, since it's a project from a local computer)

But : yes, it works like a charm as a regular sig.

Comment 3

[rdm]

Ok, here's the model code for my html sig : it's a table, an the pic is correctly sent when used as a regular signature.


<table style="text-align: left; margin-left: 0px; min-height: 143px; width: 527px;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td colspan="1" rowspan="2" style="min-height: 69px; width: 68px;" valign="center" align="left"><img src="https://sites.google.com/site/cfdocu/_/rsrc/1300102818395/config/customLogo.gif?revision=2" alt="Logo" title="Logo
Cogefim" width="71" height="98"><br>
</td>
<td colspan="2" rowspan="1" style="text-align: left; min-height: 49px; width: 225px;"><span style="font-family: Garamond; color: black; text-decoration: underline;"><span style="font-weight: bold;">xxx yyyyyyy</span> -
Assistant Recrutement &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</span></td>
</tr>
<tr>
<td style="min-height: 69px; width: 225px;" valign="top" align="left"><small><span style="font-family: Garamond;"><span style="color: rgb(102, 51, 102);"> Agence : </span>&nbsp;xxxxxxx

xxx<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; xxxxxxxx<br>
<br>
<span style="color: rgb(102, 51, 102);">GSM :</span> &nbsp; &nbsp;
xx xx xx xx xx</span></small></td>
<td style="min-height: 69px;" valign="top" align="left"><small><span style="font-family: Garamond;"><span style="color: rgb(102, 51, 102);">E-Mail :</span> &nbsp;<a href="" target="_blank">[e-mail]</a><br>

<span style="color: rgb(102, 51, 102);">Fax :</span> &nbsp; &nbsp;
&nbsp; &nbsp;xx xx xx xx xx<br>
<span style="color: rgb(102, 51, 102);">Tél :</span> &nbsp; &nbsp;
&nbsp; &nbsp; xx xx xx xx<br>
<span style="color: rgb(102, 51, 102);">Site :</span> &nbsp;
&nbsp; &nbsp; &nbsp;<a href="http://www.cogefim.fr" target="_blank">www.cogefim.fr</a></span></small></td>
</tr>
</tbody>
</table>

Comment 4

[rdm]

(In reply to comment #1)
> 
> 
> If your intention is to retain a remote location for the image, you might try
> this
> 
> <img moz-do-not-send="true" src="xxxxx"

@ Joe Sabash :
I can confirm that this workaround works very well. Despite it's not natural compared to regular signature. 
Anyway, very knoledgeable and clever support. A thousand thanks to you.

Comment 5

[Jorg K (CEST = GMT+2)]

I can confirm this bug, it just cropped up in bug 1370076 comment #5.

The template was a multipart message with an embedded image via CID: reference and the result is what is shown in comment #0, a message with a broken MIME structure.

The cause of this is in the defective auto-reply code:
https://dxr.mozilla.org/comm-central/rev/62db49c50e60514a4178651227629a9625381cb4/mailnews/compose/src/nsMsgComposeService.cpp#957

They are streaming the message instead of looking at the MIME parts properly. That works for simple templates but not multipart ones.