Email to SMS not working from some service providers

Rod_n_Nala
Contributor II

I setup a notification device on my home security system several months ago which could generate and submit a notification to my cell phone via Bells sms gateway, nnnnnnnnnn@txt.bell.ca when the system was acticated.  It has been working just fine until a few days ago.  I added another sensor to our system a few days ago and suddenly (possibly just a coincidence) I am no longer receiving notifications.  I checked on the vendor's site for the notification device and saw that the necessary notifications were being created, but they never made it to my phone.  I did some debugging and was able to send myself a text message from my email account, so Bell's SMS gateway is still working.  I informed the vendor of this and they said they manually attempted to send several text messages from their end with no luck and no error message was generated to indicate why.  Anyone know why Bell's Email to SMS gateway suddenly only works for some vendors and not others?

0 7 2,217
2 helpful replies

Accepted Solutions

Rod_n_Nala
Contributor II

Hi @BellAntgio , thank you for your reply.  Your message stated using nnnnnnnnnn@txt.bellmobility.ca . So I sent myself an email from my email account using that address and was able to receive it.  So I updated my profile on the vender's site on Sunday, March 31st to use this address format vs the one in my original post above.  Initially, I still was not receiving any text notifications, so I sent your email to the vendor's technical team asking them for the specifics to your questions.  They replied stating they could see their test notifications going to Bell's servers, though they were still using the original format above.  Our sensor was triggered shortly after their reply and I did notice that a text notification was now being sent to my phone too.  Not sure what happened during that two week time period, but everything seems to be working fine again.  Thank you.

View reply in original post

BellDRock
Community Manager

UPDATE:

Text via email will no longer be available as of December 31, 2025.

For more information see Other ways to textOpens in a new tab or window.

View reply in original post

7 REPLIES 7

BellAntgio
Moderator

Hey there @Rod_n_Nala , 

Welcome to the Community and thanks for your post.

We've sent you a private message with the steps needed to investigate your concern.

Please check your Messages within your profile avatar in the top right corner.

Unsure how to check or send a private message? See How to send a private messageOpens in a new tab or window

Rod_n_Nala
Contributor II

Hi @BellAntgio , thank you for your reply.  Your message stated using nnnnnnnnnn@txt.bellmobility.ca . So I sent myself an email from my email account using that address and was able to receive it.  So I updated my profile on the vender's site on Sunday, March 31st to use this address format vs the one in my original post above.  Initially, I still was not receiving any text notifications, so I sent your email to the vendor's technical team asking them for the specifics to your questions.  They replied stating they could see their test notifications going to Bell's servers, though they were still using the original format above.  Our sensor was triggered shortly after their reply and I did notice that a text notification was now being sent to my phone too.  Not sure what happened during that two week time period, but everything seems to be working fine again.  Thank you.

Hi,

I use the email to text gateway to get SMS alerts from my work. This is a critical function I need to rely as there is no other choice for these messages. It used to work for quite a while but I just noticed I hadn't been getting alerts when I usually get one around 10PM every day.

The error on my mail server is (email, phone # and full server name redacted with X's):

Jan 23 13:02:22 mailXXX postfix/smtp[2950817]: E6CE64024B0: to=XXXXXXXXXX@txt.bellmobility.ca, relay=bcm-central.mx.a.cloudfilter.net [3.99.74.228]:25, delay=1.8, delaystatus=bounced (host bcm-central.mx.a.cloudfilter.net [3.99.74.228] said: 552 5.2.0  XXXXX@XXXX.ca sender rejected AUP#SNDR (in reply to end of DATA command))

Can anyone at Bell fix this or tell me what the actual problem is (ie: Something I can do on my end to fix it)? As I understand it AUP means Acceptable Use Policy and SNDR means the Sender address. The sender address is valid but just goes to /dev/null/ and is signed with a DKIM signature.

This is important! If this can't be fixed my only option is to change provider.

Good morning, @JPL. Thanks for your post, and welcome to the Bell Community.

We've sent you a private message with the steps needed to investigate your concern.

Please check your Messages within your profile avatar in the top right corner. Unsure how to check or send a private message? See How to send a private messageOpens in a new tab or window

— Kris

BellDRock
Community Manager

UPDATE:

Text via email will no longer be available as of December 31, 2025.

For more information see Other ways to textOpens in a new tab or window.

JPL
Contributor II

Well, thanks for coming here and dropping that bomb on everyone. Time to move on from Bell I guess.

Not sure who you will go to.  That seems to be the sign of the times... Rogers stopped that feature quite a few years ago.