Shamil Salakhetdinov
shamil at users.mns.ru
Thu Nov 3 18:47:38 CST 2005
> MAPI is much richer, there are lots of things you can do with your own > direct MAPI calls Stuart, Yes, I know about MAPI, and about simple MAPI (I did write programs using it starting MS Access 2.0 in 1995) and I read RFC2368 etc. But using MAPI I can only send e-mail via Outlook Express and Outlook - right? And I need a method to prepare (just prepare in popped-up e-mail client, not send) e-mail message with any e-mail client - and here mailto protocol seems to be the only free(built-in) solution? Still open question: - I'm just curious and I can't find answer by myself - how mailto protocol's URL is interpreted by MS Windows system for non-MS e-mail clients? I mean: - does MS Windows(xxxxx.dll) starts non-MS e-mail clients and passes them a special command line. If yes - what format this command line should have? if not - what other way MS Windows system uses to activate non-ms e-mail clients? Shamil ----- Original Message ----- From: "Stuart McLachlan" <stuart at lexacorp.com.pg> To: "Access Developers discussion and problem solving" <accessd at databaseadvisors.com> Sent: Friday, November 04, 2005 12:38 AM Subject: Re: [AccessD] ShellExecute to send short e-mail via non-MS emailclients... > On 3 Nov 2005 at 17:33, Shamil Salakhetdinov wrote: > > > > Works with Eudora. > > > Works fine for me with Pegasus Mail. > > > Works for me with Groupwise as well. > > > Works for Outlook > > > Works for Outlook Express > > Thank you everybody! > > Obviously it works with any default e-mail client on MS Windows. > > > > > How it works under MS Windows "hoods" is described here: > > > http://www.microsoft.com/mind/0199/cutting/cutting0199.asp > > > > For me this means there is protocol all the e-mail clients follow. > > And under MS Windows mshtml.dll seems to be the program, which is calling > > default mail clients - the question is how it does that? > > > > You are using two things here. > > 1. The URI mailto. > See RFC2368 > > > 2. MAPI. > This it the protocol used to call the email client under Windows. > > In this case, you are using a part of Microsofts built in browser > (mshtml.dll is part of IE) to convert a mailto: URI to a MAPI command. > > Note that mailto: is a very simple protocol which only has a limited number > of parameters and there are cautions about using some of these. > > <quote> > Note that some headers are inherently unsafe to include in a message > generated from a URL. For example, headers such as "From:", "Bcc:", > and so on, should never be interpreted from a URL. In general, the > fewer headers interpreted from the URL, the less likely it is that a > sending agent will create an unsafe message. > </quote> > > It's up to mshtml.dll which parameters it choses to pass through the MAPI > > MAPI is much richer, there are lots of things you can do with your own > direct MAPI calls from an application that you can't do with mailto: such > as include attachments and automatically send the message with no user > intervention > > -- > Stuart > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com