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 @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" - 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: 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? so basically from i need from you is documentation for mapi and i'll try to find it there so i do not waste your time with trivial stuff. many thanks for your attention, mojmir _______________________________________________ devel mailing list [email protected] http://mailman.openchange.org/listinfo/devel
