Blog Sections Open
Why WebLogin Password Reminders Fail While SMTP Still Works
A common legacy complaint is that eForm or custom SMTP mail works perfectly, but WebLogin password reminder emails fail with an error similar to Called Mail() without being connected . That usually means two different ma
A common legacy complaint is that eForm or custom SMTP mail works perfectly, but WebLogin password reminder emails fail with an error similar to Called Mail() without being connected. That usually means two different mail paths are being used.
Why This Happens
Many projects configure SMTP for one package or custom mail helper, but WebLogin still relies on the default PHP mail path or an older mail class configuration. As a result, one part of the site sends mail and another part fails.
Symptoms
- password reminder emails never arrive
- SMTP works in eForm or custom snippets
- WebLogin shows a transport or connection error
What to Review
- Check which mail class and transport WebLogin uses.
- Compare that with the working SMTP configuration used elsewhere on the site.
- Verify sender address, authentication, and port settings.
- Look for local overrides in snippets, config files, or plugins.
Practical Conclusion
Do not assume that “mail works on the site” means every package shares the same mail transport. In older Evolution setups, mail flows are often fragmented. The safest fix is to standardize transport settings and test reminder flows separately from contact forms.
Ordering Custom RewriteRules Correctly in .htaccess
Why custom RewriteRule directives can stop working when they are placed below the friendly URL block in Evolution CMS.
Keeping eForm Stable When SEO Strict URLs Are Enabled
A practical guide to eForm pages that stop sending mail or validating correctly when SEO Strict URLs and strict routing are involved.