I hit the same thing that was discussed in http://bugs.meego.com/show_bug.cgi?id=8980: Google servers just wouldn't send "new-mail" notifications. Turns out the culprit is another google xmpp extension: this is needed before the server sends any notifications: <iq type='set' id='user-setting-3'> <usersetting xmlns='google:setting'> <mailnotifications value='true'/> </usersetting> </iq> https://code.google.com/apis/talk/jep_extensions/usersettings.html#3 I've got a patch, will attach in a moment.
Created attachment 50826 [details] [review] mail notification: ensure google notification setting is correct
Actually to be _really_ correct we should check for NS_GOOGLE_SETTINGS in connection.c:connection_disco_cb() and define GABBLE_CONNECTION_FEATURES_GOOGLE_SETTINGS... I can fix that (but not right now, my dogs demand attention).
(In reply to comment #2) > Actually to be _really_ correct we should check for NS_GOOGLE_SETTINGS in > connection.c:connection_disco_cb() and define > GABBLE_CONNECTION_FEATURES_GOOGLE_SETTINGS... > > I can fix that (but not right now, my dogs demand attention). Fair enough, but asside that this patch looks good. Let me know when it's ready.
Created attachment 50828 [details] [review] mail notification: recognize "google:setting" namespace
Created attachment 50829 [details] [review] mail notification: ensure google notification setting is correct Ok, these two patches should do it.
Patches are in git as well just in case that fits your work flow better: git://github.com/jku/telepathy-gabble.git (branch bug40565)
Merged upstream. Will be in next unstable 0.13.6 release. If you need it in stable .12 release let us know, we will discuss this possibility.
We need this in a stable .12 release.
Ok, it's in .12 branch now. Will, let us know when there is a new release.
I have released 0.12.7 with this fix: http://lists.freedesktop.org/archives/telepathy/2011-September/005736.html
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.