spark-recipe-notification-hygiene

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Recipe: Notification Hygiene

方案：通知整理

Tame notification overload by identifying noisy senders, reclassifying misplaced mail, grouping repetitive notifications, and clearing out what's no longer relevant.

Prerequisite: Read the

use-spark

base skill for command reference and filter syntax.

Access level required: triage.

通过识别消息量大的发送者、重新分类归类错误的邮件、分组重复通知以及清理不再相关的内容，解决通知过载问题。

前提条件： 阅读

use-spark

基础技能文档，了解命令参考和过滤语法。

所需权限级别： triage。

Steps

步骤

Step 1: Assess notification volume

步骤1：评估通知数量

bash

spark emails Inbox --filter "category:notification is:unread"

Count the unread notifications. If the number is high, scan the sender list for patterns - which senders dominate?

bash

spark emails Inbox --filter "category:notification is:unread"

统计未读通知数量。如果数量较多，查看发送者列表找规律——哪些发送者占比最高？

Step 2: Identify noisy senders

步骤2：识别消息量大的发送者

Look for senders that generate high-volume, low-value notifications (CI bots, social media alerts, shipping updates after delivery, etc.).

Read a few to confirm they're noise:

bash

spark thread <id>

找出那些发送大量低价值通知的发送者（CI机器人、社交媒体提醒、配送完成后的物流更新等）。

查看几封邮件确认它们属于无效消息：

bash

spark thread <id>

Step 3: Reclassify misplaced senders

步骤3：重新分类归类错误的发送者

Some "notifications" are really newsletters in disguise:

bash

spark contact-action changeCategoryNewsletters noisy-digest@example.com

Some are actually from real people and should be in People:

bash

spark contact-action changeCategoryPersonal colleague@example.com

These changes apply to all future mail from the sender.

有些“通知”实际上是伪装成通知的新闻通讯：

bash

spark contact-action changeCategoryNewsletters noisy-digest@example.com

有些邮件来自真实用户，应该归类到“个人联系人”：

bash

spark contact-action changeCategoryPersonal colleague@example.com

这些更改将应用于该发送者未来的所有邮件。

Step 4: Group repetitive senders

步骤4：分组重复发送的邮件

For senders that are useful but send too often (CI systems, monitoring alerts):

bash

spark contact-action groupEmailsFromContact ci-bot@company.com

This collapses their messages into grouped entries, reducing inbox clutter while keeping them accessible.

对于那些有用但发送过于频繁的发送者（CI系统、监控提醒）：

bash

spark contact-action groupEmailsFromContact ci-bot@company.com

这会将他们的消息合并为分组条目，减少收件箱杂乱的同时保持消息可访问。

Step 5: Bulk archive cleared notifications

步骤5：批量归档已处理的通知

For notifications that have been seen and are no longer relevant:

bash

spark action archive <id1> <id2> <id3>

Pass multiple IDs in a single command to archive in batch.

对于已查看且不再相关的通知：

bash

spark action archive <id1> <id2> <id3>

在单个命令中传入多个ID即可批量归档。

Step 6: Disable notifications for low-priority senders

步骤6：禁用低优先级发送者的通知提醒

For senders whose emails you want to receive but not be alerted about:

bash

spark contact-action unmarkContactAsImportant alerts@service.com

对于那些你想接收邮件但不想被提醒的发送者：

bash

spark contact-action unmarkContactAsImportant alerts@service.com

Tips

小贴士

The goal is to reduce the notification count to a manageable number, not zero - some notifications are genuinely useful.
Reclassification at the contact level (
```
contact-action
```
) is more effective than per-message (
```
action
```
) because it fixes all future mail.
Grouping is a middle ground between keeping and blocking - the emails still arrive but don't flood the inbox.
Run this recipe after a vacation or any period of inbox neglect to quickly get notifications under control.
Combine with
```
recipe-newsletter-cleanup
```
for a full inbox declutter session.

目标是将通知数量减少到可管理的程度，而不是清零——有些通知确实有用。
在联系人级别（
```
contact-action
```
）进行重新分类比单条消息级别（
```
action
```
）更有效，因为它能解决未来所有的邮件问题。
分组是保留和屏蔽之间的折中方案——邮件仍会收到，但不会淹没收件箱。
假期或长时间未整理收件箱后运行此方案，可快速控制通知数量。
结合
```
recipe-newsletter-cleanup
```
方案进行全面的收件箱清理。