Inbound email/parsing

[jamie.robson.89]

Hey everyone - hoping someone can help with this.

We’ve recently built a feature that allows users to copy in a generic email, and have that email/thread sent to the app, and logged against the correct company/user (CRM app).

We’re coming up against issues with parsing, whereby in some cases the email is being parsed and stored correctly, and in other cases, it’s failing. Something to do with the structure being different depending on the email client.

This is a really crucial part of the app, and so I’m willing to go with a third-party provider if needed. I believe we tried Nylas originally, but there was again some problems here which led us down the parsing route.

Any suggestions really appreciated! If someone has done this before and can show, please let me know !

[johnny]

Which email API are you using? Postmark makes inbound parsing easy

[jamie.robson.89]

We’re using SendGrid - is Postmark better?

[mikeloc]

@jamie.robson.89

is Postmark better?

Better? Perhaps. Awesomer? Apparently.

Postmark is awesome

We have been struggling with Sendgrid the last couple of years with black listed ip-addresses, mails ending up in spam and mails blocked by mailservers. We only do transactional mails to our customers but still Sendgrid can not deliver good enough. We have been in contact with support, tweaking the settings but still the same problems. So we decided to try Postmark. After a couple of weeks testing it works like a a dream - all our mails are suddenly delivered. Everyday and all the time. The pl…

[johnny]

Sendgrid can also do inbound parsing but yep I prefer Postmark

[jamie.robson.89]

Alright thanks - it sounds like one of these is “the” solution then.

Appreciate the quick replies!

[aj11]

We tried sendgrid parsing before for the same use case and had the same problem. Not sure if postmark is better.

We decided to stick to Nylas and are looking to upgrade to a Bubble enterprise plan to get through the security review for the full email sync.