3 ms·
My app does a lot of folder/label management on the user's behalf, and some of the issue I've run into are: * UID MOVE not always being supported (meaning you
by 33degrees 11y ago
My app does a lot of folder/label management on the user's behalf, and some of the issue I've run into are:
* UID MOVE not always being supported (meaning you need to copy and expunge), and weirdness around gmail's IMAP extensions. This could be abstracted away with a good high level library, but I haven't found any for Ruby that covers all the cases properly.
* Gmail offers OAuth, but for regular IMAP, needing to store user's email and password and the security risks that come with that.
* Needing to know when new messages arrive, so either polling regularly, or keeping a bunch of connections open and using IDLE.
Nothing unsurmountable, but using a service like Nylas means I can spend more time developing features instead.
- kuschku 11y agoWell, the Nylas engine doesn’t provide any authentication by default. It just assumes if you enter the username correctly, the account is yours. Which makes it hard to self-host without building a different auth system around it.
- 33degrees 11y agoWhat I mean is, Nylas takes care of asking for and storing the user's credentials to their email account(s), all you need to store is the token that accesses the Nylas API.