|
|
Browse by Tags
All Tags » DevMsgTeam » MIME (RSS)
Showing page 1 of 2 (15 total posts)
-
We had an issue recently where the customer had written an application to process MIME messages that had body parts encoded with the koi8-r charset …or at least that’s what it said: ------_=_NextPart_001_01C9F067.D9742103 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable If you use code similar to the following, the resulting characters returned were not correct. private string ReadBodyPart() { CDO. IDataSource oIDsrc; ADODB. Stream objBpStream = new
-
Recently, I helped a customer with an issue where they were wondering if it was essential to set the ToRecipients , CcRecipients , and BccRecipients if they were setting the same values in the MimeContent property when doing a CreateItem call in Exchange Web Services. While trying to test out the scenarios, I thought “maybe it depends on the order of the elements in your <t:Message>. I soon realized that the order of the properties in the <t:Message> node seemed to matter. As it turns
Posted to Wiz/dumb (Weblog) by pcreehan on September 16, 2009
Filed under: MIME, Exchange 2007, Exchange Web Services (EWS), DevMsgTeam
-
Redistribution of files in the “ C:\Program Files\Microsoft\Exchange Server ” folder and sub-folders is not advised/supported. Yes, this does include the “C:\Program Files\Microsoft\Exchange Server\Public” folder also. These files are installed when the Exchange 2007 (or later) tools are installed. If you need these files with the minimal installation, then use the Exchange installer to install them – the box will need to be at least in an Exchange Admin role. There is no installer/redistributable
Posted to Dan's WebDAV 101 (Weblog) by danba on April 2, 2009
Filed under: Microsoft.Exchange.Data.dll, powershell, Microsoft.Exchange.Data.Directory.dll, HOWTO, Exchange, Exchange 2007, 2007, mime, distribution, DevMsgTeam, installer, multivalve, C:\Program Files\Microsoft\Exchange Server, installation, transport agent, Microsoft.Exchange.Data.ContentTypes.dll, eula, redistribution
-
I’ve worked quite a few cases recently regarding problems some folks have had either reading or composing TNEF content. I’ve learned quite a bit myself as a result, and I thought I’d share. I decided I would do a series of blog posts on the topic and hopefully save some of you the time I spent learning all this. So, being the first post on the topic, I suppose now would be a good time for a review on just what TNEF is and how it’s structured. TNEF stands for Transport-Neutral Encapsulation Format.
Posted to Wiz/dumb (Weblog) by pcreehan on January 16, 2009
Filed under: Outlook, Exchange, MAPI, MIME, DevMsgTeam, TNEF
-
Microsoft released preliminary protocol documentation for Exchange 2007 (as well as Microsoft Office 2007 and SharePoint Server) as part of Microsoft's Interoperability Principles. The Exchange protocols are now publicly available on the Open Protocol Specifications section of MSDN in preliminary form for developers to review and provide feedback. You can read more about the announcement in this press release. Here is the press release: Microsoft Publicly Posts Additional Protocol Documentation http://www.microsoft.com/presspass/press/2008/apr08/04-08ProtocolPR.mspx
Posted to Dan's WebDAV 101 (Weblog) by danba on May 1, 2008
Filed under: Outlook, meeting, WebDAV, Exchange, properties, security, VCalendar, mime, stream, appointment, distribution, attachments, .msg, mapi, authentication, category, messaging, c++, property, icalendar, availability, folders, descriptor, access, http, rtf, format, transport, meeting requests, guid, autodiscovery, permission, attachent, rfc2445, personal, sms, encode, book, s/mime, rpc, resources, protocol, users, uid, decoding, client, configuration, message body, redirects, X-, rfc2447, rss, ietf, specifications, groups, directory access, protocal, nspi, flagging, journal, mailbox, attachements, extends, personal distribution, flags, provisioned, streams, note, address, events, working, encoding, compressed, search folder, permissions, server, permissible, conversion, standard, schema, hours, directory, body, offline, rfc2446, behalf, structures, notifications, oab, converts, smtp, address book, remote operations, operations, contacts, structure, response messages, MS-OXO-, decode, compressed stream, warning, rights-management, retrieval, information, core, enriched text format, forum, specs, extensions, .msg file, structs, bulk, msg files, object, best body retrieval, voice mail, .msg files, reminder, msg file, bulk data transfer, rights management, enriched, support, mms, templates, pop3, data transfer, phishing, best, compression, document, documentation, DevMsgTeam, webdav101blog
-
Microsoft released preliminary protocol documentation for Exchange 2007 (as well as Microsoft Office 2007 and SharePoint Server) as part of Microsoft's Interoperability Principles. The Exchange protocols are now publicly available on the Open Protocol Specifications section of MSDN in preliminary form for developers to review and provide feedback. You can read more about the announcement in this press release. Here is the press release: Microsoft Publicly Posts Additional Protocol Documentation http://www.microsoft.com/presspass/press/2008/apr08/04-08ProtocolPR.mspx
Posted to Dan's WebDAV 101 (Weblog) by danba on May 1, 2008
Filed under: Outlook, meeting, WebDAV, Exchange, properties, security, VCalendar, mime, stream, appointment, distribution, attachments, .msg, mapi, authentication, category, messaging, c++, property, icalendar, availability, folders, descriptor, access, http, rtf, format, transport, meeting requests, guid, autodiscovery, permission, attachent, rfc2445, personal, sms, encode, book, s/mime, rpc, resources, protocol, users, uid, decoding, client, configuration, message body, redirects, X-, rfc2447, rss, ietf, specifications, groups, directory access, protocal, nspi, flagging, journal, mailbox, attachements, extends, personal distribution, flags, provisioned, streams, note, address, events, working, encoding, compressed, search folder, permissions, server, permissible, conversion, standard, schema, hours, directory, body, offline, rfc2446, behalf, structures, notifications, oab, converts, smtp, address book, remote operations, operations, contacts, structure, response messages, MS-OXO-, decode, compressed stream, warning, rights-management, retrieval, information, core, enriched text format, forum, specs, docment, extensions, .msg file, structs, bulk, msg files, object, best body retrieval, voice mail, .msg files, reminder, msg file, bulk data transfer, rights management, enriched, support, mms, templates, pop3, struct, data transfer, phishing, best, compression, document, documentation, DevMsgTeam
-
There is no mechanism to add an attachment in WebDAV. You will need to create/recreate the item using a WebDAV PUT. The text you would be putting would be the mime of the item, which also contains the attachment. It’s useful here to use CDOSYS to create a message and add an attachment – then extract the MIME from the message and use it for the WEBDAV PUT. You will need a header of "translate" set to "f". If the message already exists, you will need to, you must do a GET on the message stream, which
Posted to Dan's WebDAV 101 (Weblog) by danba on March 12, 2008
Filed under: WebDAV, Exchange, mime, message, get, put, example, attachmentment, add, DevMsgTeam, webdav101blog
-
' This example shows how to enumerate attachments on a message. X-MS-ENUMATTS will ' return phantom urls to attachments on the message. These URLs can be used with GET ' and DELETE (starting with Exchange 2003 SP1). ' For listing and reading an attachment, you will first need to get a list of attachments ' using X-MS_ENUMATTS. After getting the list of attachments you will need to parse out ' then the URL from the returned information, you can then do a GET to read the attachments. First get a list
Posted to Dan's WebDAV 101 (Weblog) by danba on March 12, 2008
Filed under: WebDAV, Exchange, mime, stream, attachments, attachment, VB, message, enumerate, delete, get, sample, item, folder, vbscript, script, example, X-MS-ENUMATTS, DevMsgTeam, webdav101blog
-
' This example shows how to do a PUT of a message to a folder. What is being written with a PUT would ' be the MIME of a message and such MIME can also contain the MIME of the message. PUT works against ' messaging items directly such as mail messages. It cannot be used to add an attachment without ' recreating the entire message. PUT is a desctructive write against the URL specified. ' You can use Outlook Express to create a mime message. To use this sample, create a mime message ' and save it as
Posted to Dan's WebDAV 101 (Weblog) by danba on March 12, 2008
Filed under: WebDAV, Exchange, mime, VB, read, get, put, translate, sample, vbscript, script, example, DevMsgTeam, webdav101blog
-
'The example below demonstrates how to do a WebDAV GET. ' GET works against items and attachments. When used against an item, it give you ' the mime stream of both the message and attachment. You cannot get the mime of only the message ' if there are attatchments on that message. Use X-MS-ENUMATTS to enumerate attachents - this returns ' back a phantom URL for each attachment which can be used by GET. ' NOTE: You need to have a header of "Translate" set to "f" in order to read mime of an item with
Posted to Dan's WebDAV 101 (Weblog) by danba on March 12, 2008
Filed under: WebDAV, Exchange, mime, VB, read, get, translate, sample, vbscript, script, example, DevMsgTeam, webdav101blog
1
|
|
|
