Hi Julien,

Well, I sent you that link back in May, but apparently that was a very 
busy time for you.  ;-)

If you find something useful in my little project, I'd be honored if you 
would merge some of my ideas back into the trunk.

Actually, I think projects like this shouldn't exist outside of Openchange, 
they should be part of it. One of my concerns with the Openchange project 
has always been that it seems rather academic. When you visit the web
site, it's not that clear how you can actually use it. I suppose there are a 
lot of people out there who need your libraries and put something together
that works for them. Just like I did. It would be great if you could find
someone who could focus on the application or end user aspects and put
together a section on the web site that deals with real life applications.

And I would really appreciate it if someone more professional than me
could look at my code. There are quite a few things in there which are
just hacks to make it work, reactions to whatever I got from my
company's Exchange server. I'd love to continue working on it, but
for now my Linux machines are locked out from the company network.

best regards


   dirk



-----Original Message-----

From: Julien Kerihuel <[email protected]>
To: Development list <[email protected]>
Sent: Thu, Dec 3, 2009 4:58 am
Subject: Re: [openchange][devel] imap proxy


On Wed, 2009-12-02 at 18:41 -0500, [email protected] wrote:
> Guten Abend Sandra,
> 
> I've been in the same situation and I compiled this:
> http://q.freeshell.org/ex2md
> 
> It served me very well until the admin boneheads locked up the
> firewall so that only corporate supplied machines with corporate
> Winblows and corporate AV and corporate FW and corporate spyware that
> verifies the aforementioned can get through.
> 
Hi Dirk,

Didn't know your project finally ended in a published and public
project. I'm truly glad to see new extensions being developed on top of
openchange. Moreover I think your tool - without having looked at the
source code yet - is worthwhile to numerous user.

Given that you are patching openchange source directly, would it make
sense to you we import this code within openchange trunk instead?

This would guarantee your tool still compiles among forthcoming
revisions/updates and make it more available to wider number of users.

Maybe ending up in new updates / comments / potential bug fixes getting
applied in the future.

Let me know what is your opinion on this.

Cheers,
Julien.
> 





_______________________________________________
devel mailing list
[email protected]
http://mailman.openchange.org/listinfo/devel

Reply via email to