• This software will be banned on same german hoster because they do not have detailed options to controle sending limit per minute and no option to controle max. connections per minute. We migrate now to 4th mail server and all banned this plugin after using it.

    They give us the option: Controle sending limit and max. connection limit or stop sending via this mailserver.

    So we contact the support.
    1. We told @wpmanageninja that we have the most powerfull managed server by kinsta with 32 CPU and 64GB RAM.
    2. We told them that hoster do not find any issue on managed server.
    3. We told them that mail server provider contact us that our plugin send to much and open to many connections. And what is @fluentcrm is doing?

    1. We told @wpmanageninja that we have the most powerfull managed server by kinsta with 32 CPU and 64GB RAM. They wrote back: ou need to switch from shared hosting to managed server.
    -> Sorry what?! We talked about that we using powerfull managed server in all tickets and in every reply. Why you talking about shared hosting?

    2. We told them that hoster do not find any issue on managed server. They wrote back: You need to check the shared server log.
    -> Sorry, again: We have no shared hosting and we have no issue on webhosting/server. The support and our devs already checked this.

    At the same time we already told you that our mail server provider ping us and say: we have the issue on mail server. So why you still talk about hosting?

    3. We told them that mail server provider contact us that our plugin send to much and open to many connections. They wrote back: The max. connections per minute and sending speed is controled by CPU and RAM. You need to switch from shared hosting to a more powerfull server.
    -> Sorry, what?! If sending speed and max. connections is our problem and this is controled by CPU and RAM: Why we shoud have more CPU and more RAM? If we purchase more powerfull server we will have more sendings per minute and more max. connections per minute.

    So it will make our problem larger, not smaller.
    “From your description, it appears that your mail server has identified FluentCRM as a potential issue. They’ve provided you with some specific recommendations to limit the plugin’s usage: Max. 1000 emails per 10 minutes Max. 400 SSMTP connections per 10 minutes FluentCRM currently can not control at this speed you mentioned.

    The processing time of FluentCRM is largely dependent on the allocation of server resources such as the number of CPUs, total memory, server stacks, and MySQL configuration directives. The number of CPUs is particularly critical for processing tasks.” …
    “I see that you are using a shared hosting and this is pretty common in a shared environment to get banned to use resources when an email campaign is being sent and a lot of resources are consumed or utilized by an email marketing application like FluentCRM.”


    Its not funny anymore. This is why we cancled +20 licence this year and this is the next one after make all details public in our official youtube channel.

    This was not the very fast dramatic support ticket where we have feeling: They reply without to read the issue and understand the problem. I have no words for free plugins like this, and double not if you using paid solution and still stuck in the same issues.

    And this is not all. We have much more like this email support.
    For example we say in a ticket that we already disabled all plugins and enabled debug and the debug log was empty. And what the support reply? “You shoud disable all plugins and enable debug”….

    This is how you waste your time and my time.
    And this is how you will make problems larger, by losing time and do not work right now on solutions but playing email ping pong with informations you already send i very clear way and text.
    This is how you make problems larger, by increase server speed to send more emails per minutes instead make them slower. And this is how you talk about you have an managed server and they reply about you need to switch from shared hosting to a managed server… I have no words for so much fails in so short time.

    On the other hand: other free email sending plugins have option to controle mail industrie basics like sending speed and max connections.

    Users asking for it here many time, also in public support base but years later we are still here and talking about shared hosting when we say we have managed server.

Viewing 1 replies (of 1 total)
  • Plugin Support Ibrahim Sharif

    (@ibrahimsharif)

    Hello @tommy83,

    Thank you for sharing your feedback. We sincerely regret that your experience with FluentCRM Features and our support has not met your expectations due to a misunderstanding. Your concerns are important to us, and we take them seriously. Let me address your points in detail to provide clarity and actionable insights.

    1. Miscommunication about Hosting and Server Resources

    We understand your frustration regarding repeated mentions of shared hosting, despite your clarification about using a managed server. This was a miscommunication, and we apologize for the confusion.

    FluentCRM, being a WordPress plugin, relies on server resources for its operations. While it is designed to work across a variety of hosting environments, certain tasks, especially those involving high email-sending volumes, require robust configurations. It was also unclear initially how many sites were being hosted, which we later discussed and clarified.

    Our intention was to explore all potential causes systematically, including resource allocation or limits imposed by the hosting environment such as cPanel or the mail server, rather than to imply your setup was insufficient.

    2. On Email Sending and Connection Limits as requested

    You’ve raised a concerning point about needing controls for email sending speed and connection limits. You have been asking in our support for the limits to control as:

    1. Max. 1000 emails per 10 minutes.
    2. Max. 400 SMTP connections per 10 minutes.

    FluentCRM offers configurations such as the “Maximum Email Limit per Second,” aligned with many industry standards. With the lowest limit set at 4 per second, this would be equivalent to 240 emails per minute. See this screenshot for reference.

    One of the most recommended email services to use in the email marketing industry, AWS SES allows a maximum of email per second is 5 once production access is approved and this can be increased to even 200-300 per second based on the delivery health using their service. I have attached a screenshot for an example: See this screenshot

    However, we acknowledge that more granular controls, such as specifying the number of connections per minute, are currently not available directly in the plugin.

    Despite not being able to control the limits from the dashboard, I provided you with 2 snippets to have more control over the speed which in your first test showed it is lower than before but requires more adjustment for your case as you informed us. The snippets recommended are:

    add_filter('fluent_crm/email_limit_per_second', function($limit, $emailSettings, $handler) {
    return 1;
    });

    add_filter('fluent_crm/process_subscribers_per_request', function($limit) {
    return 5;
    });

    The control you mentioned—e.g., limiting 400 SMTP connections per 10 minutes—is typically handled at the mail server level rather than the plugin level as it’s a Network level task and mostly done by Mail Transfer Agent software like PowerMTA, Postal SMTP, and Email Delivery Services(Use their own custom MTA) etc. Implementing such granular controls within a PHP-based WordPress plugin is challenging due to the constraints of the WordPress environment. We encourage continued cooperation in the support ticket to explore additional solutions and try to achieve what you want.

    3. Clarifying Support Responses

    We strive to provide clear and precise support. However, we acknowledge that in this instance, some responses may not have addressed your concerns adequately, leading to frustration. This was not our intention, and we apologize if you felt unheard.

    I would like to strongly mention that we strive to provide the best support we have with our resources, and features available, and we always try to go beyond our support scope. Sometimes we require the system information, specifications, and debugging information to ask for them to understand the situation. We have already been discussing the issue further and you asked us to check more things which we are checking, and you will get the update in the ticket as well.

    We are committed to improving our support processes to ensure better clarity, consistency, and quicker resolutions in the future.

    4. Regarding Comparisons to Other Plugins

    You mentioned that other free plugins offer industry-standard controls. We appreciate your feedback and would love to explore specific examples of plugins offering these features for free.

    We found WP Mail SMTP has the first requested option in their Paid version to limit the overall emails but not the connection in a specific period. I would like to ask you to refer to any free plugin that has the feature of such limits for free that you mentioned.

    5. Our Commitment to Improvement

    Your feedback has been noted and shared with our development and support teams. We are actively working to enhance the plugin and support experience, including:

    • Exploring the feasibility of introducing more granular email and connection limits. We took a new feature request for providing more granular control and allowing users to set any limit from the dashboard as well.
    • Providing clearer support communication and better documentation to address common issues.

    Once again, we deeply regret the inconvenience caused and appreciate your patience. While we understand your decision, we remain open to assisting you in any way we can. Your insights help us grow, and we thank you for helping us strive toward a better product and support system.

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this review.