[client-ses] Add support for encoded words (RFC 2047) in message headers

[kripod]

Is your feature request related to a problem? Please describe.

I came across this issue while trying to send an email to myself with my name included:

import { SendEmailCommand, SESv2Client } from "@aws-sdk/client-sesv2";

const sesClient = new SESv2Client({
  region: process.env.AWS_SES_REGION,
  credentials: {
    accessKeyId: process.env.AWS_SES_ACCESS_KEY_ID,
    secretAccessKey: process.env.AWS_SES_SECRET_ACCESS_KEY,
  },
});

await sesClient.send(
  new SendEmailCommand({
    FromEmailAddress: process.env.NOREPLY_EMAIL,
    Destination: { ToAddresses: ["Kristóf Poduszló <kripod@protonmail.com>"] },
    Content: {
      Simple: {
        Subject: { Data: "Test", Charset: "UTF-8" },
        Body: {
          Text: { Data: "Hello, world!", Charset: "UTF-8" },
        },
      },
    },
  }),
);

Unfortunately, my name came along as Krist=F3f_Poduszl=F3 instead of Kristóf Poduszló.

Describe the solution you'd like

I found out this is due to the fact that email header words aren’t encoded as described by RFC 2047.

A combination of two libraries out there – q-encoding combined with utf8.js – could solve this problem as follows:

import * as q from "q-encoding";
import * as utf8 from "utf8";

export function encodedWord(text: string) {
    return `=?utf-8?q?${q.encode(utf8.encode(text))}?=`;
}

await sesClient.send(
  new SendEmailCommand({
    FromEmailAddress: process.env.NOREPLY_EMAIL,
    Destination: {
      ToAddresses: [`${encodedWord("Kristóf Poduszló")} <kripod@protonmail.com>`],
    },
  }),
);

I think this should be done automatically, either by parsing the given addressed or providing a Content object of { Data: string | undefined, Charset?: string }, just like for the Subject and Body.Text.

[github-actions[bot]]

Greetings! We’re closing this issue because it has been open a long time and hasn’t been updated in a while and may not be getting the attention it deserves. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to comment or open a new issue.

[github-actions[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.