MailHog stops responding after 250 Ok: queued as ... if eventstream disabled in browser

[rhysm]

Have just been trialing MailHog. Very easy to get up and running!

When testing it out I was watching my Emails come through in the WebUI and clicked around some of the buttons. I noticed after clicking the toggle eventstream and it turning from green to red that after a couple more emails are sent the SMTP server stops responding to requests after the mail gets queued for delivery.

I've managed to reproduce using telnet. Steps to reproduce are:

• Send a few messages and watch them appear in the web console
• Toggle the eventviewer in the browser to off
• Send a few more messages, usually after the 3rd or 4th message the server will stop responding to quit, or any other command for that matter. For example see below:

 telnet localhost 1025
Trying ::1...
Connected to localhost.
Escape character is '^]'.
220 mailhog.example ESMTP Go-MailHog
HELO test
250 Hello test
MAIL FROM:<test@test.com>
250 Sender test@test.com ok
RCPT TO:<test@test.com>
250 Recipient test@test.com ok
DATA
354 End data with <CR><LF>.<CR><LF>
Hello
.
250 Ok: queued as 54929b149a6dd2435200000b
quit
quit




quit

I've managed to reproduce it pretty reliably, everything works fine until I toggle the eventstream to off.

[ian-kent]

Thanks @rhysm - think I can guess at the problem, I think it keeps trying to write to the closed connection, not sure it ever gets cleaned up. I'll have a look asap.