Conversation
supportThanks for the great plugin! I’ve been using this plugin on dozens of sites since it first launch. There’s one feature that I’ve often wanted from your plugin that is provided in many similar plugins. I’d like a small enhancement to the Resend button on the Email Logs page to allow emails to be resent to alternate email addresses (for example, to myself or my client or the corrected email address) PR: https://github.com/WPManageNinja/fluent-smtp/pull/394 The use case Right now, clicking “Resend” next to a logged email immediately sends another copy to the original recipient. In practice, almost every time I want to resend a logged email, it’s because I want to look at the rendered email myself in my own inbox (or forward it to a teammate or client), not because I want to send the customer another copy. What the PR does It replaces the immediate-send behavior with a small Element UI dialog (matching the existing log-viewer styling) that lets the user pick where the resend should go: Original recipient(s) — current behavior, default option, so nothing changes for users who don’t read the dialog. My account email — the email address of the currently logged-in WordPress user. A different email address — a free-text field that accepts one or more comma-separated addresses, validated both client- and server-side. A few details worth calling out: Fully backwards compatible. The /logs/retry AJAX endpoint still works without the new recipients parameter — picking “Original recipient(s)” produces the exact same request as today. No DB schema changes, no new dependencies. The original log row’s To field is never modified — only status , updated_at , and resent_count advance, so the log stays an accurate audit record of the original send. When a custom recipient is used, cc and bcc headers are stripped from the resent message so it doesn’t accidentally also go to the original copy/blind-copy recipients. Recipients are sanitized with sanitize_email() and validated with is_email() server-side; bad input returns a translated 422. Bulk Resend and the Retry-on-failed action are intentionally untouched. Files changed app/Models/Logger.php (resendEmailFromLog accepts optional recipients) app/Http/Controllers/LoggerController.php (sanitize + forward recipients) resources/admin/Modules/Logger/ResendDialog.vue (new) resources/admin/Modules/Logger/Logs.vue (open dialog instead of immediate resend) resources/admin/Modules/Logger/LogViewer.vue (same change inside the viewer) I followed the conventions already in the codebase, same Element UI components used elsewhere ( el-dialog , el-radio-group , el-input ), $t() for all user-visible strings, and the existing sendSuccess / sendError controller helpers. Would you consider merging this feature into your plugin?
Hello @robertstaddon , Thank you so much for reaching out to us, and more importantly, thank you for being such a loyal user of FluentSMTP since our very early days! It is truly inspiring to hear that you have been utilizing our plugin across dozens of your sites. I want to sincerely thank you for putting in the time and effort to develop this feature and for submitting such a detailed Pull Request. The use case you described is incredibly practical; the ability to resend an email to an alternate address for review or forwarding is a fantastic enhancement that I’m sure many of our users would find invaluable. I have personally reviewed the details of your PR, and I must say, the implementation approach—keeping it backwards compatible, maintaining the integrity of the original audit logs, and utilizing our existing Element UI patterns—is excellent. I have taken the liberty of escalating your PR ( https://github.com/WPManageNinja/fluent-smtp/pull/394 ) directly to our core development team today. We appreciate the high quality of your contribution, and our developers will be reviewing it as part of our upcoming maintenance cycle. We genuinely value community-driven improvements like this, and we will keep you updated on the status of the merge as soon as our team completes their review. Thank you once again for your contribution to the FluentSMTP ecosystem!
Thank you @ibrahimsharif
Hello @robertstaddon , Thank you so much for reaching out to us, and more importantly, thank you for being such a loyal user of FluentSMTP since our very early days! It is truly inspiring to hear that you have been utilizing our plugin across dozens of your sites. I want to sincerely thank you for putting in the time and effort to develop this feature and for submitting such a detailed Pull Request. The use case you described is incredibly practical; the ability to resend an email to an alternate address for review or forwarding is a fantastic enhancement that I’m sure many of our users would find invaluable. I have personally reviewed the details of your PR, and I must say, the implementation approach—keeping it backwards compatible, maintaining the integrity of the original audit logs, and utilizing our existing Element UI patterns—is excellent. I have taken the liberty of escalating your PR ( https://github.com/WPManageNinja/fluent-smtp/pull/394 ) directly to our core development team today. We appreciate the high quality of your contribution, and our developers will be reviewing it as part of our upcoming maintenance cycle. We genuinely value community-driven improvements like this, and we will keep you updated on the status of the merge as soon as our team completes their review. Thank you once again for your contribution to the FluentSMTP ecosystem!
Thank you @ibrahimsharif