Email Settings Plugin for OJS: What Editors Need

Email is one of the most important parts of an Open Journal Systems website. OJS depends on email for account registration, password reset, submission confirmation, editor assignment, reviewer invitation, review reminders, editorial decisions, copyediting, production, publication notices, and general author communication. If email settings are wrong, the journal workflow can slow down immediately. Authors may not receive decisions, reviewers may miss invitations, and editors may spend extra time sending manual follow-ups.

Why Email Settings Matter in OJS

In OJS, email is not only a contact feature. It is part of the editorial workflow. When an author submits a manuscript, the system may send confirmation. When an editor invites a reviewer, the invitation is sent by email. When a decision is made, the author is notified by email. When users forget their password, the reset link is sent by email. If these messages do not reach the recipient, the entire publishing process becomes unreliable.

Many journal teams only notice email problems after users complain. A reviewer may say they never received an invitation. An author may say the password reset link never arrived. An editor may think a decision was sent, but the author may not receive it. Because of this, email setup should be checked before launching a new journal, after migration, after server changes, after OJS upgrades, and whenever SMTP credentials are updated.

What an Email Settings Plugin Can Do

An Email Settings Plugin for OJS can make email configuration easier for administrators and editors. Instead of editing server files manually, the plugin can provide admin-panel controls for SMTP host, SMTP port, encryption type, username, password, sender email, reply-to address, test email, and other delivery-related settings. This is helpful for journal teams that want easier management without touching code or server configuration files.

The exact features may depend on the plugin version and OJS version, but the main goal is simple: give administrators a controlled place to manage outgoing email settings. This can reduce technical dependency and make email troubleshooting faster.

Why Editors Should Care About Email Delivery

Editors may not manage server settings, but they are directly affected when email fails. If reviewers do not receive invitations, review timelines are delayed. If authors do not receive revision requests, manuscripts remain pending. If decision emails go to spam, authors may miss important communication. If password reset emails fail, users may not be able to log in.

Editors should understand the basic email flow so they can report problems clearly. For example, instead of saying “email is not working,” they can explain whether the issue affects password reset, review invitations, submission confirmation, or all outgoing messages. This helps technical teams identify the issue faster.

Important Email Settings to Configure

• SMTP Host: The mail server used to send outgoing emails.
• SMTP Port: Common ports include 587 for TLS and 465 for SSL.
• Encryption: Usually TLS or SSL, depending on your mail provider.
• SMTP Username: The authenticated email account or mail user.
• SMTP Password: The password or app password for the sending account.
• Sender Email: The address shown as the sender of journal emails.
• Reply-To Address: The address where user replies should go.

Authenticated SMTP Is Better Than Basic PHP Mail

Some servers allow basic PHP mail, but it is usually less reliable than authenticated SMTP. With PHP mail, messages may be sent without proper identity verification, which can increase the chance of emails being rejected or marked as spam. Authenticated SMTP uses a proper email account or mail service, making delivery more controlled and traceable.

Journals should use authenticated SMTP whenever possible. This allows the sending domain, sender identity, and email authentication records to work together. It also makes troubleshooting easier because the mail provider may provide logs or error messages.

Sender Email and Reply-To Behavior

The sender email should look professional and belong to the journal or publisher domain. For example, an address like editor@journaldomain.com or submissions@journaldomain.com looks more trustworthy than a personal Gmail address. A domain-based sender also helps with branding and email authentication.

Reply-to behavior should be planned carefully. If users reply to an editorial decision, should the reply go to the journal office, the editor, or a general support email? If this is not configured clearly, replies may go to the wrong mailbox. Editors should confirm that outgoing emails show the correct sender and that replies reach the correct person.

SPF, DKIM, and DMARC Records

Email reliability depends not only on OJS settings but also on domain-level records. SPF, DKIM, and DMARC help receiving mail servers verify that your journal is allowed to send email from the domain. Without these records, messages may land in spam or fail delivery.

SPF tells mail servers which systems are allowed to send emails for your domain. DKIM adds a digital signature to confirm the message was not changed. DMARC tells receiving servers what to do if SPF or DKIM checks fail. Editors do not need to configure these records themselves, but they should ask the technical team to verify them when email delivery issues appear.

Testing Email Before Launch

A journal should not invite submissions until core email notifications are tested. Testing should include password reset, new user registration, submission confirmation, reviewer invitation, editorial decision, and contact emails. It is not enough to send only one test email. Different OJS workflow messages may use different templates, recipients, and reply-to behavior.

• Test password reset email for normal users.
• Test author submission confirmation email.
• Test reviewer invitation and review reminder emails.
• Test editor decision emails with attachments or comments if used.
• Test replies to confirm reply-to behavior is correct.
• Check inbox, spam folder, and mail server logs where possible.

Common Email Problems in OJS

Email problems can appear in different ways. Sometimes no email is sent at all. Sometimes the system shows success, but the recipient never receives the message. Sometimes emails reach Gmail but not institutional accounts. Sometimes password reset works but reviewer invitations fail. These differences matter because they point to different causes.

Common causes include wrong SMTP password, blocked SMTP port, incorrect encryption type, sender email mismatch, expired app password, missing SPF/DKIM records, hosting firewall restrictions, email quota limits, spam filtering, incorrect reply-to settings, or template-level issues. A good Email Settings Plugin should make it easier to check the configuration and send test messages.

Email Templates and Editorial Communication

OJS uses email templates for many workflow steps. These templates should be reviewed by editors, not only technical staff. The message should be clear, professional, and appropriate for the journal. Reviewer invitations should include enough information. Decision emails should be polite and structured. Submission confirmations should reassure authors that the manuscript was received.

Good email settings ensure delivery, but good templates ensure communication quality. Both are important. Editors should review templates after setup, migration, language changes, or major workflow changes.

Multi-Journal OJS Installations

Multi-journal OJS portals need extra care. Each journal may have a different contact email, editor email, sender identity, and reply-to expectation. A shared SMTP account may be used, but journal-level sender details must still be checked. If all journals send from one address, users may be confused about which editorial office is contacting them.

For multi-journal systems, administrators should decide whether each journal will use its own sender address or a common publisher address. They should also test emails from each journal separately because settings, templates, and contact addresses may differ.

Security Considerations for SMTP Credentials

SMTP credentials are sensitive. If an email settings plugin stores SMTP username and password, access to that settings page should be limited to trusted administrators. Editors may need to understand email behavior, but not every editor should be able to view or change SMTP passwords.

If the mail provider supports app passwords, use an app-specific password instead of the main mailbox password. If a staff member leaves the organization, review access and rotate credentials when needed. Email security is part of journal security.

When to Review Email Settings

• Before launching a new OJS journal.
• After OJS migration from another server.
• After changing hosting, domain, DNS, or SSL settings.
• After changing SMTP password or mail provider.
• After users report missing password reset or reviewer invitation emails.
• Before opening submissions for a new issue or special issue.

Practical Checklist for Editors and Administrators

• Use authenticated SMTP instead of relying only on basic server mail.
• Confirm SMTP host, port, encryption, username, password, and sender address.
• Use a professional journal or publisher domain email address.
• Verify reply-to behavior for author and reviewer communication.
• Review SPF, DKIM, and DMARC records for the sending domain.
• Test password reset, submission, review invitation, and decision emails.
• Limit SMTP settings access to trusted administrators.
• Document email settings and update them after server or domain changes.

GetOJS Recommendation

GetOJS treats email setup as part of launch readiness. A journal should not invite submissions until core notifications are tested. Reliable email supports every major OJS workflow, including registration, submission, peer review, editorial decision, revision, copyediting, production, and publication.

An Email Settings Plugin can make configuration easier, but it should be combined with proper SMTP setup, domain authentication, template review, role-based access, and regular testing. When email is configured correctly, editors can focus more on publishing work and less on solving avoidable communication problems.