@weaverryan it should be merged in the 2.2 branch

I think this is a good note to add. BUT, I'm not sure if the note is correct yet:

1. My impression from looking at symfony/symfony-standard#425 is that this has nothing to do with 500 errors. My understanding is that if my application spools emails in memory, and then an Exception is thrown, the terminate event would still be triggered and the spooled emails sent. What this issue seems to be is simply that if monolog has spooled any mails (which in production, it usually only logs 500 level things), those will not be sent. Is this correct? If so, I think we should change the message - it sounds like a 500-level error will prevent my application emails to not send either.

2. The "You need to comment out the ... so the mails will be sent immediately" gave me the impression (which I know you don't intend) that the if my application fails to send some memory-spooled emails, that after I change this configuration, it will immediately "catch-up" and send all the emails that were previously-not sent. I know that's not what you're trying to say, so perhaps we can reword this as well :).

Thanks for taking this on - obviously a lot of people are coming across this issue, so I would like to cover it in the docs.

Cheers!

Hi Tom!

This issue is now closed in#2830.

Thanks!

Ah. Totally forgot about this one. Glad someone else fixed it! Thanks.