We’re really excited to announce a feature that we’ve been looking forward to for a long time. As of today our new HTTP POST Formats are in Beta.
The New formats add full JSON, Multipart and a Raw format. The JSON and Multipart formats represent an entire parsed email available as as hash of keys and values. The raw format is for people who simply want an unparsed email to be delivered to their app without any alternation at all. We’re still supporting the old format under the ‘Original Format’ name.
When we first created CloudMailin we were constrained with what we could offer customers, as time went on the HTTP POST format was added to but it was never quite what we wanted. Today we’ve hit the reset button and we’re offering these new formats to everyone to try.
They’re still in beta so they might change slightly over the next few weeks but we’re keen to hear your feedback! For more details checkout the documentation now!
It’s been a long time coming but we’re excited to announce our new documentation. The old docs can still be found at http://cloudmailin-docs.heroku.com/ if anyone needs them but we’ve done a full refresh of the documentation.
We’ll be adding a whole host of new documents and as we add some great new features over the next couple of months it will be even easier to explain them in the documentation.
However, although the docs are all new they’re not perfect. We’re looking for your help! If you think there’s something that can be improved then please let us know, or even better submit a pull request on Github. We’re certain there will be some benefits for those users that help us out (although we haven’t thought of them yet).
Today we’re launching a feature that we’ve been looking forward to and working on for some time now.
As of today Authorization callbacks are in beta. Authorization callbacks allow you to accept or deny a message before any of the content is sent to your server. When CloudMailin has received the recipient and sender of the message you’ll receive a callback asking you what you want to do with the message. If you give us a positive response delivery will continue however, a 404 response for example would tell us to bounce the message.
We believe this will really help our users to take control of the messages they receive and provide a great way to provide features such as ‘virtual inboxes’ where you can accept messages destined for some users but not others.
Along with the sender and recipient you can also receive the helo domain of the sending server and the sending server’s remote IP address. Enabling you to perform checks such as SPF too.
For more details take a look at the documentation and please let us know how you get on! The feature is still in beta but it's available on micro plus and above plans. As always feel free to suggest any ideas and comments.