> >> b) exchange mail with an ISPs POP3 server
> > This part confuses me, or maybe leads me to believe that you are
> > confused. From my understanding, a POP3 client receives its mail
> > from a POP3 server, but sends it mail through an SMTP server (at
> > least that's how I've seen it work). Exchanging mail implies a
> > two way communication. Feel free to correct me if I'm wrong.
> Let me put this question another way... This client will not have a
> dedicated connection to the Internet. Therefore, we want our internal
> mail server to dial-out hourly and exchange mail with the POP3 server at
> the ISP. How can I accomplish this with the tools included in OSR
> 5.0.4?
Consider the following diagram:
ISP <--A--> SCO OpenServer <--B--> Windows Clients
Connection A is transient. SCO OpenServer will establish a connection
with this server hourly.
Connection B is constant. It's the internal network.
In the words of Bill Nye, Please, Consider the Following:
Electronic mail is based on a store and forward concept. Email moves
through the network by being copied from one machine to another,
until it reaches it's destination. Generally, at the centre of the
network is a hub, which touches all incoming and outgoing mail.
The movement between the systems is accomplished using Simple Mail
Transfer Protocol (SMTP). Programs like sendmail and mmdf are
Mail Transfer Agents that can talk SMTP. In our example, on
connection A you want to talk SMTP.
Mail is read by nodes in the network. In our example, the SCO
OpenServer box is the final resting place for e-mail. This is
the Post Office Box that mail is sent to. Once the mail has arrived
there, it is considered 'sent' by SMTP. A Mail User Agent then
reads this mail. Some Mail User Agents (Eudora, Netscape Mail)
use a Post Office Protocol to read the PO Box and transfer the
mail to another machine. This is different from SMTP. Other Mail
User Agents (mailx, scomail, scosh email) let the user read the mail
directly from the PO Box.
When a POP Mail User Agent sends mail, it cause an SMTP connection
to be created between the Mail Server and the Mail Client. In our
example, the SCO box would talk SMTP to the windows clients to receive
their outgoing mail and then forward it on to the ISP when the
hourly connection is made.
Understand? Thank you for Considering the Following.
Quote:> Thanks for the reply, its been like pulling teeth trying to get my
> questions answered here.
I'm assuming that you mean the newsgroup. I think your questions
are a little fuzzy and so people aren't taking the time to answer
them because the answers aren't simple. Part of this is because
you don't fully understand the nature of e-mail. There are some
very good books out there about e-mail and the SCO documentation
is actually pretty good as well. Look at the Mail and Messaging
Guide.
Quote:> Great to hear that dumb and smart terminals
> will share the same mail. Did I also understand that either a POP3
> client or SCO's graphical client can be used interchangeably?
Depends on how you have your POP Client configured. On my system,
I have my e-mail client (Eudora) configured to leave the messages
on the server when I retrieve them. It only deletes them after
14 days or when I delete them, which ever comes first. This is a
precausion against my laptop crashing and burning. If something
happened to my laptop, I'd still have the last couple weeks of
mail around. I can look at the e-mail on my server independantly
from my Eudora client.
Quote:> Which
> engine should I use? sendmail or mmdf? I know sendmail can get a bit
> overwhelming.
Religious debate. Pick one, join the sect :-).
If this is your first time configuring e-mail, you probably want
to get some assistance. Have you talked to a local SCO Reseller
in your area? If not, perhaps we could connect you with one.
--
----
Jim Sullivan "Don't plant your bad days. They grow into bad
SMB Segment Marketing weeks and then bad months and before you know it
416 216 4611
by