Programmer 7500

home *** CD-ROM | disk | FTP | other *** search

/ Programmer 7500 / MAX_PROGRAMMERS.iso / PROGRAMS / UTILS / NOVELL / PMAIL2.ZIP / INSTALL.DOC next >

Wrap

Text File | 1991-02-01 | 13.1 KB | 305 lines

Installing Pegasus Mail: ------------------------------------------ Pegasus Mail requires Novell NetWare ELS-I, ELS-II, 2.15C (Advanced or SFT) or NetWare 386. It needs a minimum of 320Kb on the work- station to run. It is essential that the default NetWare file structure on volume SYS: exists, specifically the NetWare-defined user mail directories under SYS:MAIL. Since NetWare creates these directories automatically, this requirement is usually self- fulfilling. Installation ------------------------------------------ To install Pegasus Mail, copy the files pmail.exe, newmail.exe and pegasus.hlp to a publicly-accessible directory on your network file server. Note that Pegasus.hlp and Pmail.exe must be in the same directory, or Pmail will not be able to locate its help. Newmail.exe can be placed elsewhere if you wish. Pconfig.exe is usable only by supervisor-equivalent users, and should be kept away from public access. Existing users can then use the program immediately. There are no extra steps required when creating users to allow them to use the system they have all they need merely by existing. Modifying NET$LOG.DAT ------------------------------------------ You should modify NET$LOG.DAT, the NetWare system login script, on the host server to contain commands similar to the following: #newmail if "%ERROR_LEVEL" > "0" then begin write "" pause end This invokes the Pegasus Mail newmail utility, which reports the number of unread messages the user has when he logs in. The write statement prints a blank line, while the pause statement gives the user a chance to see the message printed by newmail. Newmail will check for new mail on all servers to which you are attached and logged in. SUPERVISOR-equivalent users can check for mail for other users on the default server by entering "newmail USERNAME". Allowing remote server access ------------------------------------------ Pegasus Mail can deliver mail to users on other file servers if access codes are provided. When a user attempts to send mail to a user on a remote server, Pegasus Mail searches a Supervisor-defined internal table for a usercode and password on the remote server. If one is found, the system uses it to log into the remote server and deliver the message. If none is found, the system attempts to log into the remote server as the NetWare GUEST user. If all attempts fail, an error is reported to the user. To define the access information Pegasus Mail needs for remote servers, the Supervisor or a Supervisor-equivalent user should run the pconfig.exe program on the distribution disk. Pconfig presents a menu offering `Interface definition' (this option is covered later) and `Server Access definition'. Select the latter, and a window will open. If you press <Enter> while the `Add a server' entry is high- lighted, another window will open prompting you for information about the remote host. You should enter the file server's name, and a usercode and password Pegasus Mail can use on that server. The data is stored in a heavily- encrypted format which should be secure from even an ardent hacker. You can create any number of entries for remote server access the list will scroll when you have filled the window. When you have finished defining servers, press <Ctrl-Enter> to accept the definitions and return to the main menu. Choose `Save and Exit' to store the definitions. The usercode you create for mail access should be extremely limited. I recommend that it NOT be a member of group EVERYONE, and that it should have only one explicit trustee right granted to it [C] (or [CW] under NetWare 286) rights in SYS:MAIL. Pegasus Mail does not need access to any other directory on the host server, nor does it need access to any NetWare utilities. Pegasus Mail logs into the remote server for the shortest possible time to deliver mail or examine usernames, and guarantees that the user will never be left logged-in to the remote host under the mail usercode. Note: if a mail usercode on a remote server has an expired password, Pegasus Mail will fail when delivering the message, even if grace logins are enabled and plentifully available. Installing Pmail for an SMTP gateway ------------------------------------------ Pegasus Mail 2 supports the Charon v3 SMTP gateway by Brad Clements of Clarkson University (to be released early in February 1991). To install Pegasus Mail to use this gateway, run the Pconfig program supplied and choose `define Clarkson interfaces': a dialog window will appear. You must provide the following information: Queue name: this is the name of the print queue you have created (using the NetWare PConsole utility) from which Charon expects to retrieve messages. The queue need not exist at the time you define the interface. Use always: enter `Y' if you want Pegasus Mail to use the gateway for all messages, including mail to other servers. If you select `N', Pegasus Mail will only pass mail with Internet addresses to the gateway, and will use its own mechanism for all other messages. Server's internet name: Enter here the internet identity you have defined for this file server. Note that this is NOT the same as the name of the gateway itself. This address is used to form the sender's address for replies. For more information on naming, see the Charon manual. Our time zone: Type here the UNIX-format abbreviation for your time zone: this is required by the RFC822 standard for message format. Examples of time zones are: EDT, PST, GMT, GMT+1200. When you have filled in all the blanks, accept the data. That's all there is to it! Supervisor notes ------------------------------------------ Pegasus Mail makes a variety of control features available to NetWare Supervisors: these are mostly in the form of NetWare user groups, created using the Syscon utility. Pegasus Mail is aware of the following groups: MAILUSERS: If this group exists, Pegasus Mail will only run for users who are group members. Use this to control who has access to the mailing facility. If the group does not exist, all users will be permitted access. GROUPMAIL: If this group exists, Pegasus Mail will only allow mailing to NetWare user groups (using the # prefix in addresses) to members of this group. If this group does not exist, all users will be able to groupmail. GW_USERS: If this group exists, only its members will be permit- ted to send mail via the Internet gateway, if one is defined. If the group does not exist, all users will be able to mail via the gateway. Note that the gateway itself can perform access checks, and can refuse to send mail in its own right. Pegasus Mail and Microsoft Windows v3: ------------------------------------------ Pegasus Mail has been extensively tested under Microsoft Windows v3, and has been found to work properly in all modes. When designing the .PIF file for it, you should specify a minimum of 256Kb RAM, and a desired amount of 384Kb. When using Windows v3 (which requires the 3.01 NetWare shells or later to operate correctly) Pegasus Mail's notification messages for new mail will be fielded in a Windows dialog box. Pegasus Mail and DesqView, DesqView 386 and the Novell Access Server (NAS) ------------------------------------------ Earlier versions of Pmail did not run correctly in these environ- ments: version 2 will function properly, but must be set up as a full screen application. Granting extended features to users: ------------------------------------------ Pegasus Mail v2 supports a number of special features which can be enabled on a user-by-user basis by the supervisor: these features are: * Autoforwarding: the ability to redirect mail sent to one address to another address. Pmail allows you to redirect local and internet mail (from the Charon v3 gateway) to different addresses. * "Request for confirmation" denial: by default, Pegasus Mail will honour requests for confirmation of a message being read. Since this is a controversial issue, the supervisor can allow individual users to refuse to honour requests for confirmation. When a user attempts to send a message with a confirmation request to a user who has disabled this feature, a window will open immediately the message is sent indicating that no confirmation will be provided. * Delivery even while autoforwarding: if this flag is set, then a a copy of the message will be delivered even when autoforwarding is active. The message will also be autoforwarded. * Disable mail: it is possible to disable mail altogether for an account. Both Pmail and Charon v3 respect this flag. * Notification disable: individual users can indicate that they do not want the notification messages Pmail generates when mail is delivered. Both Pmail and Charon v3 respect this flag. Pegasus Mail will also support auto-reply in the next release. To grant extended rights to a user or users, run the PCONFIG program, and select "grant Extended feature rights" from the main menu. A small window will open listing all the users who currently have extended rights enabled. You can select multiple users in this list using the <F5> key - an asterisk (*) will appear next to marked users. To remove a user's extended feature rights, highlight his usercode (or select a group of codes using <F5>) then press <Del>. THIS DOES NOT DELETE THE USER! It only removes the extended rights. To grant extended rights to a user or users, press <Ins>. Another window will open listing those users who do not have extended feature rights. Again, you can select multiple users with the <F5> key. Highlight the user or users who need rights, and press <Enter>. The window will close, and they will be added to the main list. You can edit an individual user's extended features by selecting him from the main list, and pressing <Enter>. A small editing window will open. Note that any address you enter into the "Internet AF" field (that is, the autoforwarding address used by Charon v3 for autoforwarding internet mail) must be an internet format address: the NetWare syntax used by Pmail (eg, ALKALI/SUPERVISOR) is not understood by Charon v3 and will result in delivery errors. You can also control whether or not a user can alter his own extended features: highlight the user, or users on the main list, and press ^W (ctrl-W). A small window will open, and you will be asked if the user(s) is to be granted write access. If you select 'Y', the user(s) will be able to edit his own extended features (a prompt will appear when he is in his user profile indicating that he can press <F9> to edit extended features); if you select 'N', then the user will not be able to alter his extended features - he will be forced to use whatever values you set for him. If the user does not have write access to his extended features, the prompt will not appear when he is editing his user profile, and he will not be able to see or change the extended values. The ^A key in the main list enables auto-reply, which is not currently supported in v2 of Pegasus Mail. Manuals: ------------------------------------------ Manuals containing more detailed installation instructions, and full user documentation can be ordered from the author: please see the files README2.0 and ORDER.FRM in this release for more details on ordering. Licensing: ------------------------------------------ Pegasus Mail is free software. You may freely use it on all your file servers and may distribute it freely provided that the original dis- tribution is provided in full, that no part of the system, programs or documentation is altered, and that no charge is levied for the supply other than a reasonable small fee for media. Pegasus Mail is (c) 1991, David Harris, Dunedin, New Zealand, all rights reserved. Because the software is freely distributed, no warranty of performance or fitness for purpose is provided, either explicit or implicit. The author can be contacted as follows: Internet: david@otago.ac.nz (from CompuServe, the address is internet:david@otago.ac.nz) Phone (sensible, non-business hours only please, NZ is GMT+1200) (ISD 64) 3 - 453-6880. I am normally glad to help where possible, but those of you with internet access should consider joining the Pegasus Mail Users' Group, by sending a subscription request containing your name and e-mail address to: pmail-updates@splicer.cba.hawaii.edu. (CompuServe: internet:pmail-updates@splicer.cba.hawaii.edu) Pegasus Mail is not a product of the University of Otago, and the University does not officially endorse it, but the author is grate- ful for the moral support and help the University has given. David Harris, PC Consultant, University of Otago, Dunedin, New Zealand. 1 Feb '91.