Troubleshooting
Feel free to
raise an issue if you are having problems, but please check existing issues first.
Unable to receive live web UI message updates
If you are using a proxy server (for example, Nginx or Apache) to access your Mailpit instance, your proxy configuration must include the protocol Upgrade headers. Please refer to the proxy documentation or the following specific documentation about proxying websockets: Nginx, Apache, and IIS.
No browser notifications for new messages
This feature is only possible when accessing your Mailpit web UI via HTTPS, or when accessing Mailpit via http://localhost:8025. This is not a restriction of Mailpit; it is a browser security feature. Please refer to the HTTPS documentation.
452 4.5.3 Too many recipients
Mailpit has a default limit of 100 recipients per email. Many mail servers, including Gmail, impose a maximum of 100 recipients, so this is a safe limit for testing purposes. This can be adjusted by setting the --smtp-max-recipients <x> flag in Mailpit.
XMLHttpRequest blocked by CORS policy
Access to XMLHttpRequest at ‘http://example.com/api/v1/messages' from origin ‘http://anotherexample.com/' has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.
If you are trying to access your Mailpit API via browser JavaScript from another domain, you will need to specifically allow CORS (cross-origin resource sharing) from that domain.
Please refer to the CORS configuration documentation for more information.
Edit this page