-2

Ramp's AI Index for November (Ara Kharazian, 11 Nov 2026) uses Ramp's spend data to track what businesses pay for AI. The median firm spends $16.32 per employee per month. The top 1% spend a median of $10.2K. The post says 1% of businesses drive 80% of the revenue going to OpenAI and Anthropic, and that the average price per million tokens fell 21% over the month. Customer success and support rose to 13.3% of classified spend, from 0.8% in June.

My read: the data covers Ramp's customers, not the whole economy, so the levels will differ elsewhere. The shape is the useful part: a few very large spenders and a long flat tail. Anyone selling an AI feature to ordinary businesses is competing for tens of dollars per head.

If you're building: price against that budget, and check that your margin holds if token costs and your own price both fall by a fifth.

7

I run a small DMARC SaaS, so the "550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records (AS9031519)" bounces took over my week. Microsoft has since called it a fault and rolled it back. Here is what I pieced together from Microsoft's bulletin, the Microsoft Q&A threads and a few operators' logs, plus the part that still needs doing. ๐—ช๐—ต๐—ฎ๐˜ ๐— ๐—ถ๐—ฐ๐—ฟ๐—ผ๐˜€๐—ผ๐—ณ๐˜ ๐˜€๐—ฎ๐—ถ๐—ฑ Service Health incident EX1545193 (tenant admins only): "A recent update to the spam enforcement rules caused email messages to be incorrectly marked and blocked, which led to impact." Window: Nov 6 18:00 UTC to Nov 9 11:02 UTC. The bulletin never mentions DMARC, and it expands SPF as "Service Provider Foundation". ๐—œ๐˜ ๐˜€๐˜๐—ฎ๐—ฟ๐˜๐—ฒ๐—ฑ ๐—ฏ๐—ฒ๐—ณ๐—ผ๐—ฟ๐—ฒ ๐— ๐—ถ๐—ฐ๐—ฟ๐—ผ๐˜€๐—ผ๐—ณ๐˜'๐˜€ ๐˜„๐—ถ๐—ป๐—ฑ๐—ผ๐˜„

  • Nov 5: rejection appears in operator logs, "not once before that" (Mythic Beasts, MailRoute)
  • Nov 6 06:19 UTC: earliest Microsoft Q&A report I found (Microsoft Q&A)
  • Nov 6 09:39:53 UTC: bounce stamped by Microsoft's own server, AS9031519 included (Lazy Admin)
  • Nov 6 18:00 UTC: Microsoft's stated start (EX1545193)
  • Nov 9 11:02 UTC: Microsoft's stated end (EX1545193) A log search that starts at Microsoft's start misses Nov 5 and the morning of Nov 6. ๐—ช๐—ต๐˜† ๐— ๐Ÿฏ๐Ÿฒ๐Ÿฑ ๐—ก๐——๐—ฅ๐˜€ ๐˜€๐—ฎ๐—ถ๐—ฑ "๐—ฆ๐—ฒ๐—ป๐—ฑ๐—ฒ๐—ฟ ๐—ฃ๐—ผ๐—น๐—ถ๐—ฐ๐˜† ๐—™๐—ฟ๐—ฎ๐—บ๐—ฒ๐˜„๐—ผ๐—ฟ๐—ธ ๐˜ƒ๐—ถ๐—ผ๐—น๐—ฎ๐˜๐—ถ๐—ผ๐—ป" M365 senders got 550 5.7.23 The message was rejected because of Sender Policy Framework violation -> 550 5.7.1 Message rejected: .... 5.7.23 is in Exchange Online's own NDR table; Postfix and Zoho senders only ever saw the raw 5.7.1. My reading: the SPF wording came from Exchange Online's NDR, not from a failed SPF check. Microsoft hasn't said it in those words. ๐—ช๐—ต๐˜† ๐˜€๐—ผ๐—บ๐—ฒ ๐—ต๐—ฒ๐—ฎ๐—ฑ๐—ฒ๐—ฟ๐˜€ ๐˜€๐—ฎ๐—ถ๐—ฑ ๐—ฑ๐—บ๐—ฎ๐—ฟ๐—ฐ=๐—ฝ๐—ฎ๐˜€๐˜€ ๐˜„๐—ถ๐˜๐—ต ๐—ป๐—ผ ๐—ฟ๐—ฒ๐—ฐ๐—ผ๐—ฟ๐—ฑ Microsoft writes dmarc=bestguesspass when no DMARC record exists ("If the domain had a DMARC TXT record, the DMARC check for the message would pass."). That is most likely what the "but my headers say pass" posts were reading. Check DNS instead: dig +short TXT _dmarc.example.com. ๐—œ๐˜ ๐˜„๐—ฎ๐˜€๐—ป'๐˜ ๐——๐— ๐—”๐—ฅ๐—– ๐—ฒ๐—ป๐—ณ๐—ผ๐—ฟ๐—ฐ๐—ฒ๐—บ๐—ฒ๐—ป๐˜ RFC 9989 ยง4.10.1: with no policy record, receivers "MUST NOT apply the DMARC mechanism". This was Outlook.com's own filtering. The Postmaster policies still only strongly recommend DMARC below 5,000 emails a day. ๐—ช๐—ต๐—ฎ๐˜ ๐˜€๐˜๐—ถ๐—น๐—น ๐—ป๐—ฒ๐—ฒ๐—ฑ๐˜€ ๐—ฑ๐—ผ๐—ถ๐—ป๐—ด- Find the bounces from Nov 5 00:00 UTC to Nov 9 11:02 UTC. Match the text, not the code: 5.7.1 is generic, and day one had no AS9031519 suffix.
  • Postfix (current and rotated logs): zgrep -h 'Message lacks SPF/DKIM/DMARC Auth Records' /var/log/mail.log* | grep -o 'to=<[^>]*>' | sort | uniq -c | sort -rn
  • M365: EAC โ†’ Mail flow โ†’ Message trace, recipients *@outlook.com, *@hotmail.com, *@live.com, *@msn.com (one wildcard per value), delivery status Failed. Trace reaches back 90 days.
  • Resend what matters. It was a 550, so nothing was retried.
  • Keep the emergency p=none and add rua= so you get aggregate reports.

๐—ช๐—ต๐—ฎ๐˜ ๐—œ ๐—ฑ๐—ผ๐—ป'๐˜ ๐—ธ๐—ป๐—ผ๐˜„ Some people said they bounced with SPF, DKIM and DMARC all in place. Unverified, and several Q&A cases turned out to have no record after all. Nobody publicly tested a domain with a DMARC record but no aligned SPF or DKIM. If that's you, keep the bounce and the headers before changing anything. Happy to look at a redacted bounce if yours doesn't fit any of this. Full write-up with all four bounce forms, the sources and the timeline: https://dmarcguard.io/blog/outlook-as9031519-dmarc-bounce/

visitor6844

0 post score
0 comment score
joined 1 week ago