Closed Bug 1427539 Opened 8 years ago Closed 8 years ago

Comment is discarded if placed after the email address

Categories

(Thunderbird :: Message Compose Window, defect)

Product:
Thunderbird
Component:
Message Compose Window
Version:
52 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 147346

People

(Reporter: mail, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:57.0) Gecko/20100101 Firefox/57.0 Build ID: 20171226083017 Steps to reproduce: Send an email at an address containing a comment. E.g. john@example.org(comment) Actual results: Email gets send to john@example.org Expected results: Email gets send to john@example.org(comment)
Comments are supported, but they go before the e-mail address. Example: Reporter (New to Bugzilla) <test@example.com>
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
Well, that's nice, but no fix for the problem. https://tools.ietf.org/html/rfc5322 defines which comments are allowed and Thunderbird is obviously not adhering to that standard. For more context: I want to send an email to a client which performs different actions based on the content of a comment at the end of the address. As Thunderbird simply removes the comment this is obviously not working.
Well, can you point me to the exact section in RFC 5322. When reimplementing header parsing, we invested some work into getting comments going. If you have a paying client, maybe you want to consider submitting a patch or paying someone to fix it for you since TB is open source mostly maintained by volunteers.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Summary: Comment in email address is discarded → Comment is discarded if placed after the email address
The "Folding White Space and Comments" on page 11 (https://tools.ietf.org/html/rfc5322#page-11) describes the format of comments. But actually I don't understand why Thunderbird is reformatting my input anyways. Shouldn't it just use the address as is and not modifying it? Well, that client is written by me and unfortunately nobody is paying for it
(In reply to mail from comment #4) > The "Folding White Space and Comments" on page 11 > (https://tools.ietf.org/html/rfc5322#page-11) describes the format of comments. That speaks more to Folding than the placement of comments. 3.4 and 3.4.1 are somewhat more relevant to placement. If https://en.wikipedia.org/wiki/Email_addressis correct, then "comments are allowed with parentheses at either end of the local-part; e.g. john.smith(comment)@example.com and (comment)john.smith@example.com are both equivalent to john.smith@example.com."
I read Wikipedia (https://en.wikipedia.org/wiki/Email_address), too, but the important paragraph is below: Comments are allowed in the domain as well as in the local-part; for example, john.smith@(comment)example.com and john.smith@example.com(comment) are equivalent to john.smith@example.com.
Indeed. I failed to notice there are section headers.
Intersting issue. So I created a test message in draft folder and edited it using headertoolslite addon From: Wayne S Mery <vseerror@y.z> me Subject: test To: "Wayne Mery (gmail)" <wm@gmail.com> "you" When I do edit draft the compose window shows Wayne Mery (gmail)you <wm@gmail.com> But this is not new. We are staring at bug 147346
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago → 8 years ago
Component: Untriaged → Message Compose Window
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.