Some overdue maintenance got done today:
- Updated ~/.procmailrc to direct some noise into the appropriate folders, from which they had escaped due to envelope sender changes
- Ensured several (2 physical, 2 cloud/virtual) servers are fully current with Debian/Trixie (including reboots for fun kernel updates)
- Reminded myself how to log output of Tinyfugue sessions 👴

Time to do a little bit of grilling, now 🌭🍔

#Maintenance #Backlog #Procmail #Tinufugue

Nostalgic memories from 2001 🤗

# spamrc by Pawel Krawczyk [email protected] # $Id: spamrc.txt,v 1.43 2001/02/13 13:09:41 kravietz Exp $

If you look at the #procmail scoring worked back then, today anti-spam systems like Rspamd work pretty much on the same principle

https://web.archive.org/web/20010304202647/http://ceti.pl/~kravietz/spamrc/spamrc.php3

Spamrc, procmail rules for automatic spam detection

I had been thinking about the filtering part of #fcli, my #Mastodon to #email bridge as 'similar to #procmail', but today I realised that if I add custom headers to the email messages it produces I can just use procmail itself. By interfacing #Fediverse ideas with email standards I seem to be needing less and less custom code to get a setup which works for me, and making more and more use of decades old open source software, which is actually a pretty great outcome.
uhh #Procmail ist ja echt kryptisch. Aber hab doch hinbekommen zu fixen bei #SmartList. Das wurde wohl noch vor #SPF geschrieben. Heute ist wichtig, dass From korrekt ist und Ursprungssender lieber in Reply-To packen.

I'm thinking about experimenting with replacing the filters in #FCLI with something more general purpose, inspired by #procmail recipes.

Procmail uses regular expressions on email headers (and bodies), so I wonder what the equivalent is for #JSON documents. Is this an #XPath like use case? I started looking for the JSON equivalent of XPath, and found #JSONPath, and then realised that XPath supports JSON natively nowadays.

Das #Dovecot 2.4.2 Update unter #Gentoo ist auch so ein Krampf. Die neue Standardkonfiguration verlangt den User "vmail", der nicht vom Installationsskript angelegt wird. Früher™ hat das auch mit anderen Nutzern geklappt (z.B. bei #Postfix). Naja. Und die Integration mit #procmail ist jetzt auch futsch. Menooo.

Eine halbwegs hilfreiche Update-Anleitung fehlt auch. Ich hab jetzt wirklich kein komplizierte Setup, nur persönliche Mails abrufen und einsortieren, halber Vormittag dafür schon weg. 🙄

Was man nach zwei Wochen action on-site beim Kunden Samstagabend halt so macht: #Procmail Receipts zu #Sieve Receipts konvertieren.

Auf ne gewisse Art und Weise auch entspannend.

#Manitu

Looking to replace #procmail for local (client-side) mail filtering/sorting.

Only to find that #fdm also looks dead in the water. 🤔

Or maybe it's just finished and mature ...?

#email

In praise of #procmail

I thought I'd check to see how #procmail is doing after all this time.

It seems it's sort-of alive, via:

https://github.com/BuGlessRB/procmail

But even that project seems abandoned or inactive -- looking at the PRs which are there, they look good, but no-one is merging them.

I used to really like procmail -- you can also use it for more than sorting email as well.

It's also a shame that https://procmail.org just returns an empty JSON fragment `{}`.

I hope someone picks this up -- I would, but I think I might spread myself thin if I were to.

But I'm happy to, if no-one is will be...

GitHub - BuGlessRB/procmail: The mail sorting program

The mail sorting program. Contribute to BuGlessRB/procmail development by creating an account on GitHub.

GitHub

#procmail pro tipp:

alle emails die nicht an eine addresse in der domain gehen direkt in den spam ordner

* ! ^TO_*@domain.tld
$HOME/Maildir/.spam/

(ich bin allerdings nicht sicher ob man asterisk benötigt, ich habs einfach mal drin, doppelt gemoppelt und so)

edit: TO_ ist ein magic word und beinhaltet to, cc und bcc

der zielordner muss gegebenenfalls auf das eigene setup angepasst werden