You are right. All the characters can be represented within 8-bits, no unicode is needed.
But if we expect a string to be unicode, then all special characters are above ascii 127, and must be represented by 2 bytes.
You write about "raising a connect item" .. what is that?
Have any of you tried to make a subscription on your local installation, to a fake address with a special character (any above ascii 127) to see what happens?
The reason why I ask, is that I have tested this on a virtual machine I use for development. There I have a mailserver installed, that saves the mail to disk, in stead of sending it away. When I try to send to our friend jørgen, it actually send it without an error. But when I open the mail to see what is inside it, the address has been changed from jørgen@ærø.dk to firstname.lastname@example.org
. I wonder if the mailserver is causing me trouble. Although the reason for opening this thread was the same error on two different real life installations both giving an error.