I agree that it makes sense to not send an email from the trigger. We needed to be notified with fewest lag possible and there were also multiple sql server agents to be managed with minimal modification/maintenance necessary. The trigger has been running on our 4 servers for the last 10 months and so far emailing (SMTP) from it didn't cause any headache. One thing though, when a job fails we end up getting 2 emails, the original notification followed by the email trigger generates, kinda ugly but beats going to the server and reading the job history manually.