It may not be helpful in your particular case depending on how your Slack is administered and similar, but my setup is like so: - https://github.com/wee-slack/

It may not be helpful in your particular case depending on how your Slack is administered and similar, but my setup is like so: - https://github.com/wee-slack/wee-slack https://github.com/wee-slack/wee-slack with WeeChat (weechat.org) for IM only (i.e. configured so that it only notifies when an IM (one-on-one or group) is received); and - https://github.com/tomhrr/paws https://github.com/tomhrr/paws for retrieving messages from Slack as email, and sending responses to those emails to Slack. https://github.com/nicm/fdm https://github.com/nicm/fdm is used for all filtering of email, including Slack messages. This allows for rules like e.g. marking everything from Slack as read, unless it's from channel X and matches your username, or it was sent after 6pm, or similar. With this setup, IMs still come through as IMs, but everything else goes to email and is treated like email. Retrieving email and Slack messages happens based on local configuration, so it can e.g. be set up to fetch once per hour, and then all of those messages can be dealt with in one go. As the filters are refined, the number of useless messages that have to be reviewed decreases. With this configuration, at least in my experience, Slack is much less of a nuisance.