When publishing an article with the attachement the message body is coming up empty. Steps to reproduce: -send yourself from 4.x a message with an attachement; -get it in 5.0; -forward this message to the newsgroup(netscape.test) //note: when viewing the message body is empty

I don't think forwarding works yet. You'd probably see the same results in mail. Do you see this same problem on mail, Marina?

I think that forwarding is in, because i don't see this problem when forwarding to myself.

Reassign to rhp

Attachments in the FE aren't hooked up yet and forwarding is simply quoting with the old quoting code which doesn't handle attachments. In short, none of this is working yet. - rhp

marina - if you agree, pls mark as verified. We'll try this case again once the feature is implemented in 5.0.

i don't think it should be invalid, it might remain assigned or resolved as a reminder till the feature is implemented.

If you'd like, why don't you reopen this bug and assign it to you as a reminder to check this case once Rich has implemented this feature. I'll leave it up to you.

reopening and assigning to myself as a reminder

change qa contact to marina since she wants to track this bug. Thanks.

Because Forwarding and Replying is in i guess it is time to reopen this bug and assign it to the proper person. I tried today's 1999-7-22 build and repeat all steps: take an e-mail from your inbox with an attachement and forward it to the newsgroup(netscape.test)= it comes with an empty mail body.

have to update this bug:now when you forwarding an article with an attachement from your Inbox to the Newsgroup(netscape.test) it doesn't get sent (i'm able to forward a message with NO attachment from my Inbox to the Newsgroup). Steps to reproduce: -send a web page from 4.x to your 5.0 testing account; -get this message in 5.0; -click "Forward" to Newsgroup "netscape.test"; -click "Send"; //note: nothing appeared to be published in netscape.test (you can repeat all the steps above with a message with NO attachment and you'll see it published)

Reassign to sspitzer, cc rhp

Sounds like this needs to be fixed by PR1, so I added a note in the Status Whiteboard

marking m11. accepting. wishing RHP wasn't on sabatical.

(target milestone is M11 or M12 - add to mail beta tracking bug)

rhp, can you look at this?

Hi Jeff, This may actually be fixed already, but it has to do with Forwarding news messages. Marking for M12 and reassigning. - rhp

Make sure smtp and nntp share the same post message code from the base class. nsMsgProtocol.h nsMsgProtocol.cpp nsSmtpProtocol.cpp nsNntpProtocol.cpp changed.

Verified as such.