Version 1.0.0.86 was released on 27/11/2010 and it includes the following changes:
— Fixed critical bug: connection loss without recovering it
- Fixed bug: removing email body from cache after delete or mark read
- Removed: email address validation when adding account
Version 1.0.0.85 was released on 19/11/2010 and it includes the following changes:
— Support for long email addresses
- Can run even if the website is down
- Fold \ unfold from the tray icon
- Better handling of sleep and wake up
- Better synchronization between the polling thread and the application
here it is …
1. Run UAC
2. Disable UAC
Now, open Gmail Notifier preferences,
and select the ‘Use Gmail for mailto links’.
Once done, you can revert the UAC back to its original status.
Filmed with a Canon EOS 5d Mark II:
Gmail Notifier is using IMAP to communicate with Gmail, but I obviously didn’t write an implementation of the IMAP protocol but rather used for something that is ready to work with.
So like about any subject that I wish to dig into, I went to Google to search for an IMAP library. Since the software is written in C++ \ MFC, I had to find a lib that will fit.
So eventually I selected to work with Chilkat software. Although it isn’t an open source project and is a commercial package, it was good because it gave me all I needed and not just the IMAP, but also a solution for encryption and decryption of the user name and password. It also has tons of sample code which was almost good for copy paste. A great over all library but it lacks one important thing, the ability to fetch email body, leaving the attachment (if any) on the server. But it does have the option to send raw IMAP commands so it leaves an open door for that.
Very early versions of my Gmail Notifier simplified the Gmail login operation by launching the default web browser directly into the Gmail account. Since the software could use the stored password and user name to do that, it was very easy to duplicate the same process that Google did to login. But then one day, Google decided to put an end to this back door and to protect users from using all kind of third party applications that promise to login to the Gmail account. Problem was that some applications actually formed a URL that could really login, but they forgot that browsers cache URLs and keep them in history. So to create a protection that will prevent that from happening, Google added a random factor to each login session. This actually can be referred to as authentication. Now when the entire login process is authenticated, it is impossible to login from an external application like Gmail Notifier.