You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using API V1: DELETE /api/v1/messages/{ message_id } with a wrong message id, e.g.
DELETE /api/v1/messages/aaa will still delete one message (very easy to reproduce).
Found in release 0.2.1.
-Tal.
The text was updated successfully, but these errors were encountered:
Without any configuration MailHog will use in-memory storage.
Can you confirm which storage backend it is - it'll say in the MailHog logs on startup. I've had a look at the MongoDB and in-memory backend code and there's no obvious bug, but narrowing it down a bit would help!
Using API V1: DELETE /api/v1/messages/{ message_id } with a wrong message id, e.g.
DELETE /api/v1/messages/aaa will still delete one message (very easy to reproduce).
Found in release 0.2.1.
-Tal.
The text was updated successfully, but these errors were encountered: