# Email systems

Mautic marketing, company inboxes and transactional service notices.

Status: Mautic drafts prepared · Full delivery and mailbox monitoring pending

## Marketing: Mautic
ComputerUse uses Mautic for launch updates, newsletters and host recruitment. ComputerUse audiences and drafts are separate from the other businesses. Contacts must explicitly opt in; host signup is not marketing consent. Unsubscribe and suppression must be honored before any approved campaign send. Campaign preparation does not authorize sending.

## Company inboxes: Spacemail
`agent@computeruse.space`, `sales@computeruse.space` and `support@computeruse.space` are the planned company addresses. Agent inbox authentication is verified. Sales/support account type and credentials still need confirmation before all three can be completed in Thunderbird and ticket monitoring.

Spacemail uses `mail.spacemail.com`, IMAP port 993 with TLS and SMTP port 465 with TLS. Preserve its existing MX, SPF and DKIM records. See [Spacemail client setup](https://www.spaceship.com/knowledgebase/connect-spacemail-to-email-client/).

## Transactional delivery
Account verification/recovery, host assessment results, service alerts and other essential notices need a transactional delivery transport with a durable queue, idempotency, retries and bounce handling. Configure a separate authenticated sender subdomain such as `notify.computeruse.space`; use `support@computeruse.space` as Reply-To. A transactional provider can also supply Mautic's approved outbound transport, with separate sender reputation and suppression rules.

Stripe's own receipt and Connect notices should be used where appropriate to avoid duplicates. No bulk-mail server is being opened on the ThinkCentres or public application server.

## Remaining mail setup
DMARC was absent during verification. Begin with a TXT record at `_dmarc` containing `v=DMARC1; p=none;`, then assess actual sender alignment before stronger enforcement. Add a reporting destination only after that mailbox/service exists. Provider-specific sender records must come from the selected sending service; do not invent keys or publish a second SPF record at an existing hostname.