26133 - reply-all to newsgroup failed on IMAP on particular msg

Status: VERIFIED WONTFIX

(MailNews Core :: Backend, defect, P3)

Description

[selmer (gone)]

The server complained about not being able to reach the address.  Perhaps the
address was malformed?

The resulting window did not display the to: or cc: information, so it's very
very difficult to correct...

Comment 1

[selmer (gone)]

Tried this again.  The to: and cc: aren't there even after just hitting the
reply-all button.

Comment 2

[Phil Peterson]

Reassign to ducarroz

Comment 3

[laurel]

Could you let me know what build, what OS you were using?

I just tried reply-all in a newsgroup on 2000-02-01-08 m14 commercial build NT
4.0 and 2000-02-01-10 m14 commercial build linux rh6.0 and got To: and
Newsgroup: addressee headers in the compose window (html).  I don't get the cc:
however, on news messages with cc: (I can separate that issue out).

I also get no error about the address.  Maybe you could give more detail about
the steps and/or server(s) you used?

Comment 4

[selmer (gone)]

Attachment: Seamonkey Save-As copy of offending email

Comment 5

[selmer (gone)]

How nice.  Adding an attachment blows away the text in the additional comments :(

Anyway, I'm using the same build as you and I can reproduce this at will on my
machine.  I have attached the message to this bug.  The error dialog on send
tells me that <n.p.m.seamonkey> is "User Unknown" and hitting OK just takes me
back to the compose window without telling me what happened with the other
recipients.

Trying this again, I noticed that all the fields initially drew themselves, but
then they all got replaced with a grey background except the subject edit field.

Comment 6

[laurel]

OK, reply-all to the attached message posted in n.p.m.seamonkey I'm seeing an
error on send on NT only, but I indeed get newgroup: and to: headers in the
compose window. The alert dialog I see doesn't specify text for error, rather a
string ID error: [StringID(hex)=8007000e?].  I get two alerts, probably one for
each newsgroup.

I was able to reply-all from linux to this same message, and the send
succeeded.  On both machines I have the server pref set to abbreviate newsgroup
names, and indeed the names are abbreviated. On both machines, I'm using
nsmail-2/dredd as smtp mail server and had authenticated to that server under
IMAP account/nsmail-2.

That's my update info so far...

cc: sspitzer for any news input.

Comment 7

[laurel]

With regard to selmer's comments today at 16:34, I believe that symptom was bug
#25103.
His comments: "I noticed that all the fields initially drew themselves, but then
they all got replaced with a grey background except the subject edit field."

Comment 8

[Jean-Francois Ducarroz]

Laurel, could you try again to see if you still see this problem? Thanks

Comment 9

[laurel]

Using 2000-03-07-09m15 commercial build on NT 4.0 I'm still seeing similar
results as I was on feb01 when doing a reply all to the message in question:

Reply all comes up with all the headers filled in for the compose window
(plaintext compose). Upon send I get two string ID errors: 8007000e.  Upon OK,
I'm back in the compose window and the message isn't sent.

Notes:  
1. I do have my fcc folder set up properly for both my mail and news account.
2. I am able to reply all with no error to another netscape.public.mozilla.test
group message which has been cross-posted.

Comment 10

[selmer (gone)]

Mass moving M16 to M17 - look for nsbeta2 before anything else.

Comment 11

[lchiang]

Laurel - can you check this again?

Comment 12

[scottputterman]

Do we think this is common enough that we should nominate it for beta3?

Comment 13

[laurel]

Well, I didn't get the same results using jun09 commercial build, but then
again, Reply and Reply All doesn't work to pre-address the newsgroup headers
anymore; I had to Reply, then fill in the newsgroup headers myself. So, if this
bug was indeed caused by some malformed header, taking away the Reply/Reply All
functionality might explain why it's working.

To answer putterman's last question:  I haven't seen this elsewhere in
reply-alls to news postings, but I haven't used seamonkey that much for
newsreading consistently.  Until the cause is determined, it's hard to say how
common it would be.

Comment 14

[scottputterman]

marking WONTFIX unless we can reproduce.  If that's the case, please reopen.

Comment 15

[lchiang]

Mark verified for now.  If more reports of this, we'll see add'l bug reports.