Repository navigation
Conversation
mortondev
force-pushed
the
fix/cold-spam-no-signals
branch
from
November 19, 2026 15:16
9458365 to
61f1174
Compare
A new email thread was created and announced (conversation and message events, so webhooks, workflows and the team bell) before the spam filter filed it, and the sender still got the acknowledgement mail. The fixed rules (auto-responder headers, weak sender authentication, a burst) now run before the thread exists, so a match is filed in the insert and raises nothing, the way refused mail already was. Mail the AI classifier files is no longer acknowledged either.
…ift its quarantine
mortondev
force-pushed
the
fix/cold-spam-no-signals
branch
from
November 19, 2026 18:57
61f1174 to
b2b8ea3
Compare
… arrives, unannounced
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A new email from a stranger that a fixed spam rule files (auto-reply headers, failed sender authentication, or one sender opening threads in a burst) was first created as a normal conversation:
conversation.createdandmessage.createdfired, so webhooks, message workflows and the team bell went off for spam, and the sender was sent the acknowledgement mail. Only then was it moved to Spam.Mail we refuse outright (a hard DMARC reject, a suspected mail loop) already avoids all of this: it is filed to Spam in the same write that creates it and raises nothing. Fixed-rule spam now does the same.
Tests: the real-database spam tests now check that auto-reply, sender-auth and burst filings raise no created or message events and send no acknowledgement (all three failed on main), and that accepted and trusted mail still do.