Sending email is not working in ojs 2.4.8

mejiamariod · August 30, 2018, 8:27pm

Grettings

I’ve the same problem, but my log error is the following “OJS SMTPMailer: Did not receive expected 250”. The OJS installation is new with only one journal and all have the same email.

Help me please

Ryan_Hidayat_Hatuala · December 15, 2018, 3:38pm

I have get the same problem with email in OJS 2.4.8 and I have fixed the problem with following ways:

You should check if your hosting provider is open port like 465, 587, 25, or other port you want to use. See this link how to check port is blocked or not How to check if a port is blocked by my ISP? - SiteGround KB if is there you get port is not blocking with your hosting provider you can use the port.
If you get error to open “telnet” in CMD you can see this link https://social.technet.microsoft.com/wiki/contents/articles/910.windows-7-enabling-telnet-client.aspx (for windows only)
If the above way can’t solve your problem you can use email account from your hosting provider like “admin@yourdomain.com” or something like that and you must setting the email in config.inc.php in OJS installation folder. You can fill out like this:

; Use SMTP for sending mail instead of mail()
smtp = On

; SMTP server settings
> smtp_server = “mail.yourdomain.com”
> smtp_port = 26

; Force the default envelope sender (if present)
; This is useful if setting up a site-wide noreply address
; The reply-to field will be set with the reply-to or from address.
force_default_envelope_sender = off

; Enable SMTP authentication
; Supported mechanisms: PLAIN, LOGIN, CRAM-MD5, and DIGEST-MD5
smtp_auth = PLAIN
> smtp_username = “xxxx@yourdomain.com”
> smtp_password = “yourpassword”

For see your port on your domain/website, you can see in Cpanel > Email Account > Mail Client Manual Setting.

Hope this help you.
Thanks.

ramon · April 26, 2019, 4:31pm

Hello all,

Is there a way to send individual messages?
We noticed that if there’s one user with wrong email address, the message is not sent to anyone in the list.
This prevents a basic notification of all authors and editorial team, but it’s not really an email problem, it’s how OJS or SMTP handles messaging probably.
We cannot be sure if authors are filling information correctly as coauthors are not actual users.
This “problem” should not prevent using the system and notifying those with correct email address.

ctgraham · April 29, 2019, 12:42pm

When a single email message is sent to multiple recipients, it is typically best practice to treat this as a single entity - it either sends to all, or to none. To change this, you would need to edit the code, probably in the Mail::send() function:

github.com

pkp/pkp-lib/blob/b3bfb57d7a3a64ad72c93b5f1f4cfb2069bd9165/classes/mail/Mail.inc.php#L468


	 */
	function getBccString() {
		return $this->getAddressArrayString($this->getBccs(), false);
	}


	/**
	 * Send the email.
	 * @return boolean
	 */
	function send() {
		$recipients = $this->getAddressArrayString($this->getRecipients(), true, true);
		$from = $this->getFromString(true);

		$subject = PKPString::encode_mime_header($this->getSubject());
		$body = $this->getBody();

		// FIXME Some *nix mailers won't work with CRLFs
		if (Core::isWindows()) {
			// Convert LFs to CRLFs for Windows
			$body = PKPString::regexp_replace("/([^\r]|^)\n/", "\$1\r\n", $body);

I’d be primarily curious as to how the invalid addresses are getting into the system. I wouldn’t expect the sending to fail with a properly formatted (but wrong) email address, but I would expect the sending to potentially fail with a malformed email address. On the other hand, I wouldn’t expect OJS to allow the input of a malformed email address.

ramon · April 30, 2019, 5:16pm

Hello @ctgraham,

The wrong email addresses are mistyped by authors submitting articles. Coauthor emails are wrongly typed and they prevent communication with all authors if one is misspelled.
For example, there was a @gmail.com| typed in… hard to see sometimes… since coauthors are not registered users (at least in OJS 2.x), we are unable to verify this information.
Maybe adding some kind of email verification first would force a metadata check of some sort…

ctgraham · April 30, 2019, 7:20pm

Are you able to reproduce the ability of an author to add a malformed email address (like someone@gmail.com| or address@gmail,com? If so, where specifically is this possible (and what entry did you use)?

I tried this as an author and as an editor in 2.4.8 and was unable to get a malformed email address to save in the metadata.

ramon · April 30, 2019, 10:42pm

Hello @ctgraham,

It wasn’t a special character… I looked up the email history and the error was a com @gmail.comj instead of com @gmail.com.

ctgraham · May 2, 2019, 11:30am

Hmmmm… Interesting. So, it seems that your MTA (Mail Transit Authority) may be doing extra validation of the email domains (or even the whole email address?) in the process of accepting the messages. If the MTA finds an email domain that cannot be routed, it rejects the entire message.

Changing the code to send messages individually might be an option, but the recipient would lose any context of who else received the message and wouldn’t be able to reply-all to the group.

You might check with your SMTP provider whether this can be turned off.

Assuming it the provider cannot or will not turn this off, for an MTA such as yours, you might instead want to validate the domains of email addresses are valid with checkdnsrr():
https://www.php.net/manual/en/function.checkdnsrr.php
Doing this at the time of collecting the email addresses would presumably catch most of the errors. Doing this at the time of sending the message would require deciding what you want to do with the bad addresses.

omid_roshani · December 26, 2020, 7:38pm

I also have your problem, how did you solve it?