Re: [fetchmail-devel] fetchmail and mapi II

[mojmir s. <moj...@2k...>]

* Mat...@2k...rp <Mat...@2k...rp> [2009-06-16 14:11:37 +0000]:

> > as a hotfix i simply allocated lot of memory and removed the loop that
> > did nothing. i assume you do not want that kind of solution (and neither
> > do i.. in long term)
> 
> Ah, ok.

in attachment there is a patch fixing this (hopefuly) correctly.  still,
the postscript attachment i sent myself got little bit scrambled
(periodically at buffer boundaries). may be bug in stream, may be bug in
ldb_base64_encode.

btw: ldb_base64_encode can be removed from the source file mapi.c, as it
is already present in samba4.

> >> > 6. \r characters and = spread all around in mail body
> This looks like quoted printable encoding to me. hex is likely (i. e. I

i confirm. this seems to be hardcoded in mapi.c
perhaps there should be an option specifying output format? i.e. if
exchange sends it in 7bit, i'm fine with it. no need for another
translation.

> Perhaps headers do not properly declare content. Do you have an example of
> such a message (inside mutt, just pipe it into "cat - >/tmp/msg.bin", then
> mail msg.bin as application/octet-stream attachment).

in attachment. it's in czech, sorry - only sample i did not deleted

> > 	- fetchmail modifies the "From: " header
> Is it fetchmail or OpenChange or Exchange that does this?

this is what i have when i look out from outlook:
	From: "Matthias Andree" <matthias.andree@your.email>
	To: "mojmir svoboda" <mojmir.svoboda@my.email>, fet...@li...
	Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15
	Content-Transfer-Encoding: 7bit

this is what i receive after fetchmailing via mapi:
	From: MatthiasAndree@exchange_server_address.here
	To: 2K Czech <MojmirSvoboda>;, fet...@li...
	Content-Type: text/plain; charset=us-ascii
	Content-Transfer-Encoding: quoted-printable

there is some header manipulation code in mapi_fetch_headers, i'd start
search there.

best regards,
mojmir