Closed Bug 24060 Opened 25 years ago Closed 25 years ago

Send as plain text leaves mailto: tags in message

Categories

(MailNews Core :: Composition, defect, P3)

Product:
MailNews Core
Component:
Composition
Platform:
Other
Other
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: rzach, Assigned: rhp)

Details

An email address in a message composed in HTML, but sent as plain text, will contain an additional mailto: tag. To reproduce: 1. Open HTML composition 2. Address message to self 3. In the message body, enter "user@test.com" 4. Messgae | Format | Send as plain text 5. Send message Actual result: The message you receive reads: user@test.com <"mailto:user@test.com"> Expected result: The message should just read: user@test.com This is quite annoying if you happen to send to a majordomo server. Linux build 2000.01.14.16
QA Contact: lchiang → pmock
I don't think so it's a bug. I would rather say it's a feature, a nice one! I have not idea who convert the text <name>@< domain> into a maito URL? Beppe, Rich any idea?
Yes, this is a feature of the conversion process. Ben Bucksch is the owner of this code. - rhp
Anyway, if you send as HTML, you get <html><head></head> <body><a href="mailto:user@test.com">user@test.com</a></body> </html> and if you send as plaintext you get the following which is correctly plain text: user@test.com <"mailto:user@test.com"> I will mark this bug as inavlid. Fell free to file a new bug about the feature himself.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
There's a bug on that already actually: bug 28582. Mark verified.
Status: RESOLVED → VERIFIED
Zach, which bug number? (bug 28582 doesn't exist)
> I don't think so it's a bug. I would rather say it's a feature, a nice one! Thanks! However, this feature is indeed only intended to work for HTML send, not plain text send. The scenario is as following: - If the user manually creates a link the the message and sends it as plain text (maybe only to some recipients), the URL is inserted after the link text in order not to loose data. (BTW: It should be put out in angle brakes, but without extra quoutes, but that would be a different bug.) - If the user enters URLs in the body, but does not linkify them, we do the work for him, *if the message is sent as HTML*. This makes it more convient for the recipient to access the URL. However, these two functions don't mix well, but procude the described redundancy, when used together. (Same applies for "*hello*", which will propably result in "**hello**".) Proposed fix: Run the enhancement (|mozTXTToHTMLConv::ScanHTML|) only for parts, that are sent out as HTML. REOPENING.
Status: VERIFIED → REOPENED
Rich, can you take care of this "bug"?
Resolution: INVALID → ---
Ben...all yours :-)
Assignee: ducarroz → mozilla
Status: REOPENED → NEW
For the record, it's bug 23582.
heh. But this is an issue about calling the function, not in the function itself. I have no clue, were to move the call to in order to achieve the described effect.
Assignee: mozilla → ducarroz
QA Contact: pmock → lchiang
Rich, you're next...
Assignee: ducarroz → rhp
I'll get to it later... - rhp
Status: NEW → ASSIGNED
Target Milestone: M14
Ok, if the message has been forced to be plain text, we no longer do the conversion. I'll checkin when M14 opens. - rhp
Summary: Send as plain text leaves mailto: tags in message → [FIXED] Send as plain text leaves mailto: tags in message
Just checked in the fix for this problem. - rhp
Status: ASSIGNED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
Summary: [FIXED] Send as plain text leaves mailto: tags in message → Send as plain text leaves mailto: tags in message
Works on 2000.01.29.09 as expected. Verifying.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.