From 74f6230f639d31792f3244f5a179a8d2d6c46a6b Mon Sep 17 00:00:00 2001 From: Nikolai Emil Damm Date: Fri, 13 Nov 2026 21:19:56 +0100 Subject: [PATCH] fix(email): use SES's enum value for the MAIL FROM failure behaviour SES rejected the MAIL FROM attributes with a validation error: the API accepts only USE_DEFAULT_VALUE or REJECT_MESSAGE for behaviorOnMxFailure, and the provider passes the value through unchanged, so UseDefaultValue left the custom MAIL FROM domain unset. Use the API's own value. Part of devantler-tech/platform#5481. Co-Authored-By: Claude Opus 5.5 --- deploy/email/email-identity-mail-from-attributes.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/deploy/email/email-identity-mail-from-attributes.yaml b/deploy/email/email-identity-mail-from-attributes.yaml index 0c653f0..0a2d5e5 100644 --- a/deploy/email/email-identity-mail-from-attributes.yaml +++ b/deploy/email/email-identity-mail-from-attributes.yaml @@ -1,7 +1,7 @@ # A custom MAIL FROM domain for the company mail identity, so the envelope # sender is under the mailbox domain and SPF aligns for DMARC. Its MX and SPF # records are published by the DNS owner. Until they resolve, SES falls back to -# its own MAIL FROM domain (UseDefaultValue), so mail keeps flowing and DMARC +# its own MAIL FROM domain (USE_DEFAULT_VALUE), so mail keeps flowing and DMARC # still passes through the aligned DKIM signature. apiVersion: sesv2.aws.m.upbound.io/v1beta1 kind: EmailIdentityMailFromAttributes @@ -18,7 +18,7 @@ spec: forProvider: region: eu-central-1 mailFromDomain: bounce.devantler.tech - behaviorOnMxFailure: UseDefaultValue + behaviorOnMxFailure: USE_DEFAULT_VALUE providerConfigRef: kind: ProviderConfig name: default