Thanks for the feedback, but when we launched mxRaven, perch was just a tool we made for using internally to experiment with mxRaven by building a real use case to that validates our value proposition.
Additionally, its kinda hard to integrate different providers, when most of them primarily handle just the sending hop. Although many do have functionality to receive emails now, depending on something like webhooks would be a tradeoff since perch must stay online with a public endpoint (an IP or a stable domain) to receive webhooks unlike the current pull-based model. Plus if you're gonna go with SES you're probably better off plumbing a bespoke system with lambda.
hmm, seems like it has a hard dependency on mxRaven, would have been cooler if it could work with providers like SES as well
Thanks for the feedback, but when we launched mxRaven, perch was just a tool we made for using internally to experiment with mxRaven by building a real use case to that validates our value proposition.
Additionally, its kinda hard to integrate different providers, when most of them primarily handle just the sending hop. Although many do have functionality to receive emails now, depending on something like webhooks would be a tradeoff since perch must stay online with a public endpoint (an IP or a stable domain) to receive webhooks unlike the current pull-based model. Plus if you're gonna go with SES you're probably better off plumbing a bespoke system with lambda.