sync-engine

Hey-- I work at Nylas. Would love any feedback you have for the site! There's a bit more info on our "Features" page: https://nylas.com/features/ In particular: > Nylas brings email into the 21st century with modern tools, RESTful developer APIs, and open source code. Integrating with Gmail or Exchange now takes minutes instead of months. Nylas is the easiest way to build an email app. Pretty much this means we talk IMAP/SMTP/ActiveSync/MIME so your app doesn't have to. Plus there are some nice new features, like a transactional "delta" endpoint and webhooks, which makes writing mail processing code a breeze. If you're a developer, the easiest place to dig in might be our docs: https://nylas.com/docs/platform or the open source sync engine: https://github.com/nylas/sync-engine We also shipped a new desktop email app this fall, which start

They have an open source email sync engine/REST API https://github.com/nylas/sync-engine and client https://github.com/nylas/N1

It seems that sync engine was AGPL licensed from the start https://github.com/nylas/sync-engine/blob/master/LICENSE

If you're looking for an alternative, we built one at Nylas. :) https://github.com/nylas/sync-engine

The Electron UI is all local. I believe the sync engine translates between IMAP and a custom JSON protocol they've created. I'm not sure what the performance difference is, but looking at the API docs, it looks a lot nicer to work with than IMAP: https://www.nylas.com/docs/ It also seems to more accurately represent modern semantics for working with email. For example, it allows using OAuth for authentication, and it has separate fields for folders and labels, depending on the backing email service. (And unlike IMAP, the labels field is actually useful.) You can also download a transaction log to make sync faster, which I don't think has an analog in IMAP. Subjectively, I've found the performance to be rather snappy in most cases. (You can also run a local client of the sync engine, if you don't want to trust their hosted copy: https://gi

We saw some folks start working on PostgreSQL support here: https://github.com/nylas/sync-engine/pull/132 It's not something we're likely to support officially in the near future since we don't run PostgreSQL and don't have the ability to test it well with production loads, but it'd be neat to see a working community fork.

Engineer from Nylas: You can start by using our open source Sync Engine (https://github.com/nylas/sync-engine) to begin extracting your own mail and put it behind a modern RESTful API. Our ultimate goal is to finally give you and others like you an outlet and set of tools to build the next generation of awesome features that currently only Google and a few others can do.

Engineer from Nylas here: End-to-end encryption is definitely on the roadmap. In the meantime the Sync Engine service that we're currently hosting for the sake of convenience is fully open source. You can run everything yourself on your own machines and still have the modern RESTful API that Nylas exposes. No more IMAP!! There's documentation about how to get that setup with N1 here: https://github.com/nylas/N1/blob/master/CONTRIBUTING.md There's much more on the Sync Engine page here: https://github.com/nylas/sync-engine

Here's what you need to install to run the entire stack locally: https://github.com/nylas/sync-engine Sorry-- launch day craziness :) More docs to follow soon!

It's both! Most users are fine with hosted infrastructure, so they don't need to run+maintain it themselves. But you totally can if you want. The code for the sync engine and API is here on GitHub: https://github.com/nylas/sync-engine We're working on putting together a better doc that outlines how to set up the entire stack locally. Ideally this could even be a Docker container. And you should always read the source! ;)

Yep, it does all the right things. All the "heavy lifting" here is done by the Nylas sync engine which works natively with Gmail labels, actions, search, etc. and those same semantics are exposed in N1. We've spent almost 2 years building the sync technology, so it's very stable and flexible. You can check out the IMAP code here: https://github.com/nylas/sync-engine

The Nylas Sync Engine is a large Python codebase with a test suite: https://github.com/nylas/sync-engine Lots of examples of SQLAlchemy, Flask, gevent, and pytest in action to build a REST API and sync platform for email/calendar/contacts data!

Well, we've built the ingester/REST part and we're working on the frontend :) Our sync engine is open source: https://github.com/inboxapp/inbox

Hi there, Christine from Nilas here. No RFC, but we do have API docs[1] and source code[2]. :) 1. https://nilas.com/docs 2. https://github.com/inboxapp/inbox