Comments for MesQuilla http://mesquilla.com Messaging with Mozilla by rkent Thu, 04 Mar 2010 10:21:49 +0000 http://wordpress.org/?v=2.9.2 hourly 1 Comment on Mailnews Exchange Support: basic mail infrastructure by Wim http://mesquilla.com/2010/03/03/mailnews-exchange-support-basic-mail-infrastructure/comment-page-1/#comment-114 Wim Thu, 04 Mar 2010 10:21:49 +0000 http://mesquilla.com/?p=619#comment-114 He rkent, really good progress in such short time, although you might think otherwise. Please keep us posted on your great work! He rkent, really good progress in such short time, although you might think otherwise. Please keep us posted on your great work!

]]> Comment on Mailnews Exchange Support: basic mail infrastructure by Gary Kwong http://mesquilla.com/2010/03/03/mailnews-exchange-support-basic-mail-infrastructure/comment-page-1/#comment-113 Gary Kwong Thu, 04 Mar 2010 01:00:16 +0000 http://mesquilla.com/?p=619#comment-113 Hi Kent, this seems like great work - even though it may seem trivial to some people, please keep it up and push on! I'm sure many others will be grateful for the hard work that has been put in. :) Hi Kent, this seems like great work – even though it may seem trivial to some people, please keep it up and push on! I’m sure many others will be grateful for the hard work that has been put in. :)

]]> Comment on Toward mailnews Exchange Web Services support: SOAP calls by MesQuilla » Blog Archive » Mailnews Exchange Support: basic mail infrastructure http://mesquilla.com/2010/02/01/toward-mailnews-exchange-web-services-support-soap-calls/comment-page-1/#comment-112 MesQuilla » Blog Archive » Mailnews Exchange Support: basic mail infrastructure Wed, 03 Mar 2010 22:31:48 +0000 http://mesquilla.com/?p=593#comment-112 [...] my last report, I was testing and updating the old Mozilla SOAP framework for use in communicating with Exchange [...] [...] my last report, I was testing and updating the old Mozilla SOAP framework for use in communicating with Exchange [...]

]]> Comment on JunQuilla by MesQuilla » Blog Archive » Combining Thunderbird with SpamAssassin http://mesquilla.com/extensions/junquilla/comment-page-1/#comment-108 MesQuilla » Blog Archive » Combining Thunderbird with SpamAssassin Sat, 13 Feb 2010 01:23:00 +0000 http://mesquilla.com/?page_id=388#comment-108 [...] This image uses the “Junk Analysis Detail” report from my JunQuilla extension. [...] [...] This image uses the “Junk Analysis Detail” report from my JunQuilla extension. [...]

]]> Comment on Inherited Folder Properties by rkent http://mesquilla.com/2009/03/06/inherited-folder-properties/comment-page-1/#comment-107 rkent Wed, 10 Feb 2010 23:16:29 +0000 http://mesquilla.com/?p=227#comment-107 I'm not sure specifically which UI you are referring to here, as I am currently using inherited properties in several addons. But in general, the beauty of inherited folder properites is that if you don't like to apply it at the folder level, you can apply it at the account level, or globally. Most of my extensions also include the account-level option as well, or if you know the property you can always add it yourself using preferences. So which particular feature are you trying to apply to an account? I’m not sure specifically which UI you are referring to here, as I am currently using inherited properties in several addons. But in general, the beauty of inherited folder properites is that if you don’t like to apply it at the folder level, you can apply it at the account level, or globally. Most of my extensions also include the account-level option as well, or if you know the property you can always add it yourself using preferences.

So which particular feature are you trying to apply to an account?

]]> Comment on Inherited Folder Properties by blankety blank http://mesquilla.com/2009/03/06/inherited-folder-properties/comment-page-1/#comment-106 blankety blank Wed, 10 Feb 2010 22:40:34 +0000 http://mesquilla.com/?p=227#comment-106 My IMAP server has all folders at the top level (same level as INBOX) by default, and doesn't allow certain folders like Trash to be moved to be subfolders of INBOX so this doesn't help me (it doesn't work in 3.0.1). There in no UI to enable / disable filters for INBOX (I assume it's hardcoded to true) but would it be possible to add this UI to the account, since all folders appear as children of the account in Thunderbird's "All Folders" view? My IMAP server has all folders at the top level (same level as INBOX) by default, and doesn’t allow certain folders like Trash to be moved to be subfolders of INBOX so this doesn’t help me (it doesn’t work in 3.0.1). There in no UI to enable / disable filters for INBOX (I assume it’s hardcoded to true) but would it be possible to add this UI to the account, since all folders appear as children of the account in Thunderbird’s “All Folders” view?

]]> Comment on Toward mailnews Exchange Web Services support: SOAP calls by rkent http://mesquilla.com/2010/02/01/toward-mailnews-exchange-web-services-support-soap-calls/comment-page-1/#comment-104 rkent Thu, 04 Feb 2010 17:26:29 +0000 http://mesquilla.com/?p=593#comment-104 Response to Leni: I'm in the process of trying to understand SOAP better myself, but from my current understanding I would characterize the EWS SOAP as RPC style. "you might be better off building special-purpose helper libraries on top of XMLHttpRequest" I am only using a fraction of the webservices extension, and currently plan to build special-purpose helper libraries on top of that. The portion of the webservices extension I am using translates to/from XML into an intermediate format, where information is organized into nsIPropertyBag objects (and I have added some nsIArray to the mix). I still have to have another layer that will translate that to/from the Mozilla mailnews formats. I guess what you are saying is that I can use XML tools like XPath to do some of those same operations. I'll have to give that a try as well before I get too committed to my current path. "the webservices extension has more than it’s fair share of edge-case bugs" and so do other SOAP libraries. For example, I read that the AXIS2 library does not work with Exchange Server Web Services. If I am going to fix bugs, I would rather do it in the Mozilla environment at this point in my experience. And I am committed to doing any fixes that I need to the webservices code. Response to Leni:

I’m in the process of trying to understand SOAP better myself, but from my current understanding I would characterize the EWS SOAP as RPC style.

“you might be better off building special-purpose helper libraries on top of XMLHttpRequest”

I am only using a fraction of the webservices extension, and currently plan to build special-purpose helper libraries on top of that. The portion of the webservices extension I am using translates to/from XML into an intermediate format, where information is organized into nsIPropertyBag objects (and I have added some nsIArray to the mix). I still have to have another layer that will translate that to/from the Mozilla mailnews formats. I guess what you are saying is that I can use XML tools like XPath to do some of those same operations. I’ll have to give that a try as well before I get too committed to my current path.

“the webservices extension has more than it’s fair share of edge-case bugs” and so do other SOAP libraries. For example, I read that the AXIS2 library does not work with Exchange Server Web Services. If I am going to fix bugs, I would rather do it in the Mozilla environment at this point in my experience. And I am committed to doing any fixes that I need to the webservices code.

]]> Comment on Toward mailnews Exchange Web Services support: SOAP calls by rkent http://mesquilla.com/2010/02/01/toward-mailnews-exchange-web-services-support-soap-calls/comment-page-1/#comment-103 rkent Thu, 04 Feb 2010 17:10:40 +0000 http://mesquilla.com/?p=593#comment-103 (Leni wanted to post this, but he had troubles so sent by private email instead): When I first began using SOAP I didn't understand the difference between a document-oriented SOAP api and an RPC-style API. What I learned was that clients of a document-oriented API get marginal value from a SOAP library in exchange for complexity. Most of the work is in: * understanding the document structure and relationships * parsing and building documents If Exchange is going with a document-oriented API (like Zimbra did), you might be better off building special-purpose helper libraries on top of XMLHttpRequest. That's what zindus did when it switched away from the webservices extension in <a href="http://www.zindus.com/blog/2008/03/07/testing-release-2008-03-07-soapurl-and-mozilla-soap/" rel="nofollow">march 08</a> and it was definitely the right decision. Also, the webservices extension has more than it's fair share of edge-case bugs. (Leni wanted to post this, but he had troubles so sent by private email instead):

When I first began using SOAP I didn’t understand the difference between a document-oriented SOAP api and an RPC-style API.

What I learned was that clients of a document-oriented API get marginal value from a SOAP library in exchange for complexity. Most of the work is in:
* understanding the document structure and relationships
* parsing and building documents

If Exchange is going with a document-oriented API (like Zimbra did), you might be better off building special-purpose helper libraries on top of XMLHttpRequest. That’s what zindus did when it switched away from the webservices extension in march 08 and it was definitely the right decision.

Also, the webservices extension has more than it’s fair share of edge-case bugs.

]]> Comment on Toward mailnews Exchange Web Services support: SOAP calls by rkent http://mesquilla.com/2010/02/01/toward-mailnews-exchange-web-services-support-soap-calls/comment-page-1/#comment-102 rkent Wed, 03 Feb 2010 17:50:46 +0000 http://mesquilla.com/?p=593#comment-102 openchange is the open-source option that has been suggested to me before. There are a variety of reasons why I am not looking at this initially. First, as I understand it the direction that Microsoft is moving is away from MAPI and towards EWS as "true exchange support". Their Outlook for Mac (Entourage), for example, as I understand it, never used MAPI, and is being rewritten to rely completely on EWS. As an new effort, I would rather code to the future rather than the past. Your posting implies that EWS is not real Exchange support, but I don't think that is correct for the future. Second, openchange does not list Windows as supported, while this is important to TB's user base. Third, openchange is under a GPL license. As I said in my posting, I'm not ready to commit myself to that path at this point in time. openchange is the open-source option that has been suggested to me before. There are a variety of reasons why I am not looking at this initially.

First, as I understand it the direction that Microsoft is moving is away from MAPI and towards EWS as “true exchange support”. Their Outlook for Mac (Entourage), for example, as I understand it, never used MAPI, and is being rewritten to rely completely on EWS. As an new effort, I would rather code to the future rather than the past. Your posting implies that EWS is not real Exchange support, but I don’t think that is correct for the future.

Second, openchange does not list Windows as supported, while this is important to TB’s user base.

Third, openchange is under a GPL license. As I said in my posting, I’m not ready to commit myself to that path at this point in time.

]]> Comment on Toward mailnews Exchange Web Services support: SOAP calls by James http://mesquilla.com/2010/02/01/toward-mailnews-exchange-web-services-support-soap-calls/comment-page-1/#comment-101 James Wed, 03 Feb 2010 16:52:16 +0000 http://mesquilla.com/?p=593#comment-101 If you want true exchange support, why not use the http://www.openchange.org/ native MAPI support? If you want true exchange support, why not use the http://www.openchange.org/ native MAPI support?

]]>