[openchange]mapi documentation

hello dear openchange developpers,

i'm using fetchmail with mapi enabled and i want to modify sources
a little bit so that it suits more my (and perhaps other's) needs
and i need your help.

there are few problems right now in using fetchmail with mapi
(i.e. openchange support compiled in):

 - PR_SENT_REPRESENTING_NAME field originally used in fetchmail is not 
   reliable enough, because it does not have to contain the part
    <at> fully.qualified.domain.name of an email address. this causes bad
   behaviour later in the fetchmail | procmail | mutt chain.

   applying commong method "guess and fail" i found using 
   PR_SENDER_EMAIL_ADDRESS suits more my needs, but sometimes it
   contains unwanted garbage, like
   /O=TAKE-TWOINTERACTIVE/OU=2KGB/CN=RECIPIENTS/CN=AAA.BBB <at> 2kgbrn.2kgames.t2.corp

   Q: do you know perhaps what is the correct field to use?
   Q: or perhaps - is there any field in mapi saying:
       "is PR_SENT_REPRESENTING_NAME full email address ? yes : no"

 - the same problem comes with Cc and To fields

   Q: what fields includes complete email address for To and Cc fields?

 - current mapi does forwards very small subset of the email's header
   to the later stages of chain... there are only these:

Re: [openchange]mapi documentation

On Tuesday 08 September 2009 23:40:35 mojmir svoboda wrote:
> hello dear openchange developpers,
Hi,

>    Q: do you know perhaps what is the correct field to use?
>    Q: or perhaps - is there any field in mapi saying:
>        "is PR_SENT_REPRESENTING_NAME full email address ? yes : no"
The "correct" field depends on a few different factors, including exactly what 
you want to do.

You probably want to review the MS-OXCMAIL and MS-OXPROPS specifications 
(available from http://msdn.microsoft.com/en-au/library/cc307725.aspx) to get 
the fields that best suit your needs. 

HTH

Brad

Re: [openchange]mapi documentation

On Tue, 2009-09-08 at 15:40 +0200, mojmir svoboda wrote:
>  - PR_SENT_REPRESENTING_NAME field originally used in fetchmail is not 
>    reliable enough, because it does not have to contain the part
>     <at> fully.qualified.domain.name of an email address. this causes bad
>    behaviour later in the fetchmail | procmail | mutt chain.
> 
>    applying commong method "guess and fail" i found using 
>    PR_SENDER_EMAIL_ADDRESS suits more my needs, but sometimes it
>    contains unwanted garbage, like
>    /O=TAKE-TWOINTERACTIVE/OU=2KGB/CN=RECIPIENTS/CN=AAA.BBB <at> 2kgbrn.2kgames.t2.corp
> 
>    Q: do you know perhaps what is the correct field to use?
>    Q: or perhaps - is there any field in mapi saying:
>        "is PR_SENT_REPRESENTING_NAME full email address ? yes : no"

Hi Mojmir,

PR_SENDER_EMAIL_ADDRESS actually contains the sending mailbox owner's
e-mail address. In the case above, it is a typical exchange server
address representation (X500 DN) with the organization (O), organization
unit (OU) etc.

Regarding to your question, you may want to check MS-OXCDATA pdf section
2.10.3.

>  - the same problem comes with Cc and To fields
> 
>    Q: what fields includes complete email address for To and Cc fields?

Similarly, you should be able to distinguish whether the recipient has a

[openchange]OpenChange video tutorials #001: Ideas requested

Hi List,

It's been a while since my last post and some of you may have even
thought OpenChange was some kind of  ... frozen/dead (talking about
trunk here). 

Brad has been providing a lot of efforts maintaining the community up
and running, was mostly alone doing this, so I'd like on behalf of
everyone to address him a big and sincere THANK YOU.

2009 has turned pretty badly for me on several aspects and it took a
while to pass through this storm/hurricane. Anyway I'm glad to say
almost everything came back to "normal" and I'm back into OpenChange for
real 

Now let's talk about more exciting things. We have in the pipe a nice
small video tutorial on how to setup OpenChange server - thanks to
Sassyn for the video editing work  - and I'd like to extend this
concept on openchange website so we provide users a large set of
interactive/dynamic tutorials.

The main idea would be to create development/integration/setup tutorials
to help developers playing with OpenChange and take the best of it.
Video tutorial about development is not quite an easy task, but I'm
willing to take this challenge.

So finally here is the question: What you (developers/users) would like
to see as tutorial #001? You'll find below a small set of ideas, feel
free to propose others depending on your OpenChange needs:

Re: [openchange]OpenChange video tutorials #001: Ideas requested

On Wednesday 09 September 2009 22:53:02 Julien Kerihuel wrote:
> The main idea would be to create development/integration/setup tutorials
> to help developers playing with OpenChange and take the best of it.
> Video tutorial about development is not quite an easy task, but I'm
> willing to take this challenge.
Thanks for looking at this. I think it is very important to make it easy to 
get involved.

> So finally here is the question: What you (developers/users) would like
> to see as tutorial #001? You'll find below a small set of ideas, feel
> free to propose others depending on your OpenChange needs:
>
> 1. Setup OpenChange proxy
> 2. Set an OpenChange based project from scratch (autotools, Makefile,
> sample example)
> 3. Beginning with libmapi
> 4. Playing with openchange tools (create profile, openchangeclient,
> exchange2mbox etc.)
It would be good if the tutorials were broken up, so they aren't too large. 
I'd prefer to see several small tutorials than one very long one. It doesn't 
matter if some tutorials are only a few minutes.

Some ideas:
* a tour of the codebase, pointing out the apidox, different libraries, 
examples, command line tools, and some of the resources we have (svn, trac, 
wiki, buildbot)
* use of OCPF (which is a really, really powerful idea)
* a description of how libmapi works (IDL, building structures, calling down, 
getting responses) and how the proxy works
* the design of the server.

Re: [openchange]OpenChange video tutorials #001: Ideas requested

Not direclty interested in this, but maybe a good way to see somebody 
capable to add more server backends.

Maybe not related directly to users but more to developers.

A small tutorial to give developers the basics to create new server 
storage backends (suppose I'd like to add a server backend to get IMAP 
e-mails or integrate with Kolab)

Alessandro

Brad Hards ha scritto:
> On Wednesday 09 September 2009 22:53:02 Julien Kerihuel wrote:
>> The main idea would be to create development/integration/setup tutorials
>> to help developers playing with OpenChange and take the best of it.
>> Video tutorial about development is not quite an easy task, but I'm
>> willing to take this challenge.
> Thanks for looking at this. I think it is very important to make it easy to 
> get involved.
> 
>> So finally here is the question: What you (developers/users) would like
>> to see as tutorial #001? You'll find below a small set of ideas, feel
>> free to propose others depending on your OpenChange needs:
>>
>> 1. Setup OpenChange proxy
>> 2. Set an OpenChange based project from scratch (autotools, Makefile,
>> sample example)
>> 3. Beginning with libmapi
>> 4. Playing with openchange tools (create profile, openchangeclient,
>> exchange2mbox etc.)

Re: [openchange]OpenChange video tutorials #001: Ideas requested

or if not a video maybe some docs (?)

Alessandro

Alessandro Briosi ha scritto:
> Not direclty interested in this, but maybe a good way to see somebody 
> capable to add more server backends.
> 
> Maybe not related directly to users but more to developers.
> 
> A small tutorial to give developers the basics to create new server 
> storage backends (suppose I'd like to add a server backend to get IMAP 
> e-mails or integrate with Kolab)
> 
> Alessandro
> 
> Brad Hards ha scritto:
>> On Wednesday 09 September 2009 22:53:02 Julien Kerihuel wrote:
>>> The main idea would be to create development/integration/setup tutorials
>>> to help developers playing with OpenChange and take the best of it.
>>> Video tutorial about development is not quite an easy task, but I'm
>>> willing to take this challenge.
>> Thanks for looking at this. I think it is very important to make it 
>> easy to get involved.
>>
>>> So finally here is the question: What you (developers/users) would like
>>> to see as tutorial #001? You'll find below a small set of ideas, feel
>>> free to propose others depending on your OpenChange needs:
>>>
>>> 1. Setup OpenChange proxy

[openchange]AddressBook question

_______________________________________________
devel mailing list
devel <at> lists.openchange.org
http://mailman.openchange.org/listinfo/devel

[openchange][patch] cosmetic fix to utils/exchange2ical/exchange2ical_utils.c

exchange2ical_utils.c was missing a new-line at the end. So I added it
and took out all of the whitespace at the end of lines.

Thought the devs would like to see this but it didn't really need a trac ticket.

E

--

-- 
Erik Hovland
erik <at> hovland.org
http://hovland.org/

_______________________________________________
devel mailing list
devel <at> lists.openchange.org
http://mailman.openchange.org/listinfo/devel

Re: [openchange][patch] cosmetic fix to utils/exchange2ical/exchange2ical_utils.c

On Wednesday 16 September 2009 09:41:11 Erik Hovland wrote:
> exchange2ical_utils.c was missing a new-line at the end. So I added it
> and took out all of the whitespace at the end of lines.
> 
> Thought the devs would like to see this but it didn't really need a trac
>  ticket.
I committed this as rev 1516. Note that there is a lot of work about to be 
merged from the gsoc-exchange2ical branch into that area, so you might not 
want to do too many changes in there.

A schedule of "about to be" depends on getting some time to get into it.

Brad