As part of writing a new mail client I'm wondering about how to change my email-life, and how other people process/handle their incoming email.
I sort my incoming email into folders at delivery-time using procmail. Mail is generally filtered into mailboxes on the basis of the company that sent it, the person that sent it, or the machine which generated it.
Because I manage a lot of machines personally I've split things up so that I have a folder per host. So on a morning I might have unread mail in the following folders:
machines.steve.org.uk/ machines.da-db1/ machines.da-db2/ machines.da-web1/ machines.da-web2/ machines.da-web3/ machines.da-web4/
The per-machine mailboxes usually contain a single mail every day from LogWatch, along with output from any cron-jobs. For example today I received the mail:
From: Cron Daemon To: [email protected] Subject: Cron [email protected] /home/steve/bin/download-check URL http://nodejs.org/ - no longer matches v0.10.9
Generally speaking I don't need to read the per-machine messages. I'll keep the most recent 100 for reference, but only need to look if something seems "off" on a machine. But if I don't look I'd not see the node upgrade notice, so find that I do read them after all.
This suggest to me that email isn't the right way to handle this kind of thing. Instead I should use a notification system - at work we have a central service called MauveAlert (yes, Red Dwarf reference). Mauve receives "alerts" of various kinds, via UDP. The alerts are then fanned out to appropriate people via XMPP, Email, or SMSs.
I have a similarly-inspired system I use on my Debian Administration cluster. A (node) service runs non-stop collecting UDP messages and showing them on a dashboard. I look at it throughout the day to see when slaughter runs, etc.
Anyway in conslusion I get a lot of mail. Some of it is related to random projects, and all ends up in the steve.org.uk/ mailbox, some of it relates to machines, and gets filed away, and I have regular conversions with folk so I have a .people.kirsi/ folder which receives a lot of attention, for example.
ObRandom:daily() - Mark ~/Maildir/.machines.*, etc, read.
Tags: email, lumail, random 8 comments
https://www.mirbsd.org/jupp.htm
I get all² incoming mail¹ into INBOX.
â‘ Not spam after bayesian tagging using bmf, that goes into Spambox.
â‘¡ Except for one high-volume mailing list I do not really read at the moment â“ but my MUA doesnât act on unread messages in that folder.
I then proceed to peruse the new messages in INBOX, reading or deferring them as necessary. Or just deleting. Every once in a while, I skim all messages in Spambox; usually, I just pipe them all into a script that blacklists the sender IP for 24 hours, then delete them. False positives get piped into a script to train bmf instead (same with false negatives: spam that ends up in INBOX).
I tried a filtering setup once. I quickly went back to having everything put into INBOX (and deferred some of the mailing lists to ânomailâ and read them via GMane, if at all, now, either Loom or NNTP) after I found out that having more than one incoming folder distracts me a lot, as I find myself switching between them and checking for new mail a lot.