[OJS3.2.1.1] Mail-Spam-Problem

twa · February 17, 2021, 6:30am

we are facing the following problems with emails:
Emails sent through OJS are blocked by the spam filter, because the sending server uses the same domain as the reciever. Our IT deparment says »Ideally the mail Header->From doesn’t use our own domain, because this is classically classified as spam«.

Since I’m no pro with mail servers and configurations on this topic: What could I change on our OJS configuration, that the mails make it through the spam filters?

Thanks,
Tobias

ctgraham · February 17, 2021, 3:43pm

See the following settings in config.inc.php:

github.com

pkp/ojs/blob/d3483427289fd63b658ff463178d194fd3b9a5c0/config.TEMPLATE.inc.php#L318-L345


; 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.

This file has been truncated. show original

You will want to set allow_envelope_sender, force_default_envelope_sender, and force_dmarc_compliant_from to be “On”, and you will want to set default_envelope_sender to be an email address trusted by whatever you are using for your mailserver (localhost, if smtp is “Off”, or the smtp_server if smtp is “On”).

Your mailserver must publish an SPF record which matches the domain of the default_envelope_sender. The easiest way to accomplish this is to either:

Ask your IT department to include the mailserver in the current SPF record.
Use SMTP to connect to a mailserver which is already in your IT department’s SPF allowed list.

twa · February 18, 2021, 6:12pm

@ctgraham Thanks for your advice. I changed the mentioned settings:

allow_envelope_sender = On
default_envelope_sender = localhost
force_default_envelope_sender = On
force_dmarc_compliant_from = On

But now, no email is generated at all – I get the notification: “There was a problem sending an email message. Please try again later, or contact your system administrator.”

Thanks for your help!
Tobias

twa · February 18, 2021, 6:17pm

I figured out, that default_envelope_sender = localhost was the problem. If I change localhost to a valid email adress, emails are generated.

Okay, I’ll now test the behaviour of the spam filter on this and report.

Thanks,
Tobias

twa · February 19, 2021, 9:01am

@ctgraham Thank you very much – everything works fine now!

To sum it up: Changing the following entries in config.inc.php

allow_envelope_sender = On
default_envelope_sender = mail-to@adress.com
force_default_envelope_sender = On
force_dmarc_compliant_from = On

has done the job!

Tobias

putu_mega · February 23, 2021, 11:32am

Just want to share. Sometimes, your email will be blocked or unsuccessfully sent because it’s not allowed by SPF, or violated DMARC. It’s because your IP hosting is used along with spam email.
The solution is better to use third-party email hosting that supports smtp.
mxroute or mail.baby are reliable, good and cheap. I personally use mxroute.

Thank you