db_send_mail to txt.att.net recipient shows up on phone from weird 10 digit phone number

  • This is more of an AT&T question, but maybe someone else has come across this issue.

    We have a job that uses db_send_mail to send an alert to several email addresses and cell phones via sms. The mail profile is using a domain account (alerts@domain.com). The AT&T recipients receive each alert from a different 10 digit phone number, where the last digit of the phone number seems to be incremented with each message. This makes it so the cell phones can't keep the conversation threaded.

    It seems that our Verizon users receive all the sms messages from alerts@domain.com, which is good. Is there a way to force the sender address/info to flow through AT&T correctly?

    Thanks!

  • i hate to be the bearer of bad news but because its AT&T you have to live with the quirks. AT&T does this with every email (as far as i know) sent to their text gateway. att creates a text message from a "Phone Number" (the strange incremental number in the from field) for each email received and sends that to the phone breaking the message into as many 160 character text messages as needed. att will (at one time this was true have not tested in a while) translate any reply to the text into an email and send it to the email address that initially sent the email to text message.


    For faster help in answering any problems Please read How to post data/code on a forum to get the best help - Jeff Moden[/url] for the best way to ask your question.

    For performance Issues see how we like them posted here: How to Post Performance Problems - Gail Shaw[/url]

    Need to Split some strings? Jeff Moden's DelimitedSplit8K[/url]
    Jeff Moden's Cross tab and Pivots Part 1[/url]
    Jeff Moden's Cross tab and Pivots Part 2[/url]

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply