Why was my HTML attachment blocked or quarantined?

HTML attachments are a standard credential-phishing vector, so a lot of corporate mail filtering strips or quarantines them by policy — and the ones that get through often carry an interstitial warning before the recipient can open them. It isn't a setting on your side, and it's usually not worth trying to route around.

Why does my report look broken when I paste it into the email body?

Email clients are not browsers. Outlook on Windows renders with the Word engine — no flexbox, no grid, patchy positioning — and most clients strip ` `, external stylesheets and often ` ` styles entirely. A report built for a browser will not survive the paste.

What's the size limit for emailing a report?

Gmail caps attachments around 25 MB and many corporate Exchange setups are lower. A profiling or EDA report can be 40 MB on its own, so the mail bounces before any of the rendering problems get a chance to matter.

What should I send instead?

A link to the published report. It renders the same for every recipient, opens on a phone, has no size ceiling to speak of, and the recipients can comment on it in place rather than replying with a screenshot.

Can I send it to someone outside my company?

Yes — set the report's visibility to anyone-with-the-link, or add the external reviewer by name. You keep the ability to revoke it later, which an attachment sitting in someone's inbox never gives you.

Emailing an HTML report

The report is done, and the obvious move is to attach it. Three things tend to go wrong, in this order.

1. The attachment doesn't arrive

HTML attachments are one of the standard shapes of a phishing payload — a local page that renders a convincing sign-in form. Corporate mail filtering treats them accordingly: stripped, quarantined, or delivered behind a warning banner that trains the recipient not to click.

You find out about this hours later, from someone who assumed you never sent it.

2. It arrives, and it doesn't open

The rest of the failure modes from opening a local HTML file all apply: the report_files/ folder didn't come with it, fetch is blocked on the file:// origin, and on a phone the mail client won't hand the file to a browser at all.

3. So you paste the report into the body instead

This is worse in a more interesting way. Email clients are a decade or more behind browsers:

Outlook on Windows renders with the Word HTML engine. Flexbox and grid don't exist there; the layout collapses into stacked blocks.
<script> is stripped everywhere. Every interactive chart becomes an empty div.
External and <head> stylesheets are commonly removed; only inline styles reliably survive.
Dark mode in Apple Mail and Outlook recolors things you didn't ask it to recolor.

What the recipient sees is not what you rendered.

Send the link

Publish the report once and email its URL:

curl -X POST https://commareports.com/api/v1/reports \
  -H "Authorization: Bearer $COMMA_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d "$(jq -n --rawfile html report.html \
        '{title: "Q3 pipeline review", html: $html, visibility: "registered"}')"

Or drag the file — or the whole output folder — into the app and copy the link.

What changes:

It renders the same for everyone. A browser opens it, not a mail client, so the charts, the CSS and the interactivity are the ones you built.
Size stops mattering. Entry HTML up to 5 MB, assets up to 25 MB each and 250 MB per report — a 40 MB EDA report that can't be mailed at all publishes fine.
It opens on a phone, because it's a URL.
You can revoke it. An attachment is a copy you no longer control.
Replies land on the report, not in a thread of forwarded screenshots — anchored comments sit on the number someone is questioning.

Choosing who gets in

visibility is set at create time and changeable afterwards:

private — you (and the report's team), nobody else.
registered — anyone signed in to Comma, which is the right default for an internal report emailed to a distribution list.
public — anyone with the link, for the external case.

Named reviewers and domain gating are in sharing & access control.

When the report is recurring

If you're emailing the same report every week, publish it once and refresh it on a schedule instead. The link stays stable, each run appends a revision, and the weekly email becomes one sentence and a URL that's already current.

Try it

Comma is free — unlimited reports, unlimited commenters, unlimited revision history.

Publish a report and send the link →