Page 2 of 2 FirstFirst 12
Results 16 to 20 of 20

Were you able to have a "@tmo.blackberry.net" email address?... BlackBerry Pearl forum

  1. #16
    Texas512's Avatar
    Texas512 no está en línea Stack level 3
    Join Date
    Jul 2007
    Posts
    307

    Re: T-Mobile Data Plan for 4.99

    Advertisement



    Were you able to have a "@tmo.blackberry.net" email address?

  2. #17
    vinmontRD's Avatar
    vinmontRD no está en línea Stack level 3
    Join Date
    Jul 2007
    Posts
    415

    Re: T-Mobile Data Plan for 4.99

    Quote Originally Posted by Texas512
    Were you able to have a "@tmo.blackberry.net" email address?
    No - that would never have worked with this proxy trick. The proxy workaround, in combination with T-Zones, allowed you to get Internet web access that was normally not allowed with T-Zones (which is very restrictive).

    The @tmo.blackberry.net email address is explicitly part of BIS (blackberry internet services), and you won't get that unless you have a Blackberry plan or add-on. Even the normal "t-mobile internet" plans don't get you that. However: if you have any kind of plan with T-Mobile, you DO have an email address (think is was your phone number @tmomail.net - but I'm not certain).

  3. #18
    jkai2188's Avatar
    jkai2188 no está en línea Stack level 5
    Join Date
    May 2007
    Posts
    752

    Re: T-Mobile Data Plan for 4.99

    Quote Originally Posted by vinmontRD
    No - that would never have worked with this proxy trick. The proxy workaround, in combination with T-Zones, allowed you to get Internet web access that was normally not allowed with T-Zones (which is very restrictive).

    The @tmo.blackberry.net email address is explicitly part of BIS (blackberry internet services), and you won't get that unless you have a Blackberry plan or add-on. Even the normal "t-mobile internet" plans don't get you that. However: if you have any kind of plan with T-Mobile, you DO have an email address (think is was your phone number @tmomail.net - but I'm not certain).
    yeah you do have the PHONENO.@tmomail.net email address

    but you have to go to your internet explorer at home in order to access it
    Bold - 5.0.0.93 / 8310 - 4.5.0.81 ---- AT&T
    8330 - 4.5.0.77 ---- Sprint


    Blackberry's are a lifestyle

    jeff.kaiser88@yahoo.com

  4. #19
    theroadkill's Avatar
    theroadkill no está en línea Stack level 2
    Join Date
    Oct 2006
    PIN/ID
    UponRqst
    Posts
    56
    Quote Originally Posted by jkai2188
    yeah you do have the PHONENO.@tmomail.net email address

    but you have to go to your internet explorer at home in order to access it
    As memory serves that is an alias for SMS not an actual email address..

  5. #20
    vinmontRD's Avatar
    vinmontRD no está en línea Stack level 3
    Join Date
    Jul 2007
    Posts
    415

    Re: T-Mobile Data Plan for 4.99

    Quote Originally Posted by theroadkill
    As memory serves that is an alias for SMS not an actual email address..
    I just checked out T-Mobile's write up on this. It's interesting - it's a bit more than just a way to deal with SMS. T-Mobile apparently has a special gateway set up that handles SMS/MMS to email, and email to SMS/MMS, and this process lives in the tmomail.net domain.

    This is probably a bigger reply than most are looking for, but it's pretty interesting. From TMo:

    Mobile-to-mobile:
    Send/receive multimedia messages from/to MMS capable devices (mobile to mobile)
    1. The WAP Gateway (WAP GW) is the entry point of client devices to the operator-messaging environment. The WAP Gateway accepts the MMS sent by user A. Then, the WAP Gateway provider sends the MMS message to the MMSC for temporary storage.
    2. Before accepting the MMS, a check of the submitter is done for the request. User A is checked against the internal database to determine if the MMS service has been provisioned for him. If the request is accepted, the message is downloaded from the terminal.
    3. A notification message is constructed. The MMSC requests the WAP Push Proxy Gateway (WAP PPG) to send the notification. The PPG then requests the SMSC to send the notification, which goes via SMS to user B. The SMS is transparent to the user; the user will not see an SMS. The notification SMS (a binary SMS) informs the MMS client in the phone that a message is waiting to be fetched. The MMS client then asks the WAP client to fetch the respective message from the MMSC.
    4. When user B sends a request to retrieve the MMS, the user's terminal attempts to fetch the message. The output of either the original message (in the case of no media conversion) or the converted message is then downloaded to the terminal of user B via the WAP GW. The message should be deleted from the queue only if the download is successful. If a delivery report was requested, and the user of the terminal complies, a delivery report is generated and delivered to the originator. The same example follows for a read/reply request

    Mobile-to-e-mail or e-mail-to-mobile:
    Send/receive MMS messages to/from e-mail clients (mobile to/from e-mail). In the case of MMS-to-e-mail, the MMSC will deliver the MMS message to the SMTP (Simple Mail Transfer Protocol) relay for sending through the Internet.
    The MMS users can also be addressed from the Internet via e-mail. Any MMS user in VoiceStream® will be addressed as MSISDN@tmomail.net. The SMTP relay will receive the e-mail and forward it to the MMSC for delivery. The delivery takes place in the same manner as for mobile-to-mobile, starting with the notification.

    When an MMS message contains text (in a single slide or part of multiple slides), the text will be sent as part of the e-mail body, and the sound and picture elements will be sent as attachments.

    The MMS-to-email path passes most attachments through intact, but does some limited transcoding as needed to match appropriate message format standards.



    The email-to-MMS path automaticatlly resizes graphics attachments, and also transcodes as appropriate for industry standard compatibility. NOTE: All images will be resized to 160x120 pixels if they are larger.


    Legacy
    The MMS will enable legacy device support using the T-Mobile text messaging service. The T-Mobile text messaging service and MMS share the tmomail.net e-mail domain. This means that an MMS capable customer addressed as MSISDN@tmomail.net receives an e-mail in the form of an MMS message, if the message contains media of type image or sound or text longer than 160 characters. A text e-mail that is shorter than 160 characters will still be delivered to the MMS customers as a T-Mobile text messaging message. A legacy customer will still be able to receive and send e-mail as before from the T-Mobile text messaging service. An existent alias a customer may have will work even if the customer starts using MMS. This means that if user A was using alias@tmomail.net and now has an MMS device, he will be able to receive e-mails in the form of MMS messages addressed as alias@tmomail.net. Similarly, when originating an MMS message for an e-mail address, its address will be alias@tmomail.net.


    If an MMS customer sends an MMS message to a user that is legacy, the MMSC will forward the message to the T-Mobile text messaging platform for delivery. The MMSC will send another MMS message to the originator stating that the destination does not have an MMS capable phone and that the message was delivered as SMS.


    Here's a link for the intrepid reader:
    http://support.t-mobile.com/knowbase...ic/tm21396.htm

Page 2 of 2 FirstFirst 12

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •