Continuing where I left off yesterday, today will likely be about rspamd.
...the email experiment will continue tomorrow. The bed calls to me.
Discussion
Continuing where I left off yesterday, today will likely be about rspamd.
...the email experiment will continue tomorrow. The bed calls to me.
And immediately, my mind goes: what if rspamd, but rust and #roto? Iocaine for email.
So. Very. Tempting.
I guess we'll rake the road less traveled, and go on an rspamd-shaped side quest. Our party will include the great wizard, Rust, a trusty cleric, Roto, and an unhinged bard that enchanted them, and his song leads them into a maze of email, all alike, yet so different and unique.
Also: that typo. Rake the roads less traveled. An accidental phrase I will be using more, going forward, because it is beautiful.
While still in bed and planning, another side quest: how shall we name this experiment?
It's something that came up in a whim, was not premeditated, so I'm currently coming up blank.
Gonna read some more RYOMS, perhaps I will gain some inspiration.
Routinely Yacking Old Mail Selector
Roboustly Yacking Our Milter System
Yeah, I think RYOMS will be a suitable acronym. Plenty of good ways to expand it.
Today is gonna be a good day, for we are not only avoiding slop and fighting spam, we are also experimenting, and blowing things up in a lab, and that's absolutely delightful.
Boom! Heeheheheee.
I'm gonna put the repo under the iocaine org on my forge. Will probably move OJF there, too, because they're all the same family, really.
So very excited! Almost ready to jump out of bed, and not wait until the rest if the family wakes up.
I wanna haaaaaack!
Since I use a relay for outgoing mail, I only need to care about the verification parts of SPF and DKIM, for incoming mail.
This makes life a whole lot simpler.
Heh. What if... ryoms explain mail.eml?
It'd run the checks, and explain each result, and the score given. More useful than a list of checks & scores in a header.
Could even run the milter in verbose mode, where it saves the explanation to S3, to a file based on msgid or something.
Could then add an x-ryoms-info header, with an url to the explanation.
I'm gonna have so much fun with this.
Btw, this too will be Filthy Human Hands licensed. Technically not FLOSS. 0 fucks given.
Another benefit of this side quest is that I can experiment more freely with building a Roto library / module collection. A set of reusable parts.
Oooh oooh oooh. Fuuuck. I am a genius.
Ryoms web ui: log in with imap credentials, see all the reports stored on s3. Allows deleting / archiving, and I might even make it possible to fetch the raw email via imap too.
Should also have an api, so I can teach my mail cluent to fetch the report on demand, and display it in emacs.
Bayesian filtering? Mmm, not yet. I have trained rspamd on 10 years of spam and ham, and the bayesian score is still pretty useless.
The spam I catch, I usually catch without training. So I win't bother until I have to.
Why is it useless, though? Because I receive a lot if legit mail, from banks, utilities companies, forges, etc, that are all very html, very tracking pixels and shit.
@algernon ironically, identifying spam might be one of the few not-terrible applications of an LLM?
@cinebox there are no non-terrible uses of an llm. I can do better spam classification with clear, understandable rules, at a tiny fraction of the resource cost, and without relying on tech that keeps trying to DDoS me.