Easily transfer your Mailster license via the WordPress dashboard by navigating to “Newsletter” > “Account,” editing the email address, and confirming the new owner’s details. Alternatively, manage licenses directly from your Mailster account without WordPress access.
Freemius uses license keys for product access, ensuring support and automatic updates. After purchase, you’ll receive an email with your license key, and you can also find it on the Mailster Account page. Without a license, plugins can be used but won’t receive updates or support.
Gmail and Yahoo will enforce new sender authentication policies from February 1, 2024, targeting bulk senders—those emailing over 5,000 recipients daily. To combat spam, they require SPF, DKIM, and DMARC compliance, easy unsubscription options, and a spam complaint rate below 0.3%. Non-compliance may result in emails being marked as spam.
If you purchased an Envato license after October 1, 2022, it will expire in five months, halting automatic updates via WordPress. You can either upgrade your license for future updates or download the latest version from your Envato account. Your license remains valid for life per Envato’s terms.
If you experience issues sending your campaigns, verify your cron setup, as it’s crucial for successful delivery. Check for cron locks that may prevent duplicate emails and ensure your RSS feed URLs are accessible. For further assistance, consult our help article.
If your WordPress site redirects to /wp-admin/post.php, it may be due to misconfigured mod_security settings. This often stems from specific tags. To resolve the issue, contact your host, disable the module, or adjust the .htaccess file. Restart Apache after making changes for them to take effect.
To improve the chances of your Mailster campaigns landing in Gmail’s Primary Inbox, minimize images, favor plain text, limit external links, personalize sender names, and avoid excessive social links. Remember, content type and user preferences ultimately determine where emails are placed.
Mailster utilizes custom rewrite rules for user navigation and link processing on the newsletter homepage. Issues with links may arise if Permalinks are not configured. To enhance URL appearance, visit Settings > Permalink and click “Save Changes” to refresh the permalink structure. For detailed guidance, refer to the official documentation.
As of March 15, 2023, Mailster installation requires a valid purchase code for license activation. Common verification errors include invalid codes, already used licenses, and email mismatches. Ensure you accept the Terms of Service, and if issues persist, consider opening a support ticket.
Mailster offers unlimited subscribers, lists, forms, and campaigns, but server limits may affect performance. To optimize, maintain fewer subscribers, simplify custom fields, and reduce autoresponder complexity. For best results, use PHP 7.4+, at least 128MB memory, and consider a dedicated server or VPS.
Mailster forms use WordPress Nonces to prevent invalid submissions, but these can expire after 24 hours, often due to caching. If you encounter an error, consider disabling caching on pages with Mailster forms via the Advanced Settings. Alternatively, adjust nonce settings for internal forms to ensure functionality.
Mailster generates template screenshots on our server, but issues may arise. Thumbnails may not appear due to uncreated images, server restrictions, disabled options, broken HTML, or outdated versions. Ensure your server can connect, check settings, and update Mailster. You can also delete thumbnails to regenerate them.
The {post_image:X} tag in Mailster allows you to use a post’s featured image within your email campaigns. Unlike other tags, it must be placed within an tag. You can easily edit and insert images using the image picker, which provides automatic size adjustments.
Mailster’s email delivery relies on your sending server’s response, but a “success” message doesn’t guarantee inbox delivery. Emails may end up in spam, bounce back, or face delays. Use Mailster’s Email Health Check to assess deliverability and consider changing delivery methods or servers if issues persist.
The admin-ajax.php file is crucial for Mailster’s backend functions. If it’s blocked, issues may arise from plugin conflicts, host firewalls, .htaccess rules, or cross-domain mismatches. To resolve Ajax problems, check and adjust these elements or deactivate conflicting plugins.
SMTP errors can arise from various issues: mismatched sender and username, oversized messages, blacklisted receivers, or temporary server limits. To resolve, ensure your From address matches your login, reduce message size, and consider pausing campaigns. For Amazon SES, verify all email addresses used in your mailings.
Mailster adheres to WordPress Coding Standards, ensuring compatibility with compliant plugins and themes. If issues arise, test on the demo site first. Clear your cache, check for plugin conflicts, use the Health Check plugin, switch themes, and enable debugging to diagnose problems. Seek support if needed.
WordPress updates introduce new features and bug fixes. While plugins that worked previously will likely continue to function, unsupported versions may encounter errors. It’s essential to keep your site and plugins updated to avoid security vulnerabilities.
If your campaign statistics show no opens or clicks, try sending a test campaign to check links, ensure Mailster isn’t blocked by firewalls, and verify there’s no conflicting “mailster” folder on your server. Remember, subscribers may just be busy, so give it some time.
If you see an error about missing Mailster tables, visit your update page at https://yourdomain.com/wp-admin/admin.php?page=mailster_update (replace with your domain) to fix it. Alternatively, deactivate and reactivate the plugin to run a database check and create any missing campaigns.
If subscribers can’t confirm their Mailster subscription or encounter broken links, ensure your permalink structure is set correctly (Settings => Permalink => Save) and verify your server supports redirects. These steps will help resolve issues like “404 – Page not found” errors in your campaigns.
If you encounter an SMTP connection error, it’s likely due to your email service provider rejecting one of your email addresses. Ensure your “from,” “reply-to,” and “bounce” addresses match the authenticated SMTP email. Check DNS functionality and connectivity using commands like `dig` and `telnet`. If issues persist, contact your ISP for support.
Mailster requires a cron job to send campaigns. Check its status under Newsletter > Settings > Cron, where you can see the last trigger time and details. If the cron hasn’t run recently, verify your cron settings and ensure the secret hash hasn’t changed.
When sending campaigns, subscribers may be marked as errors due to invalid email addresses, non-existent domains, or server rejections. While these errors are often subscriber-based, Mailster may misclassify some as campaign-based. Common server rejections include reaching sending limits or blacklisted emails. For specifics, consult your email provider.
Occasionally, unsubscribe links in campaigns may lead to a “404 – Not Found” error. To resolve this, ensure Mailster is activated, permalinks are correctly set, and your server can handle redirects. If issues persist, consult your hosting provider for assistance.
Using GoDaddy’s email servers is possible but comes with restrictions. Limit your SMTP sends to 500 emails per account, ensure your from and reply-to addresses match your domain, and configure settings with the specified server details. Be mindful of additional limitations that may apply.
Campaigns may pause or fail to send emails due to SMTP authentication errors, incorrect credentials, or blocked ports. Ensure you’re using the correct email for authentication, check your sending limits, and consider changing your delivery method. If issues persist, pause and resume your campaign later.
Troubleshooting issues with saving templates in WordPress plugins like Mailster can be frustrating. Common causes include permission errors, plugin conflicts, cache problems, JavaScript errors, insufficient server resources, and database issues. Use tools like the Health Check Plugin for easier diagnosis, and follow systematic steps to resolve the problems effectively.
Mailster may display a “parsererror 200” when an Ajax request fails to return valid JSON, often due to third-party plugins or unexpected server outputs. To diagnose the issue, check the developer console for detailed error information.
The Browser Console is essential for tracking JavaScript errors and server-related information. Access it in Chrome (CTRL + SHIFT + J), Safari (CTRL + ALT + I), IE9 (F12), Firefox (CTRL + SHIFT + K), or Opera (CTRL + SHIFT + I) to troubleshoot effectively.