Since April 20th, you may have received some emails asking you to come back to the SaneBox website to enable your account.
This article is meant to explain why you got more than one of those emails, why you might have been enabled without coming back to the website and then disabled again, why this action is necessary to get your account running again, and lastly why enabling a single one of your addresses does not enable them all.
Why did I get so many of these emails?
Each of your email addresses has it's own Google account. Google authorizes the access to those accounts separately. You would have gotten as many emails as you have accounts filtering with SaneBox. We should soon move to a new email which will have all the information about all disabled accounts each time to make it clearer that you have to enable them all.
We have been trying different subjects and different content in these emails to clear up these various confusions and nudge our beloved customers to enable their filtering. So you will probably continue to get these emails until you come back and click on the big green "Enable Account" button on the SaneBox website. So please go do that now. It's easy!
Why did you get disabled and then enabled and then disabled again?
On April 20 2015, Google stopped accepting OAuth 1.0 tokens in order to move to their new OAuth 2.0 technology. You were initially disabled if you still had an OAuth 1.0 token and encouraged to come back to the SaneBox website to reauthorize us.
Those of you that had logged out and logged into SaneBox for whatever reason in the last 3 months would already have had OAuth 2.0 tokens. This part was fully expected. We had done the work to accept OAuth 2.0 tokens already so a single click was all you needed to get your account working again.
Unfortunately and unexpectedly Google did **not** decommission all their old servers at that time. Some of the old OAuth 1.0 servers remained active. We didn't even realize that this was happening because we fully expected everyone to enable themselves in a short time.
So, if we accidentally hit one of those old OAuth servers, your account would have been enabled even though you still had an OAuth 1.0 token.
We think Google finally realized that some of those OAuth1 token servers were still around and decommissioned them last week (around May 6th), hence the additional rounds of disabled accounts.
Why do I have to come back to the website to enable my account - can't you guys do this for me?
We would love to do that, but we can't. This is the one thing you need to do manually on a browser that is *already* logged into Gmail on the account in question. After you click the big green "Enable Account" button, we send a message to Google asking for authentication. You are then prompted by google to authenticate us for the following services: contacts (so we know who is important to you), profile (so we know how to spell your name), mail (so we can filter your email). After you click "authenticated" on the google page, they then send us back the token and this process is complete. WooHoo!
Why can't I click a single time to enable all my Google accounts?
Each of your Gmail and Google Apps accounts is completely separate. They all have a different email address, different profiles, different passwords, etc... SaneBox computers connect to each of your Inboxes as a separate unique authenticated connection. And just like you have to enter a username and password to access each of those accounts, we have to pass the unique OAuth 2.0 token for that account to google for that particular connection. And you wouldn't want Google to pass out authentication for all your accounts with a single token - what if you only want a single account serviced?
SaneBox, like countless other web apps, connects to Google via OAuth. The beauty of OAuth is that you only have to give as much information as necessary to apps connecting to your Google account, thereby keeping your login credentials safe. If you recall, we did not ask for your Gmail username and password when you signed up for SaneBox, but rather you were prompted to authorize SaneBox. This is OAuth in action and it’s a great thing.
How long will this last or will I be disabled again in 2 weeks?
Once you have a new OAuth 2 token and have reauthorized SaneBox, your account should be all set...at least until Google invents OAuth 3! And since it took them 6 years to go from OAuth1 to OAuth2, we think we have some lead time.
What is this OAuth thing anyway?
Here's a good article about the history of OAuth and why it works the way it does: http://hueniverse.com/oauth/guide/intro/
How do I get an OAuth 2.0 token for my SaneBox account?
If all your Inboxes are Sane, then you have one for each Inbox. So, stop worrying and go enjoy your Sane email :-)
If any of your inboxes are in-Sane (filtering disabled), you will have gotten several emails with directions for how to fix this. Just click in the emails.
For those that can't find that email, here are directions. Remember that you have to do this for each Gmail account that is associated with your SaneBox.
To enable your account follow these steps:
- Go to your SaneBox Dashboard (Here are directions for navigating between your email addresses on the dashboard). Click on the tabs that have a triangle with an exclamation mark.
- Click the big green “Enable Account” button. And click "authenticate" when prompted by Google.
- You are done. Stop worrying and go enjoy your Sane-ity :-)
Here's the page with the big green "Enable Account" button:
Again, if you have multiple email addresses linked to your SaneBox account, we need a separate authorization for each email address. If you need help switching between your Gmail addresses, here are instructions.
Thanks for your patience in this matter, and please be aware that you may also need to take similar steps with other third-party apps that you grant permissions to via your Google account.
If you are experiencing any issues re-enabling your account, please drop us a note at email@example.com.
Thanks for being a SaneBox user, and here’s to smooth emailing ahead.