Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(short issue description) #4018

Closed
rank-p opened this issue Feb 15, 2024 · 2 comments
Closed

(short issue description) #4018

rank-p opened this issue Feb 15, 2024 · 2 comments
Assignees
Labels
bug This issue is a confirmed bug. closed-for-staleness p2 This is a standard priority issue response-requested Waiting on additional information or feedback. ses

Comments

@rank-p
Copy link

rank-p commented Feb 15, 2024

Describe the bug

Following code:

import boto3
ses = boto3.client("ses")

ses.send_email(
    Destination={
        "ToAddresses": ["test@example.com"],
         "BCCAddresses": ["test+1@example.com]
    }
    Message={"Body": { "Html": { "Charset": "UTF-8", "Data": "test", } }, 
                       "Subject": { "Charset": "UTF-8", "Data": "test", }},
    Source="test@whatever.com"
)

Expected Behavior

Sending email to "test@example.com" as recipient and "test+123@example.com" as BCC recipient.

Current Behavior

Only sending to "test@example.com"

Reproduction Steps

Run the above code with emails that are working

Possible Solution

Send to both emails

Additional Information/Context

Is this intended behavior? I can't find anything in the docs.

SDK version used

1.34.26

Environment details (OS name and version, etc.)

MacOs Sonoma 14.2.1

@rank-p rank-p added bug This issue is a confirmed bug. needs-triage This issue or PR still needs to be triaged. labels Feb 15, 2024
@RyanFitzSimmonsAK
Copy link
Contributor

@rank-p, thanks for reaching out. Could you clarify exactly what output you're getting when you run that sample code? Debug logs would beneficial here. You can get debug logs by adding boto3.set_stream_logger('') to the top of your script, and redacting any sensitive information. Thanks!

@RyanFitzSimmonsAK RyanFitzSimmonsAK self-assigned this Feb 21, 2024
@RyanFitzSimmonsAK RyanFitzSimmonsAK added response-requested Waiting on additional information or feedback. ses p3 This is a minor priority issue p2 This is a standard priority issue and removed needs-triage This issue or PR still needs to be triaged. p3 This is a minor priority issue labels Feb 21, 2024
Copy link

github-actions bot commented Mar 3, 2024

Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.

@github-actions github-actions bot added closing-soon This issue will automatically close in 4 days unless further comments are made. closed-for-staleness and removed closing-soon This issue will automatically close in 4 days unless further comments are made. labels Mar 3, 2024
@github-actions github-actions bot closed this as completed Mar 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a confirmed bug. closed-for-staleness p2 This is a standard priority issue response-requested Waiting on additional information or feedback. ses
Projects
None yet
Development

No branches or pull requests

2 participants