brandtoss

Hello @treanormp

Thanks for reaching out.

This part is something that is influenced but not controlled by WP Mailster. It depends on the email client (GMail, Apple Mail, Outlook, …) used how the “Reply” and “Reply All” (some clients even have a dedicated “Reply to list” mode for discussion mailing lists) is utilized.
So it is different between your receivers depending on their email apps/software.

Thus the experience may vary and it is beyond the control of WP Mailster to force that client behaviour.
Please try combinations of Reply-To and FROM email address and see if you find a better fit.

Hello @sonaliprajapati
Thanks for reaching out .

Are you able to share the specific error message?
Maybe even the PHP error log (if you are able to turn on WP debugging)?

Feel free to reach out to [email protected] if you want to share this information in private.

Thanks!

Hi Michael,

thanks for reaching out.
Just released v1.8.19 – can you please update and report back if that fixes the problem?

Thanks!

Hello @wpfish

Please send me the following details to [email protected]

• Your Hoster (link to recommended IMAP settings, if you have it)
• The login credentials for a (test) email address / mailing list
• A screenshot of your IMAP settings

Thanks!

Hello @treanormp

It is pure speculation to say that you are / are not the culprit in any shared hosting environment.

Normally mailing list messages do not land you on blacklists, since in most cases all list members / recipients / participants have a high interest in receiving the emails and are unlikely to report/flag that incoming messages.

However involved email hosters can of course still do that.
So including unsubscribe links is still recommended and also to check on the amount of email you are allowed to send per second/minute/hour (hosters always have such limits) and use the WP Mailster settings for send throttling to make sure you are staying under that.

Thanks!

Hello @fabricelaborie
since I have not heard back in the last month, I am closing the issue for now.

Feel free to comment below if you want to continue the conversation.
Thanks!

Hello @fabricelaborie

Thanks for reaching out!

It is correct that WP Admin Audit executes maintenance task on a regular basis, scheduled via the cron event wp_admin_audit_maintenance that you have identified.

However: this does not touch your site’s maintenance mode. The code only cleans up database records no longer required, sends certain reminder emails, etc. So essentially behind the scenes stuff.

But maybe I am thinking wrong and you do not mean an actual maintenance mode, but see some error-style outage? Do you have any more infos like screenshots or (PHP / server) error logs?

Happy to hear we figured it out.

For anyone curious: the IONOS configuration settings are now included in our mail provider settings list.

Hi Michael.
The error “Could not instantiate mail function” is not really from WP Mailster.
If you put that into Google, you will get over a million results – about 99.999% not related to the plugin …

The message comes from the library PHPMailer that tries to send the email but cannot do so. Unfortunately, it is a very generic message.

Potential reasons include restrictions by your hoster. My first guess here was the FROM configuration.
If you say it is only sometimes happening, then my assumption would be that you send (sometimes) more emails per second/minute/hour than the hoster allows you to. Virtually all hosters have quotas, i.e. maximum allowed emails. Typically the hosters auto-block the account for a certain period of time before they can continue to send.
WP Mailster has therefore the option to enable send throttling to get around that.

You may sense a theme here: guessing.
If you want to find out what is what, ask the hoster for the reason. They should have logs about that.

The other thing to note is that most hosters typically enforce more restrictions if the standard mailer is used and not an authenticated SMTP connection.
Since you were not successful with SMTP: if you send me the credentials for a test email account via email ([email protected]), then I can help you with that.

Hope that helps.

Hi Michael / @mitfi

My guess is that your email provider (which may or may not be the same as your webhosting company) does not allow certain email headers to be set / overwritten.

Hence they are blocking your messages and you get that generic error message.

The most notorious one is the FROM email header where you may not be allowed to set the sender’s original address and may be stuck to using the mailing list address. And even for that setting: you mention using POST SMTP – be sure that you are using actual mailing list SMTP connection and not of some other of your email addresses.

Hope that helps.

Let me know how it goes!

Here is an addition to the documentation in your honor ??

https://wpmailster.com/doc-chapter/user-management/

Hello @herky-fishbine

Yes, of course.

Go to “WP Mailster” > “Users” > “Add New” (button at the top):

This will take you to the dialog to add a new, non-WP, i.e. WP Mailster user:

If you want to add WP Mailster users in bulk: please see our documentation for the CSV upload.

Hope that helps!

• This reply was modified 1 year, 2 months ago by brandtoss.

Hi @vinyloup

The error will be fixed in the next release.

However, it does not have anything todo with email delivery.
It is something that breaks when you browse the admin archived emails and/or queued emails view while there are emails with special characters (or emojis) in the subject line to be displayed.

Hi Vincent.

You see it within WP Mailster’s dashboard.

Hi @blwh

The behavior you describe is how it is at the moment.

Using groups for building sets of recipients is not compatible with unsubscriptions from (only selected) lists.

We have plans to build this feature, but it requires some significant code changes. Therefore, I cannot give you an ETA when this will be available.

Thanks!