Closed
Bug 424064
Opened 17 years ago
Closed 14 years ago
trailing colon ':' should not be included when autolinking plain text e-mail addresses
Categories
(MailNews Core :: Backend, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 278341
People
(Reporter: a.nielsen, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.8.1.11) Gecko/20071210 Firefox/2.0.0.11
Build Identifier: 2.0.0.9 (20071210)
If you have a plaintext e-mail with text such as this, generated by many mailing lists:
Or include the following line -- and only the following line -- in a
message to linux-dvb-request@linuxtv.org:
The e-mail address is highlighted, so you can click on it. But it also includes the colon as part of the e-mail address, when it's not. This means the e-mail bounces unless you remember to remove the trailing colon.
I don't know whether you can specify port addresses with e-mail domains, but either way a colon with no port address shouldn't be part of the e-mail address.
Reproducible: Always
Steps to Reproduce:
1. Type in an e-mail address with a trailing colon in an e-mail
2. Send it to yourself
3. Open the e-mail and click on the address - you'll see Thunderbird tries to send it to the address with the trailing colon
Actual Results:
Trailing colon is treated as part of the e-mail address
Expected Results:
Trailing colon should not be treated as part of the address (in the same manner as a trailing full-stop, for example.)
Comment 1•17 years ago
|
||
Confirming.
Status: UNCONFIRMED → NEW
Component: Mail Window Front End → MailNews: Backend
Ever confirmed: true
OS: Linux → All
Product: Thunderbird → Core
QA Contact: front-end → backend
Hardware: PC → All
Summary: Extra characters included when hyperlinking e-mail addresses in plaintext message view → trailing colon ':' should not be included when autolinking plain text e-mail addresses
Assignee | ||
Updated•17 years ago
|
Product: Core → MailNews Core
This is still a problem in TB8.
However, it does not happen in my dev build of TB11, where bug 278341 is fixed.
I assume it is a duplicate of it. Please reopen if it does not get fixed by the patch there.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Version: unspecified → 1.8 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•