Session times out two times a day
Proposed
My mailbox.org session times out about two times a day, and having to log in twice is very annoying. Why can't it stay logged in for a reasonable amount of time like any other modern web app?
In the general security settings, I have "Automatic sign out" set to "Never". I understand that a literal "Never" is not practical actually a technically feasible way, but ~4 hours instead is way too short.
I would like my mailbox.org session to keep me logged in at least for a week, and ideally even for more.
You can't vote. Please authorize!
No connection
Real-time notifications may not work
I'm on Beta and am logged out constantly - every time I close my browser, and when I disconnect and reconnect (or am disconnected from) the internet. This didn't happen for me on the standard platform, as it respected the "automatic sign out - never" setting. But perhaps it's not a beta thing after all...maybe this is happening more frequently for everyone. It's a real hassle to be opening my password manager multiple times a day (as I intentionally don't save passwords in my browser), and inserting 1) user name and main password 2) 2FA code 3) Guard password ... then dealing with signing out of ghost sessions that were created by Mailbox.org signing me out without my permission, and then finally resuming my work.
I have already submitted feedback to support staff on this, but nothing has improved.
I'm on Beta and am logged out constantly - every time I close my browser, and when I disconnect and reconnect (or am disconnected from) the internet. This didn't happen for me on the standard platform, as it respected the "automatic sign out - never" setting. But perhaps it's not a beta thing after all...maybe this is happening more frequently for everyone. It's a real hassle to be opening my password manager multiple times a day (as I intentionally don't save passwords in my browser), and inserting 1) user name and main password 2) 2FA code 3) Guard password ... then dealing with signing out of ghost sessions that were created by Mailbox.org signing me out without my permission, and then finally resuming my work.
I have already submitted feedback to support staff on this, but nothing has improved.
I have to login multiple times a day ever since switching to the login.
I had to turn off 2FA because this is already extremely time consuming, and interrupts the work flow
I have to login multiple times a day ever since switching to the login.
I had to turn off 2FA because this is already extremely time consuming, and interrupts the work flow
Initially I thought this was my self-destructing cookies plugin, but I've whitelisted the entire domain and others are reporting the same issue - so it's an Mailbox.org problem. Specifically, it can't become my default primary account if it logs out on its own and thus I lose desktop notifications from my browser.
Edit: For now, I've set up mailnag as an IMAP solution. Not sure what the Windows or Mac equivalent would be.
Initially I thought this was my self-destructing cookies plugin, but I've whitelisted the entire domain and others are reporting the same issue - so it's an Mailbox.org problem. Specifically, it can't become my default primary account if it logs out on its own and thus I lose desktop notifications from my browser.
Edit: For now, I've set up mailnag as an IMAP solution. Not sure what the Windows or Mac equivalent would be.
Hey,
we did start with conservative values in terms of session lifetime, as we wanted to guarantee stability when scaling up the Login 2.0.
Of course we know that logging in multiple times a week (or even per day) is annoying, and we want to improve the user experience. So for now, we increased the lifetime of a session to 16 hours (while keeping it capped at 4 days). This means, that as you can stay logged in for up to 4 days now as long as you are active every 16 hours. This should reduce the number of fresh logins needed to around 2 per week instead of 2 per day.
We actually want to increase the session lifetime even further than that, but we have to carefully monitor the system, as we're moving thousands and thousands of users per day to Login 2.0. Once the migration is done we're at more liberty to act here and improve on the session times.
I hope I could clear things up a bit.
Hendrik
Hey,
we did start with conservative values in terms of session lifetime, as we wanted to guarantee stability when scaling up the Login 2.0.
Of course we know that logging in multiple times a week (or even per day) is annoying, and we want to improve the user experience. So for now, we increased the lifetime of a session to 16 hours (while keeping it capped at 4 days). This means, that as you can stay logged in for up to 4 days now as long as you are active every 16 hours. This should reduce the number of fresh logins needed to around 2 per week instead of 2 per day.
We actually want to increase the session lifetime even further than that, but we have to carefully monitor the system, as we're moving thousands and thousands of users per day to Login 2.0. Once the migration is done we're at more liberty to act here and improve on the session times.
I hope I could clear things up a bit.
Hendrik
Replies have been locked on this page!