Closed
Bug 4723
Opened 26 years ago
Closed 26 years ago
Msgs sent from Seamonkey and viewed in 4.5 are Type C and can't be read without an editor
Categories
(MailNews Core :: Backend, defect, P3)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: esther, Assigned: bugzilla)
Details
Seamonkey 1999040710 win32 April 7 build
Hardware: Win95
1. Launch apprunner
2. Open Messenger via Task menu
3. Click on New Msg, put an email address in the To: field that you can view in
4.5., type in a subject and Send.
4. Open 4.5 in Windows and get the message. The message is displayed as a link
with a Type C, Encoding 7bit. At this point you have to click on the link and
select an option for viewing.
Note: this was only tried from Windows Seamonkey, not sure at this time, if
linux sends mail this way.
Updated•26 years ago
|
Status: NEW → ASSIGNED
Comment 2•26 years ago
|
||
virtual phil --> I'll take a look at this first. I know I18N was checking some
stuff in over the weekend involving mime encoding of outgoing messages...that
may or may not be the cause.
How about this though...our first instance of seamonkey being better at
something (in mail anyways) than 4.5!!! It can view the message just fine.
Comment 3•26 years ago
|
||
Not sure....I haven't done anything yet with sending side mime stuff. Can you
send me the message and I can take a look at it.
- rhp
Comment 4•26 years ago
|
||
Rich, I don't know if it is you either. If you want to see the problem, just
send yourself a message using the mail client. Try to view the message in
Communicator 4.5. You'll see the problem.
Updated•26 years ago
|
Assignee: phil → ducarroz
Status: ASSIGNED → NEW
Comment 5•26 years ago
|
||
Reassign to ducarroz@netscape.com, cc nhotta@netscape.com
Comment 6•26 years ago
|
||
Is this Win95 only? I have a problem of reproducing this (apprunner craches as
soon as opening the messenger, tried 4/12&4/13 build).
Could someone send a message with the problem to me (nhotta@netscape.com)?
Comment 7•26 years ago
|
||
Naoki, you need to rename your prefs.js to prefs50.js in order to get passed the
crash. I'm afraid we renamed the prefs file before we properly broadcasted the
change to everyone to give them a heads up. For more details see Seth Spitzer's
posting in the mailnews newsgroups.
Comment 8•26 years ago
|
||
Actually, I had no prpoblem with the 4/12/99 build until I renamed
prefs.js to prefs50.js. So this change starts with 4/13/99 build,
right?
In the meantime, I could run 4/12/99 build with the old prefs.js and
have not seen this problem with it. Is there a sa mple prefs.js entries
you are using somewhere. The one I'm using is found here:
http://rocknroll/users/momoi/publish/bugs/
Comment 9•26 years ago
|
||
Sorry, the URL was wrong. It is prefs.js found here that I'm using:
http://rocknroll/users/momoi/publish/
Comment 10•26 years ago
|
||
Ok. I renamed prefs.js to prefs50.js for 4/13/99 build and
mailed a msg to 4.5x client. I still cannot reproduce this problem.
Updated•26 years ago
|
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → WORKSFORME
Comment 11•26 years ago
|
||
worksforme
Comment 12•26 years ago
|
||
Since you had a specific case for this, can you verify this bug, Esther?
Reporter | ||
Comment 13•26 years ago
|
||
Using win 32 build 1999042708 and linux build 1999042708 this now worksforme
too. It magically went away. Verified as worksforme
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•