Notification There was a problem sending an email message. Please try again later, or contact your system administrator

Hi @asmecher
The last email was sent on October 21.
but the option “Request Revisions” is the only one is showing that error

Hi @ckiyan,

If some emails are delivered and others aren’t, see this thread/post: Initial review request emails not received, intermittent - #3 by asmecher

Regards,
Alec Smecher
Public Knowledge Project Team

@asmecher

Thanks for your reply but it is not a problem with spam.
Do you know anybody who can check our site?
Thanks in advance
Carlos

For us it was a problem with the size of the documents that were attaching to the email. We just use sendmail not SMTP so it was an adjustment in the configuration of sendmail itself.

Jeremy

@jhennig
Thanks for your reply. I will try and let you know if I succeed
Carlos

@jhennig
The size of the document I am trying to send it is 76KB. Do you think it should be a problem?
which settings do you suggest me to change
Screenshot 2020-10-29 at 17.24.06

This is the mail settings:
;;;;;;;;;;;;;;;;;;
; 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’

; Amount of time required between attempts to send non-editorial emails
; in seconds. This can be used to help prevent email relaying via OJS.
time_between_emails = 3600

; Maximum number of recipients that can be included in a single email
; (either as To:, Cc:, or Bcc: addresses) for a non-privileged user
max_recipients = 10

; 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

That shouldn’t be a problem. The file I was dealing with was 25MB. If I remember correctly the limit we had was 10MB so we just increased that limit. I do suspect your problem is a spam filter problem.

You may want to try turning on your envelop sender
allow_envelope_sender = On
default_envelope_sender = my_address@my_host.com
force_default_envelope_sender = On

Make sure the domain in your default_envelope_sender matches the domain of your OJS installation. If it doesn’t match this increases the spam rating. So in other words the SPF value in your email headers may say “failed”.

Jeremy

@jhennig
Thanks. our domain is http://cjph.niph.org.kh/
and I have made the changes according with your suggestionScreenshot 2020-10-29 at 18.01.58
But I got the same error
Screenshot 2020-10-29 at 18.01.37

I only got this error by clicking “Request Revisions”
Screenshot 2020-10-29 at 18.05.39

and then the “Record Editorial Decision” Screenshot 2020-10-29 at 18.07.07

Sorry that envelope sender wouldn’t solve that problem. I was thinking more in terms of solving a spam issue. Do your php error logs say anything what about send mail (email) logs? Is it possible that one of the users/authors email addresses isn’t properly formed?
Is that the only file being attached? Could there be other ones that are larger?

I once remember running into a problem where a user had a rather odd email address and it failed. We had it changed and it worked.

Some of our editors have encountered this as well, specifically with the Request Revisions option since upgrading from OJS 3.1.2.1 to 3.2.1.2. The relevant PHP error appears to be:
You must provide at least one recipient email address.
As far as I can tell, all other emails are being sent out fine.

hello
Thanks for your reply. Do you know how can this be solved?

Unfortunately no, this is still an ongoing problem.

Hi @ckiyan: do you still have this problem? It resolved for me after I updated the post-upgrade database (see: [Solved] Some contributor list articles disappear after upgrading from ojs 3.1.2.4 to 3.2.0.2 - #18 by ji_farquharson). The metadata associated with the article submission (including email addresses) was no longer linked to the article after an upgrade. It might be worth checking your author table to ensure that there are no NULL values in the publication_id column.

Hi sir @ckiyan, what about the obstacles you faced before? Have you succeeded in completing it?? because I am going through the same thing that you have experienced, please guide me

Hi sir @asmecher, because I experienced the same thing as @ckiyan what can I do, because I’ve tried several times to fix it still can’t, please guidance

Hi @RaKa

This is an older post. If you haven’t done so already, please post a new post to the forum outlining the issue you are encountering and are wishing to discuss, and referring back to this post.

-Roger
PKP Team