feat(inbound): MailgunInboundParser#28
Open
mpge wants to merge 1 commit intofeat/inbound-email-controllerfrom
Open
feat(inbound): MailgunInboundParser#28mpge wants to merge 1 commit intofeat/inbound-email-controllerfrom
mpge wants to merge 1 commit intofeat/inbound-email-controllerfrom
Conversation
Adds Mailgun as the second supported inbound provider alongside Postmark (from #27). Mailgun POSTs multipart/form-data with snake-case field names — the Spring controller already ingests a Map<String,Object>, so this parser just reads from that map and the controller routes via ?adapter=mailgun. Notes: - Mailgun's 'from' is typically 'Name <email>' — we extract the display name portion separately and fall back to the sender field for the email. Strips surrounding quotes on the name. - Mailgun hosts attachment content behind a URL (large attachments). We carry the URL through in downloadUrl; a follow-up worker can fetch + persist out-of-band. - Malformed attachments JSON degrades gracefully (empty list). 7 JUnit tests cover core field extraction, threading headers, provider-hosted attachment parsing, malformed attachments JSON, sender→from fallback, bare-email (no display name) handling, and the quote-stripping on display names.
This was referenced Apr 24, 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
1 participant
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
Adds Mailgun as the second supported inbound provider alongside Postmark (from #27). Mirrors the .NET counterpart (escalated-dotnet #25).
Mailgun POSTs
multipart/form-datawith snake-case field names (sender/recipient/body-plain/body-html/Message-Id/In-Reply-To/References/attachments). The Spring controller already ingests aMap<String, Object>from the webhook body, so this parser just reads from that map; the controller routes via?adapter=mailgun.Notes
fromis typically"Name <email>"— we extract the display name portion and fall back to thesenderfield for the email. Surrounding quotes on the name are stripped.downloadUrl; a follow-up worker can fetch + persist out-of-band.Dependencies
feat/inbound-email-controller). Merge order: feat(email): add MessageIdUtil for RFC 5322 threading + signed Reply-To #24 → feat(email): wire MessageIdUtil into EmailService outbound headers #25 → feat(inbound): scaffold InboundMessage + InboundEmailParser + InboundEmailRouter #26 → feat(inbound): PostmarkInboundParser + InboundEmailController #27 → this PR.Test plan