Bug: aws-ses-v2-local allows empty ToAddress, but AWS SES does not

[DAcodedBEAT]

When using the AWS SESv2 Go SDK to send an email with an empty ToAddress, AWS SES returns the following error:

error: operation error SESv2: SendEmail, https response error StatusCode: 400, RequestID: <request-id>, BadRequestException: Invalid email address .

However, aws-ses-v2-local does not raise any errors in the same case, which creates a discrepancy between local testing and actual AWS behavior.

Expected Behavior:

aws-ses-v2-local should reject empty ToAddress values and return a validation error similar to what AWS SES would return.

Steps to Reproduce:

• Use the SESv2 SDK to send an email with an empty ToAddress.

• Observe the error from AWS.

• Perform the same action against aws-ses-v2-local and note that no error is returned.

TODO:
Check whether this issue applies only to ToAddress, or if AWS SES also rejects requests with no destination addresses set at all (i.e., ToAddresses, CcAddresses, and BccAddresses all empty or omitted).

[domdomegg]

Check whether this issue applies only to ToAddress, or if AWS SES also rejects requests with no destination addresses set at all (i.e., ToAddresses, CcAddresses, and BccAddresses all empty or omitted).

Once we figure this out, happy to update the behaviour in aws-ses-v2-local to match :)