[kureikain]

I have been toying with this idea and my solution is to use email.

Everytime I made purchase my bank (BankOfAmerica) send me an email, I parse that email and write data to a google sheet.

It's great because I don't need to give credential to service like Plaid.

I used webhook of service like https://hanami.run and configure my bank to send email notification to [e-mail] (my own domain). Hook it up with hanami.run webhook (or any email to webhook service) and voila, now you can parse the email body and do whatever you want with it, in real time. Bank sends email pretty quick.

[arthurcolle]

Where is this setting? I just created a BofA account a few days ago because BBVA is a hellhole of despair (Simple acquisition victim) so this sounds much better.

[bobsomers]

I don't recall where it is on BofA's website, but most banks have some feature along the lines of "send me an email when a transaction over X amount happens". I just set that value to $0 or $0.01 so I get emails for every transaction made.

[arthurcolle]

Gotcha, I'll poke around, thanks! What do you use for inbound mail processing? Do you run your own mail server? I was looking to process TheOCC.com inbound emails for some options trading stuff I was doing but never decided on a solution.

[kureikain]

You can use AWS SES to process inbound email and just use lambda to parse the email.

Or sendgrid free tier support incoming procesing too.

Also, you can use my own service https://hanami.run it supports webhook

Setup an email server for inbound email with Postfix is pretty easy to. You can use mailbox_command of postfix to parse email

You can setup email on a sub domain and only point the subdomain to it.

[arthurcolle]

Maybe I'm misunderstanding - how are the first 2 plans "0 SMTP emails per day", aren't all emails going through SMTP? Sorry not an email expert, just trying to understand.

But thanks for the explanation on the AWS/Sendgrid side, appreciate the information. Still curious about your service though, it looks promising.

[kureikain]

Ah SMTP is the protocol that we used to send email over internet.

The term SMTP server is used when you are the person who send out email.

The term MX server is used when you are the person who is received email. As in, someone use an SMTP server to send you an email, by connect to MX server list on your domain. You can find MX server by doing a `MX DNS query` on the domain such as `dig hanami.run mx +short` or `dig github.com mx +short`

SMTP email limit only apply for users who want to use our SMTP service. Think sendgrid/mailgun SMTP service. It means when you want to send email through your own domain.

For incoming and email forwarding(someone send you an email and we forward to your domains) then it unlimited.

The reason is that when you use SMTP service, you can just write a simple loop and send lots of email using our SMTP server. We don't want that, our service is only for daily email, not marketing(newsletter, promotion) or transaction email(password reset etc).

Incoming email, on other hand is send out by other people to your service, and we will happily forward as many as possible.

[denimnerd42]

I'm interested, had the same line of thought, and a bofa customer too. Mind pushing anything you have to github or similar?

[kureikain]

Yes, going to clean it my code(bunch of hard code and manual stuff) a bit and share it. Always want to do it.