Article View: aus.comms.mobile
Article #654Re: "SEND TEXT AS EMAIL" option
From: John Henderson
Date: Sun, 29 May 2011 06:26
Date: Sun, 29 May 2011 06:26
71 lines
3792 bytes
3792 bytes
Rod Speed wrote: > John Henderson wrote >> Rod Speed wrote > >>> Yeah, it may well be such a dinosaur that no one bothered to support it. > >> There is a spec for SMS <=> email interoperability. > > Not the way he wants to do it, send text as email. Maybe. But the original question was about the "SEND TEXT AS EMAIL" option on an old Nokia. >> Phones seem to support it, but not our telcos. > >> To quote GSM 03.40, section 3.8: > >> "The interworking between Internet electronic mail and SMS is >> offered in both directions which enables new and old mobiles to >> send/receive Internet electronic mails via SMS." > > He's actually talking about doing the exact opposite, sending text as email, not as SMS. I reckon the option on the old Nokia is offering to send text as an SMS to a GSM 03.40 compliant email gateway. >> There's a specific PID (Protocol ID) value reserved for its use in SMS >> headers. This carries over into the 3G/UMTS specification 3GPP 23.040, >> and will undoubtedly continue as a potential feature into 4G/LTE. > > Sure, but thats the opposite of what he wants to do. > > All the current smartphones that do email have to be setup with > the email server you want to use in the same way that PC email > clients do, particularly with the url or ip of the email server and > the username and password to use. No argument from me here - I've used that mechanism on phones for years. > Come to think of it, its not at all clear how the Nokia 7250i can > do email even if you can find the mobile number to send it to > because it has no way to specify the username and password > even if the number does specify the email server to use. The formats are covered in GSM 03.40 and 3GPP 23.040, section 3.8.1. In an outgoing SMS, the required text format for en email is: [<to-email-address><space>]<message> with an incoming SMS having the format: [<from-email-address><space>]<message> As I understand it, any requirement for user authentication should be greatly simplified by the user of this service having physical possession of the SIM. That does leave the question of how a copy of mail addressed to <to-email-address> ends up at an SMS gateway which knows how to handle it. But that should be relatively simple to configure in advance, both technically and administratively. I'm guessing that the user of the service might need to login to the SMS gateway initially, and provide the authentication needed to fetch future traffic. John
Technical Details
Message-ID:
<94e782Fu50U1@mid.individual.net>Path:
arc1-ca.pugleaf.net!g2news2.google.com!news4.google.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mailReferences:
<1105100000052.10May11$rookswood@suburbian.com> <92qrmaFa3U1@mid.individual.net> <1105180000326.18May11$rookswood@suburbian.com> <93fvvmFuolU1@mid.individual.net> <1105230003216.23May11$rookswood@suburbian.com> <93t565FtvsU1@mid.individual.net> <1105260002549.26May11$rookswood@suburbian.com> <9453jlF892U1@mid.individual.net> <1105280142919.28May11$rookswood@suburbian.com> <94buojFqcfU1@mid.individual.net> <94d76iFdc1U1@mid.individual.net> <94djnqF3gaU1@mid.individual.net>Show Full Headers
Complete Article Headers
X-Google-Thread: fb718,f2c77efef8410f34 X-Google-NewGroupId: yes X-Google-Attributes: gid5e83424db6,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: arc1-ca.pugleaf.net!g2news2.google.com!news4.google.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: John Henderson <jhenRemoveThis@talk21.com> Newsgroups: aus.comms.mobile Subject: Re: "SEND TEXT AS EMAIL" option Date: 29 May 2011 06:26:11 GMT Lines: 72 Message-ID: <94e782Fu50U1@mid.individual.net> References: <1105100000052.10May11$rookswood@suburbian.com> <92qrmaFa3U1@mid.individual.net> <1105180000326.18May11$rookswood@suburbian.com> <93fvvmFuolU1@mid.individual.net> <1105230003216.23May11$rookswood@suburbian.com> <93t565FtvsU1@mid.individual.net> <1105260002549.26May11$rookswood@suburbian.com> <9453jlF892U1@mid.individual.net> <1105280142919.28May11$rookswood@suburbian.com> <94buojFqcfU1@mid.individual.net> <94d76iFdc1U1@mid.individual.net> <94djnqF3gaU1@mid.individual.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Trace: individual.net AyBQot0BIGzvJViFSepCAwr8f29FHrcitxP3GKzTuThHrE8gc= Cancel-Lock: sha1:hJscF3uWzRwPLgRBVsfysIubrRI= User-Agent: XPN/1.2.6 (Street Spirit ; Linux)