On 10/9/2014 12:17 PM, David E. Ross wrote:
> On 10/9/2014 11:35 AM, Paul B. Gallagher wrote:
>> David E. Ross wrote:
>>
>>>> RFC 5322 requires that your
>>>>    Personal Name @ Gmail <[email protected]>
>>>> instead be
>>>>    "Personal Name @ Gmail" <[email protected]>.
>>>> The quotes are required because the display name (Personal Name @ Gmail)
>>>> contains the restricted character @ ("special character" in the
>>>> terminology used in the RFC).
>>>>
>>>> While some E-mail clients might handle
>>>>    Personal Name @ Gmail <[email protected]>
>>>> without quoting the display name, such applications are not required to
>>>> do so.
>>>
>>> I just ran a test in Thunderbird, which I believe uses the same MailNews
>>> Core component as does SeaMonkey.  This test only applied to new
>>> message, not replies or forwards.
>>>
>>> If the display name is of the form "daughter @ home" with the
>>> quotes, the quotes are retained and not doubled. If the display name
>>> is that way but without the quotes, MailNews Core adds quotes to
>>> comply with RFC 5322.
>>
>> If the program added quotes around the entire display name:
>>      daughter @ home => "daughter @ home"
>> then there would be no problem. This is what happens with my real name, 
>> which contains a period. But as you've seen in my example, the actual 
>> response with an "@" character differs, most importantly in that it 
>> damages the original angle brackets intended to delineate the actual 
>> email address.
>>
>>> Not having received any E-mail messages with @ in the sender's
>>> display name, I would have to contrive such a message to test replies
>>> and forwards. I decline to do so.
>>
>> It's trivially easy to modify your own display name and compose a 
>> message, which you then save as draft or send to yourself to observe the 
>> results. But if you don't want to bother, I understand.
>>
>> The damage to the angle brackets is consistent and reproducible. When 
>> the display name contains the "@" character, the angle brackets are 
>> always mangled.
>>
>> I haven't tested with other special characters (other than period as 
>> noted above).
>>
>> I tested SeaMonkey's handling of display names containing the "@" 
>> character as follows: I went into my email settings and specified
>>      "Paul @ Gallagher"
>> WITH quotation marks as my display name (in the "Your Name" field). The 
>> results are as follows:
>>
>> 1) In the sent message source code, the display name is not quoted, but 
>> the email address is correctly enclosed in angle brackets:
>>      From: Paul @ Gallagher <[email protected]>
>> (I've purposely munged my email here to defeat the spambots, but I used 
>> a valid address in my test).
>>
>> 2) On receipt, the incoming message source code similarly contains the line
>>      From: Paul @ Gallagher <[email protected]>
>> with angle brackets but no quotation marks, mimicking the sent message 
>> source code.
>>
>> 3) In the receiving account, SeaMonkey displays that incorrectly marked 
>> sending address as
>>      "Paul@Gallaghermyprefix"@mydomain.com
>> and uses that string in the To: field of a reply.
>>
>> I conclude that SeaMonkey is stripping the quotation marks that I 
>> entered in the "Your Name" field of my account settings. The problem 
>> lies not with the parser used to compose replies (it garbles mismarked 
>> From: fields even further), but with the sending routine that strips the 
>> quotation marks and thereby creates mismarked From: fields.
>>
>> Thus, it is not a feasible option with this program to use quotation 
>> marks to delineate such a display name -- unless they must be entered 
>> with some escape character such as a backslash. I did try this:
>>      \"Paul @ Gallagher\"
>> as my display name, and it was rendered as
>>      "\\\"Paul @ Gallagher\\\""
>> in the sent and received message source codes. However, a reply to that 
>> message bounced:
>>
>> Your message cannot be delivered to the following recipients:
>>
>>    Recipient address: "Paul@Gallaghermyprefix"@mydomain.com
>>    Reason: Remote SMTP server has rejected address
>>    Diagnostic code: smtp;554 5.7.1 
>> <Paul@[email protected]>: Relay access denied
>>
>> Just as before, the display name was merged with the email address, 
>> overriding both the quotation marks and the angle brackets.
>>
> 
> In my tests, the @ character was bracketed by a blank space on each
> side.  I then repeated the tests without blank spaces bracketing the @.
>  I sent the messages to my daughter but used Send Later so that they
> would not really go out.  I then viewed the message sources.  In all
> cases, the quotes entirely bracketed the display name and only bracketed
> the display name.
> 
> I did not escape the explicit quote marks.  I did not place <> brackets
> around my daughter's actual E-mail address in my Address Book, but
> Thunderbird added them.  They were properly positioned.
> 
> I am quite sure that the same MailNews Core -- containing the Address
> Book component -- used by Thunderbird (which I used for my tests) is
> also used by SeaMonkey.
> 
> Have you tried your cases in SeaMOnkey's Safe Mode?  I will redo my
> tests in Thunderbird's Safe Mode later today, after I tend my garden
> (this being the first in many days without a heat wave).
> 

I retested in Safe Mode.  Your problem with corrupted E-mail addresses
did not appear.

I also sent messages -- both in Safe Mode and also with extensions
enabled -- with my own display name formatted as "David E. Ross @ home"
by modifying the "Your name" in the main pane of the Account Settings
window.  I sent these to a little used E-mail account of mine and then
replied to my primary E-mail account with that modified display name.  I
was unable to get a corrupted E-mail address to the recipient in any of
these cases.

By successfully testing not in Safe Mode, I believe I verified that none
of the following extensions cause your problem:
CompactHeader
MagicSLR
Mail Redirect
NoGlass theme
PopMailListRecipients
Reply to All as CC
Rise of the Tools
Send Filter
Signature Switch
Smiley Fixer
Theme Font & Size Changer
Toggle Word Wrap
Toolbar Buttons

-- 
David E. Ross

I am sticking with SeaMonkey 2.26.1 until saved passwords can
be used when autocomplete=off.  See
<https://bugzilla.mozilla.org/show_bug.cgi?id=1064639>.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to