Sending practices

smallrocksfloat.com

This domain belongs to a personal automation host operated by one person for their own use. It is not a product and has no customers, subscribers or mailing lists. All outbound mail is operational, machine-generated, and addressed to the operator's own verified addresses.

At a glance

Mail type: Transactional and operational only. No marketing, newsletters, or bulk mail.
Recipients: A fixed allowlist of two addresses, both belonging to the operator.
How obtained: Hard-coded in the infrastructure source. No sign-up form, no imported, rented or purchased addresses.
Volume: Occasional. No scheduled mail; on most days nothing is sent.
Third parties: None. Mail is never sent to anyone other than the operator.

What is sent

Operational notices

Short, machine-generated messages from the host's own automation to the operator: for example, the outcome of a task the operator emailed it. There is no scheduled digest, newsletter or recurring report, and nothing is sent unless the operator's own automation has something to report.

Authentication

The sending domain is aligned on all three mechanisms:

SPF — v=spf1 include:amazonses.com ~all
DKIM — Easy DKIM, three CNAME records published in the hosted zone, signing enabled.
DMARC — p=quarantine, with aggregate reports delivered to an address on this domain.

Bounces and complaints

Every recipient is an address the operator controls and has verified, so there is no audience to suppress and no possibility of a complaint from a stranger. If an address bounces or reports a message, it is removed from the allowlist in source control and the change is deployed; that stops all mail to it. Sending volume and reputation are monitored through the account's own metrics.

Unsubscribing

There is nothing to subscribe to. Removing an address from the allowlist stops every message to it permanently.

Inbound mail

The domain also receives mail at a dedicated subdomain, which the operator uses to send himself tasks. Messages are accepted only after passing SPF and DKIM and matching the same two-address allowlist; everything else is discarded.