Meow Mailer – Free SMTP, Everything Included vs Mikesoft TeamVault

For years, almost every WordPress site I ran ended up with a different plugin just to send email. I never really chose them. I installed whatever looked fine at the time, because honestly there is no clear winner. Most of them advertise features I don’t need, or hide the basics behind a paywall. At one point I simply wanted to see the emails my site had sent, or failed to send, and even that asked me to upgrade. That felt wrong. So I decided to build the simplest and most honest email plugin I could for WordPress. You pick one provider, set it up once, and every email your site sends goes through it. Everything is logged, so you always know what happened. No upsell maze, no ads, nothing basic locked away. That is Meow Mailer, and all of this is free: One provider, set up once. Pick the one you use and forget about it. No confusing multi provider routing. Import from your current SMTP plugin. Already set up with WP Mail SMTP or Easy WP SMTP? Meow Mailer notices and copies the provider, credentials and sender over in one click, so switching never means digging out your API keys again. A fallback for when it breaks, free. Name a second provider (or plain WordPress, which needs no setup) and it steps in only when the first one refuses an email. Your mail still goes out, the log tells you exactly who failed and why, and an alert lets you know your main provider needs a look. A real email log, free. Every email in a clean table with recipient, subject, provider and status (sent, failed, offline, pending). Click any row to read the full message, see the error, and resend it. Many plugins charge for this. Here it is free. Stays out of the way. Until you pick a provider, Meow Mailer doesn’t change how your email is sent, so activating it never breaks what already works. It still logs everything WordPress sends on its own, so you get the log from the moment you activate it. Never miss a failure. A dashboard warning appears when emails fail, so silent problems don’t go unnoticed. Dismiss it once you have had a look and it stays away until a new email fails. Failure alerts by email, free. Get told when your site stops being able to send, instead of finding out from a customer. The alert is sent by WordPress itself rather than your provider, so it still reaches you when the provider is the thing that broke. One alert per hour at most, however many emails fail. Alerts on Slack, Discord or Teams, free. Paste a webhook URL and the alerts and the weekly summary are posted to your chat as well, so finding out that email is broken never depends on email. Handy when you look after a lot of sites. Individual emails are never posted anywhere: this tells you about your site, not about the people it writes to. Weekly summary, free. A short email with what was sent, what failed, and the most common errors. Nothing is sent on a quiet week. Control WordPress’s own emails. Switch off the notifications WordPress sends by itself: new user registrations, password and email change confirmations, comment moderation, automatic update reports. Password resets are never affected, so nobody gets locked out. Background sending. Email goes out after the page has loaded, so your visitors never wait on the mail server. Offline mode. Capture every email in the log without sending. Perfect for staging and development. Filters and export. Filter by status and provider, search by subject or recipient, and export to CSV. Test and resend. Check your setup with an HTML or plain text test, and resend any logged message in one click. Auto prune. Keep logs forever, or delete anything older than 7, 30 or 90 days. Multisite ready. Set your provider up once on the main site and let every site of the network use it, or leave each site to configure its own. Email logs always stay per site. Light and private. No bloat, no tracking. Your credentials can live in wp-config.php instead of the database. What Meow Mailer will never do No open or click tracking. Other email plugins advertise it as a premium feature. It works by putting an invisible pixel in every message and rewriting every link to pass through a redirect, which means logging when your recipients read their mail and what they clicked. That is surveillance of the people your site writes to, it is personal data you then have to account for under the GDPR, and rewritten links make your email look more like spam, not less. Meow Mailer does not do it, and that is not a gap waiting to be filled in a Pro version. There is no Pro version. Supported providers Generic SMTP, Mailgun, Brevo, SendGrid, Amazon SES, Postmark, SMTP2GO, Mailjet, Resend, MailerSend, Maileroo, Gmail / Google Workspace (OAuth 2.0), Microsoft 365 / Outlook (OAuth 2.0), and Zoho Mail (OAuth 2.0). About Meow Apps Meow Mailer is part of the Meow Apps family of plugins, focused on doing one thing well with a clean, modern interface. External services Meow Mailer contacts an external service only after you choose and configure an email provider. Until then (the default “None”) and in “Offline” mode, it sends nothing anywhere. When you pick a provider, your outgoing email (recipients, subject, body, headers and attachments) and the credentials you entered are sent to that provider so it can be delivered, and only when your site actually sends an email. For Gmail, Microsoft 365 and Zoho Mail, Meow Mailer also contacts their OAuth servers when you connect and refresh your account. Nothing else is ever sent. You choose a single provider. Generic SMTP talks only to the server you configure. For the others, please review their terms and privacy policy: Mailgun (terms, privacy), Brevo (terms, privacy), SendGrid (terms, privacy), Amazon SES (terms, privacy), Postmark (terms, privacy), SMTP2GO (terms, privacy), Mailjet (terms, privacy), Resend (terms, privacy), MailerSend (terms and privacy), Maileroo (terms, privacy), Gmail (terms, privacy), Microsoft 365 (terms, privacy), and Zoho Mail (terms, privacy). Development Meow Mailer is open source. The full source, including the React code used to build the admin interface, lives on GitHub.

Mikesoft TeamVault adds a private document workspace inside the WordPress admin for teams, agencies, partners, and back-office operations that need controlled access to shared files. Instead of exposing documents through normal Media Library URLs, TeamVault keeps files in protected storage and delivers access through authenticated WordPress workflows. TeamVault is a strong fit for: internal company document areas agency-to-client document sharing managed from WordPress admin partner or vendor file exchanges that should stay private operational archives that must stay separate from the public Media Library What you can do with TeamVault: Upload files with drag and drop Organize documents in folders Rename, move, preview, download, and delete files from one interface Export a folder or the full library as ZIP Track uploads, downloads, moves, and deletions in the activity log Organize users into groups and grant per-folder permissions (view, upload, download, delete, manage) Allow preview-only access without download for sensitive documents Set per-user or per-group storage quotas Review access reports and export the activity log to CSV Send email notifications on key document events Why use TeamVault instead of the Media Library? It creates a dedicated private workspace for documents that should not mix with public website assets. It adds capability-based access control with an optional per-user whitelist. It keeps storage, maintenance, and export workflows focused on private documents instead of general media management. Privacy and access control: Files are stored outside the normal Media Library workflow Access is controlled by the manage_private_documents capability, which allows full workspace actions including upload, download, export, rename, move, and delete Optional per-folder permissions limit access to specific users or groups with granular actions and inheritance; folders with no rules keep the capability-based behavior, and administrators always retain full access Settings, groups, quotas, notifications, reports, activity logs, whitelist management, and maintenance tools require administrator-level manage_options access Optional whitelist mode adds a second authorization layer for selected users Cleanup and reindex tools help recover from migrations with missing binaries Key features: Private document storage separated from the Media Library workflow Capability-based access control with optional per-user whitelist mode TeamVault groups independent from WordPress roles Per-folder permissions with granular actions (view, upload, download, delete, manage) and inheritance Preview-only access that blocks download and ZIP export Per-user and per-group storage quotas enforced before upload Access reports by user, file, or folder, with CSV export of the activity log Email notifications for upload, download, delete, and access-denied events Folder create, rename, move, and delete operations Drag-and-drop uploads with upload validation and clear error messages Inline preview for supported files, including PDFs ZIP export for folders or the full library Activity logging for uploads, downloads, previews, moves, and deletions Maintenance tools for orphan cleanup and storage reindex Storage widget focused on the space used by TeamVault files Interface available in English, Italian, French, Spanish, and German, automatically matched to the WordPress language Support For end-user support, use the WordPress.org support forum for Mikesoft TeamVault. For direct contact, email [email protected].