Outlook Automation (parsing MSG files)

Andy Hilton andyh at totallybrilliant.com
Wed Mar 4 17:52:26 EST 2015

That’s it, blame it on the marketing person - it usually is their fault anyway :)

> On Mar 4, 2015, at 3:51 PM, Kelly Burgess <kellyb at montana.com> wrote:
>> Kelly ? Cannot see anything like that on your web pages ???
> Hi Andy,
> I'll talk to my marketing person about that, but he isn't a good listener.  You'll recognize that when you see 'New' tags on things that are several years old - not to mention still seeing listings about Omnis 3+ and Omnis 5 externals that won't even work on modern OSes. . .
> Here's the ParseMSG external command I built for Alain -
> ;  ParseMSG.Summarize (MSGpath, summaryList [,partsFolderPath]) Returns err
> ;  - MSGpath is the path to the .msg file you want to summarize
> ;  - summaryList is a 2-column list of name / value character fields, defined before calling, filled with summary info on return
> ;  - partsFolderPath is an optional path to an existing folder where .msg parts (message and attachments) will be written on return
> ;  -    (omit the third parameter to get a summary list only; include it to have any attachments written out to disk files)
> I'll send you a screenshot off list, but essentially the parts you get back include (at least the one I just tested did) :
> Subject, Reply Type, Message ID, From, Prefix, Body, Number of Attachments, Recipient Names (To/CC/BCC), Date Sent, Date Received, Date Reply.
> I see plain text in Body, but I don't know if the original I parsed contained html markup or not.
> Kelly
> _____________________________________________________________
> Manage your list subscriptions at http://lists.omnis-dev.com

More information about the omnisdev-en mailing list