Exchange 2003 and Outlook 2003 moves to Extended Support

Exchange Server 2003 goes into Extended Support on 4/14/2009.Details on our lifecycle policy for Exchange 2003 can be found at http://support.microsoft.com/lifecycle/?LN=en-us&p1=1773&x=11&y=9 Products Released General Availability Date Mainstream Support Retired Extended Support Retired Service Pack Retired Notes Exchange Server 2003 Enterprise Edition 9/28/2003 4/14/2009 4/8/2014 5/25/2005   Exchange Server 2003 Service Pack 1 5/25/2004 Not Applicable…

1

Outlook Rules!

Rules are evaluated in sequence according to the increasing order of this value. The evaluation order for rules that have the same value in this property is undefined.PidTagRuleSequence: http://msdn.microsoft.com/en-us/library/dd188686.aspx The Rule.ExecutionOrder property could be used to assign priority to rules. Rules.Item(1) represents a rule with ExecutionOrder being 1, Rules.Item(2) represents a rule with ExecutionOrder being…

1

Outlook 2007 and Simple MAPI

We have seen a lot of applications that use Simple MAPI. Unlike Extended MAPI (or MAPI), it is supported in managed code as well.Also, a lot developers have come across issues with Simple MAPI with Outlook 2007.Starting with Outlook 2007, Simple MAPI is no longer supported. However, its still supported by Exchange 2003.http://msdn.microsoft.com/en-us/library/cc815424.aspx

1

Using Powershell to send email message using CDOSYS

Scripts are used do a pre-check before getting started with debugging application.VB Scripts being the favourite on Microsoft platform.Most common being CDOSYS issues.Below is the Powershell script to send email using System.Net.Mail namespace.[System.Net.Mail.MailMessage]$message = New-Object System.Net.Mail.MailMessage(“from@contoso.com“, “to@contoso.com“, “This is Subject”, “This is body”)[System.Net.Mail.SmtpClient]$client = New-Object System.Net.Mail.SmtpClient(“XXX.XXX.XXX.XXX”)$client.Timeout = 100$client.Send($message)Long live Powershell!

0

PST folder Hierarchy

The article sheds light into how PST folder hierarchy is created.Adding a PST to an existing profile doesn’t create the all the Special Folders and looks as below: We have the IPM Root, Common Views, Search Results, Deleted Items under the “Top of Personal Folders”.In short, the IPM subtree doesn’t gets fully constructed which should…

1

What you need to know about MAPI properties

MAPI properties runs from 0001 to 3FFF4000 to 7FFF belongs to message and recipient properties, and either clients or service providers can define properties in this rangeNamed properties – 8000 onwardsSecure profile properties for Service providers – 0x67F0 through 0x67FF When we use Named properties, MAPI picks up an available property identifier. This way it…

1

GetAttachment doesn’t get Size of the attachment

For those, who don’t use Exchange Web Services API, but bank on its Requests and Responses.An email message has a attachment table that contains the attachments, and these in turn contain the properties such as PR_ATTACH_SIZE, PR_ATTACH_DATA_BIN etc. This means that email message doesn’t have any of the attachment properties on it.The GetItem could be used…

0

Personal Store (PST) without Outlook

Is there a way to access Personal Store (PST) wihtout having Outlook installed?Reason: Take out the Outlook dependency from PST 😉Further to SGRIFFIN’S blog:http://blogs.msdn.com/stephen_griffin/archive/2007/03/19/mapi-and-exchange-2007.aspxExchange 2007 onwards, MAPI isn’t included on the box and available as separate download:http://www.microsoft.com/downloads/details.aspx?FamilyID=e17e7f31-079a-43a9-bff2-0a110307611e&DisplayLang=enThe MSPST32.DLL shipped in this ExchangeMapiCdo download is the one of Exchange, that doesn’t provide support for Unicode.So, there…

1

How to get the body of the email message using Exchange 2007 Web services

Futher to SGriffin’s Weblog as below:http://blogs.msdn.com/stephen_griffin/archive/2007/02/09/exchange-web-services-and-internet-message-headers.aspxin order to access the body of an email message, the MAPI property PR_BODY_HTML (0x1013) could be used.However, we need to remember the property is binary in nature and base64 encoded.Here comes Convert.FromBase64String, System.Text.ASCIIEncoding to our rescue using which the ASCII of the body could be got, as below:    byte [] bAscii…

0

 getting inserted before the base64 encoded representation of the binary data of GIF image

When an application is creating a CDO[6.5.6756.0] Message and inserting a BodyPart of the type GIF image, and the base64 encoded representation of the binary data is initialized to the body part as shown below:Const c_Base64Sample = “R0lGODlhEAAOAPcAAAAAAIAAAACAAICAAAAAgIAAgACAgICAgMDAwP8AAAD/AP//AAAA//8A/wD”sFile = “sample.gif”sContentType = “image/gif”Set iPartAttach = iPartBody.AddBodyPartiPartAttach.ContentMediaType = sContentType & “; name=””” & sFile & “”””iPartAttach.ContentTransferEncoding = “base64”iPartAttach.Fields(“urn:schemas:mailheader:priority”)…

0