{"enrichment":{"faq":[{"a":"mailpit-integration enables you to set up a containerized Mailpit SMTP server within .NET Aspire, capturing all outbound emails during local development. Configure your ASP.NET Core application to route emails to the Mailpit container via SMTP settings, then access the Mailpit web UI to inspect rendered emails, headers, and content without sending real messages. This approach integrates seamlessly into your Aspire orchestration, allowing you to test email functionality alongside other services in a unified local environment.","q":"How to test emails locally with mailpit in a .NET Aspire project?"},{"a":"mailpit-integration is an MIT-licensed skill that integrates Mailpit, a lightweight email testing tool, into .NET Aspire projects for seamless local development workflows. It handles containerized SMTP server setup and web UI configuration, enabling developers to capture and inspect emails without external services. The skill is perfect for testing email functionality across .NET applications during development cycles, providing both UI-based inspection and programmatic API access to verify email delivery and content.","q":"What is mailpit-integration and how does it support email testing?"},{"a":"Yes, mailpit-integration supports writing integration tests by providing access to the Mailpit API, allowing you to programmatically assert on captured messages. You can verify that emails were sent, inspect their content, headers, and rendering, and validate that expected information appears in the message body. This enables comprehensive email delivery testing within your ASP.NET Core test suite, ensuring your email sender service behaves correctly without relying on external email providers during test execution.","q":"Can mailpit-integration help write integration tests that verify emails are sent and contain expected content?"},{"a":"mailpit-integration guides you through configuring SMTP settings in your ASP.NET Core application to connect to the Mailpit container running in .NET Aspire. You configure your email sender service to use Mailpit's SMTP endpoint (typically localhost:1025 in development), allowing all outbound emails to be intercepted and stored locally. This configuration keeps your development environment isolated and prevents accidental emails from being sent to real addresses during testing and debugging.","q":"How does mailpit-integration handle SMTP configuration in ASP.NET Core?"},{"a":"mailpit-integration provides access to the Mailpit web UI, where you can debug email rendering, inspect headers, and review delivery details without sending real emails. The UI displays all captured messages with full rendering previews, allowing you to verify that your email templates display correctly across different formats. You can examine SMTP logs, view raw message content, and inspect email metadata\u2014making it ideal for troubleshooting email functionality during local development before deploying to production.","q":"What can you do with the Mailpit web UI for email debugging?"},{"a":"mailpit-integration enables you to access the Mailpit API programmatically from your .NET code, allowing you to query captured messages, assert on email content, and automate email verification in integration tests. You can retrieve message details, inspect attachments, and validate that specific emails were sent with expected content. This API-driven approach complements the web UI, giving you both manual inspection capabilities and automated testing support for comprehensive email validation in your ASP.NET Core applications.","q":"How do you access the Mailpit API programmatically with mailpit-integration?"}],"shadow_tags":["local-email-testing","smtp-interception","test-fixture-pattern","email-verification","container-orchestration","development-infrastructure","api-client-testing","html-email-inspection"],"summary_rewrite":"This skill integrates Mailpit, a lightweight email testing tool, into .NET Aspire projects for seamless local development workflows. It handles containerized SMTP server setup and web UI configuration, enabling developers to capture and inspect emails without external services. Perfect for testing email functionality across .NET applications during development cycles."},"files":[{"bytes":11384,"path":"skills/aspire-mailpit-integration/SKILL.md","sha256":"a039b1d50b590ea477741f20cbe755054b9515001969ed6e9ded7f075686fd2a","url":"https://skillfed.io/files/Aaronontheweb/dotnet-skills/aspire-mailpit-integration/d8610cdd/SKILL.md"}],"id":"Aaronontheweb/dotnet-skills/aspire-mailpit-integration","links":{"html":"https://skillfed.io/Aaronontheweb/dotnet-skills/aspire-mailpit-integration","md":"https://skillfed.io/Aaronontheweb/dotnet-skills/aspire-mailpit-integration.md","repo":"https://github.com/Aaronontheweb/dotnet-skills"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":98,"language":"Shell","last_updated":"2026-07-03","license":"MIT","name":"mailpit-integration","publisher":"Aaronontheweb","stars":1085},"relations":{"similar":[{"id":"wshaddix/dotnet-skills/aspire-mailpit-integration"},{"id":"wshaddix/dotnet-skills/microsoft-extensions-dependency-injection"},{"id":"woocommerce/woocommerce/woocommerce-email-editor"},{"id":"wshaddix/dotnet-skills/dotnet-csharp-configuration"},{"id":"Aaronontheweb/dotnet-skills/microsoft-extensions-configuration"},{"id":"wshaddix/dotnet-skills/microsoft-extensions-configuration"},{"id":"mwguerra/claude-code-plugins/reference"},{"id":"Aaronontheweb/dotnet-skills/microsoft-extensions-dependency-injection"},{"id":"xu-xiang/everything-claude-code-zh/docker-patterns"},{"id":"Mindrally/skills/aspnet-core"}]},"slug":{"owner":"Aaronontheweb","repo":"dotnet-skills","skill":"aspire-mailpit-integration"},"version":"d8610cdd"}