inlets-pro VS spamscanner

I created this because of my frustration with inlets.

On one hand, this is about inlets, a product I wrote to help developers, self-hosters and enterprises to connect containers to the cloud. On the other hand, I hope you'll learn as much as I did about Proxy Protocol and how hard it is to configure for Traefik behind K3s.

How does this compare with ngrok, localtunnel, or Inlets?

It's unfortunate the only mature open source alternative[1] went on a path to seriously expensive subscriptions, 5x of a tailscale personal subscription.

[1]: https://inlets.dev/

Be specific. There are plenty of services I pay for, such as WebStorm, Photoshop, TablePlus, etc. Look at how JetBrains or TablePlus talks about their product. Take a look at inlets for a smaller scale sales pattern.

Same problem as well; there are so many attack vectors it's absurd.

I've tried rspamd, SpamAssassin, and so many other alternatives. Then I decided to try writing my own in JS.

Spam Scanner (work in progress) is at https://spamscanner.net with source code at https://github.com/spamscanner. Trying to do it in a privacy-focused way, which is incredibly challenging to say the least.

Fortunately we're thinking that with ARF in combination with human curators (privacy-focused where sensitive data is redacted during curation process), and a combination of tech - will make this at least a bit better - and completely open source too.

We're in the progress of building an SMTP alternative, so we're not just a forwarding service (Forward Email at https://forwardemail.net) - and I hope to have Spam Scanner hooked in to individual inboxes as well, so it gets smarter for the individual users as opposed to group-think.

I'm hoping that we can at least make things a bit smarter with some scrappy measures over time. Hoping to launch SMTP by April so you can use Thunderbird, Apple Mail, or K-9 for instance with your own inbox running Spam Scanner.

For a detailed description of these fields, refer to the docs. Typically, the result in the is_spam field should be enough to give you confidence that your email will not be marked as spam. Note that spamscanner does not assign a numerical value but instead opts to return a boolean.