The last mobile for which I shelled out some cash was the Sony Ericsson K700i. It's a nasty, cheap, appallingly-made little device, purchased only because it was, at the time, Vodafone CZ's lowest price offering with Bluetooth.
Admittedly, I am particularly tight when it comes to spending my own money on phones - caused partly by the resentment I feel towards the planned obsolescence that's inherent within every handset on the market; but mainly, if I'm honest, thanks to my employer's generosity in keeping me knee-deep in new toys for which I don't have to pay.
When I buy my own phone with my own hard-earned cash, there are only really two things that it has to do to keep me happy: 1) Make phone calls; and 2) Let me check my Email. But being able to do the latter of these two activities still, bizarrely, seems to surprise and impress all of my friends who have the latest and greatest shiny Scandinavian communicators.
Technologically, the tools required to send and receive Emails from mobiles have been around for donkeys' years: GPRS and a built-in web browser. You'd be hard pressed to find a phone still in existence which didn't have them. And yet, only the barest minimum of people actually seem to be Emailing on the move - mainly, those who've spent a lot of cash on a Blackberry, had their company's IT department set it up for them, and who have an enormous monthly data bill thanks to every Email being pushed to them wherever they happen to be. And if they go abroad, they either end up with a seriously inflated bill, or just disable the facility entirely.
About the Code
ChrisLacey.MobileEmail.Web is a trivial bit of code which, when hosted on a .NET web server, will enable you to send and receive Emails with the cheapest phones whilst invoking the smallest possible data transfer costs.
It's built with the one priority of being functional, whilst using the minimal possible amount of bandwidth. Each page is generally under 2KB in size, and contains the smallest amount of information to be useful:
The security model in use is one that would undoubtedly raise the eyebrows of a network manager or two, but it's one that provides the correct balance of utility and security for the kind of messages I receive. The password (optional) is supplied by means of a querystring on the URL, enabling you to bookmark it in its entirety, and not forcing you to stop to enter a password every time you connect. It's also possible to tighten things up a little by restricting access to certain hosts (e.g. vodafone.cz if you want to limit its use to a single phone network).
This model is right for me because my principal priority is checking mail quickly, and the implications of somebody hacking into it are minimal - I don't tend to receive many messages which might compromise national security. But, depending on situation, that won't necessarily hold true for everyone and so it's worth noting that, should someone steal your phone or sniff traffic on the network, there will be a chance of your messages being compromised until you get round to changing your password.
All source code is distributed as public domain. Please feel free to distribute and modify for your own purposes without restriction.
The Chilkat Email component is copyright Chilkat, hence the package cannot, unfortunately, be released as free software. Please do not use this component for any other purpose without purchasing a developer licence from Chilkat.
Simply place any required signature within this file. It will be automatically appended to every Email sent (new messages and replies).
The appSetting keys are as follows: