In 3.3.8, you shouldn't be able to enter an invalid email address. But then I didn't trying every different combination possible.

Can you look in the EventsNotification table on the database, so see if there is an invalid email address in there?

Youy might want to edit your last post since the AT is actually showing as an @ in the URL for mrs.incredible......

Looking through the ReminderFrom, I found 2 invalid email addresses.  The installation has 5 portals, and on another portal, someone entered an invalid email address.  So I guess that one bad notification will stop the whole process.  Also, I tried to experiment with the tokens {0}, and I hoped that I would have more than 0-4.  Since they appeared to be the index of the event options, I tried going 0-8, hoping that 8 would give me the description, nope didn't work.  That too also threw an exception that would stop processing, FYI.

Thanks everyone for your help.  I knew that I had something wrong with my setup/data and I was able to find it.  I'll upgrade to 3.3.8 this weekend, which should stop bad emails from getting in to the database.  And hopefully the exceptions killing the processes will go away sometime too, but without knowing the design I can't don't know how easy that is.

Brian Carlson