Closed
Bug 271117
Opened 20 years ago
Closed 19 years ago
copy to sent folder fails for .doc attachments, possibly complicated by imbedded figs
Categories
(MailNews Core :: Composition, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: csuehs, Assigned: sspitzer)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 Dear All, Often, when I try to send a .doc I get the following message: "There was an error copying the message to the sent folder. Retry?" Clicking "ok" just regenerates the same message over and over again. This often happens with large files involving weird fonts and/or imbedded graphics, a situation that happens often in my domain and that I cannot avoid at the moment. Mac users appears to recieve a file somewhat altered and garbled. Pc users appear to recieve a .doc that they cannot open. PDFs send ok, but are difficult for my collaborators to edit and correct, so I am stuck with sending .docs. This bug does not occur for all .docs, just for certain ones. When it does happen with a particular attachment, it consistently reproduced itself for that attachment. Reproducible: Sometimes Steps to Reproduce: 1.Compose message and attach an "offensive" .doc file. (email me if you want an example) 2.Click "send" 3. Actual Results: You can "see" the message being sent. Then the error message "There was an error copying the message to the sent folder. Retry?" pops up. Clicking ok regenerates the same message, and the only option to take is "cancel", which obliterates all trace of the message. What is sent is apparently corrupted. Expected Results: Send the email with attachment intact and correctly, plus copy it to the sent folder.
Comment 1•20 years ago
|
||
are they getting sent as quoted printable? tools | options | composition...
(In reply to comment #1) > are they getting sent as quoted printable? tools | options | composition... Please be patient with me, I am not techno-savvy. For ex, I cannot find your path tools / options / composition in my menus. Mac users can print the files they recieve, but they are altered (usually fonts are different and page layout altered). Pc users cannot even open recieved files, nor print them, and some do not even recieve an attachment. I have not found a "send as printable" option in my menus/options.
Updated•20 years ago
|
Product: MailNews → Core
Comment 3•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 4•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•