Closed Bug 372601 Opened 19 years ago Closed 16 years ago

Attachment not accessible after flawed sending

Categories

(Thunderbird :: Message Compose Window, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: tojoroco, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.2) Gecko/20070219 Firefox/2.0.0.2 Build Identifier: Version 1.5 (20051201) German 5 seconds after sending (the progrssbar reached the end) an email the smtp server annouce an error message. But then there exists no copy in the send-folder of the email because I deleted it int the 5 seconds. Saving the email is not possible, an notification is shown that the Attchment doesnt found. Reproducible: Always Steps to Reproduce: a) create a Message and add Attachment b) send email and wait until it were send (I send a 1.7 MB wmv attachment via smtp.gmail.com) c) delete the File that you ago have attach Actual Results: If the smtp server sends you an error you cant save the email because the original file of the attachment was deletet and you cant find an automaticly saved email in the "Send" folder. Expected Results: a change to saved the email that I before try to send For me it looks like an design-error. Its not secure to create a copy of the sendet email after sending. I would expected that after I click the send-button a copy of the email is saved in the draft-folder. This copy can be moved to the sent-folder after the email was successfuly sended.
Is this for IMAP mail or POP? For IMAP, see bug 206408.
I use pop3 (pop.gmail.com) PS: I have the same problem if I use the newest productiv version of thunderbird: Version 1.5.0.10 (20070221) German Bug 206408 seems not to be the same problem but maybe it would be possible to find one resolution for both problems. The problem of both seems to be that thunderbird creates a message, try to send it, but dont save the message localy before sending. In my reported case it save the message to late (after sending) in case of bug 206408 it dont save it localy. My proposal where to save a copy of the message LOCALY (Draft-folder) and BEFORE sending. After successful sending the saved message is move to the IMAP-Server or to the localy send-Folder
Assignee: mscott → nobody
Reporter, does this issue still occur in the latest supported 2.0.0.x / Shredder trunk nightlies? (1.5.0.x is now end-of-life and the latest supported 2.0.0.x is now 2.0.0.17)
Whiteboard: closeme 2008-11-06
RESO INCO per lack of response to last question. If you feel this change was made in error, please respond to the bug with your reasons why.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
My actual thunderbird Version 2.0.0.14 (20080528) on Mac has the same behavior. I think this is not a Error in the code, I think its a error in the design. Imagine this: * You prepare a dokument to send it by email to a customer. * You add the Dokument to Email without sending and saving this. * You make changes on the document. The additional changes/notices top secret and should not supplied to the customer. You save the changes to the document. * You take the email, make some minor changes in the body-text and send it. When you do this you will have a problem because the customer will get the document with the top-secret notice. I would expect and that thunderbird makes a copy of the attached document in the moment when I attach it.
Resolution: INCOMPLETE → FIXED
see also with imap. I suspect this to be a dupe, but if not it should be confirmed
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Whiteboard: closeme 2008-11-06 → dupeme
I can't find the dupe. Anyway this is WFM here on Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.2pre) Gecko/20100310 Lightning/1.0b2pre Lanikai/3.1b2pre ID:20100310032818 to-jo feel free to reopen it if I'm wrong and you have this issue also on latest TB 3.x release.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago16 years ago
Resolution: --- → WORKSFORME
Summary: Atachment not accessible after flawed sending → Attachment not accessible after flawed sending
Whiteboard: dupeme
You need to log in before you can comment on or make changes to this bug.