Add email blacklist functionality to server components #21
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
This PR adds server-side blacklist functionality to MailHog-Server, complementing the main MailHog application blacklist feature.
Changes Made
Blacklistfield toConfigstruct for storing blacklisted email addressesGET /api/v2/blacklist- List all blacklisted emailsPOST /api/v2/blacklist/{email}- Add email to blacklistDELETE /api/v2/blacklist/{email}- Remove email from blacklistAccept()function signature to receive blacklist parameterTechnical Details
validateSender) and recipient (validateRecipient) addressesIntegration
This PR works in conjunction with the main MailHog repository changes to provide complete blacklist functionality. The server-side components handle the core SMTP validation logic while the main application manages the user interface and configuration.
Files Modified
config/config.go- Added Blacklist field to Config structapi/v2.go- Added blacklist API endpointssmtp/session.go- Added blacklist validation to SMTP sessionsmtp/smtp.go- Updated Accept function call to pass blacklist🤖 Generated with Claude Code