Full email address not passed when using phpmailer

Confirmed on my system as well. Send to phone function works on nodes, as well as confirmation. But email notifications do not work.

I'm having the same problem just trying to use the module without the php mailer.

https://drupal.org/node/1195260#comment-4677904

The problem for me is that the $options being passed to sms_email_gateway_send is an empty array. I'm just not sure where it is being called. If anyone could help with this I would really appreciate it.

Here is where it is actually being sent to the drupal_mail function, I just need one step above this.

/**
 * Callback for sending messages.
 */
function sms_email_gateway_send($number, $message, $options) {
  $from = !empty($options['from']) ? $options['from'] : NULL;
  $to = $number .'@'. $options['carrier'];
  $params['message'] = $message;
  $message = drupal_mail('sms_email_gateway', 'sms', $to, language_default(), $params, $from);
  if ($message['result']) {
    return array('status' => TRUE);
  }
}

I'm getting the same issue. No problem with confirming the number or sending a test email with PHPmailer. When I send a test sms from the messaging settings, I get this error:

Sending of at least one e-mail failed. The error returned was:
Invalid address: XXXXXXXXXX@.
Unable to send e-mail. Please contact the site administrator if the problem persists.

So it appears that the domain is not being passed to whatever function call is taking place.

Trying to send a notification from a node update is even worse.

Sending of at least one e-mail failed. The error returned was:
Invalid address: @.
Unable to send e-mail. Please contact the site administrator if the problem persists.

It appears that neither the phone number or the domain are being passed.

Any suggestions would be greatly appreciated.

revyd,

Check out the patches i attached in this post https://drupal.org/node/1222038

I should take care of your issue for the sms if you are using the email gateway. I haven't had anyone else confirm that it works but that is what took care of the problem for me.

Please follow up to let me know if that corrected it for you or not.

Thanks,

NROTC_Webmaster,

Unfortunately the patch that worked for you did not work for me. The error I am now receiving is:

user notice: The messaging_template_text_replace() function called token replacement with an array rather than a string for $text in /home/c3church/public_html/sites/all/modules/token/token.module on line 263.
Sending of at least one e-mail failed. The error returned was:
Invalid address: .
Unable to send e-mail. Please contact the site administrator if the problem persists.

I am at a loss!

revyd,

Were you receiving the error before you applied the patch? It seems like that would be a token module issue but I can see how it would be passing the wrong information.

What version of each of the modules were you using? I'm on the following versions
messaging 6.x-4.x-dev (2011-Nov-11),
notificaitons 6.x-4.x-dev (2011-Feb-26),
smsframework 6.x-2.0-alpha1,
sms_email_gateway 6.x-1.0,
token 6.x-1.18

Let me know if I can help you out in any other way. I don't know how much you experienced you are with drupal but to print the variable just do
drupal_set_message($text); // if it is a string
or
drupal_set_message(print_r($text, 1)); // if it is an array

Prior to applying the patch I was getting this error:

Sending of at least one e-mail failed. The error returned was:
Invalid address: @.
Unable to send e-mail. Please contact the site administrator if the problem persists.

I was receiving the token error prior to applying the patch

messaging 6.x-4.0-beta8
notifications 6.x-4.0-beta7
sms framework 6.x-2.0-alpha1
sms_email_gateway 6.x-1.0
token 6.x-1.18

Looks like I should move to the dev versions of messaging and notifications. I'll do that and let you know.

NROTC_Webmaster,

Thanks. Got it working now. After I updated and re-patched the modules I had to delete the existing subscriptions and resubscribe for the sms to start working. All the error messages including the token errors are now gone.

You rock!

anytime I get errors I always update to the latest dev version because it should have all of the latest fixes.