Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Email confirmation email flagged as Spam in Outlook.com #209

Closed
davismtl opened this issue Nov 17, 2016 · 14 comments
Closed

Email confirmation email flagged as Spam in Outlook.com #209

davismtl opened this issue Nov 17, 2016 · 14 comments
Assignees

Comments

@davismtl
Copy link
Contributor

@davismtl davismtl commented Nov 17, 2016

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:

@davismtl
Copy link
Contributor Author

@davismtl davismtl commented Nov 17, 2016

Suspicion confirmed:
image

The test is still running but for now, nothing else has been flagged.

@davismtl
Copy link
Contributor Author

@davismtl davismtl commented Nov 17, 2016

We failed 1 out of 71 blacklists:

image

http://www.sorbs.net/

@rfk
Copy link
Member

@rfk rfk commented Nov 17, 2016

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.

@davismtl
Copy link
Contributor Author

@davismtl davismtl commented Nov 17, 2016

rfk confirmed it via another tool. We seem to be on two blacklists:

image

An ops bug will be filed to escalate with Amazon.

@rfk
Copy link
Member

@rfk rfk commented Nov 17, 2016

@vladikoff
Copy link
Contributor

@vladikoff vladikoff commented Dec 12, 2016

cc @jrgm @jbuck see bugzilla bug above ^

@davismtl
Copy link
Contributor Author

@davismtl davismtl commented Jan 4, 2017

@rfk do we have any updates here?

@rfk
Copy link
Member

@rfk rfk commented Jan 9, 2017

No concrete updates here, but we can dive into it in earnest now that the new year is under way:

  • When train-77 ships we should get flow events for bounces, which will let us understand get a better handle on our deliverability dynamics
  • We need get cracking on #211 and the associated auth-server issue mozilla/fxa-auth-server#1565

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

@davismtl
Copy link
Contributor Author

@davismtl davismtl commented Jan 9, 2017

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.

@vladikoff
Copy link
Contributor

@vladikoff vladikoff commented Jan 9, 2017

from mtg: discussion should migrate to feature doc / feature card.

@rfk
Copy link
Member

@rfk rfk commented Jan 9, 2017

@rfk to migrate this to features infra rather than keeping this meta-issue alive

@vladikoff
Copy link
Contributor

@vladikoff vladikoff commented Jan 24, 2017

from mtg: some of the info from here will need to be added to the feature doc...

@vladikoff
Copy link
Contributor

@vladikoff vladikoff commented Feb 6, 2017

Tracked in fxa-56 #211

@vladikoff vladikoff closed this Feb 6, 2017
philbooth pushed a commit that referenced this issue Oct 17, 2017
chore(awsbox): remove awsbox.json for fxa-content-server
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants