I have an email address that is bound to AWS SES. SES listens for incoming emails and writes them to an S3 bucket. I then have a lambda hook which listens for writes to this bucket and processes the email content. This usually means writing an emacs org-mode record on dropbox. Which is then added to my emacs agenda.
That sounds really complicated. Wouldn't you just use something like Syncthing to synchronize your org mode files across devices? I use Orgzly and Syncthing in my phone and it's good enough.
If you use it for general email stuff, just have a Cron job pulling your email down and append new stuff to a file that gets synchronized.
I don't really get why AWS, S3, or lambda are involved, unless you just wanted to see if you could do it.
I definitely used it as an exercise to learn lambda. I don't have an android phone for orgzly and at the time of creation, there weren't any solid iPhone org-mode apps.
I use org-brain on the backend and the lambda function does some processing to automatically categorize and such.
At the time I wrote it, The SES -> lambda hooks did not give you the body content of the email and required a write to S3 first. This might still be the case.
I used IFTTT for email->Dropbox for some time. Ultimately, I didn't leave much notes for myself this way, as I'm almost always close to a computer with Emacs accessible locally or remotely. For the rare case I use Orgzly on my phone, or Google Keep in a pinch.
I just e-mail myself, make sure to include “idea” or “business idea” or “game idea” or whatever in the subject line, respond to the email chain if i want to iterate, and periodically go back through the search results of emails I’ve sent myself.
I have an email address that is bound to AWS SES. SES listens for incoming emails and writes them to an S3 bucket. I then have a lambda hook which listens for writes to this bucket and processes the email content. This usually means writing an emacs org-mode record on dropbox. Which is then added to my emacs agenda.