Email confirmation email flagged as Spam in Outlook.com #209
Comments
|
Running email on acid test with Ryan |
|
We failed 1 out of 71 blacklists: |
|
Humph, if you use a popular web search engine to search for "amazon ses sorbs" you will find several threads about their sending IPs ending up in that particular blocklist. |
|
Ops bug here: https://bugzilla.mozilla.org/show_bug.cgi?id=1318513 |
|
@rfk do we have any updates here? |
|
No concrete updates here, but we can dive into it in earnest now that the new year is under way:
If that doesn't have an impact, we'll have to look at getting standalone sending IPs and enrolling in programs such as those identified in https://bugzilla.mozilla.org/show_bug.cgi?id=1318513#c19 |
|
From what I understood, we didn't need our own IP for enrolling in the program. Seems like once we are removing bounced emails, we should sign-up to that program since we should be abiding by almost every best practice and then if we still have no luck, we can look into our own IPs. |
|
from mtg: discussion should migrate to feature doc / feature card. |
|
@rfk to migrate this to features infra rather than keeping this meta-issue alive |
|
from mtg: some of the info from here will need to be added to the feature doc... |
|
Tracked in fxa-56 #211 |
chore(awsbox): remove awsbox.json for fxa-content-server



User reported on Twitter that FxA was flagged in Outlook.com as spam: https://twitter.com/ltCatscratch/status/798958950813204481
@shane-tomlinson also confirmed the same thing with his account: https://irccloud.mozilla.com/file/goLbWeUy/Screen%20Shot%202016-11-17%20at%2017.45.48.png
I tested with my dummy Outlook account but was not flagged as spam.
Things to check:
The text was updated successfully, but these errors were encountered: