Falha no envio de e-mail

Há alguns meses estamos com problemas no envio dos e-mails encaminhados aos usuários - leitores, autores, avaliadores, editores e demais usuários - cadastrados no Portal de Periódicos da UFRN, fato esse que compromete todo o fluxo editorial do sistema.

Existe alguma forma de configuração de não receber e-mails de erro de envio ou alguma forma de corrigir esses e-mail, bem como, um filtro ou um direcionamento para o próprio e-mail da revista ao invés do e-mail do administrador do portal do OJS??

Application Version - e.g., OJS

Hi @periodicosufrn

If your users are not receiving emails, you should look in your mail server logs to determine the cause. If you’re using a domain for these emails that has no SPF record, for example, this can cause problems. Mail server logs are usually quite informative, but please also include your OJS mail configuration here (without disclosing passwords, please) so we can have a look and recommend things to try.


Hello @jnugent, thanks for replying.

To clarify, the OJS is able to send emails but we are facing problems for some users, sometimes we get these errors:

gmail-smtp-in.l.google.com[] said: 550-5.7.26 Unauthenticated email from yahoo.com is not accepted due to domain's 550-5.7.26 DMARC policy. Please contact the administrator of yahoo.com domain 550-5.7.26 if this was a legitimate mail.


[RCPT DOMAIN].mail.protection.outlook.com[] said: 550 5.4.1 Recipient address rejected: Access denied. AS(201806281) [MW2NAM10FT020.eop-nam10.prod.protection.outlook.com] (in reply to RCPT TO command)

We use a institutional SMTP server managed by university IT team and we’re in touch in order to solve possible issues.

Moreover, some recipients have old mail providers, disabled inboxes or exceeded quota and we would like to know if there is any way to redirect these errors to journal admin email instead of OJS admin team email addess.

Thanks in advance.

hi @andersonqueiroz

This is helpful. Are you using the force_default_envelope_sender config.inc.php option? If not, what happens is that OJS will send email using the user who wrote the email’s address in the From: header. This will cause problems because if you have a user with a yahoo.com address, and they send an email from your OJS installation, the receiver’s email server will think that your email is spam because your OJS server is not allowed to send email on behalf of Yahoo.com (the DMARC and SPF lookups fail).

At PKPPS we turn force_default_envelope_sender to On, and then set a default_envelope_sender value to an email address we control the DNS for, so we can correctly set the SPF record. By also turning force_dmarc_compliant_from On, OJS will put the user’s original address in the Reply-To header instead of the From header and errors like the one you are describing do not occur.


Hi @jnugent,

I’m going to set force_default_envelope_sender=On in order to avoid this unwanted behavior. I could not find the force_dmarc_compliant_from on config.inc.php. Have this been added in a newer OJS version? We are currently using

Again, thank you for your assistance.

Hi @andersonqueiroz

Those settings were added to 3.1.2 but perhaps just at a later version than

If you want to stick with 3.1.2 but want this setting it may be worth the trivial upgrade to


I will update OJS soon.

Thanks @jnugent!