A desktop SMTP server and email viewer for safe email testing during development.
Papercut SMTP is a desktop application that acts as a local SMTP server and email viewer for development and testing. It captures emails sent from applications during development, preventing them from being delivered to real addresses while allowing developers to inspect every detail of the message instantly. It solves the problem of accidentally sending test emails to real users and the slow feedback loop of traditional email testing setups.
Developers and QA engineers who need to test email-sending functionality in applications, websites, or services during local development or staging.
Developers choose Papercut SMTP because it's a simple, dedicated tool that eliminates the risk of sending test emails to real recipients while providing immediate visual feedback. Its combination of a lightweight SMTP server with a rich email viewer streamlines the email testing workflow without requiring complex server setup.
Papercut SMTP -- The Simple Desktop Email Server
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Notifies and displays emails immediately upon arrival, eliminating the delay in viewing test emails, as highlighted in the 'Instant Feedback When New Email Arrives' feature.
Provides detailed inspection of emails including HTML rendering, headers, attachments, and raw MIME sections, shown in the rich view and MIME section screenshots.
Can be run as a desktop app, Windows service, or in Docker, with clear instructions for each mode in the README, including Docker Compose examples.
Supports TLS/STARTTLS and SMTP authentication for secure testing, with configuration options detailed in the SMTP Authentication and TLS/STARTTLS Support section.
Offers seamless integration with .NET Aspire projects via a NuGet package, simplifying setup for .NET developers as shown in the Aspire Integration guide.
Primarily targets Windows with native installers and a WebView2 dependency, making it less accessible for other platforms without relying on Docker.
Setting up TLS/STARTTLS requires creating self-signed certificates and editing configuration files, which can be complex and error-prone for quick setup.
Focuses solely on capture and viewing, lacking features like email forwarding, replay, or integration with automated testing frameworks.