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 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.
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.
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.