fix: restore explicit allow-all with recipient glob patterns - #250
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #250 +/- ##
=====================================
Coverage 84.6% 84.6%
=====================================
Files 31 31
Lines 9229 9229
Branches 1297 1297
=====================================
Hits 7810 7810
Misses 988 988
Partials 431 431 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
alonsoac
pushed a commit
to PBX-Virtual/mcp-email-server
that referenced
this pull request
Sep 14, 2026
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.
Summary
Follow up on #247 (comment).
*/*@*for all valid recipients, domain patterns such as*@example.com, and?/ bracket expressions.Compatibility
This restores an explicit opt-in for dynamic-recipient workflows; it does not restore implicit allow-all for an empty list. A wildcard authorizes all three operations, not drafts only. Existing entries containing glob syntax now act as patterns.
Validation
make checkmake test: 1506 passed, 37 skipped; 87.41% coveragemake docs-testmake test-e2e: 12 passed against GreenMail, including explicit wildcard send/forward/save and live managed-policy changesmake frontend: lint/typecheck, 41 frontend tests, staged asset verificationmake test-browser: 2 passedPlanned release: 1.9.0, after CI passes and merge.