× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: email API... to and CC:the same..
  • From: Tim McCarthy <timm@xxxxxxxxxxxx>
  • Date: Fri, 26 May 2000 11:23:46 -0400

> I dont understand much of this, but I got similarly confused, and came
> to
> the conclusion that SMTP sends ONE copy to a domain. So if you TO/CC
> to the
> same domain (irrespective of the user on that domain), SMTP only sends
> one
> copy of the message.
> 
        [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.

> HTH,
> 
> Brendan
> 
> > -----Original Message-----
> > From: owner-midrange-l@midrange.com
> > [mailto:owner-midrange-l@midrange.com]On Behalf Of Stone, Brad V
> (TC)
> > Sent: 25 May 2000 14:11
> > To: 'MIDRANGE-L@midrange.com'
> > Subject: RE: email API... to and CC:the same..
> >
> >
> > I did some testing.  I used my yahoo account, my work account
> (running on
> > outlook server), and the AS/400.
> >
> > >From AS400 to Outlook, I got one copy.
> > >From Outlook to outlook, I got one copy.
> > >From Yahoo to Outlook I got three copies.
> > >From Outlook to Yahoo I got two copies.
> > >From AS400 to Yahoo I got one copy.
> >
> > Odd.  This is specifying the same name on to, cc, and bcc.  May
> > be a mix of
> > the server and the client.
> >
> > Brad
> >
> >
> > >   [Tim McCarthy]  The server won't but the API might. It's the
> > > client that determines who gets copies of the message. An SMTP
> server
> > > doesn't know who's CC'ed and who's BCC'ed - that's a client
> > > determination.
> > >
> > +---
> > | 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
> > +---
> >
> 
> +---
> | 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
> +---
+---
| 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.