[horde] Outlook Debugging Day

[Patrick De Zordo]

Hello Torben, Hallo aus dem Norden Italiens,
clearly, however, this would have corresponding consequences for our strict budget.

I know "Open Source" is a point of definition since everyone can use it, but oviously all team members are just working on priority
to-do lists they substain to be important for ongoing versions of their software.
It's a very very very big work to program such a complete solution as Horde.
I really appreciate this! It's not self-evident!

I'm willing to help this project to go on his way with my possibilities.
My possibilities are unfortunately not based on a financial nature.
What I can contribute, is invest time in debugging, installing and testing, together with development team, like the "Outlook Debugging Day" yesterday.

As you know (also in Austria) a lot of people is using OL2013 (and older versions certainly).
So I guess, it could be possible to work on this OL2013 "workarround" (I know it's MS erraneous interpretation of their own AS-protocoll) for complete
ActiveSync capabilities with this very important MS product.

Correct me if I'm wrong, this could give a ulterior high boosting to Horde.
Software diffusion and awareness is one of the more important things in OpenSource, the usage compensates and gives confermation for the many thousand hours of work spent.

I really love, yah love, this worldwide and global working on a product with this verve!

In short, I really hope we are able to find some ways to get further!

Sincerly,
Patrick.

> -----Ursprüngliche Nachricht-----
> Von: horde-bounces at lists.horde.org [mailto:horde-
> bounces at lists.horde.org] Im Auftrag von Torben Dannhauer
> Gesendet: Dienstag, 27. Mai 2014 08:59
> An: horde at lists.horde.org
> Betreff: Re: [horde] Outlook Debugging Day
> 
> 
> <snip>
> 
> > My point isn't about WHEN, or IF it will be fixed. My point is that any
> workaround for Microsoft's bug that we introduce > into our code base adds
> to our future maintenance costs because it's something that will have to be
> maintained and > > worked around AGAIN, if/when it is fixed my Microsoft.
> >
> >>> This is not something that I'm going to do on my own time. If this
> >>> is really important to your organization you could consider
> >>> sponsoring the work.
> >>>
> >>
> >> Sponsoring would be nice, but correct me if I'm wrong, you know lot,
> >> really lot products on the market use OL with the respective API to
> >> send and receive emails, for now OL is THE groupware solution used in
> >> Business work.
> 
> 
> Michael, Patrick,
> 
> thanks for your extensive Outlook debugging!
> 
> I agree, that it is not Hordes "native" task to work around client bugs.
> However, as we see with the whole ActiveSync story, there are not many
> clients available following the standard strictly - many workarounds are
> required. As for Outlook 2013.
> 
> I absolutely agree with Michael that he cannot invest all of his time into the
> Outlook bugs.
> @Patrick: I spent several thousand dollars from my _private pocket money_
> to introduce EAS 14 support, which is required for Outlook. Maybe it is now
> time that you/your company spent some money to hunt down and work
> around some ugly Outlook bugs. Free Opensource does necessarily not
> mean it is free in terms of investment...
> 
> However, I recommend another approach: you can setup two accounts in
> your OL2013: one IMAP account for email usage (I prefer IMAP over EAS mail
> anyway since I thinks it is more robust), and one EAS account for contacts,
> tasks and calendar. Even in that setup there were enough bugs in
> calendar/contacts/connectivity, so let's hunt THEM down, then we can use
> Outlook with EAS+IMAP.
> 
> Regards from Salzburg/Austria,
> Torben
> 
> --
> Horde mailing list
> Frequently Asked Questions: http://horde.org/faq/ To unsubscribe, mail:
> horde-unsubscribe at lists.horde.org