Confirmation email issue on 2.1 beta 5

l3ta

l3ta

Well-known member
People registering on my site are not getting the confirmation email. The server is login the following error:

Swift_TransportExeption: Email to (insert user email here) failed: Process could not be started [sh: -t: command not found ]
src/vendor/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/StreamBuffer.php:307

Wut could be happening?
 
Sort by date Sort by votes
l3ta said:
Can I please have a XF expert address this issue? Is there a developer in the house @Chris D :(
Click to expand...
The previous guidance is sufficient and likely accurate. This is something to do with sendmail or the sendmail configuration in PHP.

The path can be overridden in XF with the following in src/config.php:
PHP: 
$config['sendmailPath'] = '/path/to/sendmail';
You may need the assistance or your host or server support to help.
 
Upvote 0 Downvote
The most likely cause here is a semicolon at the end of the sendmail_path setting line in php.ini causing the shell to treat the added paramaters as a command on its own giving the a/m error.

Another funny error I've never seen before :)
 
Upvote 0 Downvote
Yeah. Those hacks didn't work. And my host is paranoid about messing with my php, so they are kicking the can back to XF. I guess I'm out of luck 😢
 
Upvote 0 Downvote
l3ta said:
I guess I'm out of luck 😢
Click to expand...
?

Most likely all you (or your host) has to do is to remove the extraneous ; on the sendmail/path config line in php.ini.

If this is not possible, you can override the setting via config.php as suggested by Chris.
Did you try that?

But honestly, if you host fears to fix a configuration error it doesn't seem to be competent.
 
Upvote 0 Downvote
Kirby said:
?

Most likely all you (or your host) has to do is to remove the extraneous ; on the sendmail/path config line in php.ini.

If this is not possible, you can override the setting via config.php as suggested by Chris.
Did you try that?

But honestly, if you host fears to fix a configuration error it doesn't seem to be competent.
Click to expand...
I did all that, dude. Removed the semicolon, added the script, etc etc. I didn't work. Thanks for your help, tho 👍
 
Upvote 0 Downvote
Honest.

Every time a host kicks a server/hosting issue back to us (and it happens a lot), it's because they don't understand how to resolve it.

In a lot of cases we actually have to tell the customer what to tell the host to do to resolve it (as it's not something we can resolve within XF).
 
Upvote 0 Downvote
Brogan said:
Honest.

Every time a host kicks a server/hosting issue back to us (and it happens a lot), it's because they don't understand how to resolve it.

In a lot of cases we actually have to tell the customer what to tell the host to do to resolve it (as it's not something we can resolve within XF).
Click to expand...
I understand that. More often than not, it's a hosting issue. I'll see what I can do. Thank you :).
 
Upvote 0 Downvote
l3ta said:
I did all that, dude. Removed the semicolon, added the script, etc etc. I didn't work. Thanks for your help, tho 👍
Click to expand...
That does not make too miuch sense.

Did you verify that the value did actually change by checking to output of https://www.yourdomain.com/admin.php?tools/phpinfo?
 
Upvote 0 Downvote
This is really strange.

If you want to debug/trace this, you can try to change line 308 of src/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/StreamBuffer.php from
PHP: 
'Process could not be started ['.$err.']'

to

PHP: 
'Process "' . $command . '" could not be started ['.$err.']'

and afterwards try to trigger the error again and check the error log to see when command is actually being tried.
 
Upvote 0 Downvote
Kirby said:
This is really strange.

If you want to debug/trace this, you can try to change line 308 of src/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/StreamBuffer.php from
PHP: 
'Process could not be started ['.$err.']'

to

PHP: 
'Process "' . $command . '" could not be started ['.$err.']'

and afterwards try to trigger the error again and check the error log to see when command is actually being tried.
Click to expand...
Hehe, I know. I will try wut you recommend as soon as I'm near my desktop. I appreciate your continued help.
 
Upvote 0 Downvote
Kirby said:
That's great :)
What was the issue?
Click to expand...
Not sure, but the site went down for a whole day :eek: I just got an email from their syst admin saying everything was working fine now. I did notice that they changed my php version to 7.1. Maybe that did the trick. Anyways, I'm glad everything is working fine 👌
 
Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

Godleydemon
  • Question Question
XF 1.2 Confirmation Email Issue
Replies
9
Views
1K
Godleydemon
Godleydemon
Back
Top Bottom