116044 - reply looks like fwd inline?

Status: VERIFIED FIXED

(MailNews Core :: Composition, defect, P2)

Description

[(not reading, please use [e-mail] instead)]

reply looks like fwd inline?

let me give you a screen shot.

Comment 1

[(not reading, please use [e-mail] instead)]

Attachment: screen shot, did a reply.

Comment 2

[(not reading, please use [e-mail] instead)]

also note how "To:"  is quoted twice.

note, this may be related to #116022

which is the crash I get when trying to delete the extra header goop from the 
reply body.

Comment 3

[Jean-Francois Ducarroz]

Which build are you using? We got this problem a while ago and has been fixed since!

Comment 4

[Sheela Ravindran]

I am using build 2001-12-18-06 on win98. Reply does not include any header
information just the body of the message.  
Is this on today's builds?

Comment 5

[Håkan Waara]

I tried reproducing with HTML mail on using an IMAP account on today's build: 
worksforme.

2001-12-18-03, Windows 98.

Comment 6

[(not reading, please use [e-mail] instead)]

I'm using a build from this morning, my own debug build build.

Comment 7

[(not reading, please use [e-mail] instead)]

I'll double check which one I'm using, and try a nightly.

Comment 8

[Jean-Francois Ducarroz]

*** Bug 116051 has been marked as a duplicate of this bug. ***

Comment 9

[Jean-Francois Ducarroz]

Last time we got this problem it was cause by a problem with setting the query
part of an url.

Comment 10

[Tracy Walker [:tracy]]

I'm seeing this on commercial builds:

linux 2001-12-19-08-trunk
mac 2001-12-19-11-trunk

Comment 11

[Jean-Francois Ducarroz]

This is a regression caused by my checkin early this morning! I'll attach a
patch soon...

Comment 12

[Jean-Francois Ducarroz]

Attachment: Prposed fix, v1

I cannot call SetMimeOutputType() to initialize mMimeOutputType before we
execute the Init because it set the variable mAlreadyKnowOutputType to true
wich cause the Init function to not call DetermineOutputFormat which if the
function that retreive the query part of the URL mime is processing!

Comment 13

[Sheela Ravindran]

*** Bug 116338 has been marked as a duplicate of this bug. ***

Comment 14

[[not reading bugmail]]

for those that want more examples, they are in the newsgroups too.. see
n.p.m.mail-news group.. using last couple nightlies.

Comment 15

[Cavin Song]

Comment on attachment 62239 [details] [diff] [review]
Prposed fix, v1

r=cavin.

Comment 16

[(not reading, please use [e-mail] instead)]

Comment on attachment 62239 [details] [diff] [review]
Prposed fix, v1

sr=sspitzer

Comment 17

[Jean-Francois Ducarroz]

Fixed and checked in

Comment 18

[Tracy Walker [:tracy]]

verified fixed on commercial builds:

win 2001-12-26-06-trunk
linux 2001-12-26-06-trunk
mac 2001-12-26-04-trunk

Comment 19

[jay garcia]

Win98SE 2002011604

Guess what ?? It's baaaack ... But only in a newspost reply, not in email.

Comment 20

[jay garcia]

More ...

Really strange now. The ONLY server effected is msnews.microsoft.com as all 
others do not exhibit this bug.

Comment 21

[scottputterman]

an example of this is:

go to msnews.microsoft.com
subscribe to microsoft.public.msdn.magazine
put yourself in threaded mode.
Look for the 1/7/2002 6:22am message from MATEUSZ Z. titled "o grach"

Display it and then reply to it and you'll see this.

Comment 22

[jay garcia]

Seems to be mysteriously "fixed" in this morning's build 2002011703 as I cannot
dup in any group on the msnews server.

Comment 23

[scottputterman]

I'm still seeing this in the 2002011703 build.

Comment 24

[Brian Rogers]

This should be an 0.9.8 blocker.  I just tested, and this affects the latest
branch build.  Certain posts will always show this problem when you try to
reply, and when you try to delete the header junk, it will crash.

Comment 25

[Håkan Waara]

Raising priority for discoverability. Can someone give an easy way to reproduce
this?

Comment 26

[R.K.Aa.]

was this related to bug 116022?
Bug 124222 is now reported w/2002020703 - with the old steps to reproduce the crash.

Comment 27

[scottputterman]

Did this get fixed by 120502?  Seth fixed this and it occurred on the same
newsgroups.

Comment 28

[Jean-Francois Ducarroz]

It's easier to see the problem using an html compose window (like in the dump
screen)

Comment 29

[Jean-Francois Ducarroz]

the problem was cause by the fact the message id contains a "#". The fix for bug
120502 fixes this problem as well. Closing again.

Comment 30

[laurel]

OK using feb21 commercial trunk: win98, mac OS 10.1, linux rh6.2