Closed Bug 1003082 Opened 11 years ago Closed 11 years ago

Verify/verification link broken in mails for confirming registration of a Firefox Accounts for sync if reading mail in Outlook

Categories

(Cloud Services :: Server: Firefox Accounts, defect, P1)

x86_64
Windows 8.1
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: aryx, Unassigned)

Details

(Whiteboard: [qa+])

Got two reports today that the verification email with the link to verify that you are the owner of the mail address you want to use for Firefox Accounts/Sync is borked in Outlook (at least 2007). The button gets converted to an image and the link is shown as http:///
Summary: Link broken → Verify/verification link broken in mails for confirming registration of a Firefox Accounts for sync if reading mail in Outlook
Component: Server: Registration → Server: Firefox Accounts
Confirmed in Outlook 2013, the link appears to be "http://" and doesn't open properly in the browser.
Viewing the same email in thunderbird shows the correct link.
Adding John Gruen, he is our email wizard and may have some insight.
The email appears to have some outlook-specific <!--[if mso]> tags around the link: <!--[if mso]> <v:roundrect xmlns:v="urn:schemas-microsoft-com:vml" xmlns:w="urn:schemas-microsoft-com:office:word" href="http://" style="height:40px;v-text-anchor:middle;width:300px;" arcsize="10%" stroke="f" fillcolor="#0095DD"> <w:anchorlock/> <center> <![endif]--> <a href="{{{link}}}" style="text-decoration:none;font-size:20px;font-family:Helvetica;display:block;color:#FFFFFF;padding:15px !important;-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%;">{{t "Verify"}}</a> <!--[if mso]> </center> </v:roundrect> <![endif]--> If I remove them then my Outlook2013 will render the link correctly, but uglily.
Oh, I see: <v:roundrect ... href="http://" ...> I guess we need to fill in the URL here as well as in the <a> tag?
Could the "href=://" next to "xmlns:w="urn:schemas-microsoft-com:office:word" be the problem?
Priority: -- → P1
Whiteboard: [qa+]
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.