Closed NebulaBC closed 2 years ago
When I click on a incoming email I get the error Uncaught TypeError: e.threadCount is not a function
Can you confirm whether you have installed WebMail Lite from ZIP package, or from repository?
I also get the error POST https://mail.mysite.tld/?/Api/ when I try to send an email
That looks like a failure of trying to use a blocked SMTP port, it's not unusual for ISPs to block port 25 for spam-prevention reasons. Check webserver log as well as WebMail logs to find out what's causing that.
Also, is the JavaScript error reproduced reliably, or when certain conditions are met - for example, when opening a threaded mail?
And by the way, you can try disabling message threading either in account settings or in mail server options, and see if the issue occurs then.
That looks like a failure of trying to use a blocked SMTP port, it's not unusual for ISPs to block port 25 for spam-prevention reasons. Check webserver log as well as WebMail logs to find out what's causing that.
I am using Microsoft Azure, and have port 25 unblocked on the mail server. Do I need port 25 unblocked on the server hosting WebMail Lite too? (SMTP works with my mutt client.)
Can you confirm whether you have installed WebMail Lite from ZIP package, or from repository?
I am using the zip package.
Also, is the JavaScript error reproduced reliably, or when certain conditions are met - for example, when opening a threaded mail?
I have gotten an email from google and one from letsencrypt, and they both loaded fine, but any I sent to myself or sent to my email with my gmail account (plus an email I got from sendgrid) cause that error.
And by the way, you can try disabling message threading either in account settings or in mail server options, and see if the issue occurs then.
The error still occurs when I turn threading off.
Do I need port 25 unblocked on the server hosting WebMail Lite too? (SMTP works with my mutt client.)
Yes, WebMail needs to be able to access port 25 or 465 depending on which one you use to connect to SMTP server.
To check whether it's possible to establish connection to specific port from PHP you can try running this script. Extract the file from .ZIP archive, edit host and port information there, upload it onto the server where you have WebMail installed, and run it from the browser. If you connect to your mailserver via SSL (port 993 for IMAP, 465 for SMTP) you'll need this script instead.
Also, checking PHP error logs may still be needed.
The error still occurs when I turn threading off.
We've never encountered such an error. We do have a test installation of WebMail 9.2 running on Azure, works just fine. We suspect the issue might be specific to email account you use. Trying some other account on a different mail server could be worth a shot. If an issue is reliably reproduced on a specific email message, regardless of mail server used, you can save it as EML file (with some other email client) and submit it for examination.
Did you ever find a solution for this? I have the same issue, webmail lite 9.1.1, hMail 5.6.7. I tested both with and without SSL without any luck. Ran the connection test scripts successfully on all ports (25/143/587/993) Tried different accounts and domains, we only have one mailserver but with several domains.
We have an older webmail lite install that works just fine.
Thanks,
After having this issue for a long time I tried upgrading to the latest version of webmail lite 9.2 and it magically started to work just fine. Just to let anyone else that might find themselves with this issue know.
When I click on a incoming email I get the error
I also get the error
POST https://mail.mysite.tld/?/Api/
when I try to send an email