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
>    @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/[email protected]
> 
>    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
SMTP address or not based on RecipientRow RecipientFlags and related
structure fields.

>  - current mapi does forwards very small subset of the email's header
>    to the later stages of chain... there are only these:
> 
>         PR_INTERNET_MESSAGE_ID, PR_CONVERSATION_TOPIC, 
> PR_MESSAGE_DELIVERY_TIME,
>         PR_SENDER_EMAIL_ADDRESS, /* was: PR_SENT_REPRESENTING_NAME */
>         PR_DISPLAY_TO, PR_DISPLAY_CC, PR_DISPLAY_BCC,
>         PR_HASATTACH, PR_MSG_EDITOR_FORMAT
> 
>    the consequence is that threading of messages does not work.
>    so normal user would like to have at least In-Reply-To and References as
>    well.
> 
>    Q: what corresponds to these In-Reply-To and References in mapi?

You should find the necessary information in MS-OXCMSG section 2.2.1
which describes the additional set of properties added to a message when
it describes a forwarded or transfered message.

Hope it helps,

Cheers,
Julien.

---
Julien Kerihuel
[email protected]
OpenChange Project Manager

GPG Fingerprint: 0B55 783D A781 6329 108A  B609 7EF6 FE11 A35F 1F79


Attachment: signature.asc
Description: This is a digitally signed message part

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

Reply via email to