>Due to some performance and reliability issues with our current NT e-mail
>server, I have been given the task of replacing the current NT system with
>a SCO UNIX based system.
LDAP doesn't make much sense with only one email server. TheQuote:> - I plan to use LDAP slapd for internal e-mail directory service or I may
>just have a the e-mail directory in a file that is read-only exported.
idea is to allow users to move around the world and have their
email environment follow. The mail will always come from the
same place. Since the SCO Unix box will probably not have any
shell logins and only store passwords for picking up POP3 mail,
there's no environment to propogate. Since passwords are
imbedded in the POP3 mailer, there's no benifit to a single login
scheme. I don't think you'll need LDAP. Keep it simple.
Also, the email directory cannot be read-only as users are
expected to clean out the messages they have read. The files in
the mail spool directory are readable and writeable only by the
user (and the MTA).
One small problem. The default Windoze 95 POP3 polling scriptQuote:> - I plan to use popper which comes with v5.0.4
does not work. You need to use the Windoze 95 scripting tool to
create suitable login script. See:
I vaguely recall having some problems with the " " marks in
different versions of Windoze 95. 2am is not the time for
Setup the DNS on the SCO Unix box as a secondary domainQuote:> - *the bad news is that the DNS server is still a WinNT server.*
controller for the NT server and have the NT box propogate DNS
updates. When that NT server finally blows up, you'll still have
a working DNS system.
[x]email [x]news [ ]mailing list
Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
(408)699-0483 pgr (408)426-1240 fax (408)336-2558 home