Ibrahim Sharif

Hello @transit54,

It’s fantastic to hear that FluentSMTP has provided a solution that fits your needs perfectly, especially considering the scale of deployments across your low-volume sites. We understand the cost implications of paid plugins across multiple websites, and we’re thrilled that FluentSMTP offers a free alternative without compromising on functionality.

Knowing that FluentSMTP is saving you hundreds of dollars annually while still delivering a reliable and efficient SMTP solution makes our team incredibly happy. We’re constantly working to improve and expand FluentSMTP’s capabilities, and your feedback is invaluable in guiding our development efforts.

Thanks again for your kind words and for choosing FluentSMTP!

Hello @alanrogers,

It’s fantastic to know that FluentSMTP provided you with a solution without requiring a premium plugin. We strive to make our free version powerful and user-friendly, and your feedback validates that effort.

We’re also delighted to hear that Sujoy was able to quickly identify the need for the extra PHP extensions. We understand that these technical details can sometimes be tricky, and we’re committed to providing excellent support to guide our users through such situations. Enabling those PHP extensions (which are often missed in default server setups) is crucial for the plugin’s functionality and ensuring a smooth email-sending experience.

Knowing that you found our support “absolutely amazing,” especially considering you’re using the free version, is incredibly rewarding for our entire team. We believe that all our users deserve the best possible support, regardless of whether they’re using the free or premium version of FluentSMTP.

Thank you again for your positive review.

Hello @emgi2,

It truly brightens our day to hear that you’re amazed by the plugin, especially coming from a user of WP Mail SMTP.

We’re incredibly proud of FluentSMTP being a completely free and open-source solution. Our philosophy is to provide a powerful and accessible SMTP solution for everyone, without paywalls or hidden features. Knowing that you appreciate this aspect so much is incredibly rewarding.

If you ever have any questions or need assistance, please don’t hesitate to reach out.

Hello @markussss,

Thank you so much for your detailed suggestion and explanation of how displaying resend timestamps or linked log entries for resent emails would improve your troubleshooting workflow within FluentSMTP! We truly appreciate you taking the time to share this with us.

As of right now, FluentSMTP doesn’t natively display resend dates or link resent attempts to the original log entries. However, your feedback is incredibly valuable. We understand the importance of tracking resend attempts for effective email deliverability analysis, and how crucial it is to understand how FluentSMTP is operating.

I’ve forwarded your suggestion to our development team for their consideration. They’ll be evaluating the feasibility and impact of implementing such a feature. This usually involves a research and development phase, so while I can’t guarantee its immediate implementation, your suggestion is definitely on their radar.

Thanks again for your valuable input!

Hello @markussss,

Regarding your question about the fallback connection potentially doing more harm than good, it’s a valid concern. Here’s how FluentSMTP handles the fallback:

• Immediate Fallback:?The fallback connection is indeed attempted immediately after the main connection (SMTP) fails to establish a connection. This explains why you’re seeing PHP Mail() in the logs after the SMTP connection failure. It’s FluentSMTP’s automatic attempt to ensure email delivery.
• Log Interpretation:?The log entries you shared are very helpful. The?SMTP Error: Could not connect to SMTP host. Failed to connect to server?message combined with the fallback attempt indicates a potential problem preventing FluentSMTP from reaching your external SMTP server.

Based on the error and the behavior you’re seeing, the most likely cause is:

1. Firewall Interference:?A firewall on your hosting server might be blocking outgoing connections to your external SMTP server.
2. Incorrect Hostname:?The hostname you’ve configured for your SMTP server within FluentSMTP might be incorrect or unresolved.

• Retries & Cron:?FluentSMTP utilizes WordPress’s Cron system to handle retries. If an email fails to send, the plugin will automatically schedule a retry attempt.

Let me know if checking the firewall and hostname resolves the issue! If not, we can investigate further.

Hello @markussss,

We haven’t observed this issue on our end, so it’s likely something specific to your site’s environment is causing the problem. Based on your description, and considering that the filter used to work correctly, it’s possible a conflict is interfering with FluentSMTP’s ability to accurately identify and display failed emails.

To help us pinpoint the cause, could you please check your browser console for any errors while viewing the Email Logs page and specifically when switching to the “Failed” filter? These errors can give us valuable clues about what might be going wrong.

Here’s how to access the browser console:

1. Launch your browser (e.g., Google Chrome, Firefox, Safari, etc.).
2. Right-click on the webpage and choose “Inspect”, or use the shortcut “Ctrl + Shift + I” (Windows) or “Cmd + Option + J” (Mac).
3. This will open the Developer Tools window either at the bottom or the side of your screen.
4. Navigate to the “Console” tab within the Developer Tools window.

The console will display error messages, logs, and other pertinent information related to the webpage.

The issue you’re experiencing could stem from various factors, including your server configuration, hosting environment, the presence of a security plugin, or even firewall settings that might be interfering with FluentSMTP. The browser console output can help us narrow down these possibilities.

Please share the console output with us, and we’ll be happy to investigate further and offer specific recommendations. We’ll work with you to get this resolved!

Hello @markussss,

Thank you for reaching out and explaining the issue you’re experiencing with the Telegram bot after migrating your site from live to dev. I understand the confusion and time spent troubleshooting when the bot reports errors from the wrong domain.

As you’ve correctly observed, changing the site URL during the migration process (live to dev or dev to live) does indeed break the configured connection. This is because the connection details and site-specific information are stored in the database. Therefore, the Telegram bot is essentially still linked to the original domain after the migration.

Unfortunately, at this time, there isn’t an automated solution within FluentSMTP to automatically update the Telegram bot’s domain after a site migration. Reconnecting the bot after the migration, as you’ve discovered, is the current workaround.

If you have any further questions or need any help with the reconnection process, please don’t hesitate to ask.

Hello @xicoofficial,

Thank you so much for your kind words about FluentSMTP! We really appreciate you taking the time to let us know how you’re using the plugin and what features are important to you.

Regarding your inquiry about SES API V2 integration to bypass the 10MB email size limit, I can certainly log this as a feature request for potential development and implementation in future releases. I will be forwarding your request to the appropriate department for further consideration.

Thanks again for your valuable feedback!

Hello @katmac_aus,

Thanks for reaching out to us and providing detailed information about the issues you’re experiencing with FluentSMTP. I understand this is frustrating, especially since it was working well initially. The 422 “Unauthorized” error you’re seeing after re-authenticating points towards a problem with the token’s validity or the Client Secret’s configuration within your Azure environment.

Regarding the issues you have described for two different setups, I would like to primarily investigate on this problem, and for that, could you share the expiry of the token in the Azure while the Client Secret is being created?

This information will help us understand if the token is expiring sooner than expected, causing the repeated authentication issues.

Hello @squidg,

Based on your description and the troubleshooting steps you’ve already taken (reconnecting and creating a new Azure app), it seems like we need to investigate your specific website configuration and environment more closely.

Therefore, the best course of action is to create a support ticket on the WPManageNinja Support Portal (if you haven’t already done so – it sounds like you may have initiated this already). When creating the ticket, please include the following details to help us diagnose the problem efficiently:

• Your Website URL:?This allows us to take a quick look at the site’s overall configuration.
• FluentSMTP Settings:?A screenshot of your FluentSMTP settings page, particularly the Office 365 configuration, would be helpful. Please be sure to redact any sensitive information like passwords or client secrets!
• WordPress Version:?The version of WordPress you’re running.
• PHP Version:?The PHP version on your server.
• List of Active Plugins:?A list of all the active plugins on your site. This helps us identify potential conflicts.
• Debug Log (if available):?If FluentSMTP has generated any debug logs, please include them.
• Specific Examples:?Please provide a specific example of a test email you sent, including the “From” address, “To” address, and the approximate time you sent it. This helps us trace the email delivery.

Our experts on the support portal will be able to delve deeper into the logs, troubleshoot potential configuration issues, and offer tailored solutions based on your specific setup. We’ll work with you to get your email sending reliably through FluentSMTP!

We look forward to assisting you further on the support portal.

Hello @jodzeee,

To get a better understanding of what might be causing this, let’s enable WordPress debugging. This will create a log file where WordPress records any errors, warnings, or notices, which can provide clues as to why the “To” field isn’t being populated in the FluentSMTP logs for the New Order emails.

Here’s how you can enable debugging:

1. Access your?wp-config.php?file:?This file is located in the root directory of your WordPress installation. You can access it using an FTP client or the file manager provided by your hosting control panel.
2. Enable debugging:?Look for the line?define('WP_DEBUG', false);. Change?false?to?true. If the line doesn’t exist, add it.
3. Enable debug logging:?Add the following line immediately after the?WP_DEBUG?line:?define('WP_DEBUG_LOG', true);

Your wp-config.php file should now contain the following:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);

4. Save the changes:?Make sure to save the updated?wp-config.php?file.

Once debugging is enabled, WordPress will start logging errors to a file named debug.log located in the wp-content directory. The typical location of this file would be: /home/USER/public_html/wp-content/debug.log (replace USER with your actual username).

After enabling debugging, please trigger a new WooCommerce order to generate another New Order email. Then, access the debug.log file and look for any errors or warnings related to WooCommerce, FluentSMTP, or email sending. Please share the contents of the debug.log file (or any relevant excerpts) with me, and that will help me to identify the root cause of the problem.

Important: Remember to disable debugging once we’ve resolved the issue. You can do this by changing true back to false in the define('WP_DEBUG', true); line in your wp-config.php file. Keeping debugging enabled can expose sensitive information and lead to unnecessarily large log files.

Looking forward to hearing back from you with the debug log information!

Hello @hosseinkh,

To configure this, please navigate to the FluentSMTP Settings page. You will find the “Delete Logs” setting there. Simply set the number of days you want to retain logs. Any logs older than this specified period will be automatically deleted by the plugin.

I’ve also attached a screenshot for your reference: https://prnt.sc/ZgAZXj_U3aYD. This will visually guide you to the exact setting.

By configuring the “Delete Logs” setting appropriately, you can prevent your log file from growing too large and maintain optimal performance for your website.

Let me know if you have any further questions or run into any difficulties implementing this.

Hello @fahad88me,

Thank you so much for your valuable suggestion and for taking the time to explain how a MailBaby API integration would benefit you and other FluentSMTP users! We truly appreciate this feedback.

While direct integration with MailBaby’s API isn’t currently a feature within FluentSMTP, I’ve forwarded your suggestion to our development team for consideration. Adding new provider integrations involves thorough research, development, and testing to ensure a stable and reliable experience for everyone.

We appreciate you helping us make FluentSMTP even better!

Hello @morgan18,

It’s good to hear that you’re finding FluentSMTP perfectly connects with Microsoft Office 365 and that you recognize its value as the only FREE plugin offering this integration on the market. We put a lot of effort into making FluentSMTP both powerful and accessible, especially for users relying on Office 365. Knowing that it’s proving useful and fulfilling its intended purpose is incredibly rewarding.

If you ever have any questions, encounter any issues, or have any suggestions for future features, please don’t hesitate to reach out.

Hello @alexdeborba,

We’re thrilled to hear that you find FluentSMTP to be a powerful and reliable solution for ensuring email deliverability. It’s fantastic that you’re benefiting from the flexibility of multiple SMTP provider support and the dynamic email routing based on sender address. We designed these features with businesses like yours in mind, so it’s incredibly rewarding to see them making a positive impact.

We’re also glad you appreciate the detailed email logging and insights. We know how important it is to track email delivery and troubleshoot issues, so we’ve focused on making that process as effortless as possible.

Regarding your point about the lack of built-in email template customization, that’s definitely something we’ll be considering for future updates. We’re always looking for ways to improve FluentSMTP and provide even more value to our users. We appreciate the honest feedback!

It’s truly gratifying to know that you consider FluentSMTP a top-tier choice for WordPress users. Your recommendation means a lot to us.

Thank you again for your incredible support!