User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.6) Gecko/20091201 Firefox/3.5.6 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 WinXP & Thunderbird 3.0: 1. A file is created and named. 2. This file is attached to an email using the right click "Send to Mail Recipient" and sent. 3. This file is than modified and overwritten with the same file name. 4. The modified file is attached to an email using the right click "Send to Mail Recipient" and sent. 5. Result: The previous old file is sent instead of the new one. 6. The newer file version is renamed slightly and resent, resulting in the correct file being sent. Conclusion: When attaching a previously sent/attached modified/overwritten file, make sure to change the file name slightly or the older version of the file will be sent, if they are named the same. Reproducible: Always Steps to Reproduce: 1. Create a file. 2. Send file as an attachment using the right click "Send to Mail Recipient". 3. Update and overwrite the file and keep the same file name. 4. Send the updated file as an attachment using the right click "Send to Mail Recipient". 5. Recipient should receive the older copy of the file. Actual Results: Recipient receives the older copy of the file. Expected Results: The software should have detected the updated file and sent the newer file as an attachment instead of the old file. I used a PDF as a test file. I conducted the same test using the attachment process from within the program with the correct expected results - the correct updated files were sent. It appears that this bug only occurs with the right click "Send to Mail Recipient" attachment method. Thank you!

Can you check if this got fixed by bug 356808 using thunderbird from http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-comm-1.9.2/ ?

EN (Reporter of this bug), can you check if this problem has actually been fixed in the downloadable version mentioned in comment 1? It's clearly a dup of bug 356808 where it was resolved fixed.