On 10/18/07, John Weller <[EMAIL PROTECTED]> wrote: > This is where Outlook objects and MAPI score for me, I am basically > automating the keystrokes used to send an email in a similar way to > automating mail merge with Word.
The problem I have found (after surviving many versions of MAPI, CDO, etc.) is that Microsoft has little interest in providing compatibility to their API from version to version. While SMTP and other APIs are _standards_, MAPI is whatever Microsoft says it is today. I have had applications break when some MS API breaks, some of them with large deployments and costly repairs. That's why "MAPI Bad, SMTP Good." > Can anyone recommend a *simple* book on this area which doesn't assume any > prior knowledge? I don't even know what Winsock means or implies but can > nod sagely in the appropriate places (more or less) when it is mentioned. > First, I'd suggest you identify and narrow down the areas you'd like to learn more about. "Winsock" is the Windows implementation of the 'sockets' feature of networking, something like individually named slots that applications use to communicate with each other. Mail technology is a layer above that, with MTAs, MUAs, SMTP, IMAP, POP and those acronyms are explained on many fine pages like http://cr.yp.to/mail.html. Google is your friend. -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
