Customers keep telling me my order confirmations look fake. The From line says store+66295627989@shopifyemail.com and a few of them reported it as phishing.
That address is Shopify's fallback. When the domain behind your sender address cannot meet the Gmail and Yahoo authentication requirements, Shopify rewrites the From address to store+123@shopifyemail.com so the notification still gets delivered. It is not a compromise or a bug, it is the documented degraded mode, and it looks exactly like the kind of mismatch customers are trained to report.
The fix
Go to Settings > Notifications, click authenticate your domain, and publish every CNAME record in the modal. Then add a single TXT record at _dmarc with v=DMARC1; p=none. Allow up to 48 hours, then re-check the sender email section and send a real test order to confirm the From line.
I added all the CNAME records three days ago and Shopify still says my domain isn't authenticated.
Two things usually explain it. Shopify's documentation warns that the number of records may vary and that you must add every record displayed in the modal, so a partial set never validates. Separately, many DNS hosts append your domain to whatever you type in the host field, which turns a pasted full hostname into something like shopifyemail.mystore.com.mystore.com and silently breaks the lookup.
The fix
Re-open the authenticate your domain modal and compare it record for record against your DNS zone. Check whether your host wants the bare label or the full hostname, and resolve each CNAME to confirm it answers. If your domain is on Cloudflare, GoDaddy or IONOS, delete the manual records and use Shopify's automatic option instead.
We moved marketing to Klaviyo and authenticated a sending subdomain there, but our Shopify receipts still say via shopifyemail.com.
Those are two independent sending systems that happen to serve one brand. Klaviyo's branded sending domain authenticates Klaviyo's campaigns only. Shopify's order confirmations, shipping updates and refund notices never touch Klaviyo, and most of them cannot be turned off, so they keep going out under the sender email in Settings > Notifications with whatever authentication that domain has.
The fix
Authenticate the Shopify path as well: Settings > Notifications, authenticate your domain, publish the CNAMEs, and make sure one DMARC record covers the domain. Then test both paths separately, a Klaviyo campaign send and a real Shopify order, because a pass on one says nothing about the other.
I set up DMARC properly with strict alignment like the hardening guide said, and Shopify immediately stopped using my sender address.
Strict alignment demands an exact match between the From domain and the authenticated domain, with no subdomain tolerance. Shopify's documentation specifically says not to include adkim=s or aspf=s and to use adkim=r and aspf=r instead, because its sending path cannot satisfy strict alignment. When validation fails, the sender rewrite kicks in.
The fix
Edit the _dmarc TXT record to adkim=r and aspf=r, or drop both tags, since relaxed is the default when they are absent. Confirm you have exactly one DMARC TXT record, because duplicates fail validation on their own. Then re-check the sender email in Settings > Notifications.
My campaign reports say it sent to about 4,000 people but the segment I picked has 9,000. Where did the rest go?
Three filters run between your segment and the send. Smart delivery narrows the audience to engaged subscribers once a send list passes 1,000 subscribers. Bot filtering removes bot-generated signups, and List health removes anyone who bounced, unsubscribed or filed a spam complaint. The last two run on every send and cannot be turned off.
The fix
Open Apps > Messaging > Settings > Delivery to see which filters are active and toggle Smart delivery if you deliberately want the wider audience. Treat the gap as list quality data rather than a reporting error: a 9,000 person segment that resolves to 4,000 deliverable, engaged addresses is telling you where your complaint risk lives.