Markdown is a client feature. We send markdown as text and converted as html. If you look at the API there are just text and html fields http://developer.nvlope.com/v1/mail/send/
Well, could you add instant messaging functionality to IMAP? Can you manage multiple inboxes with one IMAP account? Can you do server side threading with IMAP? Can you manage attachments and messages separately with IMAP? Can you upload attachments NOT using base64 using SMTP/IMAP? Can you use labels with IMAP? Can you manage multiple domains under IMAP? etc.
As for iOS client's there are exactly 3 that come to mind. Gmail, Apple Mail and Sparrow (discontinued).
We realize that this product is not for everyone - but for those who want a zero config, hassle free product.
> Well, could you add instant messaging functionality to IMAP?
IMAP does not reimplement XMPP, which I consider a feature. If you want instant messaging, you should use XMPP, and it's perfectly possible for a client to allow you to use both.
> Can you manage multiple inboxes with one IMAP account?
Yes, this is built in to the standard and every client can do this
Yes, almost every client supports multiple accounts.
IMAP is a good candidate for the most often (and most badly) reinvented protocol around. There's plenty of reasons to expose parts off the current infrastructure over HTTP (Mandrill is really useful) but I think if your plan is "reinvent ALL the things" you need to be a lot clearer about what exactly is so backwards about on of the most well studied and well engineered pieces of infrastructure around.
I guess I didnt phrase this very well, with IMAP i mean cloud imap services.
the problem is that it is very complex, and features are not implemented consistently accross clients. Especially the newer, or not standardized ones you listed. You know that there is something wrong when an entire slew of RFCs can be replaced with a few simple api calls.
As for iOS client's there are exactly 3 that come to mind. Gmail, Apple Mail and Sparrow (discontinued).
There's a good reason for that- Apple won't let you check a mail server on the client side. So you have to do what Mailbox did and set up huge server infrastructure to check people's e-mail then send push notifications. It makes it a lot more difficult than just making a client app.
So, the "solution" is to have your users set up a .forward-filter that pings a web service on new mail? Then have a really simple status server that simply replies with number of new mails since last check (or something along those lines...) - and have your email client poll (and reset) that counter... would give a few false-positives, but probably be better than having to poll an actual (variety of) IMAP/POP3-servers.
(This obviously won't work for most end-users, sadly)
Not sure if I completely understood your requirements, but you can add several custom domains (number depends on the plan) to your account, create mailboxes and aliases for them and can send and receive from those addresses as well.
Those are added to your account and can be accessed as individual mailboxes or via the unified inbox. They are not separate accounts with separate logins. Enterprise grade account management would be a feature to add at some point in the future.
2-factor auth won't be available at beta launch (it's a MVP, we still have to see if there's enough interest), but we'll probably add 2-factor auth using https://www.authy.com at some point.
How would you write and explore, say, a cash flow forecast of a not-yet-existing product line with a cli script? I could imagine doing that in emacs, maybe, because you can probably do everything there; or on plain paper if you're quick+accurate with doing math in your head.. but in a cli script ?
Bootstrap is just a bad excuse for no design/js skills. Its JS codebase is an abomination, as well as it's overly verbose CSS. It's only good for quick-and-dirty projects and has nothing to do with a well crafted site.
