We Keep Coding

Can't access the recipients of specific emails in Outlook

I have a somewhat interesting phenomenon occurring in Outlook 2019: when we are using Exchange accounts and toggle off the "Use Cached Exchange Mode to download email to an Outlook data file" option, we are no longer able to get the e-mail addresses for recipients via the Microsoft.Office.Interop.Outlook.PropertyAccessor interface (using the MAPI property PR_SMTP_ADDRESS) from an e-mail, in which we entered the recipient e-mails using the suggested Outlook contact. (eg. when the address is entered it looks like this: 'John Smith'). When we observed the item using OutlookSpy, we noticed that the specific property's value says MAPI_E_NOT_FOUND or is not present at all. I also noticed that in these cases, Outlook puts the corresponding e-mail addresses in the BCC field, which we obviously can't access when viewing the e-mail in the recipient's inbox. Is there a way for us to get the addresses, or is there some kind of workaround for this problem?

No property is guaranteed to be present. If the property is missing, try to use Recipient.AddressEntry.GetExchangeUser().PrimarySmtpAddress (error and exceptions checks omitted).

Sent email from the program

I already created the application in windows forms c# which ready to be use by another user in another computer, but i am aware there will be an error occurred when run my program (because i didn't have enough time to check everything), so i decided to let users find the bug and report to me through email.
I have a button "Report a Problem", but how do i when users click that button, it will open the Microsoft Outlook and automatically filled up the Received Email or "To" with my own email?

I would suggest:
Process.Start("mailto:your#emailaddress.com");
This will prompt Windows to create a new mail using the default email provider (which will most likely be Microsoft Outlook if it's installed).
To use this method, please add:
using System.Diagnostics;
to the top of your code file.

Use Diagnostics.Process.Start("mailto: senderEmail")
And it'll work only if you have outlook as your default email client

Namespace : using System.Diagnostics;
Process.Start("mailto:revanayyamca#gmail.com");

Create an Historic Outlook MailItem - set details of SentOn

I need to migrate a large number of emails from Lotus Notes to a Outlook MSG format.
I need to ensure that the MSG's represent the emails in their original Lotus Notes format, including date sent, sent by, etc, and all attachments.
I have created LotusScript code to extract the email data and attachments from the Lotus Notes databases and store in a SQL database with attachments on a file store. I now need to work on code to read this data and create the Outlook messages. I have the scaffolding of a C# .Net application in place, but am struggling with being able to set read-only properties of the Outlook message, such as SentOn.
How do I/Can I set the read-only properties of the Outlook MailItem?

Are you importing the messages to Outlook first?
If you only need to create standalone MSG files, you can use Redemption (I am its author) and its RDOSession.CreateMessageFromMsgFile method -it returns an instance of the RDOMail object. You can set various RDOMail properties and call RDOMail.Save.

How can you tell if invitations have been sent for a meeting in Outlook?

I am writing a COM add-in for Outlook using C#. If a meeting was saved and invitations were not sent, Outlook puts a message at the top of the form saying the invitations have not been sent. How do I determine programmatically that invitations have not been sent for a meeting?
I tried examining each Recipient and checking the MeetingResponseStatus. I would expect it to be OlResponseNone if the invitation has not been sent but OlResponseNotResponded if the invitations have been sent but no responses have been received. However, I always get OlResponseNone for recipients that either haven't been sent an invitation or that have but have not yet reponded. I therefore can't tell apart a meeting where invitations haven't been sent from one where they have been sent but no one has responded.
I've done most of my testing in Outlook 2007, but I believe the same holds true for 2003 and 2010, all of which I need to support.

I found a partial answer in this post. I need to read the DASL property "http://schemas.microsoft.com/mapi/id/{00020329-0000-0000-C000-000000000046}/80BE0102". In Outlook 2007 and leter, you can do this with a PropertyAccessor as follows:
appointment.PropertyAccessor.GetProperty("http://schemas.microsoft.com/mapi/id/{00020329-0000-0000-C000-000000000046}/80BE0102");
However, I need to also support Outlook 2003, and the PropertyAccessor property was added in Outlook 2007. I was therefore able to use Redemption's RDOMail object with the following code (error handling omitted).
var _session = New RDOSession();
_session.Logon();
var _message = _session.GetMessageFromID(appointment.EntryID, ((Outlook.MAPIFolder)appointment.Parent).StoreID);
return (bool)_message.Fields["http://schemas.microsoft.com/mapi/id/{00062002-0000-0000-C000-000000000046}/8229000B"];
Marshal.ReleaseComObject(_message);
_session.Logoff();
Marshal.ReleaseComObject(_session);

Generate an e-mail to be downloaded by client and sent from their outlook account

One of the requirements for the application that I'm working on is to enable users to submit a debugging report to our helpdesk for fatal errors (much like windows error reporting).
I've been told that e-mails must come from a client's mail account to prevent the helpdesk getting spammed and loads of duplicate calls raised.
In order to achieve this, I'm trying to compose a mail message on the server, complete with a nice message in the body for the helpdesk and the error report as an attachment, then add it to the Response so that the user can download, open and send it.
I've tried, without success, to make use of the Outlook Interoperability Component which is a moot point because I've discovered in the last 6 hours of googling that creating more than a few Application instances is very resource intensive.

If you want the user to send an email client side, I don't see how System.Net.Mail will help you.
You have two options:
mailto:support#domain.com?subject=Error&body=Error message here...
get user to download email in some format, open it in their client and send it
Option 1 will probably break down with complex bodies. With Option 2, you need to find a format that is supported by all mail clients (that your users use).
With option 1, you could store the email details locally on your server against some Error ID and just send the email with an Error ID in the subject:
mailto:support#domain.com?subject=Error 987771 encountered

In one of our applications the user hits the generate button and it creates and opens the email in outlook. All they have to do is hit the send button. The functions is below.
public static void generateEmail(string emailTo, string ccTo, string subject, string body, bool bcc)
{
Outlook.Application objOutlook = new Outlook.Application();
Outlook.MailItem mailItem = (Outlook.MailItem)(objOutlook.CreateItem(OlItemType.olMailItem));
/* Sets the recipient e-mails to be either sent by 'To:' or 'BCC:'
* depending on the boolean called 'bcc' passed. */
if (!(bcc))
{
mailItem.To = emailTo;
}
else
{
mailItem.BCC = emailTo;
}
mailItem.CC = ccTo;
mailItem.Subject = subject;
mailItem.Body = body;
mailItem.BodyFormat = OlBodyFormat.olFormatPlain;
mailItem.Display(mailItem);
}
As you can see it is outputting the email in plaintext at the moment because it was required to be blackberry friendly. You can easily change the format to HTML or richtext if you want some formatting options. For HTML use mailItem.HTMLBody
Hope this helps.
EDIT:
I should note that this is used in a C# Application and that it is referencing Microsoft.Office.Core and using Outlook in the Email class the function is located in.

The simple answer is that what you are trying to achieve isn't realistically achievable across all platforms and mail clients. When asked to do the improbable it is wise to come up with an alternative and suggest that.
Assuming that your fault report is only accessible from an error page then you've already got a barrier to spam - unless the spammers can force an exception.
I've always handled this by logging the fault and text into the database and integrating that with a ticketing system. Maybe also have a mailto: as Bruce suggest with subject=ID&body=text to allow the user to send something by email.
I don't think an .eml format file will help either - because they'll need to forward it, and most users would probably get confused.
A .eml is effectively plain text of the message including headers as per RFC-5322.