User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.14) Gecko/2009090216 Ubuntu/9.04 (jaunty) Firefox/3.0.14 Build Identifier: 2.0.0.23 (20090817) Situation: When sending a message with an attachment referring to a file which has been moved, trashed or deleted in the mean time, a non⁻descriptive error is thrown. Error: Sending of message failed. Unable to open the temporary file /path/to/attachement. Check your 'Temporary Directory' setting. Reproducible: Always Steps to Reproduce: 1. Compose message 2. Attach file 3. Move file to trash (not the attachment, the actual file) 4. send message Actual Results: Error: Sending of message failed. Unable to open the temporary file /path/to/attachement. Check your 'Temporary Directory' setting. Expected Results: Message is sent with the attached file Suggested fix: 1. Copy file to temp dir when adding it to the list of attachments 2. Or: replace error with a more descriptive, user-friendly error like "Unable to find your attachment /path/to/file. Did you move or delete it?"

might get fixed by bug 356808?

Looks sibling of Bug 494415 which is listed in dependency tree for Bug 378046(or phenomenon of Bug 494415 with Tb 2). It may be resolved by Bug 378046.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.4) Gecko/20100608 Lightning/1.0b2 Thunderbird/3.1 (In reply to comment #2) > Looks sibling of Bug 494415 which is listed in dependency tree for Bug > 378046(or phenomenon of Bug 494415 with Tb 2). It may be resolved by Bug > 378046. Yes, that's if anyone ever cares to solve that bug, and if sanity prevails so that the solution will be "take the snapshot copy immediately upon attaching" (as proposed in comment 0, adding another voice of reason). Btw, it's telling that TB's error msg *assumes* the file should be in the temporary directory (which unfortunately is not yet true for the non-Mapi cases). In TB3.1RC2, we still behave inconsistently (taking the snapshot sometimes, and not at other times), and we still show the non-helpful error msg -> confirming.

Core bug 115841 reports the same problem and is about to be 10 years old... Due to age and morphing, bug 115841 is not in good shape, while this one is much more to the point, so pls don't duplicate this bug against the old one.

I got the same message for TB 17.0.1 on Linux/OpenSuse 12.3 (64 Bit), when the file was visible (x&r permissions on dir) but not readable (no r permission on file itself) Took some time to find the real meaning of the message. The same message is displayed both on trying to send the message, as well as when trying to save it.

See also bug 494415 comment #18, please.