How to deal with send errors

What are send errors?

The send errors are errors your email server is giving back to Mailster basically saying "I will not forward this message". Mailster retries that for some time but eventually stops which is what you see happening.

The cause can be a lot of things, e.g. hitting send limits (per hour/day) or sending email with content that the server does not like.

How can I fix this?

You need to find out what your email servers are telling Mailster. For this enable the "DEBUG" logging mode temporarily (described in the article in the troubleshooting section).
Then reset the emails not being forwarded or have new messages processed by Mailster. Wait for the error numbers to increase. Then look in the email archive in the backend, open the email in question, switch to the "Send Report" tab and look through the messages there. This should give you an indication what is going on.

Don't forget to switch back the logging level to "Normal" after this as otherwise your logging file will become very large very quickly.

Restoring Site Access / Error 500 / Blank Screen Issues

Fixing Error 500 Internal Server Error

Should you run into a situation where you either have an error 500 "Internal Server Error" or have your website only show a white screen go through the below steps to find out the cause.

What is this error 500?

A 500 error is an internal server error. It usually means that there's an error in the software running on the server or misconfiguration of the server.

The message is very generic and thus does not indicate which exact problem occurred.

How can I find out the root cause?

Depending on your webhoster there are different options available.

PHP Error Log

Many hosters provide the option to access PHP's error log through their web interface (e.g. cPanel). Look for entries like "Fatal Error".

Show Error in Browser

You can try to bump up the error reporting settings so that the real error message behind the generic message is shown.

Find the file configuration.php in the root folder of your website and open it with a text editor (we recommend Notepad++).

Now search for the this line:

public $error_reporting = 'default';

Change this to:

public $error_reporting = 'maximum';

Then save the file (do not forget to upload it via FTP if you are not working directly on the server) and then reload the site causing the error 500.

You might be able to see the error message in the browser then.

What should I do when this error is coming from Mailster?
What if you cannot login to the site?

In case Mailster is the component making trouble: don't worry, there is a way to login to the site by telling the Mailster plugin to stop it's execution.

The Email Forwarder plugin can be disabled by putting a file "no_mst_plg_exec.txt" or "no_mst_plg_exec" into the directory [joomla]/administrator/components/com_mailster. It is not important what is in the file, but the filename has to be exactly one of the both mentioned variants.

After creating the file you should be able to login to access your site's backend, again.

Then deactivate the Mailster mail (email forwarder) plugin in the Plugin Manager (putting the status to "disabled").

If you already know that this problem is due to a very large email sitting in the inbox: directly navigate to your mailing list's settings, in the "Tools" section and use the link to delete the first email from the inbox. After fixing the error do not forget to reactivate the mail plugin.

If the error is caused by something else do reach out to our support.

What if I cannot access FTP, how can I disable the email forwarder plugin?

If you cannot access the site via FTP you need to go directly into the database (e.g. using phpMyAdmin) and disable the Mailster Email Plugin there.

This can be done by opening the [prefix]_extensions table and looking for the "Mailster Email Forwarder" entry. This row has type set to "plugin", element set to "mailster" and folder set to "system". There you have to change the value of the "enabled" from 1 to 0.

How to create a log file

Debug Log File

Our support might require you to send the log file of Mailster. Usually Mailster only logs basic/sparse information. For troubleshooting needs we therefore require more information.

This is how this information can be generated:

  • go to Mailster > "Configuration" > increase "Logging Level" to "Maximum (Debug)"
    Mailster debug logging level
  • do the steps to reproduce the problem/error you want us to look at (e.g. send a test message that will reproduce the problem to your mailing list address)
  • only after you have reproduced the error (that might mean to wait 5 - 10 minutes until a mailing list message was retrieved and forwarded) put the "Logging Level" setting back to the former value
  • go to Joomla's log directory ("logs" / "log") and send us the file "mailster.log" and/or "mailster.log.php" (as a .zip archive if possible)

Log File Size

Please note that the "Maximum (Debug)" logging level produces a lot of information, therefore the log file gets big fairly quickly. Thus it is recommended to immediately switch it back to "Normal" when you have followed the steps above.

When the troubleshooting process is completed you can delete the log file.


Login / Sign-Up

We use cookies on our website. Some of them are essential for the operation of the site, while others help us to improve this site and the user experience (tracking cookies). You can decide for yourself whether you want to allow cookies or not. Please note that if you reject them, you may not be able to use all the functionalities of the site.