Why OJS Journal Emails Go to Spam or Never Arrive (and How to Fix It)

Authors say they never got a submission confirmation. Reviewers miss reminders. An editor finds a decision that was never received. When a journal’s emails fail, the editorial process stalls quietly, often for weeks before anyone notices. The good news: the causes are well understood, and most can be fixed for good.

Need the quick checklist? See OJS email not sending. This guide explains the why, so the fix sticks.

Four ways journal email fails

What happens	What it usually means
Nothing is sent at all	OJS isn’t connected to a working mail setup, or queued emails aren’t being processed
Sent, but refused	The receiving server doesn’t trust your sender: missing authentication or a poor reputation
Delivered to spam	Accepted, but judged suspicious
Some arrive, some don’t	Borderline reputation: Gmail, Outlook and university servers each decide differently

Why mail providers distrust journal emails

Missing SPF, DKIM and DMARC

These three DNS records prove an email really comes from your domain. Since 2024, Gmail and Yahoo require sender authentication, and messages without it are increasingly refused or sent to spam.

• SPF lists the servers allowed to send email for your domain.
• DKIM signs each message so the receiver can check it wasn’t altered.
• DMARC tells receivers what to do when the first two fail, and sends you reports.

Sending from the web server with PHP mail

Out of the box, OJS often sends through the server’s built-in mail function, unauthenticated and from a server with no mail reputation. It’s the single most common cause of missing journal email.

Shared hosting

On shared hosting your site shares a mail server, and its reputation, with hundreds of other sites. If one of them sends spam, your journal suffers. Many cheap hosts also cap how many emails you can send per hour, so some messages vanish without an error.

Sending as someone else’s address

When OJS sends “from” an editor’s Gmail or university address through your server, DMARC checks fail. OJS has settings to send from your own domain while keeping the editor’s address as the reply-to.

Bursts and content

Hundreds of review requests sent at once, heavy formatting, shortened links or large attachments can all push a message over a spam filter’s threshold.

How to fix it

1. Send through an authenticated mail service. Set OJS to use SMTP with a proper mailbox or a transactional email service, instead of PHP mail. This is the biggest single improvement.
2. Publish SPF, DKIM and DMARC for the domain you send from, matching the service you send through.
3. Send from your own domain. In OJS’s mail settings, use a default sender address on your domain and turn on the DMARC-compliant “from” option.
4. Make sure scheduled tasks run. Reminders and queued emails depend on OJS’s scheduled tasks (cron) running on the server.
5. Check your reputation. Look your domain and server IP up on a blacklist checker, and send a test to a mail-testing service to see your score.
6. Keep templates clean. Plain wording, a clear signature, no link shorteners. See OJS email templates.

Don’t use a staff member’s personal Gmail or Outlook account as the journal’s mail server. Use a dedicated sending account or service, and keep its password only in OJS’s configuration file.

Signs you have a problem

• Several authors report missing confirmations or decisions.
• Reliable reviewers suddenly stop responding to invitations.
• Editors find submissions or reviews they were never notified about.
• Test emails to Gmail or Outlook land in spam, or don’t arrive.

Mail rules change often, and every host is set up differently. This guide reflects common causes as of October 2026; it isn’t a guarantee of delivery to any provider.

Want it fixed properly? Our OJS support team sets up authenticated sending, DNS records and OJS mail settings, and checks the result.

Questions

Why do OJS emails go to spam?

Usually because the domain has no SPF, DKIM or DMARC records, or OJS sends through the web server’s PHP mail instead of an authenticated mail service.

Why are OJS emails not being sent at all?

Often the mail settings in OJS’s configuration are wrong, the host blocks outgoing mail, or scheduled tasks that process queued emails aren’t running.

Does shared hosting affect email delivery?

Yes. You share a mail server’s reputation with other sites, and many hosts limit sending. An external authenticated mail service avoids both problems.

Can I use Gmail to send OJS emails?

It isn’t recommended for a journal. Use a dedicated mailbox on your domain or a transactional email service, with SPF, DKIM and DMARC set up.