• Ed Wagner - Saturday, May 6, 2017 3:13 PM

    I think Sue hit the nail on the head.  If you look at https://docs.microsoft.com/en-us/sql/relational-databases/system-stored-procedures/sp-send-dbmail-transact-sql, you'll see that the @recipients parameter is definitely a varchar.  There are other parameters that are nvarchar and I can tell you from experience that they do work properly.  Specifically, I've used subject and body in this procedure as Chinese and it works fine.  The recipients parameters, however, are varchar, so they wouldn't support Unicode characters.

    I might be mistaken, but I don't think the characters that the OP has provided would be lost on a varchar parameter. At least on my my instance the below SQL returns:
    string
    ------------------------------
    Jørgen Ørum <jørgen@ærø.dk>
    aß?

    CREATE TABLE #Test (string varchar(30));
    GO

    INSERT INTO #Test
    VALUES
      ('Jørgen Ørum <jørgen@ærø.dk>'), --OPs example email
      ('αβγ'); -- Some more random Greek characters.
    GO

    SELECT *
    FROM #test;

    DROP TABLE #Test;
    GO

    So the only character that was "lost" was γ. I can't see why a varchar parameter would therefore be unhappy to receive the characters in the OPs post.

    Thom~

    Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
    Larnu.uk