How it works
Mailpit runs as a Windows service that listens on an SMTP port. When your PHP application (or any other local application) sends an email to that port, Mailpit captures it and stores it in an in-memory inbox. You can then open the Mailpit web UI to read the captured messages, inspect headers, and check HTML rendering.Default settings
| Property | Value |
|---|---|
| SMTP port | 1025 |
| Web UI | Accessible via tray → Mailpit → Localhost |
| Service name | bearsamppmailpit |
Configuring your application
Point your application’s mail settings to Mailpit’s SMTP port. Do not use port 25 — use 1025 (or whichever port you have configured in Bearsampp). For Laravel or Symfony projects, update your.env file:
mail() function, configure php.ini to use the SMTP relay:
php.ini from the tray menu (PHP → Edit php.ini), make the changes, and restart Apache.
Viewing captured emails
Make sure Mailpit is running
Right-click the tray icon → Mailpit → Start service if the service is not already active.
Send a test email from your app
Trigger an email from your application — for example, submit a registration form or a password reset request.
Mailpit stores messages in memory. All captured emails are lost when the Mailpit service restarts. If you need to preserve a message, copy its content from the web UI before stopping the service.
Tray menu options
Right-click the tray icon → Mailpit to access:Start / Stop service
Start or stop the Mailpit Windows service.
Change port
Switch Mailpit’s SMTP port to a different value. Remember to update your application’s mail config to match.
Localhost
Open the Mailpit web UI in your browser to view captured messages.
Logs
Open the Mailpit log file to diagnose connection or startup issues.
Service details
| Property | Value |
|---|---|
| Service name | bearsamppmailpit |
| Default SMTP port | 1025 |
| Log file | logs/mailpit.log |
