GNOME Bugzilla – Bug 317794
Groupwise mail folder not visible
Last modified: 2005-12-14 15:28:50 UTC
Distribution/Version: SuSE Linux 10 1. I have around 20 folders (including Mailbox, cabinet, trash, sent mails and other system folders) in my groupwise account. 2. One particular folder that was visible in the earlier versions (2.4.x on SLP 10) is currently not visible. 3. On the console (from where I have started evolution) I get the following message when its trying to fetch the summary for that particular folder: (The folder name is "kernel & research @ suse.de" ------------------------------------------------------------------------------ adding hook target 'source' (evolution:5876): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:5876): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:5876): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:5876): Gdk-CRITICAL **: gdk_gc_set_foreground: assertion `GDK_IS_GC (gc)' failed (evolution:5876): GnomeCanvas-CRITICAL **: gnome_canvas_request_redraw: assertion `GNOME_IS_CANVAS (canvas)' failed BBDB spinning up... (evolution:5876): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:5876): Gdk-CRITICAL **: gdk_gc_set_foreground: assertion `GDK_IS_GC (gc)' failed (evolution:5876): Gdk-CRITICAL **: gdk_gc_set_foreground: assertion `GDK_IS_GC (gc)' failed calendar-gui-Message: Check if default client matches (1126778712.19463.1@ssoni-test 1126778712.19463.4@ssoni-test) (evolution:5876): Gtk-CRITICAL **: gtk_entry_set_text: assertion `text != NULL' failed (evolution:5876): Gtk-CRITICAL **: gtk_tree_sortable_set_sort_column_id: assertion `GTK_IS_TREE_SORTABLE (sortable)' failed (evolution:5876): Gdk-CRITICAL **: gdk_gc_set_foreground: assertion `GDK_IS_GC (gc)' failed (evolution:5876): eab-widgets-CRITICAL **: eab_view_discard_menus: assertion `view != NULL' failed (evolution:5876): Gdk-CRITICAL **: gdk_gc_set_foreground: assertion `GDK_IS_GC (gc)' failed (evolution:5876): libegroupwise-CRITICAL **: e_gw_connection_mark_read: assertion `E_IS_GW_CONNECTION (cnc)' failed (evolution:5876): eab-widgets-CRITICAL **: eab_view_discard_menus: assertion `view != NULL' failed (evolution:5876): Gtk-CRITICAL **: gtk_entry_set_text: assertion `text != NULL' failed (evolution:5876): Gtk-CRITICAL **: gtk_tree_sortable_set_sort_column_id: assertion `GTK_IS_TREE_SORTABLE (sortable)' failed (evolution:5876): Gdk-CRITICAL **: gdk_gc_set_foreground: assertion `GDK_IS_GC (gc)' failed (evolution:5876): calendar-gui-CRITICAL **: gnome_calendar_add_source: assertion `E_IS_SOURCE (source)' failed calendar-gui-Message: Check if default client matches (1126778712.19463.4@ssoni-test 1128315243.5876.5@ssoni-test) (evolution:5876): GLib-GObject-WARNING **: value "-1.000000" of type `gdouble' is invalid or out of range for property `clip-height' of type `gdouble' calendar selection changed calendar selection changed ** kernel & Research @ suse.de **: No summary as yet : using get cursor request (evolution:5876): GLib-CRITICAL **: g_ascii_strcasecmp: assertion `s1 != NULL' failed (evolution:5876): camel-CRITICAL **: camel_folder_free_message_info: assertion `info != NULL' failed (evolution:5876): camel-CRITICAL **: camel_folder_free_message_info: assertion `info != NULL' failed (evolution:5876): camel-CRITICAL **: camel_folder_free_message_info: assertion `info != NULL' failed (evolution:5876): camel-CRITICAL **: camel_folder_free_message_info: assertion `info != NULL' failed (evolution:5876): camel-CRITICAL **: camel_folder_free_message_info: assertion `info != NULL' failed (evolution:5876): camel-CRITICAL **: camel_folder_free_message_info: assertion `info != NULL' failed -------------------------------------------------------------------------------- Is there any limit on the number/type of characters the folder name can have ? OR Is there any limit to the number of folders evolution can display in the client for any particular account. This is specifically happening in the Groupwise account.
When you try to access via IMAP, can you see the missing folders? Start evo from console after with the GROUPWISE_DEBUG env. variable set and look-in the getFolderListResponse message (for gw SOAP Access). Check if you get the folder in that SOAP response. If the folder is not returned in this list, this must be filed in the server.
Sankar: I can't access the same server with IMAP as its not enabled for IMAP access. Another thing is that, I was able to see the folder till the last build and the problem started only after updating my build to the latest one. The evolution build I have is: evolution-data-server-1.4.0.0.200509261646-0.snap.novell.0.1 evolution-exchange-2.4.0.0.200509261646-0.snap.novell.0.1 evolution-2.4.0.0.200509261646-0.snap.novell.0.1 evolution-webcal-2.4.0.1.0.200509261646-0.snap.novell.0.1 evolution-pilot-2.4.0.0.200509261646-0.snap.novell.0.1
I am using Evolution 2.4.1 to check a Groupwise 6.54 server via IMAP. If I use plain IMAP, I can see all of my folders, but if I use IMAPv4rev1, I have missing folders. This did not happen to my previous Evolution, which was 2.2.3. I was able to solve the problem by connecting as regular IMAP, and then subscribing to the missing folders. When I tried to use the Subscribe functionality via IMAP4, Evolution told me that the server did not support it. It did support it as regular IMAP, though, and after subscribing the folders showed back up whenever I switched to IMAP4. I tried changing the account type to Groupwise. It then asked me for my password, and took it without a complaint. As soon as I exit the dialog, it tells me that it Failed to autenticate and asks for the password again. It won't take the same password that works when accessing the account through IMAP. This used to work when I ran Evolution 2.0.x, but not with Evolution 2.2.3 or 2.4.1. I ran 2.4.1 with GROUPWISE_DEBUG set, and this is all it prints (although I think it repeats it more than once) when it tries to authenticate: ---------------------------------- POST /soap HTTP/1.1 SOAP-Debug: 0x8d065a0 @ 1130514355 Host: vprmail.tamu.edu Connection: Keep-Alive User-Agent: Evolution/1.4.1 Content-Type: text/xml SOAPAction: loginRequest <?xml version="1.0" encoding="UTF-8" standalone="no"?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/1999/XMLSchema" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"><SOAP-ENV:Body xmlns:types="http://schemas.novell.com/2003/10/NCSP/types.xsd" SOAP-ENV:encodingStyle=""><loginRequest><types:auth xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="types:PlainText"><types:username>mdwyer</types:username><types:password>XXXXXXXX</types:password></types:auth></loginRequest></SOAP-ENV:Body></SOAP-ENV:Envelope> gw connection dispose gw connection finalize -------------------------------- We have a Groupwise 7 test server, however, that Evolution 2.4.1 has no problem connecting to. I hope that there's something here that helps, I would really like to use continue using Evolution with our Groupwise server here at work. Please let me know what information I should collect for you next. Thanks, Mike
Thanks for the report Mike. Here are a few things: * Firstly, IMAP4rev1 is still experimental, and is not completely supported by the team, so i suggest you to stick to IMAP, which is tested. At this time, the difference between IMAP and IMAP4rev1 implementations in Evolution is that IMAP does *not* support namespaces completely which IMAP4rev1 does. * A few folders are *not* subscribed by default, and you really need to subscribe them. So not displaying folders that are not subscribed to is the right way. Ofcourse, IMAP4vrev1 reporting that server does not support subsciptions is purely a server issue, will have to talk to the server team regarding that. * Regarding the problem with groupwise protocol, i think you have not specified the right port. it should either be 8201 or 7191. The GROUPWISE_DEBUG traces you attached suggests that Evolution is not able to connect to the server itself. Hope this helps. Thanks
Created attachment 55989 [details] [review] proposed patch
Fix committed to HEAD and stable branch