Topic-icon Registration - Could not execute: /usr/sbin/sendmail

Active Subscriptions:

None
12 years 6 months ago - 12 years 6 months ago #39161 by rikbro
Although our Joomla email works fine (I receive Joomla system notifications), it isn't working properly for new registrations.

After creating a new user record (name, password, etc.), the next screen shows:
Could not execute: /usr/sbin/sendmail

However, the correct sendmail path in our Joomla server setup is:
/usr/sbin/sendmail.sendmail

I don't see from where the wrong path (usr/sbin/sendmail) is being pulled.

Any ideas?

Thanks. -- Rik

PS: Using JFBConnect 5.2.1, Joomla 3.2.0, JomSocial 3.0.5.3
JomSocial Login
Last edit: 12 years 6 months ago by rikbro.
The topic has been locked.
Support Specialist
12 years 6 months ago #39167 by alzander
Rik,
I have no clue what could be causing that. JFBConnect doesn't do anything special with emails. We simply hand them off to Joomla and say "Please deliver this email". There's no special code outside of the Joomla APIs that we use to send email, so if you're seeing that message, it means that Joomla is having issues somewhere.

When you say "I receive Joomla system notifications", what kind of messages are you getting, and which ones aren't you getting? Are you getting the new user admin emails, but not the end-user emails, or what other emails are arriving?

Let me know, and we'll help how we can. It's also possible this is an issue with Joomla 3.2.0 as there are multiple issues with that release that are being worked on.

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
12 years 6 months ago - 12 years 6 months ago #39176 by rikbro
Alex:

I was receiving administrator messages just fine. As far as I can tell, only the emails sent to new registrations were having this sendmail problem.

I now see another person at the Joomla forums with this issue after upgrading to Joomla 3.2. Accordingly, I switched Joomla over to smtp mail and was able to create a new user record with JFBConnect and smtp email fine.

Thank you for getting me pointed in the right direction. -- Rik

PS: I'm not sure if this is a related issue or not. But in JFBConnect -> Requests, I have a lot of Facebook users showing their status as "expired." Does that mean that those email requests were not sent out? If not, can I change the date/times in the database table so that those are re-queued? Or does it just mean that those FB users never responded to the original requests? Thanks.
Last edit: 12 years 6 months ago by rikbro.
The topic has been locked.
Support Specialist
12 years 6 months ago #39188 by alzander
Rik,
Glad we could help get you looking in the right direction for the email issues and that you found a solution that works for you.

PS: I'm not sure if this is a related issue or not. But in JFBConnect -> Requests, I have a lot of Facebook users showing their status as "expired." Does that mean that those email requests were not sent out? If not, can I change the date/times in the database table so that those are re-queued? Or does it just mean that those FB users never responded to the original requests? Thanks.

There's a few possibilities here. Some we have control of, others we don't:
* First, there's a bug in JFBConnect that will be fixed soon. On some sites, the acceptance of a request isn't properly recorded as being received. This will be fixed in the next release, planned for the first week of December.
* Next, Facebook doesn't return the ID of the user that is accepting the request *unless* they've already approved your application. It's a bit silly, but they do that for privacy reasons.. and that means that JFBConnect can't track if a user accepts an invitation until they've actually already used the Login with Facebook feature. There is an update they just pushed out which may allow us to fetch this information. We'll be fixing our code if it's possible.
* Beyond that, requests automatically expire on Facebook if the recipient hasn't accepted it within 2 weeks. At that point, JFBConnect marks it as expired if it hasn't been accepted (that we can detect) yet.

Finally, when a request is sent, there's no way to re-send it automatically if it's never been accepted.

I hope that helps answer your questions,
Alex
The topic has been locked.