Re: stupid smtp/mapi question

david20_at_alpha2.mdx.ac.uk
Date: 02/04/04 

Date: Tue, 3 Feb 2004 23:56:45 +0000 (UTC)

In article <XCETb.12664$L02.4728@newssvr22.news.prodigy.com>, Michael Austin <maustin@no-more-spam.firstdbasource.com> writes:
>Rut wrote:
>
>> Could someone explain the differences between smtp and mapi calls to
>> send mail? If my company used Microsoft exchange and I have a program
>> making smtp calls, what exactly is going on? Do the calls still go
>> through the exchange server or do they somehow get routed through the
>> mainframe?
>>
>> THanks,
>> Rut
>
>
>SMTP is a mail protocol -- servers speak this "language" to other servers
>
As do all SMTP mail CLIENTS.

SMTP is a protocol for transfering mail messages between systems.

>MAPI is an Mail Application Programming Interface for a mail client --
>your mail client (Outlook, Netscape, etc...) takes the message you have
>written and uses a client that talks to an interface on the mail server
>which then transmits the message via the SMTP protocol to the recipient
>domain mail server.
>
>So, in short MAPI is a client to/from server, SMTP is server to server.
>
NO.

MAPI is a Messaging API. It is used to write mail/messaging applications.

MAPI is a messaging architecture that enables multiple applications to interact
with multiple messaging systems seamlessly across a variety of hardware
platforms.

From
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/mapi/html/_mapi1book_concepts_and_architecture.asp

"MAPI is made up of a set of common application programming interfaces and a
dynamic-link library (DLL) component. The interfaces are used to create and
access diverse messaging applications and messaging systems, offering a uniform
environment for development and use and providing true independence for both.
The DLL contains the MAPI subsystem, which manages the interaction between
front-end messaging applications and back-end messaging systems and provides a
common user interface for frequent tasks. The MAPI subsystem acts as a central
clearinghouse to unify the various messaging systems and shield clients from
their differences.
"

When sending messages a MAPI application could well use SMTP as the
underlying protocol to send the messages.

MAPI compliant Client APP MAPI compliant server
     | |
   SMTP ------------->--------------- SMTP

From

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/mapi/html/_mapi1book_concepts_and_architecture.asp

"
MAPI provides cross platform support through such industry standards as SMTP,
X.400, and Common Messaging Calls (CMC)."

David Webb
VMS and Unix team leader
CCSS
Middlesex University

>
>Michael Austin
>

Relevant Pages

  • Re: OE6 and AVG (Free Edition)
    ... but the post only mentioned MAPI. ... > locally) IMAP, you need POP3 to scan locally. ... > messages stored on the server. ... Mail in a normal SMTP transaction; not in my LAN environment, ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • Re: Client vs Server storage
    ... the server is down, ... SMTP is the transport mechanism used for internet email. ... I think what you are describing is MAPI. ... Seriously, if you are going to just do POP3, save your money and get ...
    (microsoft.public.exchange.setup)
  • Re: SMTP vs. MAPI
    ... SMTP is easier to code against. ... To call MAPI ... Exchange server... ... MAPI requires exchange server. ...
    (microsoft.public.dotnet.general)
  • Re: NTDS Inter-site Messaging ERROR!
    ... I have a domain with one SBS server and another W2K3 server ... None of the Exchange Services ... The Intersite Messaging service could not receive any messages for the ... The Intersite Messaging service using the SMTP ...
    (microsoft.public.windows.server.networking)
  • Re: NTDS Inter-site Messaging ERROR!
    ... I have a domain with one SBS server and another W2K3 server ... None of the Exchange Services ... The Intersite Messaging service could not receive any messages for the ... The Intersite Messaging service using the SMTP ...
    (microsoft.public.windows.server.networking)