Logging is an opt-in setting in SMTP Mailer. Enable it in the plugin settings so the log table accumulates rows, and configure a sensible retention so the table stays compact. SleekView reads whatever is there and charts it as the table grows.

Yes. Use the from_email or subject prefix as a chart filter to split the log into transactional sends and broadcasts. A Donut card on either column surfaces the mix and a Bar card ranks the top categories without changing the underlying SMTP Mailer configuration at all.

Yes. Aggregations run on indexed columns on the log table, so high-volume sites that send tens of thousands of messages per month render charts in under a second. Retention pruning by the plugin keeps the table sized for predictable chart performance over time.

If the plugin records the active SMTP provider in a column or header field, yes. SMTP Mailer is single-provider in the typical setup, so the provider dimension only matters on multi-host deployments where different sites or environments use different upstream SMTP servers configured per environment.

Yes. The error column on the log table can be normalised into categories (timeout, authentication, rate limit) at the dataset level and then grouped on a Bar card. That gives a clean breakdown of failure causes without manual parsing of raw SMTP responses by hand.

Yes. Each chart card exposes its underlying rows for export with the active filters applied. That gives a clean handoff to the hosting provider or SMTP relay vendor when an upstream investigation needs concrete data across a particular time range or status filter.

Charts reflect what SMTP Mailer logs as sent. If the host's outbound queue delays or drops messages downstream, that is a host-level issue rather than a chart-level issue. Correlate the host's queue metrics with the SleekView dashboard to spot the gap when one occurs.

Yes. SleekView reads the log table directly, so as long as SMTP Mailer keeps writing the same columns the dashboard continues to render. If a major update renames a column the dataset is updated once and every card on the dashboard picks up the change automatically.