Open staabm opened 6 years ago
Mailhog seems to write every line of an email-attachment to the log (journalctl -u maillhog on centos). The response time goes drastically down. Is there a way to avoid this?
seems to be related to https://github.com/mailhog/MailHog/issues/96
for me, delivering mails with attachments is somewhat impossible ... slow.
I have a small spring boot application wich sends mails - when I add an 19kB(!) attachment, it takes minutes to deliver it. Every 1024byte chunk is written in the mailhog log!? And finally the sender freezes on sending...
The debugger says the process waits in InputStream.socketRead0 - I think it waits for a SMTP response.
I’m facing the same issue. Is there a way to configure MailHog to boost his attachment parsing?
+1 in 2022 for me in version 1.0.1
installed with homebrew. Testing email jobs with large attachments is nearly impossible.
Mailhog is damn slow when it comes to attach files, 10 mb file took 2 minutes to send. Had to restart docker
some of the mails we send into mailhog contain PDF files (e.g. "terms of service" or similar). these mails are ~600kb in size which leads to a "explosion" of data which needs to be transmitted to the browser on the initial requeest via https://myhost/api/v2/messages?limit=50
the reasons is, that this message ajax request already contains all attachments in a base64 (or similar?) encoded form.
would it be possible to load attachments after opening a mail instead of sending all the data when rendering the list-of-emails ?