This chapter explains how emails are sent in OJS, OMP, and OCS; the configuration options that are available; and how to troubleshoot email issues.
Records of emails that are sent are stored in the
email_log table of the database.
PKP software applications provide a number of options for configuring emails to work in your environment. The following configuration options are available for email in
;;;;;;;;;;;;;;;;;; ; Email Settings ; ;;;;;;;;;;;;;;;;;; [email] ; Use SMTP for sending mail instead of mail() ; smtp = On ; SMTP server settings ; smtp_server = mail.example.com ; smtp_port = 25 ; Enable SMTP authentication ; Supported mechanisms: ssl, tls ; smtp_auth = ssl ; smtp_username = username ; smtp_password = password ; Allow envelope sender to be specified ; (may not be possible with some server configurations) ; allow_envelope_sender = Off ; Default envelope sender to use if none is specified elsewhere ; default_envelope_sender = my_address@my_host.com ; Force the default envelope sender (if present) ; This is useful if setting up a site-wide no-reply address ; The reply-to field will be set with the reply-to or from address. ; force_default_envelope_sender = Off ; Force a DMARC compliant from header (RFC5322.From) ; If any of your users have email addresses in domains not under your control ; you may need to set this to be compliant with DMARC policies published by ; those 3rd party domains. ; Setting this will move the users address into the reply-to field and the ; from field wil be rewritten with the default_envelope_sender. ; To use this you must set force_default_enveloper_sender = On and ; default_envelope_sender must be set to a valid address in a domain you own. ; force_dmarc_compliant_from = Off ; The display name to use with a DMARC compliant from header ; By default the DMARC compliant from will have an empty name but this can ; be changed by adding a text here. ; You can use '%n' to insert the users name from the original from header ; and '%s' to insert the localized sitename. ; dmarc_compliant_from_displayname = '%n via %s'
By default, PHPMailer will send mail through PHP’s built-in
On Windows, PHP needs to be configured to send email through a SMTP server (running either on the same machine or on another machine).
On other platforms such as Linux and Mac OS X, PHP will sent mail using the local sendmail client, so a local MTA such as Sendmail or Postfix must be running and configured to allow outgoing mail.
See http://www.php.net/mail for more details on configuring PHP’s mail functionality.
Our software can also be configured to use an SMTP server as specified in
config.inc.php, either with or without authentication.
To control the address to which a bounced email will be sent, you need to set the envelope sender address. Enable the
allow_envelope_sender option in the
[email] section of the configuration file; when this option is enabled, a “Bounce Address” field appears in the Email section under Setup.
Note that this option may require changes to the server’s mail server configuration so that the user the web server runs as (e.g. “www-data”) is trusted by the sendmail program; otherwise an “X-Warning” header will be added to outgoing messages. Consult your mail server’s documentation if outgoing mails include such a header.
For example, Sendmail keeps a list of trusted users in
/etc/mail/trusted-users; other mail systems use similar files.
The command-line option used to set the envelope sender is
Email templates are installed directly in the database when a journal, press, or conference is created. If you need to edit a locale file, any change in your template file will not be reflected until you reload all templates in the system.
Reloading templates will override any modifications that you may have made. To keep those modifications, you will need to save these modification locally and re-add them to templates as required.
All PKP applications require that primary and technical contacts are configured under Setup for proper daily operations. This is required for every journal, press, or conference in the system.
OJS provides a self-registration form to all users which can be disabled or re-enabled under Admin Menu > User & Roles > Site Access Options > User Registration
Once this is enabled, every user is able to register and create an account in the Journal with a role as reader, author, and/or reviewer; however, it is not unusual for users to create spam accounts that will clutter the list of legitimate users and increase the workload for Journal Editors to verify these accounts and clean them up manually.
Mass spam account creation can be reduced with two settings in
; If enabled, email addresses must be validated before login is possible. require_validation = Off ; Maximum number of days before an unvalidated account expires and is deleted validation_timeout = 14
The first parameter is
require_validation, which is set to
Off by default. When set to
On, this parameter will require that every new user activates their account before being able to fully use the system.
The second parameter is
validation_timeout, which is set to
14 by default. This parameter only works when the
require_validation is enabled, and means that a user has 14 days to activate their new account or the account will be removed from the system automatically when the time limit is reached.
To use Gmail SMTP to send email from OJS, you can use the following settings in
For OJS 2.x:
; Use SMTP for sending mail instead of mail() smtp = On ; SMTP server settings smtp_server = "ssl://smtp.gmail.com" smtp_port = 465 ; Enable SMTP authentication smtp_auth = PLAIN smtp_username = "email@example.com" smtp_password = "password"
For OJS 3.x:
; Use SMTP for sending mail instead of mail() smtp = On ; SMTP server settings smtp_server = smtp.gmail.com smtp_port = 465 ; Enable SMTP authentication smtp_auth = ssl smtp_username = "firstname.lastname@example.org" smtp_password = "password"
Additional information about Gmail SMTP is available at https://support.google.com/a/answer/176600?hl=en.
Note that you may have to additionally configure application-specific passwords in Gmail; see https://support.google.com/accounts/answer/185833?hl=en for details.
The Sender Policy Framework (SPF) relies on permission that a server, which may be running OJS, receives from another server which hosts the main domain. This authorizes the OJS server to send emails using that domain and prevents messages from being blocked.
SPF is required when your OJS installation runs on a different server, including a subdomain, from your main domain; For instance, when you host a journal located at journal.domain.com on a server located outside of the institution which hosts domain.com.
In this situation, you will have to ask your IT services staff to enable a TXT entry in your DNS zone, which grants sending emails and notifications on behalf of @domain.com. Below is an example of a possible scenario where a SPF record is required:
Server running OJS:
IP: 10.10.10.10 Server name: myojsserver.com (this is not your domain, but only a server name which is defined by your OJS host vendor)
This server will need to be included in your DNS zone as a TXT SPF record. In this case, you will need to add the following:
Name: blank, or set to @ (depending on your domain registrar instructions) Type: TXT Value: v=spf1 ip4:10.10.10.10 a:myojsserver.com ~all
If you already have a TXT record in your DNS zone, you will need merge it to keep only one TXT record. There should only be a single DNS TXT record.
While SPF provides the provision for OJS to send emails using a return path or email envelope containing an email address with a domain other than the one the OJS server is hosted on, there are times when OJS may send email on behalf of users that use domains that you cannot adust the SPF record for. Gmail is a good example: if an admin has a
email@example.com address, there’s no way you can get Google to add us as an SPF record.
DMARC solves this by putting the user’s email in the
reply-to: address, and and putting the
default_envelope_sender in the
From: field. As of OJS 3.1.2, you can configure this via two new parameters in your
config.inc.php file, namely
dmarc_compliant_from_displayname. (If you are on OJS 3.1.2+ and don’t see those parameters in your live config file, you will want to review your
config.TEMPLATE.inc.php file and move them over as they appear there.)
If emails aren’t being received by some users, the first thing to do is check to see if you yourself can receive email. Try sending an email to yourself using the system. If you received it, the software application is probably sending email fine. You should then ask the user with the problem to check their email’s spam/junk folders.
If the user can find no record whatsoever of the email being filtered as spam or junk, you may be encountering a Sender Policy Framework (SPF) validation problem with their server. You can confirm this by viewing your server’s mail log to see if there are any reported receipt blockages/returns with SPF validation errors as the result.
As of version 2.4.6, OJS included a change to the way emails are sent out. Previously, all emails were sent using the OJS user’s email address in the “FROM” field. This unfortunately led to some issues with the journal’s outgoing emails being flagged as “spoofed” by some email servers because the email addresses in question (eg. firstname.lastname@example.org”) didn’t match the domain name of the server sending the email (eg. “myjournal.com”). (Technically, the emails were failing Sender Policy Framework (SPF) validation.) Being flagged in this way is more serious than being considered spam: in many cases, the receiving email server won’t even assign the email to a spam/junk queue, instead simply choosing to discard it.
To prevent this from happening, the PKP development team has adopted an email notification method similar to other web applications such as WordPress: send all email from the system using one central email address in the “FROM” field, with the intended recipients’ email addresses in the “REPLY-TO” Field. The central email address to be used by default would be the one provided in Journal Setup Step 1.2: Principal Contact, which should match the domain name from which the journal sends mail. (If this email address cannot match the sending domain on a per-journal basis, an alternate email address can be configured at the site level via the OJS config.inc.php file). In addition, a new “Email Header” setting has been provided in Journal Setup Step 1.4: Email Identification, which can be used to provide explanatory text to the recipient.
To properly configure this, we suggest the following:
You are receiving this email on behalf of <journal-name>. In the event of a requested response, you may respond directly to this email.