![]() I'm working to add support in the future but it's an entirely separate email protocol that doesn't have anything in commong with IMAP/SMTP. No errors were shown when I ran the commands, but mailspring is still showing the same problem. I did it and then started the daemon with the command: eval (/usr/bin/gnome-keyring-daemon -start -componentspkcs11,secrets,ssh) export SSHAUTHSOCK. Mailspring unfortunately does NOT support Exchange, which is the type of email system you get with "Office 365 Business". So I went to the arch wiki and found out that I should install libsecret and gnome-keyring. It's unclear if this is always necessary, or something that individual organizations configure. Here's a detailed breakdown of the information Mailspring sends to it's own servers as you use the product: The email address you use for your Mailspring ID and any information you explicitly add to your account, such as information you'd like to appear on your invoices. However, you may need to create an "app password" just for Mailspring in order to add your account. Mailspring connects to it's servers via HTTPS / SSL at all times. Small note about Outlook: Mailspring supports Office 365 accounts ( ) because that service supports IMAP. Sorry for the delay getting a fix out for this one, I appreciate everyone's help debugging and triaging the problem! You can download the update from GitHub releases or from, and the app should also auto-update if you have been using it. It was reported in a handful of other issues and we shipped a fix for it yesterday in version 1.7.5. Maybe both can be supported.Hey folks-thanks for filing this, this is a pretty serious bug. Unfortunately, if "Mailspring in the browser" requires all data to be locally stored, this would, I think, limit it's audience. The former would require a more expansive rework of the store data access, the latter might be reasonably straightforward. We could either support directly communicating with a backend (JMAP, context.io or Nylas API), or we could do those backends _plus_ having a local IndexedDB cache. Time permitting, I would like to work on it more I am curious to what extent you guys might be interested in supporting this - eventually, down the road if are are, I would make an effort to keep you in the loop and get your input about any architecture changes required. Maybe both can be supported.Īnyhow, I am quite interested in this. ![]() ![]() We could either support directly communicating with a backend (JMAP, context.io or Nylas API), or we could do those backends plus having a local IndexedDB cache. The other biggies are window management and the data backend. When pasting HTML, Mailspring now correctly preserves links that have other styling. One challenge going forward is finding a better way to load the internal packages (I did the requires for account-sidebar manually). When printing a thread, Mailspring no longer prints undefined beside particicpants with no name. I managed to get it to compile in webpack, and the sidebar to render some static accounts and folders. In my opinion, it is definitely feasible - a decent amount of work, to be sure, but doable. Back then, I didn't have enough time to spare, but I just worked on it some more (with the February version, not the current master). I am also super interested in a browser version - so much so that I attempted to get it running in the browser back in February of this year.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |