Attached are some preliminary objectives for Mail and News. These
definitely need flushed out! Please give these attention! There are
several gaps (IMO) and the technical detail needs to be added.
Please review and comment as previously requested :)
-Kara
---------- Forwarded message ----------
Date: Mon, 4 Jun 2001 12:45:34 -0500 (CDT)
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Preliminary Kernel Objectives
In order to assist in speedy objective development, I've tried to start
developing some preliminary objectives for our tasks, based on the most
recent organizational structure. (I've only received one response to the
last thread on organizing!)
The objectives are definitely not complete in current form, nor are they
the concrete foundation we're forced to work with. The tasks are our
foundation (also attached). The goal is to create objectives which cover
these tasks and fill in the technical gaps and details.
Our Level 1 objectives
(http://www.lpi.org/http://www.lpi.org/p-obj-101.html and p-obj-102.html)
should provide a good outline for what form and style objectives should be
written in. I've modified slightly (including bullets for specified files
and tools covered) but the rest should be developed in the same fashion as
the current Level 1 objectives. There's no need to obsess over this step
at this stage, as I plan to have this completed in a stage of formal
review.
I would like either comments, changes, and additions as well as assistance
completing (technically) the objectives I've posted; your comments and
submissions for replacement or additional objectives; and your comments
for supplementary objectives (if any).
Please begin by reviewing the current objectives for Level 1 at the URLs
listed above. Next review the task file for this group. Finally, review
the preliminary objectives file and comment. Please note that the
preliminary objectives file associates the current task numbers with the
affiliated objective. Please continue to refer to these task IDs when
commenting, reorganizing, etc. objectives.
I will continue submitting preliminary objective files for various
categories today and tomorrow. I would like good discussion and progress
toward finalizing objectives in progress by Wednesday. By Friday, those of
you interested in the contract positions to finalize objectives should be
able to begin review. By next week, I would like to publish our objectives
for public review and begin collecting preliminary items.
The next 10 days are going to be crazy, and I greatly appreciate your time
and dedication to development. We are moving extremely quickly, and
everyone is very excited about our current developments!
Please contact me if you are available 6/8 - 6/12 for contract objective
review and development. I apologize that this will encompass a weekend,
but it is necessary for succeeding with our current development schedule.
Slots are filling for the Item Writing session planned for the week of
June 18. If you had hoped to participate in this event, please contact me
to discuss availability, expenses, etc. It is likely that a two team
approach (6/18 - 6/20, 6/20 - 6/22) will be used, allowing for flexible
travel arrangements.
--
Kara Pritchard Phone: 618-398-7360
Author, RHCE Exam Cram
Director of Exam Development http://www.lpi.org/
Site Manager http://www.LinuxUsersGroups.org/
--
Mail & News
[1.2.13
Obj : Configuring Mailing Lists
Install and maintain mailing lists using majordomo. Monitor
majordomo problems by viewing majordomo logs.
Includes files and tools such as:
* majordomo
*
[1.2.14, 1.5.3, 3.9.1, 3.9.3, 3.9.4, 3.9.5, 3.9.6, 3.9.7, 3.9.9, 3.9.10]
Obj : Using Sendmail
Manage sendmail configuration including email aliases, mail quotas,
and virtual mail domains. Configure internal mail relays and monitor
internal and external SMTP servers.
Includes files and tools such as:
* /etc/aliases
*
[1.3.12
Obj : Managing Mail Traffic
Implement client mail management software to filter, sort, and
monitor incoming user mail. Includes using software such as
procmail on either server or client side.
Includes files and tools such as:
* procmail
* .procmailrc
*
[3.8.2
Obj : Serving News
Install and configure news server using inn. Includes customizing
served newsgroups.
Includes files and tools such as:
* inn
*
1.2.13 lo Check the Majordomo Log file to see if users have problems
1.2.14 hi,L1 Add email-aliases to /etc/aliases
1.3.12 lo Configure procmail to be used system-wide
1.5.3 Set up user mail quotas
3.8.2 lo Configure inn to limit the news spool to particular sets of
newsgroups.
3.9.1 Add a user to a virtual mail domain so both delivery and outbound
address rewriting work.
3.9.3 Move a user from one virtual mail domain to another.
3.9.4 Setup sendmail for virutal domain hosting
3.9.5 L1 Rebuild db for virtusertable command
3.9.6 Set up mail relay for internal server not on the internet
3.9.7 Set up a mail server with virtusertables
3.9.9 lo Add support for RBL to the MTA config file
3.9.10 L1 Use telnet (on port 25) to check status of SMTP server
