Troubleshooting Common G-Lock EasyMail Issues (Step-by-Step)
G-Lock EasyMail is a widely used desktop email marketing tool. When problems arise they’re usually configuration, connection, deliverability, or content related. Below are clear, step-by-step troubleshooting procedures for the most common issues so you can diagnose and fix them quickly.
1) EasyMail won’t send emails
Steps:
- Check SMTP settings — Confirm server, port, encryption (SSL/TLS), username, and password exactly match your provider’s instructions.
- Test connection — In EasyMail’s SMTP account settings click “Test” (or send a test message). Note any error message.
- Verify credentials — Try logging into the same SMTP account via webmail or an email client to confirm credentials work.
- Adjust port/encryption — Common combos: port 25 (no encryption), 465 (SSL), 587 (STARTTLS). Try the provider-recommended one.
- Check firewall/antivirus — Temporarily disable outbound filtering or add EasyMail to allowed apps. Ensure your network allows SMTP outbound on the chosen port.
- ISP blocking — Some ISPs block SMTP ports. Try using your email provider’s alternative SMTP or use their API (if supported).
- Account limits or blocks — Verify the SMTP account isn’t rate-limited, suspended, or requiring captcha/2FA. Contact provider support if needed.
2) Authentication errors (invalid login / authentication failed)
Steps:
- Re-enter credentials — Copy/paste username and password to avoid typos.
- Check authentication method — Some providers require OAuth or app-specific passwords (e.g., Gmail, Office365). Use app password if 2FA is enabled.
- Enable “Less secure apps” or set app password — If provider blocks basic auth, enable the allowed method or generate an app password.
- Clock skew — Ensure system date/time are correct; large clock differences can cause auth failures.
- Check provider status — Temporary outages can cause auth failures; check provider status page.
3) Messages arrive in spam or are blocked
Steps:
- Check IP/domain reputation — If you use your own SMTP server, check the server IP on blacklists (e.g., Spamhaus). If blacklisted, follow delisting procedures.
- Authenticate emails — Ensure SPF, DKIM, and DMARC are correctly configured for the sending domain.
- Reduce spammy content — Avoid excessive links, ALL CAPS, spam trigger words, and suspicious attachments. Use plain-text + HTML combination.
- Warm up sending IP/domain — Start with low volumes and gradually increase.
- Monitor bounces and complaints — Remove hard bounces and unsubscribes promptly to improve reputation.
- Test with seed lists — Send to multiple providers (Gmail, Yahoo, Outlook) and check placement; use tools for spam-score checks.
4) High bounce rate or many failed deliveries
Steps:
- Verify recipient list quality — Remove invalid addresses, duplicates, role accounts (postmaster, admin), and known disposable domains.
- Use double opt-in — Prevent bad addresses and bots from entering your list.
- Check bounce details — In EasyMail review bounce/error codes; categorize as hard or soft bounces and act accordingly (remove hard bounces).
- Throttle sending rate — Reduce concurrent connections and messages per minute to avoid provider throttling.
- Segment and retry soft bounces — Schedule retries for temporary failures, but stop after repeated soft bounces.
5) Broken images or missing links in sent emails
Steps:
- Use absolute URLs — Host images on a public HTTPS server and reference them with full URLs (https://…).
- Check image hosting — Ensure the hosting server allows hotlinking and is reachable; confirm HTTPS to avoid mixed-content blocking.
- Embed vs link — If embedding (inline attachments), confirm EasyMail’s settings include images in the message rather than referencing local paths.
- Verify link formatting — Ensure links include the correct protocol (https://) and aren’t truncated by editors.
- Test rendering — Send test messages to multiple clients (Gmail, Outlook, mobile) to check how images/links display.
6) Importing contacts fails or CSV errors
Steps:
- Use UTF-8 encoding — Save CSV as UTF-8 without BOM to prevent character issues.
- Match column headers — Ensure required headers (email, name) match EasyMail’s import expectations or map them during import.
- Remove invalid rows — Check for stray commas, unmatched quotes, or empty lines and clean the file.
- Limit file size — Split very large lists into smaller files if import times out.
- Check for duplicates — Use EasyMail’s dedupe options or pre-clean the CSV.
7) Project or message templates not saving
Steps:
- Check disk permissions — Ensure EasyMail has write access to its installation/data folders.
- Run as administrator — On Windows, run EasyMail with elevated privileges and retry saving.
- Check path length and characters — Avoid extremely long paths or special characters in file names.
- Backup and reinstall — Export existing templates if possible, then reinstall or repair the application.
8) Slow performance or high CPU usage
Steps:
- Limit concurrent tasks — Reduce simultaneous sends, connections, or database operations in settings.
- Increase memory / close other apps — Free system resources or upgrade RAM if needed.
- Optimize database — Compact or repair EasyMail’s database or move it to a faster drive (SSD).
- Update software — Ensure you’re on the latest EasyMail version with performance fixes.
9) Unexpected crashes or errors
Steps:
- Record error messages — Save logs and exact error text from EasyMail’s logs folder.
- Check for updates — Install the latest patch or version.
- Run on clean profile — Create a new EasyMail profile or fresh Windows user to test if corruption is profile-specific.
- Contact support with logs — Provide logs, steps to reproduce, and system info when contacting G-Lock support.
Quick troubleshooting checklist (summary)
- Verify SMTP credentials & test connection
- Confirm SPF/DKIM/DMARC and check blacklists
- Clean and validate recipient lists
- Host images/links on HTTPS public servers
- Limit send rate; respect provider limits
- Keep EasyMail and OS updated; check permissions
- Save logs and contact support when needed
If you want, tell me which specific error message or behavior you’re seeing and I’ll give the exact commands/setting values to change.
Leave a Reply