eMessaging: email ID nombreñ with special caracteres

Product Feature: REport
Operating System: Windows 2003

Database: SQL 2005

Configuration: Apache TomCat
Version: 1.4M7


According to client Report is showing delivery successful for email with special characters and email is getting converted by emesaging from the original email ID : nombreñ com to an email without the special character: nombren�� . Client did not expected this behavior from emessaging. Client expected that once get the bounce with error due to special character: nombreñ the individual sent report (Bounc report) gets update as: Email ID :nombreñ Status : Delivery Failed. Unfortunately emessaging 


is not updating and keeps the status as Succesfuly.Please see attached files. email ID: nombreñ
EM] ERROR [pool-1-thread-10] AbstractMessageSender.doSend(331) | Invalid Addresses 2015-03-26 16:11:21,022 [EM] ERROR [pool-1-thread-10] EmailMessageProcessor.sendMessage(200) | SendFailedException : javax.mail.SendFailedException: Invalid Addresses; nested exception is: com.sun.mail.smtp.SMTPAddressFailedException: 501 5.1.3 Syntax error in mailbox address "nombreno?" (non-printable character) 2015-03-26 16:11:21,022 [EM] INFO [pool-1-thread-10] pasta_name.log(92) | 50 Error occurred in envioEmail profile: Invalid Addresses 2015-03-26 16:11:21,085 [EM] DEBUG [pool-1-thread-10] AbstractMessageProcessor.updateSendJobRecord(1295) | Update SendJob Record 2015-03-26 16:11:21,085 [EM] DEBUG [pool-1-thread-10] EmailValidator.convertSpecialCharsToUnderscores(135) | TRYING TO CONVERT EMAIL ADD:nombreño�� 2015-03-26 16:11:21,085 [EM] DEBUG [pool-1-thread-10] EmailValidator.convertSpecialCharsToUnderscores(144) | CONVERT SUCCESSFUL: 2015-03-26 16:11:21,085 [EM] ERROR [pool-1-thread-10] AbstractMessageProcessor.handleAddressAndSendError(2099) | Invalid email address nombreño�� 2015-03-26 16:11:21,085 [EM] DEBUG [pool-1-thread-10] AbstractMessageProcessor.handleAddressAndSendError(2106) | SEND BOUNCE MESSAGE FOR DOC_ID: 6982 2015-03-26 16:11:21,085 [EM] DEBUG [pool-1-thread-10] AbstractMessageComposer.composeBounceMessage(598) | Compose bounce message for profile id 5050


UPDATED: October 18, 2017
Engineering  have tried this email id in a local environment with hmail server and it works fine.
When email address is there, message is successfully delivered and when email address is not there, status is currently updated as failure with Permanent Bounce.

Even in customer logs also, we could see, there was an error from mail server, and  e-messaging created manually bounce ( as per designed in emessaging ) and sent it to bounced mesasge to the mailbox emessaging. This was sent successfully. However, status was not updated correctly as we never received bounce message from customer mail box.

Conversion of special character is actually an internal mechanism as per design and it does not really create any problem and issue for bounce update or any other process.