300869 - Cannot send a template message with pasted images (embedded attachments) when using IMAPS (port 993 - IMAP SSL)

Status: RESOLVED INCOMPLETE

(Thunderbird :: Message Compose Window, defect)

Description

[Tony Pecora]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.9) Gecko/20050711 Firefox/1.0.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.9) Gecko/20050711 Firefox/1.0.5

When using IMAPS (port 993 - IMAP SSL)
Account Settings - Server Settings - Use Secure Connection (SSL)

Create a new mail with images pasted into the body (embedded - not attached)
then save the  message to the templates folder - tested it with any size message
from 2K - 500KB, but all had pasted images (from tiny spacer gifs to larger
images).  Click on inbox, then back to templates, loads mail from IMAPS
Templates folder, mail looks fine in preview - all images present.  Double click
to send the template as a new mail.  Template comes up with no images (just
place holders), proceed to send mail anyway and I get this window

[Status: Attaching fetch>UID>^INBOX^^Templates>14...]
[Progress: with progress bar]

then I get this error window (immediately): Send Message Error
[Sending of message failed.  There was an error attaching
fetch>UID>^INBOX^^Templates>14. Please check if you have access to the file]

Cannot send the message.

Reproducible: Always

Steps to Reproduce:
1. Use IMAPS - Account Settings - Server Settings - Use Secure Connection (SSL)
2. Create a new mail
3. Use FireFox and goto http://www.google.com
4. CTRL-A (select all)
5. CTRL-C (copy)
6. Go back to new mail (Compose: no subject) and paste CTRL-V
7. Enter Subject: TEST
8. Save as Template
9. Close window, double click template.
10. Click Send.  (2 error windows will then appear)
Actual Results:  
Sending Messages - TEST
[Status: Attaching fetch>UID>^INBOX^^Templates>##...]
[Progress: with progress bar]

Send Message Error
[Sending of message failed.  There was an error attaching
fetch>UID>^INBOX^^Templates>##. Please check if you have access to the file]

## - represents a number like 14 or 21

Expected Results:  
Mail sent successfully

I've tried this on both Win2K and WinXP with Thunderbird 1.0.5, using two
different IMAP servers

Win2K box - 1.7GHz Pentium, 1.5 GB RAM, 40GB HD
WinXP box - 2.2GHz Athlon64 3500+, 2GB RAM, 120GB HD

Comment 1

[laurent.hollecou]

The problem appears on Debian too.
To resolve the problem waiting for a new version, you can close your template
and with a right-click on it, choose "open like a new mesage" then the images
will appear correctly

Comment 2

[hans]

Problem with templates exists in current version too. Seems that TB has problem with images in template folder. 
We use templates very often. When save email as template, and later use template pictures disappear. Seems that path to some images is not correct (ex. path is to other emails). 
If you create emails from scratch and put images,everything seems ok. Problem exists only if you save email which was received from another person.
The only solution which I've found is create new folder and change in settings Templates -> new folder. New folder work correctly.
I hope somebody will  repair this bug because I'm fed up with explaining to customers how they should create new folders and how change settings.

Regards,
Hans

Comment 3

[Ludovic Hirlimann [:Usul]]

This works for me with Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.3pre) Gecko/20090818 Shredder/3.0b4pre. My template folder is hosted on a SSL accessed imap server. A lot of code has changed since the last activity happened on this bug, IMAP support has improved a lot. Hans, Laurent, Tony, could one of you guys take the time to test with http://www.mozillamessaging.com/en-US/thunderbird/early_releases/ and comment on this bug if the issue is still present for you ?

Comment 4

[[:Aureliano Buendía]]

Tony and\or hans could answer to comment #3, please?

Comment 5

[Joshua Cranmer [:jcranmer]]

RESOLVED INCOMPLETE due to lack of response to last question. If you feel this change was made in error, please respond to this bug with your reasons why.