A bounce in one organization suppresses the recipient for every organization
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start by reading services/email/msa/models.py, especially SuppressionQuerySet.is_suppressed, then trace the only writer in services/email/msa/tasks.py at record_bounce. Determine the intended organization scope, expiry, and owner-visible behavior for cross-organization bounces; done means those decisions are recorded and covered by the relevant behavior tests.
由索引模型根据 Issue 内容生成。
描述
A bounce in one organization suppresses the recipient for every organization. One tenant can block a shared recipient address for all tenants for 30 days.
SuppressionQuerySet.is_suppressed treats a bounce entry from any organization as suppressing for 30 days, regardless of which organization is sending:
models.Q(org=org)
| models.Q(reason=self.model.Reason.BOUNCE, created_at__gte=bounce_cutoff)
A single permanent 5xx for a shared recipient address therefore blocks that address relay-wide for every other tenant. Examples of such a 5xx are a policy refusal, a spam block, or a full mailbox at the receiving host. The block also hits tenants that have a healthy relationship with the recipient. The suppression entry carries no indication of which tenant produced it. There is no owner-visible reason beyond the word "bounce".
Evidence:
services/email/msa/models.py:SuppressionQuerySet.is_suppressedservices/email/msa/tasks.py:record_bounce, the only writer of bounce entries
Decisions to make:
- Must a cross-organization bounce suppress at all?
- Must it expire faster than an organization's own bounce?
- How does an organization learn that a recipient it never mailed is suppressed for it?
Found during the sandbox-credentials change (#259). This fault is older than that change.
- 主要语言
- Python
- 星标
- 4
- 派生
- 0
- 平均合并
- 2 小时 40 分钟
- 30 天内合并 PR
- 163
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
codingjoe/relay 的其他 Issue
-
enhancement real sec
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
-
bug side quest
难度 2/5 1-3 小时 新手友好度 77/100
维护者通常 1 天内回复
-
bug side quest
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
bug side quest
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
side quest test
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
相似的 Issue
-
changelog investigate
难度 2/5 1-3 小时 新手友好度 67/100
ramnes/notion-sdk-py#433 ·
-
docs pkg:core
难度 1/5 1 小时以内 新手友好度 84/100
pydantic/pydantic-ai#11929 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
intake/intake-esm#789 ·
-
难度 2/5 1-3 小时 新手友好度 82/100
MemMachine/MemMachine#1877 ·
维护者通常 3 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
openedx/openedx-authz#579 ·
维护者通常 1 天内回复