3 ms·
It's amazing that the popular mailing list manager Mailman doesn't seem to have the feature of user-defined filtering. You should be able to send a command to t
by kazinator 4y ago
It's amazing that the popular mailing list manager Mailman doesn't seem to have the feature of user-defined filtering. You should be able to send a command to the list robot not to send you messages that match certain criteria.
If you embroil yourself in some debate you don't want, you will still see the subsequent posts, as you continue to be Cc:'d on the debate. CC's reach you directly, bypassing the robot.
But the filter would at least not show you newly started discussions which match some pattern.
Furthermore, it should be easy to move or synchronize such rules between mailing lists (even on different servers, run by different orgs).
Of course, you can always filter locally in your MUA or possibly MTA.
- Karrot_Kream 4y agoThis is one of my most disliked parts of the email model. I generally have an MTA running and IMAP server where I set rules such as blocking mailing list threads and use my MUAs as dumb clients to fetch from the IMAP server. Setting the rules on the MTA is a bit of a pain but it works and keeps my setup portable.
- u801e 4y ago> If you embroil yourself in some debate you don't want, you will still see the subsequent posts, as you continue to be Cc:'d on the debate. CC's reach you directly, bypassing the robot. This is where client side filtering comes in. Mail and News clients come with sophisticated filtering capabilities. For example, if you keep getting CC'd in a flame war type thread, you could filter replies based on the From header, the Subject header, and/or even checking for certain terms in the message body.
- tbrownaw 4y ago> Of course, you can always filter locally in your MUA Well, the user's agent is the correct place to put the user's filters.
- kazinator 4y agoFrom purely and efficiency point of view, filter which removes events should be as high up the chain as possible. As close to the source as possible. Say that the mailing list robot is processing an email from somebody and it turns out that every single mailing list subscriber is blocking that email for one reason or another. The mailing list robot can drop it in the bitbucket. No mail servers need to be contacted. In this situation, it would be possible for the mailing list to do something interesting: it could prevent that message from making into the list archive, like it never happened. That is not possible with user filtering. If nobody receives the message due to downstream user filtering, the robot has no way of knowing that. Effectively the list-side user defined filters could act as a vote of whether a message is actually accepted by the mailing list and made available in its web archive. If the current subscribers don't accept a post, then the list of such doesn't accept the post.