✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView Kanban for WP Mail SMTP

SleekView Kanban reads WP Mail SMTP email logs straight from the WordPress database, groups them into delivery statuses like pending, sent, failed, and bounced, and lets your team drag rows across lanes to retry, archive, or escalate without ever leaving WordPress.

♾️ Lifetime License available

SleekView Kanban board for WP Mail SMTP

Why WP Mail SMTP logs need a kanban view

WP Mail SMTP stores every outbound email as a row in wp_wpmailsmtp_emails_log with a recipient, subject, mailer name, sent timestamp, and a status column that drives the rest of the delivery pipeline. The default email log screen shows these rows as a flat table sorted by sent time. That is fine for a few transactional emails per day, but quickly turns into noise once a site sends thousands of receipts, password resets, and form notifications across multiple mailers.

SleekView Kanban reads the same email log table and groups rows by the status field, which is the natural pipeline column for this plugin. Each card surfaces the recipient address, the subject line, the mailer used, and a relative time stamp so admins can scan a column without opening every log row. Failed and bounced messages sit in their own lanes instead of polluting the sent pile.

Dragging a card from one column to another writes the new status back to the same log row, so resend hooks, reporting, and WP Mail SMTP's own dashboard stay in sync. Bulk drags update every row in a single SQL transaction, so a queue of fifty failed sends can be moved into a retry lane in one sweep without a hundred separate page loads.

Workflow

From email log to kanban in four steps

1

Point SleekView at WP Mail SMTP

Install SleekView, then pick WP Mail SMTP from the data source picker. The plugin auto-detects the email log table, every custom field, and the mailer column. No queries to copy, no schema to map by hand, just confirm the log rows look right in the preview.
2

Pick status as the kanban column

Open the view config and set the group-by column to status. SleekView reads every distinct value WP Mail SMTP writes, including pending, sending, sent, failed, and bounced, then turns each one into a kanban lane with the row count next to the lane title.
3

Choose what shows on each card

Decide which fields appear on the front of each card. Most teams pick the recipient address, the subject, the mailer name, and the sent timestamp. Raw headers and error messages open in a side panel so the board stays scannable on a laptop.
4

Turn on drag-and-drop writes

Flip the drag-and-drop switch and SleekView starts writing status changes back to the email log on drop. Hook a retry handler to the failed lane and dragging a card out of failed automatically triggers wp_mail to retry the original send through the active SMTP mailer.

Sample board

Sample WP Mail SMTP delivery board

A live SleekView Kanban grouping WP Mail SMTP log rows by status, with cards showing recipient, subject line, and the mailer that handled the send.
Pending
47
Order receipt to anna@studio.co
mailer: SendLayer, queued 1m ago
Password reset to dev@team.io
mailer: SMTP, queued 2m ago
Form reply to leads@acme.com
mailer: Mailgun, queued 4m ago
Sending
6
Weekly digest to subs list
mailer: SendGrid, batch 3 of 14
Order shipped to maya@shop.com
mailer: SMTP, in flight
Invoice PDF to billing@firm.io
mailer: SendLayer, in flight
Sent
1,824
Welcome to noah@studio.co
mailer: SendLayer, 12m ago
Order receipt to ivy@craft.shop
mailer: SMTP, 18m ago
Password reset to ada@team.io
mailer: Mailgun, 22m ago
Failed
31
Order receipt to oldaddress@ex.co
bounce: 550 user unknown
Password reset to support@gone.io
auth: 535 invalid credentials
Form reply to leads@acme.com
rate: 421 try again later

Comparison

Default email log vs SleekView Kanban

Default WP Mail SMTP log

  • Flat email log table sorted by sent time with no grouping by delivery status
  • No visual sense of how many messages failed or are stuck in pending at a glance
  • Resending a failed email requires opening the row, scrolling, and clicking resend
  • Bulk actions limit you to delete and export with no card-style preview of payload
  • Mobile admins get the same dense WordPress log table with painful horizontal scroll

SleekView Kanban

  • Groups log rows by status with live row counts next to each column title
  • Drag a card out of failed to trigger a resend through the active WP Mail SMTP mailer
  • Card fronts surface recipient, subject, mailer name, and relative sent timestamp
  • Failed and bounced messages sit in their own lanes so the sent pile stays clean
  • Capability-aware drops respect WordPress roles so only admins can purge failed logs

Features

What SleekView Kanban gives you for WP Mail SMTP

Native WP Mail SMTP field support

SleekView reads every email log column directly, including recipient, subject, mailer name, headers, and the raw status message. Pick exactly which fields show on the card front, which open in a side panel, and which stay hidden but searchable from the filter bar above the board.

Drag to retry or archive

Every drop writes the new status value back to the email log table in a single update. Hook into the status change to retry the wp_mail call when a card leaves the failed lane, or to mark a row archived so it disappears from the active board without losing the underlying record.

Filter by mailer, recipient, or date

A filter bar above the board narrows lanes by mailer, recipient domain, or sent date range. Saved filters are per-user, so the dev clearing failed transactional emails keeps a focused board while the marketing team filters to digest sends from the same email log.

Audience

Three teams using the WP Mail SMTP kanban

Site admins triaging failures

Admins keep a board pinned to the failed lane and drag rows back into pending to retry the send. A clean failed pile means transactional emails never silently disappear for days.

DevOps watching deliverability

DevOps teams use the board grouped by status to spot deliverability dips early. A sudden surge in the bounced lane during a campaign is obvious on a kanban in a way no log table makes obvious.

Support teams checking sends

When a customer says they never got an email, support filters the board to that recipient and sees which lane the message landed in, without asking the admin to dig through the log.

The bigger picture

Why a kanban beats a list for email logs

Outbound email is a pipeline, not a log. WP Mail SMTP captures every send beautifully, but the default log table treats a delivered receipt and a hard bounce as visually identical rows separated by nothing more than a small status pill. That works when a site sends ten emails a day.

It falls apart at a thousand. A kanban board fixes the shape of the data, not just its presentation. Lanes give admins instant counts of how many messages are pending, sent, or failed right now, drag-and-drop turns retry actions into one gesture instead of a modal, and filters let each team focus on the mailer they own.

The same WP Mail SMTP data powers a different mental model, one that surfaces deliverability problems early instead of burying them under a stream of successful sends, and one that turns failed messages into actionable cards instead of forgotten rows.

Questions

Common questions about SleekView Kanban for WP Mail SMTP

SleekView reads WP Mail SMTP data directly from the WordPress database, so any version that writes to the email log table works. The free core and the Pro license both expose the same log schema, which means the kanban renders the same way regardless of which WP Mail SMTP plan you run.

 

By default a drop only updates the status column. You can extend it with a hook that calls wp_mail again with the stored payload when a card leaves the failed lane, and that is exactly how most teams wire it up. SleekView keeps the two actions separate so accidental drags never trigger a resend storm.

 

Yes. SleekView views are configuration only, so you can build one board filtered to transactional sends and another to marketing digests from the same email log. Each user picks their default board, and admins can pin shared boards to the WordPress sidebar for the whole ops team.

 

SleekView reads distinct status values on every load, so a new status shows up automatically as its own lane at the end of the board. You can drag it into the right position in the pipeline, assign a color, and decide which fields the lane's cards should surface, without rebuilding the view.

 

No. The drag handler updates the same status column that Pro reporting reads, so charts on the WP Mail SMTP dashboard refresh on the next page load and never drift from the live state of the kanban board in front of the admin moving the cards.

 

SleekView respects WordPress capabilities, so you can require manage_options or a custom capability before a card can leave the failed column. Support agents see the lane and can scroll it, but the drop target rejects their card with an inline message instead of silently triggering a resend.

 

Each lane uses a virtual scroller, so a column with thousands of cards still renders fast and stays responsive on a laptop. The lane header shows the exact count, and the filter bar at the top of the board narrows large lanes without resetting the scroll position or any cards already in motion.

 

SleekView reads and writes the existing WP Mail SMTP log tables and never adds shadow tables for email data. View configuration sits in its own small options table, so uninstalling SleekView leaves every log row, status, and reporting widget exactly where WP Mail SMTP wrote it.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView