Re: [Evolution-hackers] IMAP vs. IMAPX in Evo 2.30--recommendations?
On Tue, 2010-06-29 at 15:22 -0400, Paul Smith wrote: Hi all. I'm wondering if anyone can provide a summary/recommendation for IMAP vs. IMAP+ (IMAPX) in Evo 2.30 (I'm actually building the very latest gnome-2.30 branch from git)? I use a dovecot IMAP server which I don't think supports any of the advanced IMAP features (?), Um, I'm using Dovecot to test the QRESYNC support (which I just committed to master). $ ssh twosheds /usr/sbin/dovecot --exec-mail imap * PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS] Logged in as dwmw2 The only thing I want to use that it doesn't yet support is NOTIFY. but I see that the IMAPX implementation in Evo is constantly being fixed/updated (by David Woodhouse lately) while the IMAP backend seems stagnant (or stable?). Should I switch my accounts to use IMAPX instead of IMAP? I think so. What about (does anyone know) connecting to Exchange servers using Exchange's IMAP? Should I be using IMAPX there? As long as you're using 2.30.2 or later, yes. There are some IMAPX fixes in 2.30.2 which you wouldn't want to be without, including a workaround for the fact that the crappy Exchange server lies to clients about RFC822.SIZE, leading to truncated mails. -- David WoodhouseOpen Source Technology Centre david.woodho...@intel.com Intel Corporation ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] [evolution-kolab] IMAPX and sync- vs. async-Backends
On Tue, 2010-06-29 at 16:14 +0200, Christian Hilberg wrote: Hi there, reading about the new IMAPX implementation used by Evo =2.30, I found it stated that Maybe if imapx had come up before, many backends such as groupwise, mapi etc. would have followed this design rather than a sync one. -- Chenthill in [1] Does this mean that the Camel IMAPX code is ready to support a backend like ours (for Kolab2) to be implemented as an async one rather than a sync one (which is the case for the MAPI-, Exchange- and SCALIX-Backends (and maybe others, too))? The internal implementation of IMAPX provider is async, the requests would be pipelined and run based on priority. Which means that one would be able to fetch multiple messages parallely unlike other providers where its sequential. Though one would have to still use the sync api's which camel provides. Adding new camel async api's is a task for future. - Chenthill. Best regards, Christian [1] http://chenthill.wordpress.com/2010/01/11/evolution-with-improved-imap-support-imapx/ ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] IMAP vs. IMAPX in Evo 2.30--recommendations?
On Wed, 2010-06-30 at 11:03 +0100, David Woodhouse wrote: On Tue, 2010-06-29 at 15:22 -0400, Paul Smith wrote: Hi all. I'm wondering if anyone can provide a summary/recommendation for IMAP vs. IMAP+ (IMAPX) in Evo 2.30 (I'm actually building the very latest gnome-2.30 branch from git)? I use a dovecot IMAP server which I don't think supports any of the advanced IMAP features (?), Um, I'm using Dovecot to test the QRESYNC support (which I just committed to master). I have an older version than you, I guess, because I don't have all those things (although I see I do have IDLE which is nice): * CAPABILITY IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS UIDPLUS LIST-EXTENDED I18NLEVEL=1 QUOTA AUTH=PLAIN AUTH=LOGIN This is the standard IMAP server at my ISP so I can't really change it (as far as I know). What about (does anyone know) connecting to Exchange servers using Exchange's IMAP? Should I be using IMAPX there? As long as you're using 2.30.2 or later, yes. There are some IMAPX fixes in 2.30.2 which you wouldn't want to be without, including a workaround for the fact that the crappy Exchange server lies to clients about RFC822.SIZE, leading to truncated mails. Yep, I'm using the latest content of the git gnome-2.30 branch, checked out/built this morning. I've switched over so I'll let you know if there are any issues, thanks! ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
[Evolution-hackers] evolution-data-server binary breakage
Hi, I have found that evolution-data-server-2.30.1 installs libedataserver as libtool version 11 (libedataserver-1.2.so.11) whereas evolution-data-server-2.30.2.1 installs it as libtool version 13 (libedataserver-1.3.so.13). I didn't spot this until I was half-way through installing gnome-2.30.2 and empathy ceased working. Now that I have got half-way through I am inclined to carry on as I will have to recompile something or other. Do you by any chance know what in gnome-2.30 has a dependency on libedataserver apart from empathy and will now be broken? It would do people a favour if you could announce when you are doing binary breakage on a minor release point. Doesn't this also breach gnome guidelines? Chris ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] evolution-data-server binary breakage
On Wed, 2010-06-30 at 22:20 +0100, Chris Vine wrote: I have found that evolution-data-server-2.30.1 installs libedataserver as libtool version 11 (libedataserver-1.2.so.11) whereas evolution-data-server-2.30.2.1 installs it as libtool version 13 (libedataserver-1.3.so.13). Rationale for the change is here: https://bugzilla.gnome.org/show_bug.cgi?id=619184 ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] evolution-data-server binary breakage
On Wed, 30 Jun 2010 17:36:51 -0400 Matthew Barnes mbar...@redhat.com wrote: On Wed, 2010-06-30 at 22:20 +0100, Chris Vine wrote: I have found that evolution-data-server-2.30.1 installs libedataserver as libtool version 11 (libedataserver-1.2.so.11) whereas evolution-data-server-2.30.2.1 installs it as libtool version 13 (libedataserver-1.3.so.13). Rationale for the change is here: https://bugzilla.gnome.org/show_bug.cgi?id=619184 Ah OK, thanks. Can you help me on what gnome components compiled for gnome-2.30.0/1 might now be broken and require recompilation (apart from evolution itself, that is)? It looks from that bug report as if that will include ekiga, as well as empathy. Something in the README on this would have been a kindness: I can see than not complying with gnome release rules might be the lesser of two evils but it is handy to know about it. Chris ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] evolution-data-server binary breakage
On Wed, 2010-06-30 at 22:53 +0100, Chris Vine wrote: Can you help me on what gnome components compiled for gnome-2.30.0/1 might now be broken and require recompilation (apart from evolution itself, that is)? It looks from that bug report as if that will include ekiga, as well as empathy. Given the same situation again I would not agree to such a change now that I'm fully aware of the extent of the pain it causes. Instead I would have tracked down exactly which projects are affected by the removed symbols (in this case probably not that many) and notified each project individually. Packages requiring recompilation on Fedora 13 were: $ repoquery --whatrequires --alldeps libedataserver-1.2.so.11 | sort almanah-0:0.7.2-1.fc13.i686 anerley-1:0.1.8-3.fc13.i686 anjal-0:0.3.2-1.fc13.i686 contact-lookup-applet-0:0.17-3.fc12.i686 contacts-0:0.9-5.fc13.i686 dates-0:0.4.11-3.fc13.i686 deskbar-applet-0:2.30.0-1.fc13.i686 ekiga-0:3.2.6-2.fc13.i686 empathy-0:2.30.1-2.fc13.i686 evolution-couchdb-0:0.3.2-2.fc13.i686 evolution-sharp-0:0.21.1-5.fc13.i686 giggle-0:0.4.96-1.fc13.i686 glabels-0:2.2.7-1.fc13.i686 gnome-launch-box-0:0.4-17.fc13.i686 gnome-panel-0:2.30.0-1.fc13.i686 gnome-phone-manager-0:0.65-5.fc12.i686 gnome-phone-manager-telepathy-0:0.65-5.fc12.i686 gnome-python2-evolution-0:2.30.0-2.fc13.i686 jana-0:0.4.5-0.3.20090622gitb416a41.fc12.i686 libopensync-plugin-evolution2-1:0.22-3.fc13.i686 mail-notification-evolution-plugin-0:5.4-18.fc13.i686 moblin-panel-myzone-0:0.0.13-2.fc13.i686 moblin-panel-people-0:0.0.10-4.fc13.i686 nautilus-sendto-0:2.28.4-1.fc13.i686 planner-eds-0:0.14.4-18.fc13.i686 ruby-revolution-0:0.5-3.svn210.fc12.i686 syncevolution-0:0.9.2+1.0alpha1-1.fc13.i686 tasks-0:0.16-2.fc12.i686 tracker-search-tool-0:0.8.4-1.fc13.i686 ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
