Closed Bug 1175412 Opened 10 years ago Closed 8 years ago

After completing FTE, I received 2 different sign-up confirmation emails for the "FIREFOX & YOU" newsletter

Categories

(Firefox OS Graveyard :: Gaia::First Time Experience, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(b2g-master affected)

RESOLVED WONTFIX
Tracking Status
b2g-master --- affected

People

(Reporter: dholbert, Unassigned)

Details

(Whiteboard: [spark][aries])

STR: 1. Go through the First Time Experience (in a newly-flashed device, in my case) 2. During this process, sign into your Firefox Account. (not sure if this matters, but it might, because it's one way that you provide your email address) 3. At the final screen, leave the "sign me up for email" box checked (as it is by default), and complete the FTE process. 4. Check your email inbox (on any computer). ACTUAL RESULTS: I received two distinct emails with the following subject line: > Action required: Please confirm your subscription to Firefox & You It wasn't (quite) two copies of the same email, because the "reply-to" field was different. The first one looked like this (shortened with [SNIP]): > Reply-To: "Mozilla" <reply-[SNIP]-625560@e.mozilla.org> and the second one looked like this: > Reply-To: "Mozilla" <reply-[SNIP]-625561@e.mozilla.org> Note the "0" vs "1", just before the @. So, we're generating & sending two distinct emails. This is probably bad, given that many people (me at least) are apprehensive at signing up for mailing lists due to concerns about receiving too much mail. If we send 2 confirmation emails for no good reason, this will likely turn many users off (and leave them with a negative impression).
I've encountered this problem twice, BTW; sometime around 5/29, when I first flashed my Xperia Z3C with Firefox OS, and today when I reflashed it with an updated aries.zip file. So, it wasn't a one-off server blip. (The first time, IIRC, the two emails were separated by several hours. Today, they came back-to-back, right away.)
Actually it looks like on my last flash (5/29), the two emails I received had these 2 subject lines: (1) Action required: Please confirm your subscription to Firefox OS (2) Action required: Please confirm your subscription to Firefox & You and they were sent about 10 hours apart. After my reflash today, both email confirmations had the same subject line, about "Firefox & You". (Side note: I don't think I've ever clicked the "click to confirm" link, if that matters.)
Suspect this is spark/aries -specific? I'm also not sure who deals with the subscriptions. I'm also worried about this opt-out/mandatory opt-in approach. A part of the dogfooding program should include some respect for people's time and choices.
Keywords: qawanted
Whiteboard: [[spark][aries]
QA Contact: bzumwalt
Whiteboard: [[spark][aries] → [spark][aries]
Issue occurs as stated on Spark 3.0 On Flame user receives two emails only if they tap done on "About Firefox OS" screen after completing Firefox Account signup (this page has email field already filled with same email user put in for Firefox Account.) On Spark devices the user only needs to complete Firefox account signup in order to get both emails. Device: Flame 3.0 Build ID: 20150617010205 Gaia: 6271f932e1e918a35ee89f54288bd13385143a71 Gecko: d7c148c84594 Gonk: a4f6f31d1fe213ac935ca8ede7d05e47324101a4 Version: 41.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0 Device: Aries 3.0 Build ID: 20150617002346 Gaia: 6271f932e1e918a35ee89f54288bd13385143a71 Gecko: d7c148c84594 Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd Version: 41.0a1 (3.0) Firmware Version: D5803_23.1.A.1.28_NCB.ftf User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Keywords: qawanted
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.