Bugzilla

My mother reached out to me stating her email stopped downloading on July 16th. Prior to that I had her on 128ESR. In anticipation of 140, I had previously tried to update her to 137+ but it TB seemed "broken" for lack of a better word. I decided to let 128ESR update to 140 when it was finally the new ESR.

When I remoted into her machine to take a look, I saw she was at 140.0.1. I sent a few test messages and clicked Get Messages but they didn't come through. On it's face, 140.0.1 seemed operational and I didn't see anything in Status Bar indicating any issues or errors. My first instinct was AT&T's abominable "Security Key" method of doing OAuth2 but that wasn't the case. How do I know? I generated a new Security Key via my mom's webmail account and then deleted her saved email password. After restarting TB, I was waiting for it to prompt me for a password but it never did.

I then downloaded 128.12.0ESR, uninstalled 140.0.1, re-installed 128.12.0ESR and launched TB with --allow-downgrade. It launch fine and then prompted for a password. I input the Security Key password but it rejected it. Tried once more, rejected again. I then input the regular email password and it accepted it and gave me the windows asking to allow TB to manage her account which I did. After this, all email since the 16th began spooling to the Inbox along with test messages I sent.

I then did another upgrade to 140.0.1 thinking it was just the old Security Key that needed to be wiped and that her regular password was now sufficient. Still, it no longer would spool new messages I just sent after updating for a 2nd time to 140.0.1. Once again, reverting back to 128.12.0ESR with --allow-downgrade caused the newer test messages to spool to the Inbox.

I didn't quite know if this belonged in Account manager or not. And if any STR are needed, it would be these:

STR:
1. Have at @att.net account that's currently working with 128.x ESR that was previously set up for IMAP / OAuth2 via Security Key method (and was configured via Security Key method since the TB 102.x > 115.x days)
2. Update to 140.x

Actual Result:
1. New messages are not pulled from Inbox

Expected Results:
1. New messages are pulled from Inbox

My mother reached out to me stating her email stopped downloading on July 16th. Prior to that I had her on 128ESR. In anticipation of 140, I had previously tried to update her to 137+ but TB seemed "broken" for lack of a better word. I decided to let 128ESR update to 140 when it was finally the new ESR.

When I remoted into her machine to take a look, I saw she was at 140.0.1. I sent a few test messages and clicked Get Messages but they didn't come through. On it's face, 140.0.1 seemed operational and I didn't see anything in Status Bar indicating any issues or errors. My first instinct was AT&T's abominable "Security Key" method of doing OAuth2 but that wasn't the case. How do I know? I generated a new Security Key via my mom's webmail account and then deleted her saved email password. After restarting TB, I was waiting for it to prompt me for a password but it never did.

I then downloaded 128.12.0ESR, uninstalled 140.0.1, re-installed 128.12.0ESR and launched TB with --allow-downgrade. It launch fine and then prompted for a password. I input the Security Key password but it rejected it. Tried once more, rejected again. I then input the regular email password and it accepted it and gave me the windows asking to allow TB to manage her account which I did. After this, all email since the 16th began spooling to the Inbox along with test messages I sent.

I then did another upgrade to 140.0.1 thinking it was just the old Security Key that needed to be wiped and that her regular password was now sufficient. Still, it no longer would spool new messages I just sent after updating for a 2nd time to 140.0.1. Once again, reverting back to 128.12.0ESR with --allow-downgrade caused the newer test messages to spool to the Inbox.

I didn't quite know if this belonged in Account manager or not. And if any STR are needed, it would be these:

STR:
1. Have at @att.net account that's currently working with 128.x ESR that was previously set up for IMAP / OAuth2 via Security Key method (and was configured via Security Key method since the TB 102.x > 115.x days)
2. Update to 140.x

Actual Result:
1. New messages are not pulled from Inbox

Expected Results:
1. New messages are pulled from Inbox

My mother reached out to me stating her email stopped downloading on July 16th. Prior to that I had her on 128ESR. In anticipation of 140, I had previously tried to update her to 137+ but TB seemed "broken" for lack of a better word. I decided to let 128ESR update to 140 when it was finally the new ESR.

When I remoted into her machine to take a look, I saw she was at 140.0.1. I sent a few test messages and clicked Get Messages but they didn't come through. On it's face, 140.0.1 seemed operational and I didn't see anything in Status Bar indicating any issues or errors. My first instinct was AT&T's abominable "Security Key" method of doing OAuth2 but that wasn't the case. How do I know? I generated a new Security Key via my mom's webmail account and then deleted her saved email password. After restarting TB, I was waiting for it to prompt me for a password but it never did.

I then downloaded 128.12.0ESR, uninstalled 140.0.1, re-installed 128.12.0ESR and launched TB with --allow-downgrade. It launched fine and then prompted for a password. I input the Security Key password but it rejected it. Tried once more, rejected again. I then input the regular email password and it accepted it and gave me the windows asking to allow TB to manage her account which I did. After this, all email since the 16th began spooling to the Inbox along with test messages I sent.

I then did another upgrade to 140.0.1 thinking it was just the old Security Key that needed to be wiped and that her regular password was now sufficient. Still, it no longer would spool new messages I just sent after updating for a 2nd time to 140.0.1. Once again, reverting back to 128.12.0ESR with --allow-downgrade caused the newer test messages to spool to the Inbox.

I didn't quite know if this belonged in Account manager or not. And if any STR are needed, it would be these:

STR:
1. Have at @att.net account that's currently working with 128.x ESR that was previously set up for IMAP / OAuth2 via Security Key method (and was configured via Security Key method since the TB 102.x > 115.x days)
2. Update to 140.x

Actual Result:
1. New messages are not pulled from Inbox

Expected Results:
1. New messages are pulled from Inbox

My mother reached out to me stating her email stopped downloading on July 16th. Prior to that I had her on 128ESR. In anticipation of 140, I had previously tried to update her to 137+ but TB seemed "broken" for lack of a better word. I decided to let 128ESR update to 140 when it was finally the new ESR.

When I remoted into her machine to take a look, I saw she was at 140.0.1. I sent a few test messages and clicked Get Messages but they didn't come through. On it's face, 140.0.1 seemed operational and I didn't see anything in Status Bar indicating any issues or errors. My first instinct was AT&T's abominable "Security Key" method of doing OAuth2 but that wasn't the case. How do I know? I generated a new Security Key via my mom's webmail account and then deleted her saved email password. After restarting TB, I was waiting for it to prompt me for a password but it never did.

I then downloaded 128.12.0ESR, uninstalled 140.0.1, re-installed 128.12.0ESR and launched TB with --allow-downgrade. It launched fine and then prompted for a password. I input the Security Key password but it rejected it. Tried once more, rejected again. I then input the regular email password and it accepted it and gave me the windows asking to allow TB to manage her account which I did. After this, all email since the 16th began spooling to the Inbox along with test messages I sent.

I then did another upgrade to 140.0.1 thinking it was just the old Security Key that needed to be wiped and that her regular password was now sufficient. Still, it no longer would spool new messages I just sent after updating for a 2nd time to 140.0.1. Once again, reverting back to 128.12.0ESR with --allow-downgrade caused the newer test messages to spool to the Inbox.

I didn't quite know if this belonged in the Account Manager section or not. And if any STR are needed, it would be these:

STR:
1. Have at @att.net account that's currently working with 128.x ESR that was previously set up for IMAP / OAuth2 via Security Key method (and was configured via Security Key method since the TB 102.x > 115.x days)
2. Update to 140.x

Actual Result:
1. New messages are not pulled from Inbox

Expected Results:
1. New messages are pulled from Inbox