Skip to content

Email Infrastructure Verification

Last verified: 2026-06-25.

This document records the launch email infrastructure check for Epic 6. It covers provider readiness. Backend delivery wiring is recorded separately in Email delivery implementation.

Decision

Use Amazon SES in eu-west-1 for MamNajem app transactional email.

Launch sender:

  • From address: [email protected]
  • From name: MamNajem
  • Sender domain: mamnajem.pl
  • Custom MAIL FROM domain: mail.mamnajem.pl

Verified Provider State

SES account:

  • ProductionAccessEnabled: true
  • SendingEnabled: true
  • EnforcementStatus: HEALTHY
  • 24-hour send quota: 50000
  • send rate: 14 messages/second
  • account-level suppression reasons: BOUNCE, COMPLAINT

Domain identity mamnajem.pl:

  • identity type: DOMAIN
  • VerifiedForSendingStatus: true
  • verification status: SUCCESS
  • DKIM signing: enabled
  • DKIM status: SUCCESS
  • MAIL FROM domain: mail.mamnajem.pl
  • MAIL FROM status: SUCCESS
  • MAIL FROM MX failure behavior: REJECT_MESSAGE

Sender address:

  • [email protected] is not configured as a separate SES EMAIL_ADDRESS identity.
  • That is acceptable for launch because the parent domain identity mamnajem.pl is verified and SES accepted a send from [email protected].

Test Send

A provider-level test send was completed through SES v2 from [email protected] to the AWS SES mailbox simulator success address.

Message id:

0102019efd9c2fe4-c52f2a59-c7c3-4146-a90d-6d38ee137418-000000

This verifies that the selected region, account, sender domain, and sender address can submit transactional email without emailing a real user.

Integration Runtime Contract

Current integration runtime uses /opt/mamnajem-integration/shared/app.env and has AWS credentials/region managed by the architecture deployment. No new SES secret is required for app email delivery.

EP6-T3 added non-secret backend config for the app email sender:

  • email delivery enabled flag;
  • SES region, default eu-west-1;
  • from address, [email protected];
  • from name, MamNajem;
  • optional test-recipient override for non-production manual checks.

The backend must use the normal AWS SDK credential chain already available in the integration runtime. Do not add static SES SMTP secrets for launch.

Bounce And Complaint Handling

Launch handling requirement:

  • keep SES account-level suppression enabled for BOUNCE and COMPLAINT;
  • log send attempts and provider message ids without full recipient email or email body;
  • treat SES send failure as notification-delivery failure, not as reason to roll back unrelated workflow state unless a specific workflow later requires hard email delivery;
  • add explicit SNS/webhook handling only if a later legal, account-security, or compliance email requires app-level bounce state.

Infrastructure Notes

The older CDK bootstrap stack name mamnajem-integration-ses-bootstrap is not present in CloudFormation. Do not rely on that stack existing during launch checks. The live SES identity and current architecture Terraform/CDK state are the source of truth.

Architecture origin/integration already configures Cognito auth email to use the same SES identity for customer sign-up and password reset email. App transactional email now uses the backend sender described in Email delivery implementation.