144732 - Can not forward message as inline while *previous* signature existing.

Status: RESOLVED DUPLICATE of bug 49484

(MailNews Core :: Networking, defect)

Description

[Yeh You-Ying]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0rc2) Gecko/20020510
BuildID:    2002051006 (RC2)

While forward a message as inline with "previous" signature, 
the message can not besent out.


Reproducible: Always
Steps to Reproduce:
1. Make a signature with HTML style
2. Send a HTML message with your HTML signature
3. Get the message and forward it as inline with your HTML signature
4. You will see it can not be sent out.
5. IF you removed the "previous" signature, and then the forward message can be
    sent out.

Actual Results:  The message should be sent out any way.

This problem exists for long long long time.

Comment 1

[Yeh You-Ying]

Attachment: My HTML Signature

Comment 2

[Yeh You-Ying]

Attachment: I send this HTML message to myself, with my HTML signature file

Comment 3

[Yeh You-Ying]

Attachment: Source of forwarded message.

Comment 4

[Yeh You-Ying]

Attachment: What I saw while sending message with 2 signatures...Just fail...

Please note the red circle and words in the pic.
If I removed the red circle, the message can be sent out successfully.

Comment 5

[timeless]

this is in the release notes

*** This bug has been marked as a duplicate of 49484 ***

Comment 6

[esther]

Reporter, the dup for this bug was resolved as worksforme and verified.  In that
bug it stated very early on that <div class="signature "> tags didn't work, but
toward the end of the bug the messages that were failing were working.  I saved
your message to my local folder and was able to forward it to myself (note I did
not have your HTML signature to add to the message because it was attached to
this bug in plain text)I was in HTML compose and did a forward inline.  The
forwarded message came in OK, complete with your signature.  I confirmed this
worked in the 6.2.2 commercial released build and latest commercial build.
Please attach your html signature again using the HTML option and/or try this on
the 6.2.2 commercial build.  I may be missing something in testing your bug.