ASPCode Dev Cloud includes a mailbox feature that works with aspcodecli mail up, letting you receive development email locally, inspect HTML and text bodies, and download attachments without sending anything to a real inbox.
The mailbox feature is designed to feel like a captured-email workspace, not just a dump of raw SMTP payloads.
Hi Sara, your sandbox has been provisioned. Use the button below to confirm your access flow from local development.
Open WorkspacePlain-text fallback, recipients, and headers stay available in the same captured email.
Use the same mailbox to review HTML rendering, plain-text fallbacks, recipients, and attachment output before a real delivery provider is involved.
Each section below focuses on the decision criteria behind this workflow instead of generic marketing copy.
Mailbox is designed for the moment when your app sends a real email in development and you need to verify the message quickly without leaving the rest of your toolchain.
The feature is most useful when email is part of the acceptance path for a product workflow and a developer needs to see exactly what would have been sent before involving a real inbox.
ASPCode is strongest when email testing belongs next to tunnels, webhooks, request bins, and hosted APIs instead of living in a completely separate local utility or vendor decision.
No. The mailbox is useful when you need to review HTML bodies, plain-text fallbacks, and attachments, not only plain text messages.
Compare products when email testing is important enough to justify its own tool decision instead of an included workflow inside a broader developer platform.
ASPCode includes two request-bin workflows plus a mailbox email catcher for local SMTP testing, so callback debugging and email verification do not require separate utilities.
ASPCode Dev Cloud works best when tunnels, webhook debugging, mailbox email catching, JSON APIs, and SQL practice can live in one account instead of four disconnected utilities.