RE: email API... to and CC:the same..

Tim,
By mail client, I guess you dont mean the POP client, but the client that is
sending the mail to the SMtP server?

The client that sends tells the SMTP server the TO/CC addresses, and leaves
the server to pass them on.

The SMTP server talks to each of the target domains and passes on one copy,
irrespective of the number of users it is for. It leaves the SMTP server at
the target domain to route the mail to individual users within it's domain.

As I said, I am guessing that this is the procedure because it took me a
while to fit it logically together. Previously my experience had been using
a proxy server, and the AS/400 routes everything to the PC to forward on (as
a client).

NB My understanding is also that SMTP servers do not know the contents of a
mail, but they do know the 'envelope' that contains the addresses - which is
different than the TO/CC/BCC that we get to see. Which is why you can send a
BCC to a server, and it has the ability to route this mail without
announcing it.

Brendan

>       [Tim McCarthy]  No. SMTP servers do not understand the contents
> of the mail. They don't have the ability to determine who gets mailed
> and who gets copied - that's a mail client function. Some of mail client
> differences you're seeing may relate to the different client
> capabilities - some are SMTP clients, some are MAPI.

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---