This is probably one of the "worst practices" in a trigger.
For starters, you need to elevate secutity.
Secondly, the amount of overhead that occurs with each Insert/update/delete is significant.
You may want to explore inserting a record into a "message" table in the trigger, and have a different process scan this table for changes or additions. If there is somehting to do, the process sends the email.
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/