Bug 506052
Summary: | Send message with PS attachment. The attachment will change after received. | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Qunfang Zhang <qzhang> |
Component: | thunderbird | Assignee: | Gecko Maintainer <gecko-bugs-nobody> |
Status: | CLOSED UPSTREAM | QA Contact: | desktop-bugs <desktop-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.3 | ||
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-06-17 22:52:03 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Qunfang Zhang
2009-06-15 12:11:14 UTC
Could you please paste here the output of diff? The only thing I see here is adding EOL to the end of the file, which is OK in case of a text file (which application/postscript actually is). (In reply to comment #1) > Could you please paste here the output of diff? The only thing I see here is > adding EOL to the end of the file, which is OK in case of a text file (which > application/postscript actually is). I'm sorry for my unclear description. After my using "diff" commond to check the original file and the received one, there's the output: 687c687 <%%EOF --- >%%EOF \No newline at the end of file We found this bug in the upstream database (https://bugzilla.mozilla.org/show_bug.cgi?id=163783) and believe that it is more appropriate to let it be resolved upstream. The difference is the same as what I could reproduce here. Given that Postscript is an ASCII file, adding EOL to the end of the file changes nothing. I did immerse myself to the RFC MIME definitions and found that they don't deal with this situation at all. So this bug is either NOATBUG or UPSTREAM. I voted for the second option. We will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates. Thank you for the bug report. |