KamoCRM

An organization's NoReply domain is chosen by name, not by row order

FixEmailService
Se descapó
28 de septiembre de 2026 a las 5:46 UTC
Autor
Kamo
Compromit
e43179d

The campaign From, the transactional Reply-To and the provider default domain each took "the first root org_domains row". Organization.getDomains() is unordered, and the platform organization holds several root rows — kamocrm.com and localhost today (Yugabyte returns localhost FIRST), and kamouniverse.com now that **************** are platform doors. Whichever row the database happened to return decided the platform's NoReply domain, and a new row landing ahead of kamocrm.com would have moved it onto a domain nobody configured SPF for. OrgPrimaryDomain.rootRow picks the way every other hostname decision on the platform does (OrgApiHosts.preferred): active before inactive, registrable only, fewest labels, then alphabetical — kamocrm.com before kamouniverse.com, never localhost while a real domain exists. An organization with a single root domain gets exactly the row it got before.

Todos los cambios

Como lo que ves enviaste?

Todo llega a su espacio de trabajo por sí solo. Comience en el plan gratuito y lea esta página de nuevo en un mes.

Arranzar gratis para siempreVer Precios