Re: OT: Vista


"D.Duck" <Don@xxxxxxx> wrote in message
news:B6adnaLcFomvxbjbnZ2dnUVZ_silnZ2d@xxxxxxxxxxxxxxx

"Nate" <nsaptaemcscpnanm@xxxxxxxxxxxxxx> wrote in message
news:%xcVh.4539$H_5.1815@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx

The OS will communicate in terms of SMTP, or another e-mail protocol.
Those protocols did not change in Vista. If the workstation has an
issue communicating it would likely be with the server that serves the
e-mail protocol (services). But it is VERY unlikely that Chuck's
computer even talked to his friend's computer...let alone communicated
with it. I would think he has a firewall.

Nate

You're saying that in some circumstances two computers sending/receiving
email have "direct" contact?

I'm saying in most cases they do not have direct connection.

However...there are cases where two computers would communicate e-mail
directly. Both would need to have a protocol service running to
transport the message...or it would have to send in straight text...a
simple file level command...copy/paste.

Nate

So in simple terms, the email service most of us use, the
sending/receiving PCs do not directly communicate.


I would say that is accurate.

In my case...my PC uses an application to generate an e-mail. Be it OE,
Outlook, Mozila...whatever app it is...it generates a message and then
creates a package to send to the SMTP server. That server uses DNS to route
the message to another server. The message package is transmitted across
the network and decoded at the other end. The decoded mesaage is then sent
from the receiving server on to a client on that network. That client would
need an e-mail reader application to open the message.

In a sense, the two clients are communicating. The applications on those
two clients will need to open and understand the package. That is typically
not an OS level issue though. It's an application. So you have OS, client
applications, server applications and services all running in this
communications scenerio. And that is keeping it simple.

Nate


.

Relevant Pages

  • Re: network booting
    ... So the client would need to tell on which offset into on of the ... The client asks the server to open a specific file (by ... component of DOS 3.3, as well as RWTS. ... code on the C64 can send commands (using a serial protocol called IEC) ...
    (comp.sys.apple2)
  • Re: client -server interaction over XML supporting multiple protocols
    ... > NETBEUI to access the server to access the functionalities exposed. ... > server doesnot know in advance which client is using what protocol. ... size of the XML and Xfunctionality will determine the demands ...
    (comp.lang.cpp)
  • OpenSSH: SSH2 sshd - Increase key size from 2048 to 8192 bits (Cygwin)
    ... I am only using the SSH2 protocol. ... key, normally 768 bits, generated when the server starts. ... The client compares the RSA host key ... the server and the client enter an authentication ...
    (comp.security.ssh)
  • Authenticating authorised clients was Re: Helpful clients in client-server Nethack
    ... I don't see how an asymmetric cypher would help. ... that the client is approved by the organisers. ... CHAP, challenge handshake authentication protocol. ... The closed source clients and server know a passphrase. ...
    (rec.games.roguelike.nethack)
  • Re: Help a Noobie please with opening a port
    ... Unless the WARP client is making CERN proxy requests, ... 'Selected Protocols' and created a new protocol using Port range ... LocalHost or Internal (if on other server) ... Microsoft ISA Server Partners: Partner Hardware Solutions ...
    (microsoft.public.isaserver)