2 ms·

> 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 3y ago
  From 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.