Neu bei MailBeez? Jetzt die Grundlagen lernen


11 minutes, 23 seconds

Antworten auf häufig gestellte Fragen

Generelle Fragen und Problem-Lösungen zu MailBeez

Kurze Antwort: So oft Sie wollen. Eine einfache, minimale MailBeez Installation wird 1x täglich den Versendeprozess über einen Cronjob ausführen. Sie können das System aber auch mehrfach ausfühen - Dank der integrierten Protokollierung besteht keine Riskio, dass Emails dopplet versendet werden.

Nein, jede Email wird genau 1x an jeden Kunden mit passenden Kriterien gesendet. Alle Emails werden in der Tabelle 'mailbeez_tracking' protokolliert.

Problem: Alle Fenster zeigen immer nur den Lade-Indikator - das System schein sich aufgehängt zu haben.

Lösung 1: Shop Konfiguration

Stellen Sie sicher, dass die URL des Shop-Frontends gleich mit der URL des Admin-Bereiches konfiguriert ist.

Lösung 2: Server Konfiguration

Bitten Sie Ihren Server-Admin um Prüfung der Einstellung X-Frame-Options. Wenn diese auf SAMEORIGIN gesetzt ist, wird die angeforderte Seite nicht in iframes angezeigt werden. Mehr Informationen hierzu finden Sie auf


Technisch gesehen sind die Popup-Fenster iframes. Der Webserver kann so konfiguriert sein, dass dieser dem Browser mitteilt nur dann Inhalte in iframes anzuzeigen, wenn diese von der absolut (auch http / https) identischen Domain geladen werden. Wenn die Admin-Seite über https, das Shop-Frontend aber über http geladen wird stimmen die Urls nicht überein.

Aus der Apache Dokumentation:

"The X-Frame-Options HTTP response header can be used to indicate whether or not a browser should be allowed to render a page in a frame or iframe. Sites can use this to avoid clickjacking attacks, by ensuring that their content is not embedded into other sites."

With sending high volume of Emails the risk of getting black-listes is increasing due to numerous reasons. We recommend to configure certified email sending service in the Email Engine Configuration.

MailBeez is installed on your server, and operated from within your store’s admin area, and as such, does not export any data to us, or indeed any 3rd party. In short, you keep your customer’s data in your system so there are no data protection issues.

Have a cup of tea and relax. Ahh, that’s better. Now, if for any reason your automatic installation fails, please remove the MailBeez configuration with this SQL statement:

DELETE FROM configuration WHERE configuration_key LIKE ‘MAILBEEZ_%’;

(in ZenCart you might need to add your DBPREFIX to the tablename configuration.)

Now you should see the initial install-button and can start from new.

When you insert a Stylesheet section in your templates these will break: Since the curly brakets  {…} are also used by the template system, you need to surround these with literal-tags like this:

     {  CSS... }

That tells the template system to ignore the lines in between

Your security token must only contain characters and numbers.

On Servers with Suhosin following settings can cause blank popups when previewing the templates:


MailBeez requires to use eval and gzinflate.

Also check your apache configuration: A configuration entry like Header set X-Frame-Options: 'sameorigin' can cause the browser not to show iframe contents from different domains (e.g. if your admin page is using a different domain name then your store)

You have a SEO add-on installed which is attempting to rewrite the URLs of the MailBeez system.


You need to add:


as exclusions to avoid rewriting these URLs.

You have a Security solution installed (e.g. osc_sec) which does not allow certain URL parameters, for example: ../.


You need to configure / adopt this solution to allow these parameters for /mailbeez.php page requests.

Almost all pop-ups call mailhive.php located in the store-root.


Please check your configuration located in includes/configure.php. The value for the constant DIR_FS_CATALOG must end with /, e.g. like define(‘DIR_FS_CATALOG’, ‘/home/yourshop/public_html/’);

Check if you have entered VALID email addresses for the “Copy To” and “Send Simulation to” fields.

Please check your “send copy to” and “send simulation to” email address. An invalid email address can stop the sending process.

This will very likely also happen with your order confirmation emails as well, and the reason that it does happen is not related to MailBeez. We would recommend to check the linefeed settings of your email system (usually found in your general store admin area – not MailBeez). See if a change to “LF” helps.

When your MailBeez is not sending any Emails at all, please check the email addresses you entered for “sent copy to” and “send simulation to”, you find both in MailBeez > Configuration.

Both email addresses must be valid – invalid email address can stop the sending of more emails

When campaigns just won’t start sending, the number of emails to generate might exhaust you servers memory. Please try to reduce the number of recipients by choosing a shorter time-frame in the module’s configuration.

Issues related to certificates

The domain you entered during the ordering process does not match with your server domain. Please to go Mailbeez > tab “about” and find the exact server domain in the red box and contact us to request a valid certificate

Make sure the cronjob calls mailhive using http, e.g.

wget[token]=run > /dev/null


lynx -dump[token]=run

Please request a free test certificate, making sure to provide us with the exact URL of the test server. Please to go Mailbeez > tab “about” and find the exact server domain in the red box.

You have a modification in your admin system which limits characters for configuration settings.

Solution: Remove the “maxlength=”110″ modification from function_draw_input_field() defined in “/includes/functions/html_output.php”

Issues related to osCommerce

It is very likely that you are using FWR Security, and if this is the case, please add catalog/mailhive.php as an exception and allow “/” in the URL.

Find the addon at, and in the documentation find the section called “Excluding Certain Files from Cleansing”. Follow the instructions and add mailhive.php like this:

// If you need to exclude a file from cleansing then you can add it like below  

Background: the Advanced modules use “/” in their URL, which is a valid character, but cleansed by FWR Security.

Please take a look at this thread for more information:

Issues related to ZenCart

When clicking on a link in an email sent by MailBeez (clicktracker active) following error appears:

PHP Fatal error: Class 'email' not found in (…)/mailhive/common/classes/oscommerce/emailMB.php on line 14


Remove the file


this file was included in one of the first 2.7 packages and is actually a bug so it MUST not be there.

Instead add the clicktracker code to /includes/application_top.php as described in MailBeez

Since MailBeez V2.7 the option “Override Zencart Email Template System” seem not to work anymore: The Email content generated by MailBeez is shown inside the Zencart Email Template.

There are different ways of solving this:

1. create your own template

create a template file


with you only fill with the variable:


  2. configure a SMTP Server

go to mailbeez > configuration > email system, switch to “SMTP” and configure a SMTP server – this will bypass the zencart email function.

  3. adopt the zencart code:

To make Zen Cart compatible with MailBeez V2.7 please perform a small change as you find on:

zencart checks if the mailcontent starts with a html-tag. With MailBeez V2.7 the htmlemailboilerplate template is introduced, which improves the visual presentation of the emails in different email clients. This template does not start with a html-tag.

The code change checks if the template CONTAINS a html-tag, which is a much more flexible approach.

In alternative you can configure MailBeez to sent through a SMTP server rather then using zencarts email function.

In MailBeez > configuration > email engine you need to switch to SMTP and configure an SMTP server of your choice. Then MailBeez is having 100% control on the email content sent out.

Quick Solution: configure a SMTP Email Server or sending through Newsletter2Go in MailBeez > Configuration > Email Engine. This will bypass the zencart email function and give MailBeez full control for sending emails

Mailbeez on Zen Cart relies on the Zen Cart mail engine which queries each email address to find out which format the recipient prefers (reverse look-up). If you think all emails are sent in TXT you probably have been testing MailBeez with an email address w/o an account in your Zen Cart installation.

If your Zen Cart is configured to send HTML emails, you need to set up a customer account with your CC-email / send-copy-to email and configure this account to receive emails in HTML format.

When using this email address for testing / CC you should now receive the HTML version.

Here’s a handy tutorial on how to configure Zen Cart to be able to send emails as HTML:

If you want to force Zen Cart to always send emails in HTML format, you can override the format detection with following changes:



if ($customers_email_format == '' && ADMIN_EXTRA_EMAIL_FORMAT == 'HTML' && in_array($module, array('newsletters', 'product_notification')) && isset($_SESSION['admin_id'])) {
       $customers_email_format = 'HTML';

insert afterwards

$customers_email_format = 'HTML';

that overrides the format to “always HTML”

When you choose not to override Zen Cart’s email template system, the body content of the MailBeez modules will be merged into Zen Cart’s default email template, located in:


and there you can remove the subject line.

Something goes wrong, but Zen Cart doesn’t show the PHP errors.

Have a look in your “/cache” directory for files starting with “myDebug…”, these files contain the PHP error Messages.

A typical reason is you inserted a Stylesheet section in your templates, since the curly brakets  {…} are also used by the template system, you need to surround these with “literal”-tags like this:

     {  CSS... }

Fehler gefunden? Möchten Sie diese Seite verbessern?   diese Seite bearbeiten