Track SMTP2GO delivery feedback without inventing an inbox
Configure outbound event webhooks, correlate message outcomes, and keep reply receiving as a separate infrastructure choice.
Reviewed
SMTP2GO’s delivery webhooks report events for outgoing mail. They are useful for bounces and delivery monitoring, but do not turn the service into an incoming mailbox for customer replies.
Configure a feedback receiver
- Follow the current webhooks overview and setup guide.
- Subscribe to the events your application needs and configure the documented receiver authentication controls.
- Correlate each authenticated notification with the provider email identity and application send intent.
- Store event processing durably before acknowledging and tolerate duplicates/out-of-order outcomes.
Do not invent a MailKite-compatible signature header. Follow SMTP2GO’s current scheme and test the actual protection you configured rather than trusting an event-shaped JSON body.
Verify failure handling
Use a controlled send and inspect activity/feedback. Confirm a duplicate notification is harmless and a complaint or permanent failure cannot be cleared by a late delivery update. Avoid retrying suppressed or rejected recipients automatically.
If you need incoming replies, keep the From/Reply-To identity backed by an actual receiving service. MailKite can provide signed incoming JSON on a verified address, but that requires an explicit routing and application integration.
Source: SMTP2GO feedback documentation. Report endpoints and delivery webhooks are alternatives to repeated uncontrolled polling, not proof of final inbox placement.