Thread

Hi, I’ve made update to latest build EE (20090515) on my two websites and e-mail contact form stopped sending e-mails. Could you plase verify this issue. Thanks.

[Mod Edit: Moved to the Technical Support forum]

Gabriel:

Can you please see this KB Entry and let us know if any of the tips help.

Thanks,

-greg

Moderator’s note: Split from this thread.

Hi, I’ve got the same problem. I can’t received emails generated by EE. Contact form not working and from Communicate tab I received error:

Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.

But, when I built test form on my server based on PHP using mail() function independent from EE, the e-mails was delivered.

What’s wrong??

Let’s get to this methodically: What version and build of EE are you using? Is this a new problem, appearing all of a sudden? Has it worked before? If so, what happened to make it stop?

Hi Ingmar!

As I wrote in the first post. I’ve upgraded to version 1.6.7 (20090515).

Full story: I’ve built my two websites time ago. Everything still worked fine. I still made regular upgrade of the system to latest released build.

Last weekend I’ve made upgrade both websites on build 20090515. They are runing on same webhostng company so configurations are the same. I was tested contact form on the website after upgrade and I find that they are not working. I tried sent email from Comunication tab and I received error:

Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.

So I tried re-configure settings and choose SMTP function. Now, e-mails from Communicate tab was delivered. Then I find that contact form on the website usig mail() function, and reconfigurated EE settings on SMTP can’t help. So I built test e-mail form with simple PHP mail() function and I was surprised, e-mails was sent! So now I don’t know. The EE tells me about not allowing mail() on the webhosting but mail() working fine outside of EE!
I wrote to webhosting compamny about allowing mail() but I’m sure they send me answer: mail() was always allowed.

Edit: Im just made test instalation of the latest EE on other webhosting and contact form working well.

As I wrote in the first post. I’ve upgraded to version 1.6.7 (20090515).

Very good. These were two separate threads I merged, so this piece of info got lost somewhere in the process.

I was tested contact form on the website after upgrade and I find that they are not working.

Are you quite sure it was the latest build update that broke it? Or could it have been some other change, perhaps to the server, at some point in the past?

Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.

That does sound like a server configuration issue. Can you please turn on Email debugging, and let us know what error messages, if any, you are getting?

I wrote to webhosting compamny about allowing mail() but I’m sure they send me answer: mail() was always allowed.

By all means, do let us know if and when they do get back to you.

I received reply from webhosting company. The mail() function was allowed. But the EE still can’t send emails, Communication tab still tells “Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.”

So, have you turned on email debugging? It should give us a little more info apart from “Unable to send email using PHP mail()”. That said, if using an SMTP works and is an option for you, I’d simply go down that route.

Hi I’m back with this problem. I received from webhosting support this record from server log:

Jun  2 23:06:31 localhost suhosin[21525]: ALERT - mail() - double newline in headers, possible injection, mail dropped (attacker
'xxx.xxx.xxx.xxx', file '/home/mywebsite.com/admin/core/core.email.php', line 1293)

I think, it’s possible EE bug and I’m surprised I’m the only one.

Is there any chance you have safe_mode turned on?

Hi Sue. I had problems with writing files on the server by Entry Gallery module (saving templates to files as well) so I asked support to turn off safe_mode. Is it possible connection with my issue?

Safe_mode needs to be turned off, for sure.

Actually, this looks like a special version of PHP, using “suhosin”. This is a patch, so I’m not sure if it’s feasible to simply turn it off.