windows 10
1.5.0
Bug?
Emails are now showing NIL as the recipient/sender names since I update this morning eg.
To: NIL
The same on ubuntu 16.04, happening since upgrade to 1.5.0 from 1.4.2
+1
This is also happening for me on all incoming mail since updating. Picture: 
Happens on macOS.

FWIW i'm only seeing this on emails w/o friendly names, and only on _new_ emails.
I'm seeing expected (read: blank) behavior on emails that were indexed pre-upgrade.
I'm also seeing this for emails with blank subject lines.
+1 on Mac OSX 10.14 Mojave and Mailspring 1.5.0
Duplicate of #1150
Same thing on Windows 10
+1 on Ubuntu 18.04, Mailspring version 1.5.0
And this NIL text is used when composing / replying to such and email through mailspring. So the recipient is getting puzzled a bit: "why do you call me NIL?". On Mac, version 1.5.0.
This needs to fix asap. @bengotow agreed?
+1 on Kubuntu 18.04, Mailspring 1.5.0
Same issue here. Windows 10, Mailspring version 1.5.0
+1 Kubuntu 18.10, Mailspring 1.50.
Interestingly this happens only for some accounts, mostly for addresses without a specified name.
+1 Ubuntu 18.04 version 1.5.0
+1 for Windows 10
Same here, windows 10, mailspring v1.5.0, some senders are showing up as NIL. This didn't happen in previous versions.
+1 Kubuntu 18.10, Mailspring 1.50.
Same as MacOSx High Sierra, Mailspring Version 1.5.0. This is really annoying and non-user-friendly.
I have raised a PR https://github.com/Foundry376/Mailspring/pull/1176 , which seems to sort out the issue. I am unsure whether this is a proper solution or not as I have not explored the codebase properly.
Hey folks! Thanks for reporting this—I've narrowed this down to a patch to libetpan I made to add support for Proton Bridge (which uses some nonstandard IMAP header formatting). I'm going to revert this and ship a patch release this weekend.
@bengotow I've updated to 1.5.1 and still seeing a lot of NIL as name (previous emails), do i need to do a fresh setup again ?
@bengotow I've updated to 1.5.1 and still seeing a lot of NIL as name (previous emails), do i need to do a fresh setup again ?
I had to go to Manage Accounts > Rebuild Cache... in order for the fix to work. Can confirm the NIL issue is resolved on v1.5.2 on Mac 10.13.6
Hey folks—thanks for all the feedback about this. It sounds like the 1.5.1 upgrade and rebuilding the email cache do the trick. I'm going to close this! Happy holidays—
Most helpful comment
Hey folks! Thanks for reporting this—I've narrowed this down to a patch to libetpan I made to add support for Proton Bridge (which uses some nonstandard IMAP header formatting). I'm going to revert this and ship a patch release this weekend.