cfe2971c2e
Summary:
Previously, the generic IMAP auth screen presented one security option to
users: "Require SSL". This was ambiguous and difficult to translate into
the correct security options behind the scenes, causing confusion and problems
connecting some accounts.
This patch does the following:
* Separates security settings for IMAP and SMTP, as these different protocols
may also require different SSL/TLS settings
* Reworks the generic IMAP auth page to allow specifying security settings
with higher fidelity. We looked at various different email apps and decided
that the best solution to this problem was to allow more detailed
specification of security settings and to ease the burden of more options
by having sane defaults that work correctly in the majority of cases.
This new screen allows users to pick from "SSL / TLS", "STARTTLS", or "none"
for the security settings for a protocol, and also to instruct us that
they're OK with us using known insecure SSL settings to connect to their
server by checking a checkbox.
We default to port 993 / SSL/TLS for IMAP and port 587 / STARTTLS for SMTP.
These are the most common settings for providers these days and will work
for most folks.
* Significantly tightens our default security. Now that we can allow folks to
opt-in to bad security, by default we should protect folks as best we can.
* Removes some now-unnecessary jank like specifying the SSLv3 "cipher"
in some custom SMTP configs. I don't think this was actually necessary
as SSLv3 is a protocol and not a valid cipher, but these custom
configs may have been necessary because of how the ssl_required flag was
linked between IMAP and SMTP before (and thus to specify different
settings for SMTP you'd have to override the SMTP config).
* Removes hard-coding of Gmail & Office365 settings in several
locations. (This was a major headache while working on the patch.)
This depends on version 2.0.1 of imap-provider-settings, which has major
breaking changes from version 1.0. See commit for more info:
|
||
|---|---|---|
| .. | ||
| apm | ||
| build | ||
| docs | ||
| docs_src | ||
| dot-nylas | ||
| internal_packages | ||
| keymaps | ||
| menus | ||
| script | ||
| spec | ||
| src | ||
| static | ||
| .babelrc | ||
| .travis.yml | ||
| .watchmanconfig | ||
| book.json | ||
| CHANGELOG.md | ||
| CONFIGURATION.md | ||
| CONTRIBUTING.md | ||
| ISSUE_TEMPLATE.md | ||
| LICENSE.md | ||
| package.json | ||
| README.md | ||
Nylas Mail - the open-source, extensible mail client
Nylas Mail is an open-source mail client built on the modern web with Electron, React, and Flux. It is designed to be extensible, so it's easy to create new experiences and workflows around email. Want to learn more? Check out the full documentation.
Want to help build the future of email? Nylas is hiring!
Download Nylas Mail
You can download compiled versions of Nylas Mail for Windows, Mac OS X, and Linux (.deb) from https://nylas.com/download. You can also build and run Nylas Mail (Previously N1) on Fedora. On Arch Linux, you can install n1 or n1-git from the aur.
Build A Plugin
Plugins lie at the heart of Nylas Mail and give it its powerful features. Building your own plugins allows you to integrate the app with other tools, experiment with new workflows, and more. Follow the Getting Started guide to write your first plugin in five minutes. To create your own theme, go to our Theme Starter guide.
If you would like to run the N1 source and contribute, check out our contributing guide.
Themes
The Nylas Mail user interface is styled using CSS, which means it's easy to modify and extend. Nylas Mail comes stock with a few beautiful themes, and there are many more which have been built by community developers
Bundled Themes
- Dark
- Darkside (designed by Jamie Wilson)
- Taiga (designed by Noah Buscher)
- Ubuntu (designed by Ahmed Elhanafy)
- Less Is More (designed by Alexander Adkins)
Community Themes
- Arc Dark
- Predawn
- ElementaryOS
- Ido—Polymail-inspired theme
- Solarized Dark
- Berend
- LevelUp
- Sunrise
- ToogaBooga
- Material
- Monokai
- Agapanthus—Inbox-inspired theme
- Stripe
- [Kleinstein] (https://github.com/diklein/Kleinstein)—Hide the account list sidebar
- BoraBora
- Honeyduke
- Snow
- Hull
- Express
- DarkSoda
- Bemind
- Dracula
- MouseEatsCat
- Sublime Dark
- Firefox
- Gmail
- Darkish
To install community themes:
- Download and unzip the repo
- In Nylas Mail, select
Developer > Install a Package Manually... - Navigate to where you downloaded the theme and select the root folder. The theme is copied into the
~/.nylas-mailfolder for your convinence - Select
Change Theme...from the top level menu, and you'll see the newly installed theme. That's it!
Want to dive in more? Try creating your own theme!
Plugin List
We're working on building a plugin index that makes it super easy to add them to Nylas Mail. For now, check out the list below! (Feel free to submit a PR if you build a plugin and want it featured here.)
Bundled Plugins
Great starting points for creating your own plugins!
- Translate—Works with 10 languages
- Quick Replies—Send emails faster with templates
- Emoji Keyboard—Insert emoji by typing a colon (:) followed by the name of an emoji symbol
- GitHub Sidebar Info
- View on GitHub
- Personal Level Indicators
- Phishing Detection
Community Plugins
Note these are not tested or officially supported by Nylas, but we still think they are really cool! If you find bugs with them, please open GitHub issues on their individual project pages, not the Nylas Mail (N1) repo page. Thanks!
- Jiffy—Insert animated GIFs
- Weather
- Todoist
- Unsubscribe
- Squirt Speed Reader
- Website Launcher—Opens a URL in separate window
- In Development: Cypher (PGP Encryption)
- Avatars
- Events Calendar (WIP)
- Mail in Chat (WIP)
- Evernote
- Wunderlist
- Participants Display
- GitHub
When you install packages, they're moved to ~/.nylas-mail/packages, and Nylas Mail runs apm install on the command line to fetch dependencies listed in the package's package.json
Building the docs
Plugin SDK docs are available at https://nylas.github.io/nylas-mail/. Here's how you build them:
Until my patch gets merged, docs need to be built manually using mg's fork.
git clone git@github.com:grinich/gitbook.git
cd nylas-mail
./node_modules/.bin/gitbook alias ../gitbook latest
Then to actually build the docs:
script/grunt docs
./node_modules/.bin/gitbook --gitbook=latest build . ./_docs_output --log=debug --debug
rm -r docs_src/classes
If you want to preview the docs:
pushd ./_docs_output; python -m SimpleHTTPServer; popd
Just want to publish everything? There's a helper script that does it for you:
script/publish-docs
Configuration
You can configure Nylas Mail in a few ways—for instance, pointing it to your self-hosted instance of the sync engine or changing the interface zoom level. Learn more about how.
Feature Requests / Plugin Ideas
Have an idea for a package or a feature you'd love to see in Nylas Mail? Search for existing GitHub issues and join the conversation!