Problem with RFC822 phrase handling setting and option 'Use CN as phrase"

After upgrading Iseries from Domino release 8.0.2 to 8.5 problem occurs. We have a user ‘Frédéric LASTNAME’ who was trying to send mail outside. He got mail router errors with option ‘Sender Denied’. After struggeling for a long time trying to figure out the problem, i tried to send an email from his notes account to my outlook mail. Here things got bizar.

The Display name in the outlook mail i received is correct (“Frédéric LASTNAME” F.LASTNAME@COMPANY.be) but the Email address looks like this (=?windows-1252?Q?=22Fr=E9d=E9ric_Van_Olmen=22_=3CF=2EVanOlmen=40Sermar=2E?= =?windows-1252?Q?be=3E?=)

I then thought it could be the phrase handling that is causing the problem. So after changing the setting in the Configuration Document of the server :

MIME - Advanced - Advanced Outbound Message Options - RFC822 phrase handling

from ‘Use CN as phrase’ to ‘Do not add phrase’ things start working again.

I tried a test message from that users notes mail file to my outlook account and the mail is normal except his CN name is now missing. But the Email address is now okay.

I then send a test message to the mail domain he had problems with (delivery failures : sender denied) and the problem was gone. He could again send mail to those people.

Has anyone gotten in this strange BUG.

If so please let me know if there is a fix for it. Our management would like to use the CN phrases in their mails. please send info to p.vanboom@conti7.be

Thanks in advance

Subject: Outbound SMTP addresses: RFC821 part garbled when 822 phrase contains non-ASCII chars?

Looks like the same bug as this thread:http://www-10.lotus.com/ldd/nd85forum.nsf/dba3ca7e515d55ff85256a0700727b35/d01e02df79d758fb8525764d0029680f?OpenDocument

Subject: Re: Problem with RFC822 phrase handling setting and option 'Use CN as phrase"

My apologies for such a late response, Peter. Its very interesting that only one particular User is having difficulty with using their CN as a phrase. Unless you have already done so, I strongly recommend that you engage IBM Lotus Software Support in concern of this problem.