Closed Bug 1624543 Opened 6 years ago Closed 6 years ago

[SUMO User Issue] Specific email not receiving emails Investigation of 576788998@qq.com

Categories

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

Product:
Cloud Services
Component:
Server: Firefox Accounts
Version:
74 Branch
Platform:
x86_64
Windows 10
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: u659510, Unassigned)

Details

User:
Support Case link

The user has tried the following:
*

I verified with the user that their email is indeed working.

Can we investigate on our side what might be happening or to see if we can unlock the account by attached identity verification.

OS: Unspecified → Windows 10
Hardware: Unspecified → x86_64
Version: unspecified → 74 Branch
Flags: needinfo?(jbuckley)

Hi there, Firefox Accounts received 2 bounces from your email address 576788998@qq.com . I've cleared these bounces, could you please add accounts@firefox.com to your address book and try signing in again? Thanks!

+------------------+------------+---------------+---------------+
| email            | bounceType | bounceSubType | createdAt     |
+------------------+------------+---------------+---------------+
| 576788998@qq.com |          3 |             9 | 1584614786453 |
| 576788998@qq.com |          3 |             9 | 1584615059114 |
+------------------+------------+---------------+---------------+
Flags: needinfo?(jbuckley)

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Severity: normal → S3

The severity of these bugs was changed, mistakenly, from normal to S3.

Because these bugs have a priority of --, indicating that they have not been previously triaged, these bugs should be changed to Severity of --.

Severity: S3 → --
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.