Was there ever an answer to this? Because I have the same problem. Other WordPress emails work fine in Hotmail, just not the ones produced by Wp-Comment-Mail.
Thanks 🙂
@lusans @aaceuk Thank you for the report. I’ve opened a new GitHub issue here for us to track this and figure out what’s going on with Hotmail: https://github.com/websharks/comment-mail/issues/259
@aaceuk Ah, thank you for sharing that. I’ve referenced that link in the GitHub issue; that should make it easier to fix this in the next release. 🙂
Hi, so is this getting fixed? …
I was contemplating to buy comment mail cause the feature set is great, but when I read here that the issue was found over a month ago and is still not fixed I’m stating to have doubts about whether buying it will be a wise decision.
I edited the PHP to change the Doctype and managed to fix it myself
Ok that’s great, will try that myself as well then.
But was just saying, if I’m going to buy a product I expect the devs to make sure their products works. And not fixing a serious issue like this over a month after the solution has been reported just seems very lackluster to me.
I mean what if there are other issues?
Can I rely on the devs to fix it?
Judging from how this issue has been handles so far I’d say no. Especially considering that this issue was first reported 6 months ago and nothing was done about it. It was a user (you) who found the issue…
But even then after someone pointed them to the exact solution, still no fix into the core files. I mean what’s up with that. I don’t mind paying for software, but if I do I do expect devs to be on top of bugs and especially a big issue like this.
@janpaul999 You can follow our development here: https://github.com/websharks/comment-mail/issues
Issues are ranked by priority. I took a closer look at the problem and the proposed solution mentioned above, and I’ve moved the issue to the Next Release milestone so that we can get this fixed for the next release. Thank you for your patience.
This issue has been fixed in the dev branch and the fix will go out with the next release: https://github.com/websharks/comment-mail/issues/259#issuecomment-219488455
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support