mailpace-rails VS curlconverter

I run a small transactional email provider (https://mailpace.com), our IPs are very rarely added to blocklists- but we are very strict on what we allow through our service, and surprisingly we’ve had no long term delivery issues with any of the big providers.

So thanks to the federated/decentralized design of email, is totally possible to be part of the network without any special privileges.

We are sending millions of emails every day though, which is quite different to sending a couple hundred personal emails a week. If you’re running this on a cloud host, expect to be blocked by default. However if you can find a small vps provider you’ll have better luck on sending yourself.

If you’re going to learn anything, email is a good bet. It’s barely changed in 30 years, and I suspect it will not change much for a long time.

I built my own transactional email provider (https://mailpace.com), I wish I had found this link before I started.

I would also recommend reading the email RFCs, they’re not that difficult to understand and the history explains a lot. Email aside we can learn a lot from this kind of distributed, decentralised system design in the future.

Their website at https://mailpace.com/ says that it's only intended for transactional mails however

Give MailPace a try [0]. The creator seems like a great guy, and the service does what it says without any bs. I've been using it for a while now for side projects, and can only recommmend it.

0: https://mailpace.com/

I agree that this is a challenge! If you want to use the hosted version, it's impossible to avoid the need for that trust. I'm working on making self-hosting easier for this reason.

Some other services (like Firefox Relay) will use AWS' Simple Email Service for everything. I opted to go for [MailPace](https://mailpace.com/), an independent, privacy-focused provider instead, which is an improvement but still not ideal. I believe that SimpleLogin lets you self-host your email, which is best from a privacy perspective, but I'm slightly concerned about the UX of having to think about email deliverability. Still experimenting with that!

You could use an SMTP relay service and not worry about deliverability while still self hosting your email. I don't self host email anyway but for other things I use https://mailpace.com/ - it's has probably the best pricing in the market and works very well. Emails are delivered very quickly.

When I was launching my new website, I was looking for an email provider. That's when I came across OhMySMTP, a simple and privacy-friendly transactional email service. My web framework of choice, Laravel, unfortunately doesn't support OhMySMTP by default. Luckily, OhMySMTP does provide a swiftmailer transport plugin! This can be installed in any Laravel project, and can be configured like official transports.

Simple way would be to add a “curl” options, looks like you’d just need to write up a method that matches this Request interface [0] to some curl command substrings you mash together.

Problem is of course: the headers and options are all going to be included. You could make it so it organizes them better though, maybe indenting and grouping like-options together so it’s easier to remove stuff.

[0] https://github.com/curlconverter/curlconverter/blob/e4b6fb74...

I made a fork of the Chrome DevTools that adds exactly this. You can tell Chrome to use a different version of the DevTools if you start it from the command line

https://github.com/curlconverter/curlconverter/issues/64#iss...

Someone added a ColdFusion Markup Language generator to https://curlconverter.com/cfml/ last year and after a few months I decided to remove it since I've never heard of it so nobody could possibly be using it, and the next day the guy who added support for it and 3 other people complained about it, so it seems like they're out there.

https://github.com/curlconverter/curlconverter.github.io/pul...

Relevant tools: - Browser dev tools and front-end tooling to debug JS and reconstruct requests in your code - grep.app and SourceGraph to check open-source parsers for some URLs (often, there are such repositories) - curlconverter to quickly draft a script from the cURL command - Regex and regex playgrounds to extract data from inline JavaScript - GraphQL introspection tools - Optionally, Fiddler or Wireshark to intercept and debug network requests (I don't use but my teammate does)

Original author here. Many smart people have contributed code over the years, but one warrants special mention.

About a year ago, verhovsky showed up out of nowhere. He rewrote the core of the application and increased the professionalism across the board. (dedicated domain, github page hosting, UI refresh, privacy improvements, and much more)

The tree-sitter PR is a monster achievement: https://github.com/curlconverter/curlconverter/pull/278

Search for parseAnsiCString in there. I don't think that had ever been implemented in JavaScript before.

For you, verhovsky, 10x engineer might be an understatement. Thank you!