- Shipped
- September 16, 2026 at 6:03 PM UTC
- Author
- Kamo
- Commit
- a0f12dc
A campaign may name its own From on a verified domain; otherwise it goes as the org's bulk sender — which must itself be on a verified domain (saveSender refuses anything else). CampaignFrom picks the relay by that domain, because SPF is decided by the address a relay leaves from: an org's verified domain only through the shared org relay (47.181.8.86), KamoCRM's hello.kamocrm.com only through the platform relay (47.181.8.87), any other host for either, and an unverified From nowhere. The releaser takes the due recipient first, then a ready host its campaign may use; a campaign with none waits while the org's other campaigns go. Mail as an org's verified domain is DKIM-signed after its last saveChanges, with the session barred from converting it to 8bit on the way. New send blockers NO_SENDING_DOMAIN and FROM_DOMAIN_NOT_VERIFIED. Delivery reports count against the warm-up of the relay the campaign's From sent it through. KamoCRM's sending campaign is unaffected: noreply@hello.kamocrm.com is platform-managed, so it keeps leaving through .87, and the shared relay is switched off in KamoCRM's rotation.