WordPress se recusa a enviar e-mails, "... seu host pode ter desativado a função de email ()"

Eutenho omesmoproblema com o Ubuntu Serverno Amazon EC2.i Obterproblema ao usar o link de redefinição de senhae também outroe-mail denotificaçãonãoestavamfuncionando.

Então,aquiestão as soluções quefuncionaramparamim.word-press used wp_mail()funçãoparaenviare-mail queprecisa PHPMailer classe que usou omailerphp armazenadoem /usr/sbin/sendmail.

Useesta simplesfunção PHPprimeiropara verificar o PHP Mail

 <?php
$to = "[email protected]";
$subject = "Test Email Function";
$txt = "Hello world!";
$headers = "From: [email protected]" . "\r\n" .
"CC: [email protected]";

mail($to,$subject,$txt,$headers);
?>
 

Seissonãoestiverfuncionando,vocêprecisainstalar o Php Mailer. Useeste comandoparainstalar o PHP Mailno Ubuntu Server.

 sudo apt-get install sendmail
 

Em seguida,verifique asfunções dee-mailpressionadaspelo Word.

I has same issue with Ubuntu server on Amazon EC2.I get issue while using reset password link and also other notification email were not working.

So here is solutions which worked for me.Word-press used wp_mail() function to send email which need PHPMailer class which used php mailer stored in /usr/sbin/sendmail.

Use this simple php function first to check php mail

<?php
$to = "[email protected]";
$subject = "Test Email Function";
$txt = "Hello world!";
$headers = "From: [email protected]" . "\r\n" .
"CC: [email protected]";

mail($to,$subject,$txt,$headers);
?>

If this is not working then you need to install php mailer. Use this command to install php mail on Ubuntu server.

sudo apt-get install sendmail

Then check word-press email functions.

Se a outragrande respostas aquinão ajudar,tente isto:

Euencontreiessemesmoproblemae nada queeupudesseencontrarem qualquer uma das sugestõespara o WordPress resolvidoparamim.

Entãoeu comecei ainvestigar sefosse aprópriainstalação do PHP que desabilitou afunção de correio,masnenhuma dessefuncionava. Tudoparecia quefoi configurado corretamente.

Todosessesproblemas começouparamim Uma vez queeu atualizeimeu servidorpara Centos 7,que usa o Selinux (segurança aprimorada Linux)e o queeu aprendinas últimas duas semanas com Selinux é que se algonãoestiverfuncionando,mas Tudoparece que deveriaestarfuncionando ... Isso significa que o Selinux é silenciosamentee secretamentebloqueando vocêem segundoplano.

e viola.

Se vocêestiverem execuçãoe OS que use o Selinux,bastaexecutar o seguinte comando como root:

setsebool -P httpd_can_sendmail=1

Existe uma configuração de segurança queimpedeinerentemente que o servidor do servidorenvieemail. Quando você viraesse switche diz ao Selinux,tudobem para o servidor Webenviare-mail,tudo de repentefunciona.

If the other great answers here don't help, try this:

I encountered this same problem and nothing I could find in any of the suggestions for WordPress solved it for me.

Then I started investigating if it was the PHP installation itself that had disabled the mail function, but none of that worked either. Everything looked like it was configured properly.

All of these problems started for me once I upgraded my server to CentOS 7 which uses SELinux (Security Enhanced Linux) and what I've learned in the last couple of weeks with SELinux is that if something isn't working, but everything looks like it should be working... that means SELinux is silently and secretly blocking you in the background.

And viola.

If you are running and OS that uses SELinux, just execute the following command as root:

setsebool -P httpd_can_sendmail=1

There is a security setting that inherently prevents the webserver from sending email. When you flip that switch and tell SELinux it's ok for the webserver to send email, everything suddenly works.

Eu corriparaisso hoje;Nomeu caso,a situação aconteceuporque o arquivo dos hosts do servidortem omesmonome de domínio doendereço dee-mail,apontandopara localhost.O registro MX apontapara um servidor diferente,mas o arquivo hostsestá substituindo DNSe WPestátentandoentregar oemail localmente.Removendo o domínio do arquivo hostse reiniciar o Sendmail resolveuesseproblema.

I ran into this today; in my case the situation happened because the server's hosts file has the same domain name of the email address, pointing to localhost. The mx record points to a different server, but the hosts file is overriding DNS and WP is trying to deliver the email locally. Removing the domain from the hosts file and restarting sendmail resolved this issue.

Eunão sei seisso ainda é relevantepara você ounão,mas desde quenão há respostaescolhida,eupensei queme deixetentar uma vez.

Na verdade,euenfreteiexatamente omesmoproblema desde quemeu host do OpenShift de repente cedeu hojee parou deenviare-mails. Escavando o códigoe o Codex,eu vimpara saber sobre afunção WP_MAIL ()e finalmente o Googleme levou aquie vi comoissopoderia ser substituído.

Building on @ RALF912's Resposta,modifiquei o script umpoucopara que o código use a API da Web do SendGrid.comparaenviare-mailsem vez dopadrão WordPress (queeupresumo:

 <?php

function sendgridmail($to, $subject, $message, $headers)
{
    $url = 'https://api.sendgrid.com/';
    //$user = 'yourUsername';
    //$pass = 'yourPassword';

    $params = array(
        'api_user'  => $user,
        'api_key'   => $pass,
        'to'        => $to,
        'subject'   => $subject,
        'html'      => '',
        'text'      => $message,
        'from'      => '[email protected]',
      );


    $request =  $url.'api/mail.send.json';

    // Generate curl request
    $session = curl_init($request);
    // Tell curl to use HTTP POST
    curl_setopt ($session, CURLOPT_POST, true);
    // Tell curl that this is the body of the POST
    curl_setopt ($session, CURLOPT_POSTFIELDS, $params);
    // Tell curl not to return headers, but do return the response
    curl_setopt($session, CURLOPT_HEADER, false);
    curl_setopt($session, CURLOPT_RETURNTRANSFER, true);

    // obtain response
    $response = curl_exec($session);
    curl_close($session);

    // print everything out
    //print_r($response);
}

//only for testing:
/*$to      = '[email protected]';
$subject = 'Testemail';
$message = 'It works!!';
echo 'To is: ' + $to;
#wp_mail( $to, $subject, $message, array() );
sendgridmail($to, $subject, $message, $headers);
print_r('Just sent!');*/

if (!function_exists('wp_mail')) {
    function wp_mail($to, $subject, $message, $headers = '', $attachments = array())
    {
        // use the PHP GnuPG library here to send mail.
        sendgridmail($to, $subject, $message, $headers);
    }
}

function plugin_init()
{
   /* $to      = '[email protected]';
    $subject = 'Testemail';
    $message = 'It works Live!';
    //echo 'To is: ' + $to;
    wp_mail( $to, $subject, $message, array() );
    //print_r('Just sent!');*/
}
 

e funcionou!

I don't know whether this is still relevant to you or not, but since there is no answer chosen, I thought let me give it a try once.

Actually, I had faced the exact same problem since my openshift host all of a suddenly gave way today and stopped sending mails. Digging through the code and codex, I came to know about the wp_mail() function and finally google led me here and I saw how it could be overridden.

Building on @Ralf912's answer, I modified the script a bit so that the code uses sendgrid.com's web api to send mails instead of wordpress default one (that I presume :

<?php

function sendgridmail($to, $subject, $message, $headers)
{
    $url = 'https://api.sendgrid.com/';
    //$user = 'yourUsername';
    //$pass = 'yourPassword';

    $params = array(
        'api_user'  => $user,
        'api_key'   => $pass,
        'to'        => $to,
        'subject'   => $subject,
        'html'      => '',
        'text'      => $message,
        'from'      => '[email protected]',
      );


    $request =  $url.'api/mail.send.json';

    // Generate curl request
    $session = curl_init($request);
    // Tell curl to use HTTP POST
    curl_setopt ($session, CURLOPT_POST, true);
    // Tell curl that this is the body of the POST
    curl_setopt ($session, CURLOPT_POSTFIELDS, $params);
    // Tell curl not to return headers, but do return the response
    curl_setopt($session, CURLOPT_HEADER, false);
    curl_setopt($session, CURLOPT_RETURNTRANSFER, true);

    // obtain response
    $response = curl_exec($session);
    curl_close($session);

    // print everything out
    //print_r($response);
}

//only for testing:
/*$to      = '[email protected]';
$subject = 'Testemail';
$message = 'It works!!';
echo 'To is: ' + $to;
#wp_mail( $to, $subject, $message, array() );
sendgridmail($to, $subject, $message, $headers);
print_r('Just sent!');*/

if (!function_exists('wp_mail')) {
    function wp_mail($to, $subject, $message, $headers = '', $attachments = array())
    {
        // use the PHP GnuPG library here to send mail.
        sendgridmail($to, $subject, $message, $headers);
    }
}

function plugin_init()
{
   /* $to      = '[email protected]';
    $subject = 'Testemail';
    $message = 'It works Live!';
    //echo 'To is: ' + $to;
    wp_mail( $to, $subject, $message, array() );
    //print_r('Just sent!');*/
}

And it worked!

Eutive omesmoerro,ambas asfunções (correioe wp_mail)funcionaram,maseu aindatinhaesseerroirritante. A correçãofoimuitofácil,mas demorei algumas horasparaencontrar omotivo. Entãoeu vou compartilhar aquiminha soluçãonoproblema quepode ser (oupodenão) omesmo com o seu.

Eutentei email ()funçãoe funcionou,mas quando você oteste,vocênãoespecifica o últimoparâmetro chamado 'parâmetros'no correio ()função. E o WP usaisso.

 @mail("[email protected]",$title,$body,$headers,"[email protected]");
 

Então,basicamente,esteparâmetro ("[email protected]") comflag "-f"fazemail () Função Verifique se oendereço dee-mail "[email protected]" listouna lista "Trusted Emails" .

Então,seissonão acontecer,ele retornafalse,o quefaz wp_mail () retornafalsose leva àmensagem deerro.

Então,a solução épedir a Hosterfazerissopor você,ou se vocêestiver usando o CPanel,basta adicionar conta dee-mailparaesteendereçoe eleirá adicioná-lo automaticamentena "lista confiável".

I had the same error, both functions(mail and wp_mail) worked, but I still had this annoying error. The fix was very easy, but it took me few hours to find the reason. So I will share here my solution on the problem which might be (or might not) the same with yours.

I tried mail() function and it worked, but when you test it you don't specify the last parameter called 'parameters' in mail() function. And WP does use it.

@mail("[email protected]",$title,$body,$headers,"[email protected]");

So, basically, this parameter ("[email protected]") with flag "-f" makes mail() function check if the email address "[email protected]" listed in the "trusted emails" list.

So if it doesn't, it returns false, which makes wp_mail() returns false and leads to the error message.

So, solution is to ask hoster to do this for you, or if you are using cPanel, just add email account for this address and it will automatically will add it into the "trusted list".

Chamado - IDS dee-mails registradosparaenviare-mails via scriptsie. (WordPress)

.
1. Login seu cPanel.
2. Vápara a seção dee-mail> Em seguida,cliqueem IDs dee-mail registrados.
3. então adicione ([email protected]) ou onde seu WordPress sediou.ou seja ([email protected]).Em seguida,envie algunsminutospara ativar aespera 15minutepara 1 hora,dependendo do seuprovedor de hospedagem,entãofuncionará.

it called -Manage Registered Email-Ids For Sending Mails via Scripts ie.(Wordpress)

1. Login your Cpanel.
2. Go to Email Section > then Click Registered Email IDs.
3. then add ([email protected]) or where your wordpress hosted. ie ([email protected]) . then submit, it takes few minute to activate wait 15minute to 1 hour depending to your hosting provider, then it will work.

Eutinhaesseerropara asidadese tenteitantas soluções quenãofuncionavam.Eutenho umainstalação do WordPresspersonalizadano AWS EC2.Primeiro Desligado Certifique-se de que o seu correio AWS SES seja ativadopormeio de suporte,eles devemestarnamesma região (oufechar)no SESe EC2. Eu usei o Google Suite (Gsuite)parae-mailpara receber/enviare-mail.

Certifique-se de que oemail dotesteenvieno AWS SESe Gsuite.

Instale o WordPress Plugin WP Mail SMTP,use a opção "Outro SMTP",pegue suas credenciais SMTP da AWS SES,é aqui quefiqueipreso.

Você deve ativar a caixa detick "SSL"para criptografia,isso altera aportapara 465paramim.Finalmentemeuteste dee-mailenviado de Worpdress com sucesso.

I had this error for ages and tried so many solutions that didn't work. I have a custom Wordpress install on AWS EC2. First off ensure your AWS SES mail is enabled through support, they must be in the same (or close) region in SES and EC2. I used Google suite(gsuite) for email for receiving/sending mail.

Make sure the test email sends in AWS SES and Gsuite.

Install the Wordpress plugin WP Mail SMTP, use the option "Other SMTP", grab your SMTP credentials from AWS SES, this is where I got stuck.

You must enable the tick box "SSL" for Encryption, this changes the port to 465 for me. At last my email test sent from Worpdress successfully.