Ján Miklá?

I’m glad it worked for you, @sitenoob247. I’ve marked the thread as resolved.

For other folks with this issue, please look at this reply – the values are specific for @sitenoob247 website, so the queries won’t work exactly for you, but steps descriptions should help with debugging and fixing the issue.

@sitenoob247 just to make sure, when checking the value of AUTO_INCREMENT in SELECT AUTO_INCREMENT FROM information_schema.TABLES WHERE TABLE_SCHEMA = 'wordpress' AND TABLE_NAME = 'wp_mailpoet_newsletter_option_fields';
the 'wordpress' is the name of the database, and likely is different – so don’t forget to change it to whatever your database name is.

@sitenoob247 the missing auto increment is still the issue. On every plugin activation or update, we populate missing data. In case of wp_mailpoet_newsletter_option_fields, there should be 31 rows. When adding new row, we only specify the name and newsletter_type while the rest is filled automatically. However, since the ID column is set as PRIMARY, it needs to have unique values. The uniqueness is guaranteed by using AUTO_INCREMENT, which ensures, that the ID is always bigger than the previous one.

For some reason, the auto increment is not set on the ID column. My colleagues stated some usual reasons in previous replies (manual change, other plugins, backups, restores…), but that aside, please follow these steps, which I hope will fix that issue for you:

1. Backup wp_mailpoet_newsletter_option_fields table, as you’ll be altering it.
2. Deactivate MailPoet plugin.
3. Change the ID 0 to 14 – this is only to ensure that all IDs have non-zero integer values.
   UPDATE wp_mailpoet_newsletter_option_fields SET id = 14 WHERE id = 0;
4. Change the ID column to be auto-incremented.
   ALTER TABLE wp_mailpoet_newsletter_option_fields MODIFY id INT NOT NULL AUTO_INCREMENT;
5. Ensure that the AUTO_INCREMENT is set to 15.
   SELECT AUTO_INCREMENT FROM information_schema.TABLES WHERE TABLE_SCHEMA = 'wordpress' AND TABLE_NAME = 'wp_mailpoet_newsletter_option_fields';
6. Activate MailPoet plugin. This should run the Populator, which should insert remaining 17 options.
7. Check wp_mailpoet_newsletter_option_fields table, that it contains 31 rows.

@sitenoob247 one other thing, could you please run

SELECT AUTO_INCREMENT
FROM information_schema.TABLES
WHERE TABLE_SCHEMA = 'wordpress'
AND TABLE_NAME = 'wp_mailpoet_newsletter_option_fields';

to see what’s the AUTO_INCREMENT set to (wordpress is the database name, wp_mailpoet_newsletter_option_fields is table name)? It should be greater by one than the largest ID in that table. So, in my case, it’s 32 – this is the value to which the following ID will be automatically assigned. If that value is lower or not set, that will cause issues.

Hi @sitenoob247,

Could you please share the content of wp_mailpoet_newsletter_option_fields by running this query SELECT * FROM wp_mailpoet_newsletter_option_fields (note that wp_ is default WordPress table prefix and can differ in your case)? There are no private or personal data in this table, so it’s safe to share it here. It should look something like this:

Hi @barbarawebnauta,

Thank you for your feedback. We’re aware that Threads icon is missing (among others) and want to assure you, that updating these icons is on our roadmap. While I don’t have specific date when this will be addressed, we aim to have it done by the end of the year.

Hi @laconicsky,

The reason is that MailPoet’s CSS styles (responsible for hiding and showing these forms) are loaded only after the form is rendered on the page.

By default, these styles should be loaded in the page header before any content is rendered, ensuring that they are applied immediately (e.g., not showing the form sooner than configured).

If you use optimization plugins, it’s possible that they changed when those styles are loaded (e.g. to optimize page load), but also caused this issue.

Hi @kunstromy,

I’m sorry to hear about the disruption. On October 1, there was an issue processing your payment (you should have received an email to update your payment method), and while Stripe retried several times over the weekend, the subscription was automatically cancelled on October 8, after seven more attempts.

To continue using MailPoet, you’ll need to subscribe to a new plan. Please feel free to reach out if you need any help with this.

• This reply was modified 4 months ago by Ján Miklá?. Reason: Added note about email notification to update payment method

Hi @angeliquevancampen, could you please try it now? It can take up to 24 hours for DNS records to be changed everywhere, but I’ve checked now, and it looks like your domain is now verified.

Hi @bluedogranch. Unfortunately, the MailPoet cron can only be accessed from your server’s command line and won’t work from external services.

In MailPoet > Settings > Advanced > Newsletter task scheduler (cron), when you select Linux cron, there is a command that is used, which already include the argument that’s needed for it to function (the argument includes a path to your WordPress installation on your server). You can’t pass this argument from an external cron service.

Hi @pigi77, this error message comes from the PHPMailer library, which MailPoet uses when sending emails. As the KB article suggests, we normally see SMTP Error: data not accepted error when From address doesn’t match.

But the issue can also be in the email content and/or headers. If you see this error for the first time with a specific newsletter, I’d recommend trying sending a different one, with different content to a couple of subscribers (ideally those, who can’t receive the first one). If this new email is successfully sent, the issue might indeed be the content of the email, which the server rejects.

@brayhalv what task scheduler do you use? I can’t say for sure, but using Linux cron might solve that issue for you, as the cron would always run from the same domain. It’s more difficult to set up, but might be worth trying out.

@brayhalv I don’t have much knowledge about how WPML works, but if you have two domains, both of which can be used to send emails, I don’t know if there is a solution that won’t pause sending every time an email is sent from .de domain.

But it’s strange that it didn’t cause any problems at the beginning.

Is it possible, that it never tried sending an email from .de before?

@brayhalv that can very well be the case. What you described (activate on .com then use on .de) sounds like could cause issues like this. Unfortunately, MailPoet doesn’t officially support WPML, and we know there are different kinds of issues when it’s used, and this might just be another one.

@brayhalv The confirmation email is not sent because when MailPoet is set to send with the MailPoet Sending Service but the API key is invalid, it pauses the sending of all emails.

When you validate an API key, it uses the website’s URL to connect it to your MailPoet subscription. But MailPoet also regularly validates the API key via cron tasks in the background. It might be that the cron reports a different website, which would cause the sending to pause, as it would think that the API key is used on the wrong website.

Could you please check, what is your site_url() and home_url()?