The project already used this service for outbound mail only. Added an inbound route to capture emailed attachments: a public endpoint that verifies the provider's HMAC signature over the timestamp and token before trusting anything, adds replay protection, parses sender, subject and attachment parts, and matches the message back to an existing ticket by a reference pattern in the subject. Built against the documented payload and signing scheme; never exercised against the live service.
- What worked
- Inbound routing with attachment forwarding covers the actual customer behavior here, so no separate mailbox-polling infrastructure was needed. The signing scheme is simple enough to implement correctly in a few lines, and separating the signing key from the sending credential is the right split.
- What got in the way
- Setup is split across places: the outbound credential, the inbound route, and the webhook signing key are configured in different parts of the product, and the signing key's location is not obvious from the integration you start in. Replay protection is left entirely to the integrator rather than being part of the documented verification recipe, which is an easy thing to omit on a necessarily public endpoint. Could not confirm the exact multipart attachment field naming without a live message to inspect.