This should apply for the K750i as well. The w800i phone has a built-in POP email client. GMail uses SSL for both POP and SMTP e-mail transfers.  The w800i has support for SSL/TLS in its mail client.

However, the phone does not come with two root certificates required to get Gmail to work. Gmail uses two different certificates on pop.gmail.com and smtp.gmail.com, and each of these certificates are issued by two certification authorities. The trick to get gmail to work is simply install the root certificates of these two CAs. These are Thawte and Equifax.

To get the root certificates, open the Certificates manager in Windows XP or 2000 ( open a blank Microsoft Management Console , by typing mmc at the command prompt, and then add the Certificates snap-in). In the certificates tree, under Trusted Root Certification Authorities , find the certificate for Equifax Secure Certification Authority and Thawte Premium Server CA.

Now, export each of these certificates in turn as a DER encoded binary X.509 certificate. Send these two files via a bluetooth or infrared link (does not work when the files are copied using file manager ). The phone will prompt to accept the certificates and you are good to go :).

Gmail also has a mobile interface at http://m.gmail.com, but this is not good enough to compose emails.

While working with the System.Timers.Timer class last week, I found that the timer_elapsed method is not synchronized, i.e the event is fired without waiting for the completion of the previous invocation.

Say for example you have a method that pulls up the latest records from a table and do some processing. The timer event can fire while you are doing this processing and have still not marked the records as processed. The safe way is to wrap the code in the timer_elapsed event inside a lock statement.

I was reading a blog post on blogs.msdn.com about why each version of VS is tied to a version of the runtime, and the reasons why multiple versions of the runtime are not supported. Anyways I can't find the link :).

For VS 2005, an add-in is under development to build under 1.1.  Targetting the latest version of  .Net is viable for server side projects (ASP .Net etc..). However, for client applications this is not always possible.  The majority of Windows computers will now have the 1.1 Framework, so applications can be deployed without worrying too much about distributing a 20 MB runtime. It will probably take about 6 months to a year for the same thing to happen to the 2.0 Framework. Untill then, those developing for 1.1 are still stuck with an IDE that rewrites code, makes controls disappear and other magical stuff that makes one tear their hair out.

On the same topic, where can I find statistics on what percentage of Windows machines have what version of the runtime. Internet Explorer sends the .Net version on the UA string, so it might be possible to measure the usage of 2.0 versus 1.1 This should be easy for MS to pull up from their web server logs and publish the stats :)..