[fetchmail-devel] [Feature #5736] Add support for EAS

[<ad...@be...>]

Feature Request #5736, was updated on 2014-Mar-14 12:36
You can respond by visiting: 
http://developer.berlios.de/feature/?func=detailfeature&feature_id=5736&group_id=1824

Category: None
Status: Open
Priority: 1
Summary: Add support for EAS

By: m-a
Date: 2014-Mar-15 11:19

Message:
Logged In: YES 
user_id=2007
Browser: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0

This is rather unlikely to happen because there is a
precedent that did not work out:
  I have had a Google Summer of Code contribution that added
MAPI access, but it was not properly integrated at the time,
and I have never received - in spite of multiple calls for
help - a test account so I could integrate the code and test.

Plus given the little spare time I have, I would rather not
waste that on proprietary stuff when we have open protocol
like IMAP. I have my mobile client (K9mail on Android) use
IMAP and don't feel the need to switch to legacy stuff - I'd
expect that someone offering mail services also offers
standard access ports.

I would consider adding stuff for the "master" branch in Git
if someone offered the code, providing that - I have made
bad experience in other projects, that's why it looks
restrictive and is restrictive:

* There is sufficient evidence that the protocol is not
patent-encumbered

* Requisite libraries are under OSI approved and
GPL-compatible licenses, and should be AGPLv3 compatible.

* I get a permanent royalty and restriction free copyright
and patent license to the code that permits me to relicense
the code and permits users of open-source licensed
derivatives to use any involved patents royalty-free

* there is a sustainable commitment of the contributor to
answer questions to the code and help maintain it (I am not
accepting Google summer of code contributions or other way
that I suspect to me of a hit-and-run style)

* I get a reliable communications channel, and the address
of a backup person (family, friend) that I can ask why the
EAS contributor is not responding

* I get a personal long-term EAS test account, with
contractual guarantee for at least five years, so I can keep
checking the code still works before releases. I am not
going to pay for the account, it has to be sponsored or
donated in some way.

* Integration into fetchmail must be in a way that EAS
support easily be disabled at build-time with no ill effects
at run-time.

The code would, however, be permitted to use
standards-compliant langauges that offer C linkage, such as
C++11, given sufficient cross-platform support (which I
consider as Linux, BSD, Solaris, Cygwin).

----------------------------------------------------------------------

By: dbesler
Date: 2014-Mar-14 12:36

Message:
Logged In: YES 
user_id=65358
Browser: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.1; .NET CLR 3.0.04506.30; MS-RTC LM 8; .NET CLR 3.0.04506.648; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET4.0C; .NET4.0E; Zune 4.7; McAfee)

Add support for the EAS (Exchange Active Sync) 
protocol for:
a) retrieval of mail from an EAS service
b) deliver mail to an EAS service

EAS has become a standard supported protocol for 
mobile e-mail clients. Although the initial merit of 
this feature request may seem to be far fetched, 
EAS has addressed some of the issues that are 
present in the legacy protocols of POP, IMAP, etc

A collection of Exchange Interoperability Technical 
Articles can be found here:
http://msdn.microsoft.com/en-us/library/hh285606
(v=exchg.140).aspx

If the project members are interested and willing, I 
would be interested in particpating in the 
development and testing of this feature.

----------------------------------------------------------------------
You can respond by visiting: 
http://developer.berlios.de/feature/?func=detailfeature&feature_id=5736&group_id=1824