@@ -92,18 +92,31 @@ DKIM may take 5–30 min to propagate. Other records refresh on |
| 92 | 92 | their own. The verification turns green once all records are |
| 93 | 93 | seen. Move on; come back to confirm. |
| 94 | 94 | |
| 95 | | -### A4. Generate Postmark API token |
| 95 | +### A4. Grab the Postmark API token |
| 96 | 96 | |
| 97 | | -After domain shows verified: |
| 97 | +You can do this immediately after creating the Server — domain |
| 98 | +verification is independent of token issuance. |
| 98 | 99 | |
| 99 | 100 | 1. Postmark → **Servers** → **shithub-prod** → **API Tokens** |
| 100 | 101 | tab. |
| 101 | 102 | 2. The default Server token shown there is what we'll use. |
| 102 | 103 | 3. **Copy it.** Keep in your password manager. |
| 103 | | -4. **Sender from:** decide on the From address. Convention: |
| 104 | | - `shithub <noreply@shithub.sh>`. Postmark will accept any |
| 105 | | - address on the verified domain; no per-address signature |
| 106 | | - needed. |
| 104 | + |
| 105 | +**About the From address.** Postmark has no "Sender From" field |
| 106 | +on the Server — the From string lives in the body of each API |
| 107 | +call. Once your domain is DKIM-verified (Phase A2), every |
| 108 | +address `*@shithub.sh` is authorized to send; no per-address |
| 109 | +"Sender Signature" needed. We pass the literal From string to |
| 110 | +Postmark via the inventory in Phase D3: |
| 111 | + |
| 112 | +``` |
| 113 | +email_from: shithub <noreply@shithub.sh> |
| 114 | +``` |
| 115 | + |
| 116 | +The `noreply@` mailbox doesn't need to actually exist as an |
| 117 | +inbox — replies to it bounce, which is the documented behavior |
| 118 | +(`docs/public/user/notifications.md` notes that reply-by-email |
| 119 | +isn't supported). |
| 107 | 120 | |
| 108 | 121 | ### A5. Set up DNS for the app + docs subdomains |
| 109 | 122 | |
