Mailspring: Bug: Office365 IMAP does not login with correct app password

[AlexDunmow]

Describe the bug
Office 365 imap with an app password.

 * OK The Microsoft Exchange IMAP4 service is ready. [TQBFADIAUABSADAAMQBDAEEAMAAxADMANgAuAGEAdQBzAHAAcgBkADAAMQAuAHAAcgBvAGQALgBvAHUAdABsAG8AbwBrAC4AYwBvAG0A]
 1 CAPABILITY
 * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS ID UNSELECT CHILDREN IDLE NAMESPACE LITERAL+
 1 OK CAPABILITY completed.
 2 LOGIN "***@***.***.**" *********
 2 NO LOGIN failed.

Either via "Office365" or "imap/smtp".

Doesn't happen on Microsoft connection tester. Username and password is DEFINITELY correct:

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Set up account'
2. Click on 'Office 365 or IMAP/SMTP'
3. Fill in details
4. No login

Expected behavior

Mailspring logs in and everything works.

Screenshots

Setup: (please complete the following information):

• OS: Ubuntu
• OS Version 19.10
• Mailspring Version: 1.7.4

Additional context
Add any other context about the problem here. If this issue is related to a particular account or email service, be sure to mention it so this report is actionable!

[Bnoa69]

Almost same issue, with Ubuntu 19.10 (pop os). Unable to connect with office365 account. I have a blank screen after setting up my account.

[AndreaRicchi]

Same here on Linux Mint 19.3. Connecting either with Office 365 or via IMAP/SMTP results in error: cannot read property emailAddress of undefined office

[Bnoa69]

Same issue with my Outlook/Hotmail account.

[BinaryPaean]

Same on Windows/Office365/Mailspring 1.7.4. After attempting to add an O365 account I either receive a "success" message briefly (followed by no account being added) or a completely blank pop-over window which would ordinarily show the redirected logon page.

[cweedall]

I can also confirm the Windows/Office365/Mailspring 1.7.4-d54ff730 problem. "Success" message, the pop-up disappears, then nothing suggesting it was actually successful (i.e. no new accounts in Manage Accounts).

[edwardzhxi]

can't log in 365 account at all with a blank screen forever...

[compliancygroup]

This is happening for me on ANY account other than Google (Ubuntu 19.10). Mailspring says account created, then nothing.

[steefdebruijn]

Same problem here on MacOs 10.14.6, Mailspring 1.7.4, DavMail 5.4.0. Blank pop-up after creating account.
DavMail works with Mutt, so we can eliminate that.

When starting mailspring in dev mode (mailspring -d) I get the following error in the JS console:

index.js:16 Window load time: 649ms
onboarding-helpers.ts:121 Using Empty Template
/Applications/Mailspring.app/Contents/Resources/app.asar/src/error-logger.js:101 TypeError: Cannot read property 'emailAddress' of undefined
    at _AccountStore.addAccount (account-store.ts:223)
    at OnboardingStore._onFinishAndAddAccount (onboarding-store.ts:129)
    at EventEmitter.eventHandler (/Applications/Mailspring.app/Contents/Resources/app.asar/node_modules/reflux/src/PublisherMethods.js:36)
    at EventEmitter.emit (/Applications/Mailspring.app/Contents/Resources/app.asar/node_modules/eventemitter3/index.js:72)
    at Function.trigger (/Applications/Mailspring.app/Contents/Resources/app.asar/node_modules/reflux/src/PublisherMethods.js:52)
    at Object.functor [as finishAndAddAccount] (/Applications/Mailspring.app/Contents/Resources/app.asar/node_modules/reflux/src/createAction.js:32)
    at onboarding_helpers_1.finalizeAndValidateAccount.then.validated (create-page-for-form.tsx:170) Object
module.exports.ErrorLogger.reportError @ /Applications/Mailspring.app/Contents/Resources/app.asar/src/error-logger.js:101
account-store.ts:223 Uncaught (in promise) TypeError: Cannot read property 'emailAddress' of undefined
    at _AccountStore.addAccount (account-store.ts:223)
    at OnboardingStore._onFinishAndAddAccount (onboarding-store.ts:129)
    at EventEmitter.eventHandler (/Applications/Mailspring.app/Contents/Resources/app.asar/node_modules/reflux/src/PublisherMethods.js:36)
    at EventEmitter.emit (/Applications/Mailspring.app/Contents/Resources/app.asar/node_modules/eventemitter3/index.js:72)
    at Function.trigger (/Applications/Mailspring.app/Contents/Resources/app.asar/node_modules/reflux/src/PublisherMethods.js:52)
    at Object.functor [as finishAndAddAccount] (/Applications/Mailspring.app/Contents/Resources/app.asar/node_modules/reflux/src/createAction.js:32)
    at onboarding_helpers_1.finalizeAndValidateAccount.then.validated (create-page-for-form.tsx:170)

Maybe this helps...

On Manjaro 19.0, AUR Mailspring and AUR DavMail (can't check versions at the moment) IT WORKS.

[timescam]

On Manjaro 19.0, AUR Mailspring and AUR DavMail (can't check versions at the moment) IT WORKS.

the one on aur (1.7.2) is not the latest version (1.7.4)

[steefdebruijn]

Thanks. Installed MacOs version 1.7.2 and it works now.

Problem is related to Mailspring version 1.7.4. (or .3, can't check because can't download macos binary for that version)

Nice workaround: account(s) can be added on version 1.7.2, after restarting mailspring it is updated to 1.7.4 but accounts keep working...

[matiyin]

Same issue here on v1.7.4 .deb Linux Mint, trying to onboard IMAP, or Yahoo or Outlook. White screen of death (js error). Will try 1.7.2 and upgrade from there later.

TypeError: Cannot read property 'emailAddress' of undefined at _AccountStore.addAccount (account-store.ts:223) at OnboardingStore._onFinishAndAddAccount (onboarding-store.ts:129) at EventEmitter.eventHandler (/usr/share/mailspring/resources/app.asar/node_modules/reflux/src/PublisherMethods.js:36) at EventEmitter.emit (/usr/share/mailspring/resources/app.asar/node_modules/eventemitter3/index.js:72) at Function.trigger (/usr/share/mailspring/resources/app.asar/node_modules/reflux/src/PublisherMethods.js:52) at Object.functor [as finishAndAddAccount] (/usr/share/mailspring/resources/app.asar/node_modules/reflux/src/createAction.js:32) at onboarding_helpers_1.finalizeAndValidateAccount.then.validated (create-page-for-form.tsx:170)

[shanerbo]

If you encounter this issue, you shall downgrade your mailspring to 1.7.2

[matiyin]

Thanks, I found out already via Github where I reported it also.
I must say I was a bit disappointed with your first reply that offered no solution but instead asked me if I wanted to consider a paid subscription. I guess it was some automated reply.. So far Mailspring is the best client I found for linux, and I'm willing to pay for quality, but hesitant when there's no good support. So please take this feedback to improve your response to new possible clients :)

Sent from Mailspring (https://link.getmailspring.com/link/[email protected]/0?redirect=https%3A%2F%2Fgetmailspring.com%2F&recipient=cmVwbHkrQUFXQ0JMM0RGN0dVM1hPNUQ1NlFFREY0TkVVN0xFVkJOSEhDRDdSWUE0QHJlcGx5LmdpdGh1Yi5jb20%3D), the best free email app for work
On Mar 2 2020, at 6:57 pm, ERBO [e-mail] wrote:

If you encounter this issue, you shall downgrade your mailspring to 1.7.2 (https://link.getmailspring.com/link/[email protected]/1?redirect=https%3A%2F%2Fgithub.com%2FFoundry376%2FMailspring%2Freleases%2Ftag%2F1.7.2&recipient=cmVwbHkrQUFXQ0JMM0RGN0dVM1hPNUQ1NlFFREY0TkVVN0xFVkJOSEhDRDdSWUE0QHJlcGx5LmdpdGh1Yi5jb20%3D)

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub (https://link.getmailspring.com/link/[email protected]/2?redirect=https%3A%2F%2Fgithub.com%2FFoundry376%2FMailspring%2Fissues%2F1811%3Femail_source%3Dnotifications%26email_token%3DAAWCBL4A3WCW6D5QHEWPEE3RFPXPLA5CNFSM4K24I5VKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENQJNNA%23issuecomment-593532596&recipient=cmVwbHkrQUFXQ0JMM0RGN0dVM1hPNUQ1NlFFREY0TkVVN0xFVkJOSEhDRDdSWUE0QHJlcGx5LmdpdGh1Yi5jb20%3D), or unsubscribe (https://link.getmailspring.com/link/[email protected]/3?redirect=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAWCBL3V3U3QPYL7W4EAZM3RFPXPLANCNFSM4K24I5VA&recipient=cmVwbHkrQUFXQ0JMM0RGN0dVM1hPNUQ1NlFFREY0TkVVN0xFVkJOSEhDRDdSWUE0QHJlcGx5LmdpdGh1Yi5jb20%3D).

[lys861205]

If you encounter this issue, you shall downgrade your mailspring to 1.7.2

Can use it after downgrade to 1.7.2?

[matiyin]

yes 1.7.2 works thanks

On Mar 12 2020, at 4:14 am, West [e-mail] wrote:
>
>

If you encounter this issue, you shall downgrade your mailspring to 1.7.2 (https://github.com/Foundry376/Mailspring/releases/tag/1.7.2)
Can use it after downgrade to 1.7.2?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub (https://github.com/Foundry376/Mailspring/issues/1811#issuecomment-597985079), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AAWCBLZT3FMQPDWTW245CQLRHBHRZANCNFSM4K24I5VA).

[jwshive]

For me, downgrading to 1.7.2 did not fix my issue.

[veronicacary]

I experienced the same issue just now on 1.7.4 on Mint 19.3 Cinnamon. Downgrading to 1.7.2 resolved this issue for me- I was able to get my O365 account added without issue. Then, I was able to install 1.7.4 and things are working as expected. I am using the Deb (non-Snap) version- not sure if that's an important detail. :)

[bengotow]

Hey folks! Thanks for reporting this and submitting a fix - I'm sorry it's taken me so long to ship a build with the changes. I honestly can't believe it's April already. I'm doing QA tonight and I'll ship the 1.7.5 release with the patch ASAP tomorrow!

[bengotow]

Hey folks, thanks for reporting this. Happy to say this has been resolved in 1.7.6 which shipped this afternoon. 🚀 The app should auto-update, but if it doesn't you can also grab the new release from GitHub's Releases tab or from https://getmailspring.com/download. Thanks for your patience and help tracking this down, enjoy the update!