Evaluate listmonk + Amazon SES for self-hosted newsletter

## Goal
Evaluate whether [listmonk](https://listmonk.app/) plus [Amazon SES](https://aws.amazon.com/ses/pricing/) can replace a Mailchimp-style newsletter workflow with a low-cost, self-hosted option.

## Context
- Expected volume: under 1,000 outbound emails per month.
- listmonk is a free/open source, self-hosted newsletter and mailing list manager with PostgreSQL as its main dependency.
- Amazon SES currently lists a flexible free tier of up to 3,000 message charges per month for the first 12 months after starting SES.
- SES outbound email pricing is currently $0.10 per 1,000 emails after free-tier coverage, with possible extra charges for outgoing mail data, attachments, and optional add-ons.
- If Virtual Deliverability Manager is enabled, each outbound email counts as two message charges, so 1,000 sends/month would still be 2,000 message charges before any inbound usage.

## Research tasks
- [ ] Confirm whether the AWS account qualifies for the current SES free tier or AWS Free Tier credits.
- [ ] Confirm whether SES production access/sandbox exit is required for the intended sender domain and list size.
- [ ] Estimate monthly cost at 1,000 outbound emails/month with and without SES add-ons.
- [ ] Verify domain requirements: SPF, DKIM, DMARC, MAIL FROM, bounce/complaint handling, and unsubscribe handling.
- [ ] Decide where listmonk would run and how PostgreSQL backups would be handled.
- [ ] Confirm import/export workflow for existing subscribers and Mailchimp-style forms.
- [ ] Validate that listmonk supports the needed templates, campaigns, analytics, and unsubscribe/list-management behavior.
- [ ] Document risks around deliverability, list hygiene, and legal/compliance requirements for bulk email.

## Acceptance criteria
- Clear yes/no recommendation on using listmonk + Amazon SES for this newsletter use case.
- Expected monthly cost for under 1,000 emails/month.
- Deployment outline with DNS records, backup plan, and rollback/export plan.
- Decision on whether to proceed with implementation or keep the current workflow.