Seth Galitzer
sgsax at ksu.edu
Tue May 13 13:47:52 CDT 2003
Arthur, Pegasus doesn't have an object model. It does, however, support a commandline mode for sending messages. Basically, you generate a text file containing the particulars of the message using a set of known line "tags", and then run Pegasus with a commandline flag and the path to the text file. You do not have access to the address book or mail folders using some kind of API. However, Pegasus does use standard mbox format for mail folders. At the worst, you could parse those maually. Address books are a different matter. If you have an option, you might want to look at Eudora, which does have an object model that is documented and has a pretty workable API. Alternatively, if all you need to do is send messages, I have some code that does this in a self-contained fashion that requires no ActiveX controls. It only works with Win2K & XP, however. I haven't found out why specifically, but I think it's just more dll hell. Pegasus is used widely here. It's not my favorite email client, but's it's pretty clean and has a relatively small footprint. Seth On Tue, 2003-05-13 at 11:52, Arthur Fuller wrote: > I have some slick email routines that work with Access, but until today they > have assumed Outlook and its object model. Suddenly I have to assume > Pegasus, about which I know nothing. I'll search the list for references in > a moment, but right now I don't know a thing about it. Is it easy? Tough? > What are the advantages of Pegasus as opposed to Outlook? Should I consider > switching my own email client? > > TIA, > Arthur > -- Seth Galitzer sgsax at ksu.edu Computing Specialist http://puma.agron.ksu.edu/~sgsax Dept. of Plant Pathology Kansas State University