Post by @algernon@come-from.mad-scientist.club

@algernon@come-from.mad-scientist.club 8 hours ago

That score idea from yesterday was too simple.

I need more than that.

I'll have a reports object in the context. Each report has a name, a score, and an explanation. The script can add a report anytime. Can ask for a summarized score. Can list them.

This lets me run ryoms in "explain" mode, where it will format the reports in the end, instead of acting like a milter. Will still stop at the same time.

16 hours ago

One thing I can add ahead of time is the scoring system. I can make score available in the context, an f32 that every callback can fiddle with as they please.

The decision what to do with the score is also the responsibility of the script. The runtime merely provides a way to track it.

19 Replies

0 Boosts

Luddicus Mus

@algernon@come-from.mad-scientist.club 8 hours ago

Same idea can be borrowed for #iocaine too, in the future.

Luddicus Mus

@algernon@come-from.mad-scientist.club 8 hours ago

The whole reason for this project is two-fold: I want a non-slop, understandable milter, and I want to experiment with how to drive things like this, so I can use the lessons learned in iocaine too.

Why nit experiment there? Because iocaine3 already works, I needed a greenfield project, something to rebuild from the grounds up. Something I need too, not just for experimentation.

This last part is where iocaine is inadequate: I already have it. I don't need to rebuild it, I just want to.

With ryoms, I have to build it.

Luddicus Mus

@algernon@come-from.mad-scientist.club 6 hours ago

Heh, I don't even need to provide a report score summary function from the Rust side. It's a few lines of Roto.

fn score() -> f32 {
let s: f32 = 0.0;
for report in reports.list() {
s = s + report.score();
}
s
}

Luddicus Mus

@algernon@come-from.mad-scientist.club 5 hours ago

A'ight. Time to figure out how to better test this thing without deploying it. And I don't mean miltertest. I want something like:

ryoms explain message.eml \
--client-hostname "[127.0.0.1]" \
--helo "telchar.local" \
--mail-from "<me@example.com>" \
--rcpt-to "<me@example.com> \
--report-to report.txt

And it would then simulate a milter session, run all the things the milter would run, and then save the report to a file. Not to stdout, because the script might log there, and we don't want to mix the two.

~12 more replies

Luddicus Mus

@algernon@come-from.mad-scientist.club 4 hours ago

Progress!

❯ ryoms --script roto/example explain message.eml
Explanation {
filename: "message.eml",
report: ReportSummary {
score: -100.0,
},
reports: [
Report {
name: "PERMIT_LOCALHOST",
score: -100.0,
explanation: Some(
"Localhost is permitted to do anything.",
),
},
],
}

It doesn't parse the email yet, only runs a connect, but it can grab the reports, and structure them in a format I can then shove into a template engine.

jack

@jackeric@beige.party 5 hours ago

@algernon this can be reduced surely - something like

fn score() -> f32 {
reports.list().iter().map(|&x| x.score()).sum()
}

1 more replies