check for existing subscribers

I’ve just installed MailPoet – and that was first observation during the tests.
Question to the DEV Team – is there any solution of this problem ?

Hi @kayahnung and @xnhaze,

MailPoet will continue to send a confirmation email out when a subscription request form is filled out, even if that subscriber already exists in the MailPoet database already.

If the second subscription request is coming from a real person, they likely do not remember that they are already subscribed. Resending the confirmation email allows them to confirm their subscription and ensure they are subscribed, or re-subscribe if they have accidentally unsubscribed.

If the second subscription request is coming from a spam bot, then we recommend protecting your subscription request with captcha. If it is a MailPoet generated form, you can activate the built-in captcha functionality under MailPoet > Settings on the “Advanced” tab – this can be an explicit captcha or an invisible one via Google. We recommend doing this for ALL MailPoet users as blocking spam bots from using your sign-up form as an email testing ground can ensure that you do not hit our bounce or spam limits in our sending system.

Lastly, if the second subscription request is coming from an actual person but who is maliciously attempting to use your site to blast a specific other person with emails, our recommendation is to use a firewall plugin to block that malicious person’s IP address from accessing or using your site.

Hope that helps clear up the options here!

no, that helps not and there are no options… you should do that as an option, when installing the plugin, also you could ask if you use woo or not.

mailpoet creates 40 database tables and on top i should install another plugin…

@xnhaze: you can use the mailpoet_subscription_before_subscribe action, found here: https://kb.mailpoet.com/article/274-list-of-filters-and-actions

just do a database query on your own. if support was good, he would write it here. but it isnt…

Hi again @kayahnung,

Thanks for sharing your idea about writing a custom snippet to block the confirmation email in this case. While we do recommend continuing to send the confirmation email, for privacy and clarity reasons as discussed above, if you wish to make this change and are able to create such a snippet, please do share it here.

In the meantime, I was just wondering, what is the root cause of this question? That is, how often are you seeing the same email address submitted on your opt-in form, that the re-sending of confirmation emails becomes an issue?

You mentioned that some emails are re-subscribing “every day” and I’m wondering in what case this would happen. If your site is under attack by a spam bot, then this is a deeper issue that should be addressed, rather than just blocking the confirmation emails.

Or, if you have some sort of automated third party process that is subscribing your visitors over and over again automatically, it may be worth it to revisit this process to better understand why repeated subscribes for the same visitor would be required.

add_action('mailpoet_subscription_before_subscribe', function($data) {
$email = $data['email'];
global $wpdb;
$result = $wpdb->get_results("SELECT email, status FROM {your_database_prefix}_mailpoet_subscribers WHERE email = '$email' AND status != 'unconfirmed'");

if (count($result) > 0) {
throw new \MailPoet\UnexpectedValueException("E-Mail already exist!");
}
}, 10, 1);

sorry, but i don’t have time to discuss with you, why you should do a very basic feature, at least optional.

• This reply was modified 11 months, 2 weeks ago by kayahnung.
• This reply was modified 11 months, 2 weeks ago by kayahnung.
• This reply was modified 11 months, 2 weeks ago by kayahnung.