Commented Unassigned: Sender name/email not available in message properties in MAPI when sending an email [16880]

June 13, 2014, 11:51 pm

≫ Next: Created Unassigned: Subject of email should be on the title bar of window of MFCMAPI [16882]

≪ Previous: Commented Unassigned: Sender name/email not available in message properties in MAPI when sending an email [16880]

$

0

0

Hi Team,

I am developing an application that will tell attachment in email using MAPI.

1) When I send an email, the sender name is coming up in some systems and there is a problem in others. I have implemented the technique that is provided in MFCMAPI ( I have used AdviseSink Notifications ).

2) Where sender name is not coming, its giving "0x8004010f <Bad Ptr>" values. When I can retrive PR_MESSAGE_DELIVERY_TIME, then there shouldn't be any problem to retrieve sender name of an email. And I can't even check for bad pointer.

3) 0x800A001E gives sender name of email when the mailbox is connected to Exchange and 0x800D001E gives sender name of email when the mailbox is connected to Internet email. Kindly name these properties. And, even these properties give bad pointer values when AdviseSink Notifications are implemented.
Comments: ** Comment from web user: talib2608 **

This is not a bug in MFCMAPI, but it is a bug in MAPI subsystem. Where to post about the bugs of MAPI subsystem. There are many.

2) There is inconsistency here: We look for property names for most of the properties and named prop name for some. Also, while retrieving property we can't send parameter as PidLidInternetAccountName. We have to send as 0x800A001E or 0x800D001E.

---

Created Unassigned: Subject of email should be on the title bar of window of MFCMAPI [16882]

June 14, 2014, 1:09 am

≫ Next: Commented Unassigned: Sender name/email not available in message properties in MAPI when sending an email [16880]

≪ Previous: Commented Unassigned: Sender name/email not available in message properties in MAPI when sending an email [16880]

$

0

0

Hi Team,

I have configured a Outlook.com account in Microsft Outlook and sent an email. I have opened that email in MFCMAPI by opening the sent items folder of the configured account. The title bar of the window is sender. It should be the subject of the email.

Commented Unassigned: Sender name/email not available in message properties in MAPI when sending an email [16880]

June 14, 2014, 1:14 am

≫ Next: Commented Unassigned: Sender name/email not available in message properties in MAPI when sending an email [16880]

≪ Previous: Created Unassigned: Subject of email should be on the title bar of window of MFCMAPI [16882]

$

0

0

Hi Team,

I am developing an application that will tell attachment in email using MAPI.

1) When I send an email, the sender name is coming up in some systems and there is a problem in others. I have implemented the technique that is provided in MFCMAPI ( I have used AdviseSink Notifications ).

2) Where sender name is not coming, its giving "0x8004010f <Bad Ptr>" values. When I can retrive PR_MESSAGE_DELIVERY_TIME, then there shouldn't be any problem to retrieve sender name of an email. And I can't even check for bad pointer.

3) 0x800A001E gives sender name of email when the mailbox is connected to Exchange and 0x800D001E gives sender name of email when the mailbox is connected to Internet email. Kindly name these properties. And, even these properties give bad pointer values when AdviseSink Notifications are implemented.
Comments: ** Comment from web user: talib2608 **

If MAPI_E_NOT_FOUND is returned when the property is not available would be good. "0x8004010f <Bad Ptr>" as a returned value would confuse some developers

Commented Unassigned: Sender name/email not available in message properties in MAPI when sending an email [16880]

June 16, 2014, 6:40 am

≫ Next: Closed Unassigned: Sender name/email not available in message properties in MAPI when sending an email [16880]

≪ Previous: Commented Unassigned: Sender name/email not available in message properties in MAPI when sending an email [16880]

$

0

0

Hi Team,

I am developing an application that will tell attachment in email using MAPI.

1) When I send an email, the sender name is coming up in some systems and there is a problem in others. I have implemented the technique that is provided in MFCMAPI ( I have used AdviseSink Notifications ).

2) Where sender name is not coming, its giving "0x8004010f <Bad Ptr>" values. When I can retrive PR_MESSAGE_DELIVERY_TIME, then there shouldn't be any problem to retrieve sender name of an email. And I can't even check for bad pointer.

3) 0x800A001E gives sender name of email when the mailbox is connected to Exchange and 0x800D001E gives sender name of email when the mailbox is connected to Internet email. Kindly name these properties. And, even these properties give bad pointer values when AdviseSink Notifications are implemented.
Comments: ** Comment from web user: sgriffin **

0x8004010f is the same thing as MAPI_E_NOT_FOUND. It's not a bad pointer. You're not checking the type of the returned property. It was PT_ERROR, which means you should be looking at the .err member and interpreting it as an error code.

There's no inconsistency. You need to read about named properties:
http://msdn.microsoft.com/en-us/library/office/cc765864(v=office.15).aspx

I'm closing this bug. Please don't add further to it. If you want to discuss something, post on the discussions tab.

Closed Unassigned: Sender name/email not available in message properties in MAPI when sending an email [16880]

June 16, 2014, 6:40 am

≫ Next: Commented Unassigned: Subject of email should be on the title bar of window of MFCMAPI [16882]

≪ Previous: Commented Unassigned: Sender name/email not available in message properties in MAPI when sending an email [16880]

$

0

0

Hi Team,

I am developing an application that will tell attachment in email using MAPI.

1) When I send an email, the sender name is coming up in some systems and there is a problem in others. I have implemented the technique that is provided in MFCMAPI ( I have used AdviseSink Notifications ).

2) Where sender name is not coming, its giving "0x8004010f <Bad Ptr>" values. When I can retrive PR_MESSAGE_DELIVERY_TIME, then there shouldn't be any problem to retrieve sender name of an email. And I can't even check for bad pointer.

3) 0x800A001E gives sender name of email when the mailbox is connected to Exchange and 0x800D001E gives sender name of email when the mailbox is connected to Internet email. Kindly name these properties. And, even these properties give bad pointer values when AdviseSink Notifications are implemented.

Commented Unassigned: Subject of email should be on the title bar of window of MFCMAPI [16882]

June 16, 2014, 6:49 am

≫ Next: New Post: Mfcmapi error when accessing public folders

≪ Previous: Closed Unassigned: Sender name/email not available in message properties in MAPI when sending an email [16880]

$

0

0

Hi Team,

I have configured a Outlook.com account in Microsft Outlook and sent an email. I have opened that email in MFCMAPI by opening the sent items folder of the configured account. The title bar of the window is sender. It should be the subject of the email.
Comments: ** Comment from web user: sgriffin **

I don't repro this. On the message you're looking at, do you see a PR_SUBJECT property? What value does it have? What about PR_CONVERSATION_TOPIC?

New Post: Mfcmapi error when accessing public folders

June 16, 2014, 9:41 pm

≫ Next: Commented Unassigned: Sender name/email not available in message properties in MAPI when sending an email [16880]

≪ Previous: Commented Unassigned: Subject of email should be on the title bar of window of MFCMAPI [16882]

$

0

0

social.msdn.microsoft.com/Forums/en-US/3a2e9489-6137-42fb-95d1-bebcfe2ea138

Commented Unassigned: Sender name/email not available in message properties in MAPI when sending an email [16880]

June 18, 2014, 2:37 am

≫ Next: Commented Unassigned: Sender name/email not available in message properties in MAPI when sending an email [16880]

≪ Previous: New Post: Mfcmapi error when accessing public folders

$

0

0

Hi Team,

I am developing an application that will tell attachment in email using MAPI.

1) When I send an email, the sender name is coming up in some systems and there is a problem in others. I have implemented the technique that is provided in MFCMAPI ( I have used AdviseSink Notifications ).

2) Where sender name is not coming, its giving "0x8004010f <Bad Ptr>" values. When I can retrive PR_MESSAGE_DELIVERY_TIME, then there shouldn't be any problem to retrieve sender name of an email. And I can't even check for bad pointer.

3) 0x800A001E gives sender name of email when the mailbox is connected to Exchange and 0x800D001E gives sender name of email when the mailbox is connected to Internet email. Kindly name these properties. And, even these properties give bad pointer values when AdviseSink Notifications are implemented.
Comments: ** Comment from web user: talib2608 **

Why don't you just return the macro 'PT_ERROR' when you have defined it? In other cases it returns as 'PT_ERROR' and not "0x8004010f <Bad Ptr>". This was so simple and it is taking you so much time.

PR_SENT_REPRESENTING_NAME and PR_SENT_REPRESENTING_EMAIL_ADDRESS still not coming when sent an email. PR_MESSAGE_DELIVERY_TIME comes up. PR_SENT_REPRESENTING_NAME and PR_SENT_REPRESENTING_EMAIL_ADDRESS comes up only when sent using public folder.

---

Commented Unassigned: Sender name/email not available in message properties in MAPI when sending an email [16880]

June 18, 2014, 2:38 am

≫ Next: Commented Unassigned: Sender name/email not available in message properties in MAPI when sending an email [16880]

≪ Previous: Commented Unassigned: Sender name/email not available in message properties in MAPI when sending an email [16880]

$

0

0

Hi Team,

I am developing an application that will tell attachment in email using MAPI.

1) When I send an email, the sender name is coming up in some systems and there is a problem in others. I have implemented the technique that is provided in MFCMAPI ( I have used AdviseSink Notifications ).

2) Where sender name is not coming, its giving "0x8004010f <Bad Ptr>" values. When I can retrive PR_MESSAGE_DELIVERY_TIME, then there shouldn't be any problem to retrieve sender name of an email. And I can't even check for bad pointer.

3) 0x800A001E gives sender name of email when the mailbox is connected to Exchange and 0x800D001E gives sender name of email when the mailbox is connected to Internet email. Kindly name these properties. And, even these properties give bad pointer values when AdviseSink Notifications are implemented.
Comments: ** Comment from web user: talib2608 **

.

Commented Unassigned: Sender name/email not available in message properties in MAPI when sending an email [16880]

June 18, 2014, 2:40 am

≫ Next: Created Unassigned: Wrong values in Meeting [16890]

≪ Previous: Commented Unassigned: Sender name/email not available in message properties in MAPI when sending an email [16880]

$

0

0

Hi Team,

I am developing an application that will tell attachment in email using MAPI.

1) When I send an email, the sender name is coming up in some systems and there is a problem in others. I have implemented the technique that is provided in MFCMAPI ( I have used AdviseSink Notifications ).

2) Where sender name is not coming, its giving "0x8004010f <Bad Ptr>" values. When I can retrive PR_MESSAGE_DELIVERY_TIME, then there shouldn't be any problem to retrieve sender name of an email. And I can't even check for bad pointer.

3) 0x800A001E gives sender name of email when the mailbox is connected to Exchange and 0x800D001E gives sender name of email when the mailbox is connected to Internet email. Kindly name these properties. And, even these properties give bad pointer values when AdviseSink Notifications are implemented.
Comments: ** Comment from web user: talib2608 **

.

Created Unassigned: Wrong values in Meeting [16890]

June 18, 2014, 2:58 am

≫ Next: Commented Unassigned: Wrong values in Meeting [16890]

≪ Previous: Commented Unassigned: Sender name/email not available in message properties in MAPI when sending an email [16880]

$

0

0

I have created new meeting and in the "To:" field there is just one entry. By opening it in Outlook it shows it as shown in 1.png. When I open it in MFCMAPI, it shows 2 values as shown in 2.png

Commented Unassigned: Wrong values in Meeting [16890]

June 18, 2014, 2:59 am

≫ Next: Commented Unassigned: Wrong values in Meeting [16890]

≪ Previous: Created Unassigned: Wrong values in Meeting [16890]

$

0

0

I have created new meeting and in the "To:" field there is just one entry. By opening it in Outlook it shows it as shown in 1.png. When I open it in MFCMAPI, it shows 2 values as shown in 2.png
Comments: ** Comment from web user: talib2608 **

.

Commented Unassigned: Wrong values in Meeting [16890]

June 18, 2014, 3:00 am

≫ Next: Commented Unassigned: Subject of email should be on the title bar of window of MFCMAPI [16882]

≪ Previous: Commented Unassigned: Wrong values in Meeting [16890]

$

0

0

I have created new meeting and in the "To:" field there is just one entry. By opening it in Outlook it shows it as shown in 1.png. When I open it in MFCMAPI, it shows 2 values as shown in 2.png
Comments: ** Comment from web user: talib2608 **

Concentrate on the "To" field in MFCMAPI also.

Commented Unassigned: Subject of email should be on the title bar of window of MFCMAPI [16882]

June 18, 2014, 5:23 am

≫ Next: Commented Unassigned: Subject of email should be on the title bar of window of MFCMAPI [16882]

≪ Previous: Commented Unassigned: Wrong values in Meeting [16890]

$

0

0

Hi Team,

I have configured a Outlook.com account in Microsft Outlook and sent an email. I have opened that email in MFCMAPI by opening the sent items folder of the configured account. The title bar of the window is sender. It should be the subject of the email.
Comments: ** Comment from web user: talib2608 **

Snapshot of the sent item and exported properties from MFCMAPI are attached

Commented Unassigned: Subject of email should be on the title bar of window of MFCMAPI [16882]

June 18, 2014, 5:24 am

≫ Next: Commented Unassigned: Sender name/email not available in message properties in MAPI when sending an email [16880]

≪ Previous: Commented Unassigned: Subject of email should be on the title bar of window of MFCMAPI [16882]

$

0

0

Hi Team,

I have configured a Outlook.com account in Microsft Outlook and sent an email. I have opened that email in MFCMAPI by opening the sent items folder of the configured account. The title bar of the window is sender. It should be the subject of the email.
Comments: ** Comment from web user: talib2608 **

I have used Outlook 2010 and Outlook Hotmail Connector.

---

Commented Unassigned: Sender name/email not available in message properties in MAPI when sending an email [16880]

June 18, 2014, 6:26 am

≫ Next: Commented Unassigned: Wrong values in Meeting [16890]

≪ Previous: Commented Unassigned: Subject of email should be on the title bar of window of MFCMAPI [16882]

$

0

0

Hi Team,

I am developing an application that will tell attachment in email using MAPI.

1) When I send an email, the sender name is coming up in some systems and there is a problem in others. I have implemented the technique that is provided in MFCMAPI ( I have used AdviseSink Notifications ).

2) Where sender name is not coming, its giving "0x8004010f <Bad Ptr>" values. When I can retrive PR_MESSAGE_DELIVERY_TIME, then there shouldn't be any problem to retrieve sender name of an email. And I can't even check for bad pointer.

3) 0x800A001E gives sender name of email when the mailbox is connected to Exchange and 0x800D001E gives sender name of email when the mailbox is connected to Internet email. Kindly name these properties. And, even these properties give bad pointer values when AdviseSink Notifications are implemented.
Comments: ** Comment from web user: sgriffin **

Your attachments illustrate the difference between regular properties and named properties. In attachmant 1.pn, where you wrote "no property names", those were named properties (easily identified by the IDs greater than 0x8000). So there is no PR_* macro associated with that value (can't be, since it's not constant), and the Named prop name has the name I looked up with GetNamesFromIDs.

In attachment 2, you highlighted the Named prop name column for properties under 0x8000, which are not named properties. So they wouldn't have names to look up.

You really need to go read the documentation I linked. It explains all this.

As for your comment about PT_ERROR - are you even talking about MFCMAPI? I don't understand the context of the complaint.

Commented Unassigned: Wrong values in Meeting [16890]

June 18, 2014, 6:28 am

≫ Next: Closed Unassigned: Wrong values in Meeting [16890]

≪ Previous: Commented Unassigned: Sender name/email not available in message properties in MAPI when sending an email [16880]

$

0

0

I have created new meeting and in the "To:" field there is just one entry. By opening it in Outlook it shows it as shown in 1.png. When I open it in MFCMAPI, it shows 2 values as shown in 2.png
Comments: ** Comment from web user: sgriffin **

In what universe is this a bug in MFCMAPI? I just report the properties as I find them. You should look at the recipient table.

And PLEASE STOP ABUSING MY BUG REPORTING SYSTEM I have a discussions area where you could ask your questions.

Closed Unassigned: Wrong values in Meeting [16890]

June 18, 2014, 6:28 am

≫ Next: New Post: PR_ATTACH_LONG_PATHNAME giving value when email is saved

≪ Previous: Commented Unassigned: Wrong values in Meeting [16890]

$

0

0

I have created new meeting and in the "To:" field there is just one entry. By opening it in Outlook it shows it as shown in 1.png. When I open it in MFCMAPI, it shows 2 values as shown in 2.png

New Post: PR_ATTACH_LONG_PATHNAME giving value when email is saved

June 20, 2014, 5:38 am

≫ Next: New Post: PR_ATTACH_FILENAME showing wrong value

≪ Previous: Closed Unassigned: Wrong values in Meeting [16890]

$

0

0

Your image isn't loading. What was the original filename? What does PR_ATTACH_FILENAME show? What does PR_ATTACH_LONG_FILENAME show? What values were you expecting them to show?

New Post: PR_ATTACH_FILENAME showing wrong value

June 20, 2014, 5:38 am

≫ Next: New Post: PR_ATTACH_FILENAME showing wrong value

≪ Previous: New Post: PR_ATTACH_LONG_PATHNAME giving value when email is saved

$

0

0

Your image isn't loading. What was the original filename? What does PR_ATTACH_FILENAME show? What does PR_ATTACH_LONG_FILENAME show? What values were you expecting them to show?