Xref: utzoo comp.mail.sendmail:2315 comp.mail.misc:4230
Path: utzoo!attcan!uunet!know!zaphod.mps.ohio-state.edu!wuarchive!udel!rochester!kodak!mccrave
From: mccrave@kodak.kodak.com (Donna McCrave)
Newsgroups: comp.mail.sendmail,comp.mail.misc
Subject: Mail architecture
Message-ID: <1990Oct29.170344.27870@kodak.kodak.com>
Date: 29 Oct 90 17:03:44 GMT
Distribution: na
Organization: Eastman Kodak Co.
Lines: 23

Here is your chance to wax philosophic on the net.  I have the
task of "making the email in our division work."  The rest is
up to me.  My group has about 400 Sun systems spread out over
three plants.  There are some other miscellaneous systems, but
the main concern is smtp mail.  There is a mix of stand alone
systems, data-less clients, disk-less clients, and large file
servers.  Most systems use NIS.  We will also be providing
Internet mail, and have our own subdomain.

I would like to design an architecture that requires minimal
effort to keep going.  It should be easy to bring systems in and
out of the loop. I don't mind replacing the libc.a's on all the
machines with the libc.a that includes libresolv.a.  I know that
I need to set up a rather intelligent mail hub, but I am unsure
of the role that the rest of the systems should play in order
to keep maintenance of sendmail configurations to a minimum.

Does anyone have any recommendations on an email architecture
for a large department, or any leads on some reference material?
 

Donna McCrave
mccrave@SSD.Kodak.COM