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

Unexpected error: bypass_list_management is mutually exclusive with bypass_bounce_management, bypass_spam_management and bypass_unsubscribe_management #395

Closed
tmacht opened this issue May 20, 2021 · 3 comments
Assignees
Labels
Enhancement New feature or request
Milestone

Comments

@tmacht
Copy link

tmacht commented May 20, 2021

When I pass the following mailSettings to SendToSingleRecipientAsync I get the error message "bypass_list_management is mutually exclusive with bypass_bounce_management, bypass_spam_management and bypass_unsubscribe_management.".

mailSettings: new MailSettings
{
    BypassSpamManagement = true
}

Any idea why? Because I think I should only get this error message if bypass_spam_management AND bypass_list_management were true, but bypass_list_management is false in my example.

@Jericho
Copy link
Owner

Jericho commented May 20, 2021

This is an interesting situation!!!!

SendGrid is complaining about the mere presence of bypass_list_management in the JSON payload despite the fact that its value is set to false.

I guess SendGrid expects us to omit bypass_list_management (and presumably also the other bypass_xxx_management) when their respective value is false.

I'll double check the docs in case I missed something but I don't remember reading anything about omitting certain settings in some scenarios.

@Jericho Jericho self-assigned this May 22, 2021
@Jericho Jericho added this to the 0.82.0 milestone May 22, 2021
@Jericho
Copy link
Owner

Jericho commented May 23, 2021

🎉 This issue has been resolved in version 0.82.0 🎉

The release is available on:

Your GitReleaseManager bot 📦🚀

@tmacht
Copy link
Author

tmacht commented May 25, 2021

Great, thanks, the error is gone.

@Jericho Jericho removed this from the 0.82.0 milestone Dec 26, 2021
@Jericho Jericho added Enhancement New feature or request and removed Improvement labels Dec 26, 2021
@Jericho Jericho added this to the 0.82.0 milestone Dec 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants