Ok - A quick follow up here. We will need to get a patch out related to this. I was able to duplicate the problem this afternoon and after reviewing the code more and more I found that it was only doing this if the EmailTO field had this token and not the Email Message (Whooops
). We implemented some of these checks recently to improve performance in not handling the the replace statement unless the token was present but... obviously the token is not going to be present in the EmailTO field
So... This will be available in the next patch or hot fix as 04.10.50 and I have just verified that this fix is working properly within our development environment. Thank you for bringing this to my attention.
Thanks,
Chad