We upgraded to OJS version 3.5.0.1 mid November but have only recently noticed that emails have not been getting sent out to registered uses. There were no server changes as we have been running OJS since version 3.1 basically using the same config file. There are no new messages in the email log table and the server has not been changed.
We updated to version 3.5.0.3 after reading other users experiencing similar problems. SMTP is configured correctly because we are able to send test emails via a python script from the server and the dmarc compliant variables are set and configured.
Is there another setting that I should be looking for that will allow emails to be sent again in version 3.5.0.3? I’m pretty much at the end of possibilities here because the email system in 3.3 worked and now it doesn’t and I am getting no errors in the server logs.
The reports that we’ve had on 3.5.0-3 are that the changes since 3.5.0-1 have resolved the DMARC compliance issue that users were facing. Are any emails getting through, i.e. test emails sent from the Journal Manager’s Users & Roles area?
Regards,
Alec Smecher
Public Knowledge Project Team
Thanks for the reply. There are no emails that are getting through. They are being logged in the email_log table and the notification screens are being displayed letting the user know that the process was complete but no email notifications are being sent.
Did you update the config.inc.php with new entries that were added to the configuration template since your old release? Those are documented in the release notes (docs/release/) and the various release notebooks (3.3, 3.4, and 3.5). The upgrade to 3.4 in particular notes one added configuration variable related to email delivery.
Beyond that, since you’re not getting delivery errors in OJS, it’s likely that your SMTP basics are configured correctly (e.g. OJS can get the messages to the MTA without complaint), but that something from that point on is discarding them. The most common causes for that are DMARC et al.
Do you have access to the server’s email delivery logs? Those would likely explain the rejection – but not all hosts give access.
Regards,
Alec Smecher
Public Knowledge Project Team
I am using the new config.inc.php file that ships with version 3.5.0.3. I moved all of the database, email and other configurations to the new config file. I turned on show stacktrace and display errors for the last run but, no errors were shown. I’m using smtp so, I don’t think I need the sendmail path. I do not have have access to the smtp server log because it is a campus wide service that they make available to us.
I’m not sure of the registration workflow but, I do have a bunch of users that are disabled awaiting email confirmation. I’m not sure if the email is sent before or after the database entry. But the users are being stored but they are not receiving an email.
I believe that I have the minimum DMARC settings configured in the config file.