Hi, to any other experiencing that problem, it was realted to the use of Amazon SES API and it is solved on latest amazon SES integration extension version.
Thank you André for your support testing out our patch.
Stefano.
ps: actually it is a but of the Amazon library (gulp!) solve double enconding the sender name… which technically has no meaning at all!