imapfilter VS webcontainer-core

Shouldn't be _too_ hard to convert your scripts.

I ran into the same problem and one workspace disallows App passwords. You can simply get the OAuth token with a little python script and then use it as the password: https://github.com/google/gmail-oauth2-tools/blob/master/pyt...

(see for example https://github.com/lefcha/imapfilter/issues/186)

My first real exposure to Lua was as the configuration language of imapfilter. Absolutely loved both.

https://github.com/lefcha/imapfilter

Use [imapfilter](https://github.com/lefcha/imapfilter) to store the attachment in a local folder and delete/archive the mail. Then use something like [inotify](https://en.wikipedia.org/wiki/Inotify#:~:text=inotify%20(inode%20notify)%20is%20a,reports%20those%20changes%20to%20applications.)%20is%20a,reports%20those%20changes%20to%20applications.)) to run a script that sends the new pdf to the printer

Imapfilter runs lua scripts. Since it's basically just a lua interpreter with a pre-imported library, you can pretty much do any processing you might like, but... IMHO it doesn't seem great: the documentation is so-so, the API is a bit clunky and lacks basic functionality (eg. you have to decode utf8 mime headers yourself) and (personal opinion) writing an imapfilter script is not easier than using an IMAP library in whatever your favorite programming/scripting language might be.

You could look at something like imapfilter. It's designed to do what you want, I think, though I've never used it.

I know this one is an issue, and for that you will want to use an email client with the bridge. I have used a protonmail docker container shenxn/protonmail-bridge-docker with imapfilter to provide client side filtering.

If you can see yourself writing some scripts to clean it up, I can recommend imapfilter as a starting point. I learned enough Lua to be able to use this effectively. The "config" file is actually just a Lua script.

I believe that Google still offers IMAP access (I think you need to set up app passwords, or possibly jump through some OAUTH hoops), letting you use something like imapfilter to set up rules, connecting to Gmail, then doing the filtering.

imapfilter with a Lua script to send messages to Spamassassin.

Another tool actually meant for this is imapfilter: https://github.com/lefcha/imapfilter

How does it work? There is no backend whatsoever. The API Security Academy leverages WebContainers, a new technology that allows running full-blown node instances directly in the browser. Each WebContainer contains a live GraphQL application, so you'll not only understand why a vulnerability is risky, but also how to exploit it and, most importantly, how to fix it.

StackBlitz made the claim "... run Node.js, entirely inside your browser" #658, then had to revise it's claim to "We currently do not expose a way to use WebContainer outside of StackBlitz.com,".

> Wasm though seems like the likely general heir, and will have many different offerings for how to do that (Deno being one!).

I was recently blown away by some ideas that StackBlitz [0] apply based on WebContainers. The idea of a "server in the browser", they allow you to run Node-based environment like that via Wasm.

[0] https://stackblitz.com/

[1] https://webcontainers.io/

See https://webcontainers.io.

This very simple fact is well known flaw, which was already often criticized and asked for solutions by users. It doesn't only affect this kind of very exotic bootstrap applications but also significantly limits rusts usefulness in many other areas. Pure browser based scientific code documentation and example notebooks (e.g. jupyterLite) and sandboxed CI and IDE solutions (e.g. web containers) as available for many other languages are simply not available for rust because of this very fundamental issue.

Looks like they plan to open it. From the FAQ section of README (https://github.com/stackblitz/webcontainer-core#faqs):

> Is there a developer API?

I'm skeptical about stackblitz claims. The last time I checked that is closed source code https://github.com/stackblitz/webcontainer-core/issues/658.

StackBlitz claimed https://blog.stackblitz.com/posts/introducing-webcontainers/ to have implemented Node.js in the browser, though I have not observed any evidence of that being true and correct https://github.com/stackblitz/webcontainer-core/issues/658.

The other honorable mention is StackBlitz, a web-based web editor for making containers that run Javascript applications. Interestingly, StackBlitz is championing WebContainers, a technology that allows developers to start NodeJS servers within the browser. The downside is, this technology only works with Javascript-based projects (NodeJS, NextJS, etc). I include it here because WebContainers could easily be extended to support other languages via WASM, like Ruby. I’ll also add in Buildah, a tool for building OCI images. I won’t say much about this tool because it’s designed for building images; you still need another service, like Podman, to actually create the containers.