OJS Email Problems: Why Your Journal Notifications Go Missing

Few things derail a journal's workflow faster than email problems. Authors submit manuscripts and never receive confirmation. Reviewers miss deadline reminders because the emails landed in spam—or never arrived at all. Editorial decisions go unacknowledged because the author genuinely didn't get the notification.

If your OJS installation has email issues, you're not alone. It's one of the most common problems journal managers face, and it's gotten worse as email providers have tightened their filtering.

Why Email Deliverability Has Become Harder #

Email in 2025 isn't what it was a decade ago. Major email providers—Gmail, Outlook, Yahoo, and institutional systems—have implemented increasingly strict filtering to combat spam and phishing.

These systems evaluate incoming email against multiple criteria:

Sender authentication — Does the sending server have proper SPF, DKIM, and DMARC records proving it's authorized to send email for your domain?

Sender reputation — Has your sending IP address been associated with spam? Does it have a history of legitimate email?

Content patterns — Does the email look like typical spam? Certain phrases, formatting patterns, or attachment types trigger filters.

Recipient behavior — Do people who receive your emails open them, or do they mark them as spam?

An OJS installation sending email through a basic server configuration often fails these checks, especially if your hosting wasn't set up with email authentication in mind.

Common OJS Email Failure Patterns #

Understanding how OJS email fails helps identify where problems originate:

Emails Never Sent #

Sometimes OJS doesn't send emails at all. This typically indicates a configuration problem—the system isn't properly connected to an email sending mechanism. Check your OJS email settings; if something is misconfigured at the system level, no notifications go out.

Emails Sent but Rejected #

Your server sends the email, but the recipient's server rejects it outright. This often happens when your sending server lacks proper authentication or has a poor reputation. The email never reaches even the spam folder—it's refused at the door.

Emails Delivered to Spam #

The email reaches the recipient's server but gets flagged as suspicious. It lands in spam or junk folders where recipients rarely look. This is particularly frustrating because the email technically "worked"—but practically failed.

Inconsistent Delivery #

Some emails arrive fine; others don't. This often indicates borderline reputation or authentication issues where different recipient servers make different decisions about your email.

Factors That Affect Your Journal's Email #

Several elements influence whether your OJS emails reach recipients:

Hosting Environment #

Shared hosting environments are particularly problematic for email. Your server shares an IP address with potentially hundreds of other websites. If any of those sites send spam, the shared IP's reputation suffers—affecting your emails even though you did nothing wrong.

VPS and dedicated servers give you a dedicated IP address, putting email reputation in your own hands. However, new IP addresses often start with neutral or poor reputation simply because they have no history.

Email Authentication Records #

Three DNS records significantly impact deliverability:

SPF (Sender Policy Framework) — Specifies which servers are authorized to send email for your domain. Without an SPF record, recipient servers have no way to verify your emails are legitimate.

DKIM (DomainKeys Identified Mail) — Adds a digital signature to emails proving they weren't tampered with in transit and genuinely came from your domain.

DMARC (Domain-based Message Authentication) — Tells recipient servers what to do with emails that fail SPF or DKIM checks, and provides reporting on authentication failures.

Many OJS installations lack proper configuration of these records, making their emails look suspicious to modern email systems.

Sending Method #

OJS can send email several ways:

PHP mail() — The default method uses your server's built-in mail function. Simple to configure but often produces poor deliverability because it lacks authentication and sends from servers without established reputation.

SMTP — Connecting to a dedicated email server through SMTP protocol. Better deliverability if configured with a reputable email service, but requires additional setup.

Third-party services — Services like Amazon SES, Mailgun, or SendGrid specialize in email delivery and have established infrastructure with high deliverability rates.

Email Content #

OJS's default email templates are generally fine, but certain modifications can trigger spam filters. Excessive formatting, embedded images, shortened URLs, or certain phrases associated with spam can all hurt deliverability.

Signs Your Email Setup Needs Attention #

Watch for these indicators of email problems:

Authors reporting non-receipt — If multiple authors mention not receiving submission confirmations, the problem is likely systemic rather than individual spam filters.

Reviewer acceptance delays — Reviewers not responding to invitations may simply not have received them.

Bounce notifications — If you or your server receive bounce messages, emails are being rejected. The bounce messages often explain why.

Low engagement from notifications — If response rates to deadline reminders or editorial requests have dropped, emails may be reaching spam folders rather than inboxes.

Emails working for some domains but not others — If Gmail users receive emails fine but university addresses don't, different email systems are evaluating your emails differently.

What Journal Managers Can Check #

While fixing email deliverability often requires technical work, you can investigate some aspects:

Verify OJS email settings — Check that your email configuration in OJS matches what your hosting provider supports. Incorrect settings can prevent sending entirely.

Test with multiple addresses — Send test emails to Gmail, Outlook, Yahoo, and any institutional addresses common among your authors and reviewers. Check both inbox and spam folders.

Check spam folder patterns — If emails arrive in spam, look at the headers. Many email clients show why a message was flagged, providing clues about what's failing.

Review server mail logs — If you have hosting access, server mail logs show whether emails were sent and what responses (if any) recipient servers returned.

The Bigger Picture #

Email deliverability isn't something you configure once and forget. Email standards evolve, provider policies change, and reputation requires ongoing maintenance. A setup that worked perfectly two years ago may now be problematic.

For journals where reliable communication is critical—which is essentially all journals—email infrastructure deserves serious attention. Missing a handful of notifications might seem minor, but the cumulative effect on editorial workflow, author experience, and reviewer relationships compounds over time.

The solution usually involves some combination of proper DNS authentication, SMTP configuration with a reputable service, and ongoing monitoring. The specific approach depends on your hosting environment, budget, and technical resources.