The official Mailgun for WordPress plugin does not log emails locally. The settings that decide deliverability live in wp_options under the mailgun key: API key, region (US or EU), useAPI flag, override-from address and name, and the open/click/HTML-only tracking trio. The native settings page handles one site at a time and hides the region as an unlabelled dropdown.

SleekView Charts reads the option array on every blog, normalises the keys, and presents them as chart sources. A Number card pins blogs sending through Mailgun. A Pie shows the EU-vs-US region mix. A Bar ranks blogs by transport mode (API vs SMTP fallback). An Area card plots tracking-flag changes over time so a privacy-driven cleanup reads as a curve.

The from-address column gets a dedicated Pie too: addresses that match the verified sending domain versus those that do not. SPF and DKIM alignment becomes a slice rather than a per-site click hunt, which is the audit ops actually want.

Transactional email is the kind of system that fails in invisible, expensive ways. Mailgun for WordPress puts every consequential decision into a single option array on each blog: which datacenter your customer data crosses, whether your messages are tracked, whether the plugin sends through the modern HTTP API or the legacy SMTP fallback, and whether the from-address aligns with your verified sending domain. The native settings page handles one site at a time and hides the region as an unlabelled dropdown, so a multisite network ends up with subtle inconsistencies that nobody discovers until a deliverability dip or a GDPR audit.

The override-from problem is especially insidious: a marketing team sets a custom address three years ago, the domain's DKIM record evolves, and now every email from that subsite quietly lands in spam without an obvious culprit. The chart layer pulls the per-site config into one comparable surface so the cause and the symptom can finally meet in the same place.