Closed Bug 323335 Opened 19 years ago Closed 19 years ago

Cannot open txt attachment

Categories

(Thunderbird :: Mail Window Front End, defect)

x86
Linux
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: kserrine, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 Build Identifier: Thunderbird 1.5 here is the message source (minus some of the headers) MIME-Version: 1.0 Content-type: multipart/mixed; Boundary="0__=09BBFA67DFE67B378f9e8a93df938690918c09BBFA67DFE67B37" Content-Disposition: inline X-Screened: intramail2.cis.cat.com --0__=09BBFA67DFE67B378f9e8a93df938690918c09BBFA67DFE67B37 Content-type: text/plain; charset=US-ASCII we are using the server at: 172.22.120.155 to try to send smtp mail (See attached file: snap report error.txt) --0__=09BBFA67DFE67B378f9e8a93df938690918c09BBFA67DFE67B37 Content-type: application/octet-stream; name="snap report error.txt" Content-Disposition: attachment; filename="snap report error.txt" Content-transfer-encoding: base64 U3lzdGVtLldlYi5IdHRwRXhjZXB0aW9uOiBDb3VsZCBub3QgYWNjZXNzICdDRE8uTWVzc2FnZScg b2JqZWN0LiAtLS0+IFN5c3RlbS5SZWZsZWN0aW9uLlRhcmdldEludm9jYXRpb25FeGNlcHRpb246 IEV4Y2VwdGlvbiBoYXMgYmVlbiB0aHJvd24gYnkgdGhlIHRhcmdldCBvZiBhbiBpbnZvY2F0aW9u LiAtLS0+IFN5c3RlbS5SdW50aW1lLkludGVyb3BTZXJ2aWNlcy5DT01FeGNlcHRpb24gKDB4ODAw NDAyMTEpOiBUaGUgbWVzc2FnZSBjb3VsZCBub3QgYmUgc2VudCB0byB0aGUgU01UUCBzZXJ2ZXIu IFRoZSB0cmFuc3BvcnQgZXJyb3IgY29kZSB3YXMgMHg4MDBjY2M2OC4gVGhlIHNlcnZlciByZXNw b25zZSB3YXMgNDUwIDQuNy4xIFJlbGF5aW5nIGRlbmllZC4gUGxlYXNlIFJlZ2lzdGVyIGF0IGh0 dHA6Ly9zbXRwcmVnLmNpcy5jYXQuY29tDQo= --0__=09BBFA67DFE67B378f9e8a93df938690918c09BBFA67DFE67B37-- Reproducible: Didn't try The attachment can be saved to the harddrive and viewed manually.
Content-type: application/octet-stream; I believe that's the problem; it's an incorrect content type
Here is another one that doesn't open. The content-type seems correct in it: Content-Type: multipart/mixed; boundary="----------=_1137183159-21311-120" MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.44 This is a multi-part message in MIME format... ------------=_1137183159-21311-120 Content-Disposition: inline To log into Bugzilla, use the following login and password: Login: kserrine@cat.com Password: To change your password, go to: https://bugzilla.mozilla.org/userprefs.cgi Before submitting bug reports, please: - read the bug-writing guidelines: http://www.mozilla.org/quality/bug-writing-guidelines.html - look at the list of most frequently reported bugs to make sure your problem hasn't already been reported: http://www.mozilla.org/quality/most-frequent-bugs/ To submit a bug report, go to: https://bugzilla.mozilla.org/enter_bug.cgi We encourage you to to get involved in the Mozilla project. There are many ways to help out -- see our Get Involved page for ideas: http://www.mozilla.org/get-involved.html ------------=_1137183159-21311-120 Content-Type: text/plain; name="SpamAssassinReport.txt" Content-Disposition: inline; filename="SpamAssassinReport.txt" Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Mailer: MIME-tools 5.411 (Entity 5.404) Spam detection software, running on the system "monty.cis.cat.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see postmaster@cat.com for details. Content preview: To log into Bugzilla, use the following login and password: Login: kserrine@cat.com Password: To change your password, go to: https://bugzilla.mozilla.org/userprefs.cgi [...] Content analysis details: (1.6 points, 4.7 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.2 NO_REAL_NAME From: does not include a real name 1.4 ADDRESS_IN_SUBJECT To: address appears in Subject ------------=_1137183159-21311-120--
Completely removed Thunderbird and re-installed. Problem no longer exists.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.