Rebecca Ellis, Antje Faber, Roland Haidl, Carsten Höger, Johannes Meixner, Lars Müller, Edith Parzefall, Thomas Siedentopf, Robert Simai, Rebecca Walter.
SuSE Linux eMail Server III
SuSE GmbH Schanzäckerstr. 10 D-90443 Nürnberg Phone: +49-0911-7 40 53 31 (Vertrieb) Fax: +49-911-7 41 77 55 (Vertrieb) e-mail:
[email protected] WWW: http://www.suse.de
Rebecca Ellis, Antje Faber, Roland Haidl, Carsten Höger, Johannes Meixner, Lars Müller, Edith Parzefall, Thomas Siedentopf, Robert Simai, Rebecca Walter.
SuSE Linux eMail Server III
1st Edition 2001 SuSE GmbH
Copyright This product is the intellectual property of SuSE GmbH. It may be copied in its entirety or in excerpts only if each copy is marked with this copyright label. Layout: LATEX Geeko icons by Rolf Vogt
Linux is a trademark of Linus Torvalds. XFree86™ is a trademark of The XFree86 Project, Inc. MS-DOS, Windows, Windows 95, Windows 98, and Windows NT are trademarks of the Microsoft Corporation. UNIX is a trademark of X/Open Company Limited. Other (registered) trademarks included herein are: T-Online by Deutsche Telekom and SuSE and YaST by SuSE GmbH . All product names are used without guarantee of free usability and may not include trademarks. The corporation SuSE GmbH essentially conforms to the written format of the vendor. Other products named here can be trademarks of their respective vendors.
Contents
Contents
1
The SuSE Linux eMail Server
1
2
Support and Services
3
2.1
No Registration, No Product Support or Maintenance . . . . . .
3
2.2
Product Support for the SuSE Linux eMail Server III . . . . . .
3
2.3
Maintenance for SuSE Linux eMail Server III . . . . . . . . . .
4
2.4
Getting Help Fast . . . . . . . . . . . . . . . . . . . . . . . . .
5
2.5
Reaching the Support Team . . . . . . . . . . . . . . . . . . . .
6
3
Before Installing. . .
7
3.1
Selecting Host Name and Domain . . . . . . . . . . . . . . . .
7
3.2
Updating to eMail Server III . . . . . . . . . . . . . . . . . . .
7
3.2.1
Survey . . . . . . . . . . . . . . . . . . . . . . . . . .
8
3.2.2
Data Backup . . . . . . . . . . . . . . . . . . . . . . .
8
3.2.3
Reinstalling . . . . . . . . . . . . . . . . . . . . . . . .
9
3.2.4
Restoring data . . . . . . . . . . . . . . . . . . . . . .
9
Installation with DHCP . . . . . . . . . . . . . . . . . . . . . .
10
3.3 4
Scenarios and Check Lists
11
4.1
One Network Interface . . . . . . . . . . . . . . . . . . . . . .
11
4.1.1
Only Internet . . . . . . . . . . . . . . . . . . . . . . .
11
4.1.2
Only Intranet . . . . . . . . . . . . . . . . . . . . . . .
11
4.1.3
Intranet with Router to the Internet . . . . . . . . . . . .
12
4.1.4
In the DMZ . . . . . . . . . . . . . . . . . . . . . . . .
12
Two Network Interfaces . . . . . . . . . . . . . . . . . . . . . .
13
4.2.1
Static Internet and Intranet Connection . . . . . . . . .
13
4.2.2
Dial-Up Internet Connection and Static Connection to the Intranet . . . . . . . . . . . . . . . . . . . . . . . .
13
In the DMZ . . . . . . . . . . . . . . . . . . . . . . . .
14
4.2
4.2.3
i
Contents
5
Installation of SuSE Linux eMail Server with YaST2
5.1 5.2 5.3 5.4 5.5 5.6 5.7
5.8
5.9
5.10 5.11 5.12 5.13 5.14 5.15 5.16
5.17
5.18
ii
Starting Your System from CD-ROM . . . . 5.1.1 Boot Settings . . . . . . . . . . . . . The Opening Screen . . . . . . . . . . . . . 5.2.1 Other Installation Options . . . . . . YaST2 Takes Over . . . . . . . . . . . . . . Selecting a Language . . . . . . . . . . . . . Mouse Selection . . . . . . . . . . . . . . . . Keyboard and Time Zone . . . . . . . . . . . Preparing the Hard Disk . . . . . . . . . . . 5.7.1 Selecting the Partitioning Method . . 5.7.2 Standard Partitioning . . . . . . . . . 5.7.3 Manual Partitioning . . . . . . . . . 5.7.4 Resizing a Windows Partition . . . . Logical Volume Manager (LVM) . . . . . . . 5.8.1 Configuring LVM with YaST2 . . . . 5.8.2 LVM — Partitioner . . . . . . . . . . 5.8.3 LVM — Setting Up Physical Volumes 5.8.4 Logical Volumes . . . . . . . . . . . LILO — Introduction . . . . . . . . . . . . . 5.9.1 LILO — Background Information . . 5.9.2 LILO — Multiple Operating Systems 5.9.3 LILO — SuSE Linux Only . . . . . . 5.9.4 LILO — Multiple Hard Disks . . . . 5.9.5 LILO — When All Else Fails . . . . 5.9.6 LILO — Other Configuration . . . . 5.9.7 LILO — Problem Cases . . . . . . . Root Password . . . . . . . . . . . . . . . . Confirming Installation . . . . . . . . . . . . Partitioning and Formatting the Hard Disk . . Installation of Packages . . . . . . . . . . . . Monitor Settings . . . . . . . . . . . . . . . Final Installation Steps . . . . . . . . . . . . Network Configuration . . . . . . . . . . . . 5.16.1 Static Network Configuration . . . . 5.16.2 Dial-on-Demand Configuration . . . SuSE Linux eMail Server Basic Configuration 5.17.1 Part One . . . . . . . . . . . . . . . 5.17.2 Part Two . . . . . . . . . . . . . . . Graphical Login . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15 15 16 16 17 18 18 19 19 21 21 22 23 24 25 26 27 28 30 30 31 31 31 32 33 35 36 36 37 37 38 40 40 40 40 40 40 41 42
Contents
6
The Administration System
43
6.1 6.2 6.3 6.4
43 43 44 44 44 46 46 47 47 47 48 48 49 49 50 50 51 51 52 52 52 53 53 54 54 55 56 57 57 57 58 58 58 58 59 59 59
The Home Page in the Browser . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the Server as the Administrator (‘cyrus’) . . . . . User Administration . . . . . . . . . . . . . . . . . . . . . . . . 6.4.1 Creating a New User . . . . . . . . . . . . . . . . . . . 6.4.2 Modifying User Accounts . . . . . . . . . . . . . . . . 6.4.3 Changing the Password of ‘cyrus’ . . . . . . . . . . . 6.4.4 Modifying Administrator Information . . . . . . . . . . 6.5 Arranging Users in Groups . . . . . . . . . . . . . . . . . . . . 6.5.1 Creating a Group . . . . . . . . . . . . . . . . . . . . . 6.5.2 Editing Groups . . . . . . . . . . . . . . . . . . . . . . 6.6 Managing Shared Folders . . . . . . . . . . . . . . . . . . . . . 6.6.1 Creating a Folder . . . . . . . . . . . . . . . . . . . . . 6.6.2 Specifying Folder Rights . . . . . . . . . . . . . . . . . 6.6.3 Editing Folders and Rights . . . . . . . . . . . . . . . . 6.6.4 Direct Mail Delivery and Folder-Based Mailing Lists . . 6.7 Virtual Users and Domains . . . . . . . . . . . . . . . . . . . . 6.7.1 Creating and Editing Virtual Domains . . . . . . . . . . 6.7.2 Creating a Virtual User . . . . . . . . . . . . . . . . . . 6.7.3 Editing Virtual Users . . . . . . . . . . . . . . . . . . . 6.7.4 Adding Clients to the Name Server . . . . . . . . . . . 6.7.5 Removing Clients from the Name Server . . . . . . . . 6.8 Configuring the Components of the Mail System . . . . . . . . 6.8.1 Postfix: Basic Options . . . . . . . . . . . . . . . . . . 6.8.2 Postfix: Expert Options . . . . . . . . . . . . . . . . . . 6.8.3 Mail Retrieval: Fetch Mail . . . . . . . . . . . . . . . . 6.8.4 IMAP Configuration: Access by Clients . . . . . . . . . 6.8.5 Mail Queue: Monitoring the Mail Transport . . . . . . . 6.9 System: Additional Options . . . . . . . . . . . . . . . . . . . 6.9.1 Create or Remove a CA . . . . . . . . . . . . . . . . . 6.9.2 Apache Configuration: Secure Access with SSL . . . . 6.9.3 LDAP Browser: Editing the LDAP Database . . . . . . 6.9.4 E-mail Newsletters: Sending a Message to All Users . . 6.10 Resources: Managing Calender Resources . . . . . . . . . . . . 6.10.1 Resources: Creating and Deleting Resources . . . . . . 6.10.2 Creating Resource Groups . . . . . . . . . . . . . . . . 6.10.3 Resource Groups: Editing and Deleting Resource Groups
iii
Contents
7
Setting User Options
7.1
7.2
7.3
8
Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1.1 Personal Data: Entering and Modifying Personal Data 7.1.2 Changing the Password . . . . . . . . . . . . . . . . . 7.1.3 Certificate: Downloading a Certificate . . . . . . . . . Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.1 New: Creating a New Folder . . . . . . . . . . . . . . 7.2.2 Edit: Folder Properties and Access Rights . . . . . . . SIEVE: Mail Filtering . . . . . . . . . . . . . . . . . . . . . . 7.3.1 Mail Filters . . . . . . . . . . . . . . . . . . . . . . . 7.3.2 Vacation Notice: Sending Automatic Replies . . . . . 7.3.3 SIEVE Editor: Creating Custom Scripts . . . . . . . .
. . . . . . . . . . .
SKYRiXgreen — An Appointment, E-mail, and Task Manager
8.1
8.2 8.3
8.4
8.5
iv
61
Introduction . . . . . . . . . . 8.1.1 What is SKYRiXgreen? 8.1.2 Features . . . . . . . . 8.1.3 Program Differences . 8.1.4 System Requirements Access . . . . . . . . . . . . . Mail . . . . . . . . . . . . . . 8.3.1 Folder Management . 8.3.2 Writing a Message . . 8.3.3 Reading Messages . . 8.3.4 Replying to a Message 8.3.5 Forwarding a Message 8.3.6 Bouncing Messages . 8.3.7 Deleting messages . . 8.3.8 Using address books . 8.3.9 Attachments . . . . . Address Books . . . . . . . . 8.4.1 Overview . . . . . . . 8.4.2 Selecting an Address . 8.4.3 Adding an Address . . 8.4.4 Editing an Address . . 8.4.5 Deleting an Address . 8.4.6 Moving Addresses . . Appointments . . . . . . . . . 8.5.1 Overview . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
61 61 61 61 62 62 63 64 64 66 67 69
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
69 69 69 70 70 70 71 72 73 73 74 74 74 74 75 75 75 75 76 76 76 77 77 77 77
Contents
8.6
8.7
9
8.5.2 Personal Appointments . . . . 8.5.3 Palm Appointments . . . . . . 8.5.4 Resource Appointments . . . 8.5.5 Creating a New Appointment 8.5.6 Modifying an Appointment . 8.5.7 Deleting an Appointment . . . 8.5.8 Proposing an Appointment . . 8.5.9 Print Preview . . . . . . . . . Tasks . . . . . . . . . . . . . . . . . 8.6.1 Tasks . . . . . . . . . . . . . 8.6.2 Creating a Task . . . . . . . . 8.6.3 Modifying a Task . . . . . . . 8.6.4 Marking a Task as Done . . . Options . . . . . . . . . . . . . . . . 8.7.1 Preferences . . . . . . . . . . 8.7.2 Signature . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
Preparing to Set Up an E-Mail Client . . . . . . . . . . . Configuration with Netscape Communicator Version 4.7x 9.2.1 Configuring the IMAP Mail Client . . . . . . . . 9.2.2 Configuring the LDAP Address Book . . . . . . Netscape Communicator Version 6.x and Mozilla 0.9x . 9.3.1 Configuring the IMAP Mail Client . . . . . . . . 9.3.2 Configuring the LDAP Address Book . . . . . . Setting up KMail as of Version 1.3 . . . . . . . . . . . . Configuration with Pine Version 4.33 . . . . . . . . . . . 9.5.1 Configuring the IMAP Mail Client . . . . . . . . 9.5.2 Configuring the LDAP Address Book . . . . . . Outlook Express Version 5.x and 6.0 and Outlook 2000 . 9.6.1 Configuring the IMAP Mail Client . . . . . . . . 9.6.2 Configuring the LDAP Address Book . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. 87 . 88 . 88 . 89 . 89 . 90 . 91 . 95 . 97 . 97 . 99 . 101 . 101 . 102
Configuring External Mail Applications
9.1 9.2
9.3
9.4 9.5
9.6
87
10 Arkeia Backup of the SuSE Linux eMail Server
10.1 Arkeia by Knox Software . . . . . . . . . 10.1.1 Licensing Conditions . . . . . . . 10.1.2 Expanding Your Use of Arkeia . . 10.2 Backing Up the SuSE Linux eMail Server 10.3 Installation . . . . . . . . . . . . . . . .
78 78 79 80 81 81 81 81 82 82 82 82 83 83 83 85
. . . . .
105
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
105 105 105 105 106
v
Contents
10.3.1 Preparation . . . . . . . . . . . . . 10.3.2 Explanation of Concepts . . . . . . 10.3.3 Backup Server Installation . . . . . 10.3.4 Configuration . . . . . . . . . . . . 10.3.5 Short Description . . . . . . . . . . 10.4 Recovery . . . . . . . . . . . . . . . . . . 10.4.1 General Procedure During Recovery 10.4.2 Complete Recovery . . . . . . . . . 10.4.3 Partial Recovery . . . . . . . . . .
vi
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
106 106 107 107 117 120 120 120 121
11 Glossary
125
12 YaST and SuSE Linux License Terms
131
Bibliography
135
1
The SuSE Linux eMail Server
1 The SuSE Linux eMail Server The SuSE Linux eMail Server is an Open Source e-mail solution based on welltested, reliable components that meet Internet standards, such as SMTP, IMAP4, POP3, and LDAP. The number of available e-mail users per server is limitless and is only restricted by the server hardware. The SuSE Linux eMail Server centrally manages all mails according to the IMAP standard on one server. Users have — regardless of their physical location or the e-mail client used — access to their messages and folders over both the Internet and the company’s LAN. Some of the new or updated features of SuSE Linux eMail Server III include: • Virtual Mail Domains • Simple DNS Management • POP3 Multidrop-Capability • Mailing Lists • New web-based mail client SKYRiXgreen • SKYRiX Date Calender and Resource Management • Integrate Browser for LDAP Directory Service • Optimized and Accelerated Administration Front-end This manual will discuss the updates from the previous versions to the new SuSE Linux eMail Server III and how to install it from scratch using the YaST2 tool. Other chapters provide details of server administration over the administration web interface, implementation of the integrated web mail client SKYRiXgreen, and the configuration of external e-mail clients. Information on the SuSE Linux Enterprise Server can be found in the accompanying guide. Our special thanks go to: Technical Project Manager Remo Behn, Product Manager Lars Müller, and developers Thomas Bartels, Carsten Höger, and Ralf Haferkamp; Helge Hess and Jan Rissman of SKYRiX Software AG; and the assistents and beta testers Johannes Meixner, Jochen Röder, Thomas Siedentopf, and Robert Simai.
1
1
2
The SuSE Linux eMail Server
2
Support and Services
2 Support and Services 2.1
No Registration, No Product Support or Maintenance
To guarantee the best product support, only requests from registered users will be processed. On the back of the CD cover, find two stickers, each labeled with product registration code. This code is unique and serves to verify the authenticity of your SuSE product. Affix one of the registration code labels to the designated field on the registration card. We recommend that you leave the second label on the product, so that the registration code is close at hand if you require consulting. After sending the completed registration form by mail or registering using the online form at http://support.suse.de/en/register/, you will become a registered user and can access our product support, maintenance, and more.
2.2
Product Support for the SuSE Linux eMail Server III
Product support already included in the purchase price of the SuSE Linux eMail Server III spans over a time period of 30 days after the registration date and includes the services listed below. This support is not intended as training material or as an introduction to SuSE Linux itself. It is intended as a guide for the basic installation of the system. Support can be requested only in respect to configuration problems, not pertaining to conceptual questions.
Product Support Coverage Product support covers the basic installation of the SuSE Linux eMail Server III on a machine, and the configuration of the basic hardware and the following peripherals using the configuration tool YaST2: • Network Card (Ethernet) • DSL (Ethernet) • ISDN Card • Modem
3
2
Support and Services
Product support also provides services to help with the following aspects of configuration: • Basic configuration of external mail programs – – – – –
pine Kmail IMAP as of Version 1.3 (with KDE 2.2) Mozilla as of Version 0.9x Netscape Messanger as of Versionen 4.7x and 6.x Outlook 2000, Outlook Express as of Version 5.x
• Configuring external and internal distributors and mailing lists • Basic configuration of name service (DNS) of another zone on the mail server • Basic configuration of protection against undesired web advertisements or spam • Support for setting up a virus scanner based on H+B Antivir data • Support for setting up a simple attachment and content filter based on file endings • Support for restricting the size of a mail and the internal and external user circle • Support for name and IP address changes • Support for using the mail server as LDAP authentication server • Support for choosing a backup strategy • Performance consulting and hardware outfitting • Configuration of time server usage
2.3
Maintenance for SuSE Linux eMail Server III
The maintenance of the SuSE Linux eMail Server III is an active maintenance contract, preventative support, customized according to your specific IT requirements. You will receive the following services, which is up-to-date and guarantees utmost user-friendliness: • Fixes and patches for resolving critical errors (security, data loss) of the SuSE Linux eMail Server III. • Each patch includes extensive documentation. • You will be actively contacted by mail from the SuSE Enterprise Support Services. • The patches themselves are made available on a secured web server for download.
4
2.4
Getting Help Fast
• You will obtain support from SuSE Enterprise Support Services for installing the patches. Maintenance can also be optimized with our Update Service. In addition, you will receive all patches and fixes for your SuSE Linux product quarterly, shipped on CD. Your registration automatically entitles you to SuSE Linux eMail Server III Maintenance for a period of 12 months. Thus, you will be guaranteed a stable and tested system.
2.4
Getting Help Fast
Register your product online at our web site (http://support.suse.de/ en/) and send your request by e-mail to
[email protected]. Please give your customer information in the e-mail text before describing the problem. Note the use of uppercase and lowercase in your customer information. This way, your e-mail can be automatically processed (see File 2.4.1). Do not use any unnecessary attachments and, if you need to insert configuration files, enter them directly in ASCII format in the request letter. Example: FIRSTNAME: John LASTNAME: Doe COMPANY: Doe & Co. Inc. STREET: Easy Street 7 CITY: Nowhereville ZIP: 12345 COUNTRY: USA REGCODE: EMAIL:
[email protected] My Problem: problem description ... My Hardware: hardware description ...
File 2.4.1: Support Request by E-Mail
5
2
Support and Services
2.5
Reaching the Support Team
You can reach the Support Team via the following contact information and during these hours of operation: • E-mail:
[email protected] Processing: weekdays • WWW (e-mail): http://support.suse.de/en Processing: weekdays • Phone (calls answered by Enterprise Support Services): Phone: +49 (0) 421 526 23 40 Open: Monday through Friday 9:00 a.m. – 6:00 p.m. (except for legal holidays) • Fax: +49 (0) 911 740 53 477 Processing: weekdays • Mail: SuSE GmbH Support Schanzäckerstr. 10 D-90443 Nürnberg More information on our extended support services can be obtained at: www. support.suse.de/en
6
3
Before Installing. . .
3 Before Installing. . . With SuSE Linux eMail Server III, you have a high-performance product based on the SuSE Linux Enterprise Server. It will spare you hour-long, complicated configuration sessions as well as allow quick setup of a powerful e-mail server designed to meet most of your needs. Nevertheless, it involves a little bit more than just sticking the CD into the drive and installing right away. Although the installation does not take much time, the individual steps can be quite complicated. There are many components which need to be considered and coordinated with one another.
3.1
Selecting Host Name and Domain
Give some thought to the name of your SuSE Linux eMail Server. Changing the host name or even the domain name after installation is quite troublesome. Therefore, first consider a sensible name for the SuSE Linux eMail Server before beginning with installation. In addition, SuSE Linux eMail Server can be implemented as name server for your intranet, provided you have not set up one already. A properly set-up name service (DNS) is absolutely essential for the smooth functioning of a mail server. Even if you do not technically have Internet connectivity — you are not directly reachable from the Internet — you should still assign a reasonable domain name to your intranet. Names such as “company.local” are not very suitable for this purpose, because e-mail sent to the Internet with
[email protected] will never come back. What about company.com? The advantage here, too, is that this does away with any other obstacles that might otherwise hinder your future publication in the Internet. Make sure the name you are using has not already been assigned. Find out if your desired domain already exists by simply entering the respective domain as a URL (possibly with the prefix www.) using any web browser. Obtain more thorough information in one of the related databases, such as http://www.internic.com/whois.html.
3.2
Updating to eMail Server III
You cannot use the fully automatic update mechanism of SuSE Linux to update your SuSE Linux eMail Server Version II to the new SuSE Linux eMail Server. The only way to transfer the existing data and configuration from the SuSE Linux eMail Server II to the SuSE Linux eMail Server III is to follow the instructions in this section.
7
3
Before Installing. . .
SuSE cannot accept any responsibility for data loss during a system update. Make sure you possess a backup of all your data before starting the installation of the SuSE Linux eMail Server.
3.2.1
Survey
The update to SuSE Linux eMail Server III is carried out in three steps: 1. save data 2. install new 3. restore data When restoring the data, it must be changed, so needs to be converted by the script restore.sh to be usable for SuSE Linux eMail Server III. After the installation of SuSE Linux eMail Server III, the data is stored into a temporary directory, from which it is converted and restored to the respective directories.
Caution For an update to SuSE Linux eMail Server III, you need to have enough disk space available after the installation to store the data to the temporary directory. This means that, for an update to SuSE Linux eMail Server III, you might need a larger hard disk.
The most storage-intensive items are e-mail on the IMAP server. Find out exactly how much space they need by typing the following command: du -skc /var/imap /var/spool/imap
This should produce output like the following: 405 181178 181583
/var/imap /var/spool/imap total
All amounts are in kilobytes. In the above example, the mails occupy about 181178 KB. This is approximately 177 MB. As the temporary directory by default /tmp is used.
3.2.2
Data Backup
Before starting the installation of SuSE Linux eMail Server III, log in to the old eMail Server as ‘root’. Insert CD 1 of the new eMail Server and mount the CD in the file system with the command mount /cdrom. Copy the backup program with cp /cdrom/backup.sh /tmp into a temporary directory and make it executable with chmod u+rx /tmp/backup.sh if necessary.
8
3.2
Updating to eMail Server III
To deposit your data in a temporary directory, save this change and run the script with the following command: bash ./backup.sh backup.tar.gz
If you would rather have them on a streamer (e.g., SCSI) use this command: bash ./backup.sh /dev/st0
The vacation notes are not restored. After saving your data to an external medium, install the new SuSE Linux eMail Server, overwriting the old version. Perform a boot from the first CD and follow the instructions in YaST2.
3.2.3 Reinstalling During the installation, keep the following three requirements in mind: • During the installation, reformat the old eMail Server partitions. Otherwise, the system might not work properly afterwards. Warning: Do not format your backup! • Use exactly the same name as the old eMail Server with exactly the same domain. For example, if your old eMail Server was called mail.company. com, use exactly this same name for your new server. • The LDAP BaseDN must have exactly the same name as the previous SuSE Linux eMail Server. Otherwise it will not be possible to adequately integrate the old data.
3.2.4
Restoring data
After the new server has been successfully installed, run the script /usr/share/ doc/packages/imapweb/tools/restore.sh without any arguments by entering restore.sh. This should produce the following output: /usr/share/doc/packages/imapweb/tools/restore.sh -x file.tgz -x extract or /usr/share/doc/packages/imapweb/tools/restore.sh [-i] [-p] [-l] [-f] [-c] [-a] -i restore only imap folder -p restore only procmail rules -l restore only ldap directory -f restore only fetch accounts -c restore only CA and certs -a restore all
First copy the backup containing the old data with the option -x into the directory /tmp/imapbak. If the backup is on a directly accessible streamer tape, use the following command:
9
3
Before Installing. . .
/usr/share/doc/packages/imapweb/tools/restore.sh -x /dev/st0
If the backup is in /tmp, use the following command: /usr/share/doc/packages/imapweb/tools/restore.sh -x /tmp/backup.tar.gz
There are several ways to restore and convert your old data, depending on your requirements. The options are: -i: Only the e-mails and the user structures contained in “cyrus-imapd” are re-
stored. This includes the directories and subdirectories of each user and the qouta information. -p: Only the “procmail” rules are restored and converted. -l: Converts only the LDAP directory. Inserting the wrong password is not a problem, because you always have the possibility to use -l to start the
restoration again. -f: Restores the data of the “Fetch Mail” interfaces -c: Restores CA and server certificates -a: Performs all the above steps in sequence.
In case some data cannot be restored correctly, you still have the backup archive from which to transfer the data manually.
3.3
Installation with DHCP
With DHCP, you can also assign SuSE Linux eMail Server its name and IP address during installation. This will only work, however, if you use DHCP to assign, along with the IP address, the complete host name, including domain name.
Note The name of your SuSE Linux eMail Server cannot be changed later. It will not work if the DHCP server is not reachable when booting or if another host or domain name is assigned.
If the clients are also configured via DHCP, the DHCP server or a configured name server must perform the name resolution for your local network and must be recognized by the SuSE Linux eMail Server as the name server.
10
4
Scenarios and Check Lists
4 Scenarios and Check Lists This list of possible network constellations outlines the most important configuration elements to keep in mind. Before installing, give some thought to which scenario correlates best with your preferred network topology. A network interface can be represented by an ethernet connection (network card) or by a PPP connection (modem, ISDN). The suggestions listed here serve as a help guide. Configurations that vary from the examples presented here are also possible.
4.1
One Network Interface
The following describes various options for running the SuSE Linux eMail Server with only one network interface.
4.1.1
Only Internet
The SuSE Linux eMail Server is connected to a leased line to the Internet and has been assigned a public IP address. See Figure 4.1. The address of the default gateways can be obtained from your provider. Usually, SuSE Linux eMail Server has its own name service. Otherwise, do not start the eMail Server’s DNS and only specify a reachable DNS (provider). An “mxrecord” for the eMail Server must exist on a publicly accessible name server. Specifying a relay host is usually not necessary, but ask your provider if unsure.
Internet
eMail Server
Figure 4.1: SuSE Linux eMail Server Connected to the Internet
4.1.2
Only Intranet
The SuSE Linux eMail Server is only accessible over the local network and has been assigned a non-public IP address. E-mail is not transferred to any other network (e. g., Internet). See Figure 4.2 on the following page. As no connection can be established to the outside, there is no gateway. If an additional network segment be accessible, the default gateway is the corresponding router. For your local network, use SuSE Linux eMail Server as DNS or specify
11
4
Scenarios and Check Lists
an existing and properly configured name server. Specifying a relay host is not necessary.
eMail Server
local net
other local net
router optional
Figure 4.2: SuSE Linux eMail Server Only in the Local Network
4.1.3
Intranet with Router to the Internet
The SuSE Linux eMail Server is only available over the local network and has been assigned a non-public IP address. A connection to the Internet can be set up by way of a router accessible over the local network. See Figure 4.3. The default gateway is, in this example, the address of the router. The DNS of the SuSE Linux eMail Server or another DNS on the local network can be used as name server, as already described in Section 4.1.1 on the preceding page. In addition, it makes sense to enter a second DNS as “forwarder” in /etc/named. conf. This can be a second DNS in the local network, which is able to resolve external addresses, or the name server of the provider. Usually, the relay host given by the provider must be specified in order to send e-mail into the Internet. The router must also be configured accordingly. Internet
Router
local net
eMail Server
Figure 4.3: SuSE Linux eMail Server Connected to the Internet via a Router
4.1.4
In the DMZ
The SuSE Linux eMail Server is in a DMZ (DeMilitarized Zone) and protected by a firewall. See Figure 4.4 on the next page. The SuSE Linux eMail Server can run in a DMZ with SuSE Firewall on CD, for instance. The SuSE Linux eMail Server will then receive a private IP address. In this case, the firewall must be configured (forwarding) to enable data to be transferred to and from the SuSE Linux eMail Server. The default gateway could be the firewall server. SuSE Linux Firewall on CD features an SMTP proxy server for this purpose as well.
12
4.2
Internet
Two Network Interfaces
Firewall
local net
DMZ
eMail Server Figure 4.4: SuSE Linux eMail Server in a DMZ
4.2
Two Network Interfaces
If the SuSE Linux eMail Server has two network interfaces, one of the following configurations can be made for your network.
4.2.1
Static Internet and Intranet Connection
The SuSE Linux eMail Server is accessible from the Internet as well as from the local network. See Figure 4.5. The default gateway is usually given by the provider. Here, too, it is advisable to specify the DNS running on the SuSE Linux eMail Server as the name server then enter the DNS of the provider (if available) in /etc/named.conf as “forwarder.” It may be necessary to specify a relay host (ask your provider).
Internet
eMail Server
local net
Figure 4.5: SuSE Linux eMail Server Connected to Local Network and Internet
4.2.2
Dial-Up Internet Connection and Static Connection to the Intranet
You have a network interface for your local network and also an ISDN card for your Internet connection. An IP number is dynamically assigned each time you dial into the Internet. See Figure 4.6 on the next page. In this case, the default gateway is the IP address, specified as “Point to Point Partner” in the ISDN card configuration. When the connection is set up, the provider substitutes this address with a public IP address. Again, define the local address as name server. Also, specify at least one DNS of your provider or enter this as a forwarder in /etc/named.conf. The DNS of the provider can also be automatically forwarded as the connection is set up, eliminating the need to specify another name server. Specifying a relay host (provider) is usually not necessary.
13
4
Scenarios and Check Lists
Internet
ISDN
eMail Server
local net
Figure 4.6: SuSE Linux eMail Server with ISDN Connection to the Internet
4.2.3
In the DMZ
The SuSE Linux eMail Server is connected over an internal and external firewall at each network interface. The external firewall can be specified as default gateway and configured as such (forwarding), allowing the local network to be accessed as well. See Figure 4.7. Internet DMZ int. Firewall
ext. Firewall
local net
eMail Server
Figure 4.7: Connected to Internal and External Firewalls
14
5
Installation of SuSE Linux eMail Server with YaST2
5 Installation of SuSE Linux eMail Server with YaST2 On the following pages, find instructions for installing SuSE Linux and SuSE Linux eMail Server with YaST2.
5.1
Starting Your System from CD-ROM
Insert the SuSE Linux eMail Server III CD in your CD-ROM drive then turn on your computer. SuSE Linux will be started for installation.
5.1.1
Boot Settings
If your machine does not boot from the CD-ROM, change the settings in the computer’s BIOS, depending on the kind of CD-ROM drive in the machine.
EIDE (ATAPI) CD-ROM Drive
At initial start-up, a diagnosis of the computer’s hardware is conducted and, among other things, the random access memory is tested. You can recognize this by the system memory count. At the bottom of the screen, you will be told which key calls up the BIOS setup — usually Del or F1 . Press the key specified and the BIOS setup will appear. If your machine is equipped with an AWARD BIOS, the necessary entry will be labeled BIOS FEATURES SETUP. Other manufacturers use similar entries, such as ADVANCED CMOS SETUP. Select the corresponding entry and con firm with ←- . Relevant for your purposes is the subitem normally listed as “Boot Sequence” (of the drives). The default setting for this is usually C, A or A, C. In the first example, when booting, the machine will search the operating system on the C drive then on the A drive. Select ‘Boot Sequence’ then press Page ↑ and Page ↓ until you get a setting with the CD-ROM before the hard disk, the A, CD-ROM, C sequence, for example. Next, exit these settingsby pressing . To save the changes, select ‘SAVE & Esc EXIT SETUP’ or press F10 , after which you will be asked if you want to exit the BIOS setup and save the changed settings.
15
5
Installation of SuSE Linux eMail Server with YaST2
SCSI CD-ROM Drive
During start-up, the computer’s hardware will be initialized and, among other things, the random access memory will be tested and the system memory count will be displayed on the screen. At the bottomof thescreen, you will be told which key calls up the BIOS setup — usually, Del or F1 . Press the key specified and the BIOS setup will appear. . In the case of an Adaptec host adapter, it is a key combination of Ctrl + A Select ‘Disk Utilities’. The system will check the hardware installed and display the corresponding information. Make note of the SCSI ID for your CD-ROM. Next, exit the menu with Esc to open ‘Configure Adapter Settings’. Find ‘Boot Device Options’ under ‘Additional Options’. Se lect this menu and press ←- . Now enter the CD-ROM drive . ID and press ←- Return to the start screen in the SCSI BIOS by pressing Esc twice, which can be exited by confirming with ‘Yes’ to reboot the machine. If the machine does not boot from the CD-ROM, it will have to be started with the boot floppy. The start screen will appear and the installation will begin.
5.2
The Opening Screen
A screen as in Figure 5.1 on the next page shows that the system is ready to boot for the installation. Select ‘Installation ’ here (the default selection). Either wait a few seconds or just press ←- to load the kernel. A few seconds later, a minimal Linux system loads and takes over the rest of the installation procedure. A number of messages and copyright notices will then appear on the screen. At the end of the loading process, the YaST2 program will start. A few seconds later, the graphical interface of YaST2, the SuSE Linux installation program, will be displayed.
5.2.1
Other Installation Options
If you press any key before the wait time is up, automatic start-up will be disabled and other options can be selected. These are especially useful if problems occur with the graphical display. As the actual launching of the installation to the hard disk is initially preceded by some dialogs and specific queries, cancel if there are problems then choose different options following a reboot.
A Different Graphics Mode for YaST2
Choose the standard VGA (640x480) graphics mode compatible to any graphics card using the function keys. In the worst case scenario, select pure text mode. In the text-mode YaST2 screen, one menu item to the next using Tab skip from and, inside a menu, using ↑ and ↓ . ←- continues to the next screen.
16
5.3
YaST2 Takes Over
Kernel Parameters
Under ‘boot options:’, enter only the specialized kernel parameters required by certain types of hardware next to the name of the system to boot. Options Other than YaST2
Select the following options with ↑ and ↓ . ‘Manual Installation’ starts the text installation program YaST. This is, however, only necessary if the computer has less than 64 MB. A rescue system is available under ‘Rescue System’, the last resort for an already installed system in cases of severe damage to the system. ‘Memory Test’ starts an extensive and time-consuming memory test capable of detecting memory significantly errors faster than the BIOS memory test run during boot. Press ←- to confirm your selection.
Figure 5.1: The Initial Boot Screen
5.3
YaST2 Takes Over
Now the actual installation of SuSE Linux starts with the YaST2 installation program. Figure 5.2 on the following page shows what the screen will look like. During this phase, the hardware available on your system is checked and prepared for the installation. A bar in the middle shows the progress of the installation. All YaST2 screens have a common format. On the left, help texts are shown, providing information on the current topic. All entry fields, lists, and buttons on the YaST2 screens can be accessed with the mouse. If your cursor does not move, your mouse has not been automatically recognized by Linux. You will then need to use your keyboard, as explained in Section 5.2.1 on the preceding page.
17
5
Installation of SuSE Linux eMail Server with YaST2
Figure 5.2: The Hardware Analysis
5.4
Selecting a Language
SuSE Linux and YaST2 are adapted to use the language selected. English is the default setting for the International distribution of SuSE Linux. These settings can be changed individually.
Figure 5.3: Selecting the Language If your mouse cursor still does repeatedly until the ‘Next’ notwork, press Tab button is selected, then press ←- .
5.5
Mouse Selection
If YaST2 did not recognize your mouse type automatically, an entry screen will appear as shown in Figure 5.4 on the facing page.
18
5.6
Keyboard and Time Zone
Figure 5.4: Selecting the Mouse Type To select your mouse type, use ↑ and ↓ . The mouse documentation should provide a description of the mouse type. Select the mouse type from the list. The first three items in the list are the most common mouse types. Try these first if you donotknow either by the type ofyour mouse. Confirm your selection pressing Alt + T or pressing Tab then confirming with ←- . Test if the mouse pointer on the screen follows your movements. If the cursor does not move, select a different mouse type and try again.
5.6
Keyboard and Time Zone
In the next step (Figure 5.5 on the next page), the keyboard layout and time zone are selected. In the field ‘Hardware clock set to’, choose between local time and GMT. Your selection depends on the clock settings in the BIOS of your computer. If this is set to GMT, SuSE Linux will automatically apply the time change between Daylight Savings and Standard Time. Now select the desired keyboard layout. Usually, this corresponds to the language chosen. Select the correct time zone in the other column. Test your keyboard with special characters such as ‘|’ and ‘@’ to see if they appear correctly. If it does not work, you chose the wrong layout. Continue the installation with ‘Next’.
5.7
Preparing the Hard Disk
To prepare the hard disk, divide the entire disk space into separate partitions then set up appropriate file systems. The minimum requirements are the following three partitions:
19
5
Installation of SuSE Linux eMail Server with YaST2
Figure 5.5: Selecting the Keyboard Layout and Time Zone
• A boot partition, approximately 20 MB in size, where the files required by SuSE Linux for booting are stored. Since these files can only be accessed by BIOS functions during startup and BIOS only allows for limited hard disk access, this partition should be located on the first hard disk and at the beginning of the disk space whenever possible, ensuring that the BIOS can access all files needed for booting. • A swap partition at least twice as large as your memory, required for swapping data from main memory. • The remaining disk space makes up the root partition where all other data is stored. This partition should be at least 900 MB in size for SuSE Linux eMail Server, as approximately 500 MB of software will be installed and enough space must be left for temporary and log files, mail user data, and e-mails. At least 20 MB of space should be allowed for each mail user. In most cases, the SuSE Linux eMail Server is the only system on the machine and is only installed on a single hard disk. If this is so, it is easiest to select the hard disk then ‘Entire hard disk’. At this point, YaST2 will perform the partitioning, using the appropriate partition sizes for the given hard disk space. During this process, any data still remaining on the hard disk will be deleted to free up the entire hard disk for the SuSE Linux eMail Server. If SuSE Linux eMail Server is the only system on the machine, but there are two hard disks, partition manually. For normal operation, SuSE Linux eMail Server is the only operating system installed on the computer. It is not recommended to use this server machine as anything else. If the installation is for test purposes, however, it can be installed along with Windows or another operating system. It is best to install this test server on its own hard disk. If that is not possible, consider using the Windows Resizer to make enough space available for SuSE Linux eMail Server.
20
5.7
5.7.1
Preparing the Hard Disk
Selecting the Partitioning Method
In the new installation, only one dialog will be shown for the hard disk (Figure 5.6). All the hard disks detected on your computer will be shown. Choose the disk on which to install the SuSE Linux eMail Server. There is no risk in selecting the hard disk. No existing data will be deleted and no changes will be made to your system at this point. To partition manually, select ‘Custom partitioning -- for experts’. To use LVM, choose ‘User defined partitioning with LVM’. Find more information on this in Section 5.8 on page 24.
Figure 5.6: Selecting the Hard Disk
5.7.2
Standard Partitioning
It is recommended to use the entire hard disk for the server installation. If, however, you are installing a test machine and want to keep an existing installation of Microsoft Windows, see Section 5.7.4 on page 23 for information on resizing the existing Windows partition. YaST2 will now show all partitions present on the chosen hard disk (Figure 5.7 on the next page). The free storage space is shown and automatically selected. To assign more disk space to SuSE Linux eMail Server, select more partitions in order from the last to the first in the list. It is not possible, however, if you have three partitions, for example, to choose the second one for the SuSE Linux eMail Server and the first and third for other operating systems to use. If you click ‘Entire hard disk’, the entire hard disk and all the partitions will be made available for the SuSE Linux eMail Server. This is the recommended installation for SuSE Linux eMail Server.
Caution If you choose ‘Use entire hard disk’, you will lose all the information on your hard disk.
21
5
Installation of SuSE Linux eMail Server with YaST2
During the course of the installation process, YaST2 will verify whether there is sufficient storage for the installation and whether the three standard partitions can be created. If this is not the case, you will be prompted to alter your selection. If there is enough storage space, YaST2 will apply your settings so that the entire hard disk or selected partitions can be distributed over the three default partitions: boot, swap, and root.
Figure 5.7: Selecting the Partitions
5.7.3
Manual Partitioning
If the SuSE Linux eMail Server is the only system on the machine, but there are two hard disks, proceed with the following partitioning: On the first hard disk, create these partitions: • First, a boot partition approximately 20 MB in size formatted with the ext2 file system. Use /boot as the mount point. • A swap partition about twice as large as your memory, formatted for swapping. Use swap as the mount point. • The remaining disk space comprises the root partition, normally formatted with the ext2 file system. / must be specified as the mount point. / symbolizes the root directory of the entire file system. Alternatively, format this partition using reiserfs. For the SuSE Linux eMail Server, we recommend ext2. This partition should be at least 700 MB in size, because approximately 500 MB of software will be installed and enough space is needed for temporary files. Create the following partition on the second hard disk: • Use the entire disk space as the var partition, normally formatted with the ext2 file system. Use /var as the mount point. Alternatively, format this partition with reiserfs. The mail user’s data and e-mails are saved to the
22
5.7
Preparing the Hard Disk
/var directory, in this case, on the second hard disk. Allocate at least 20 MB
space for each mail user. If, after a while, the second hard disk no longer has enough room for the mail users, this hard disk can subsequently be replaced by a larger one without too much trouble.
5.7.4
Resizing a Windows Partition
SuSE Linux eMail Server can coexist with other operating systems on your ma-
chine, but it is not recommended for an actual server machine. If Microsoft Windows is already installed on your machine and the hard disk selected for SuSE Linux eMail Server only has one partition with Windows (which is normally the case for preinstalled machines), shrink the part of your hard disk reserved for Windows without having to remove the operating system.
Caution The Windows Resizer only works if the computer has one hard disk with exactly one Windows partition.
Figure 5.8: Available Options for Windows Partitions
Note Make sure you have a functioning Windows boot disk available, so you can boot Windows again if problems occur.
Before shrinking the Windows partition, boot Windows first. Run both scandisk and defrag. They will scan the files used in Windows and move them to the beginning of the hard disk before the Windows Resizer scans the hard disk.
23
5
Installation of SuSE Linux eMail Server with YaST2
YaST2 shows, in the first bar graph, how much memory Windows is currently
occupying and how much hard disk memory is still available. The second bar graph suggests how the new hard disk should be repartitioned (Figure 5.9). You can accept this suggestion or customize the partition borders using the slidecontrol.
Figure 5.9: Adjusting the Windows Partition If Windows files with a fixed position exist (like the swap file), problems can occur if these files are in the range to use for the SuSE Linux eMail Server. In this case, boot Windows and try to remove the fixed position marks.
Caution There is no guarantee that either modifying an already running Windows partition will be successful or that Windows and all of its previously running applications will operate smoothly afterwards, because making subsequent changes to already running partitions is always a critical procedure. Always back up your data first. Also, DOS-based applications could still be operating within the limits their original partitions and could thus ruin the newly created SuSE Linux partition by overwriting the middle of it.
The cleanest but most complex solution is to completely erase the Windows partition from the hard disk, including all its data then reinstall Windows in a reduced Windows partition. In doing so, reserve the remaining disk space — do not create any partitions there. YaST2 will be able to automatically recognize the available disk space when installing the SuSE Linux eMail Server.
5.8
Logical Volume Manager (LVM)
The Logical Volume Manager (LVM) enables flexible distribution of your hard disk space over several file systems. Since partitions can only be changed on a
24
5.8
Logical Volume Manager (LVM)
running system with difficulty, LVM was developed. It makes a virtual “pool” (volume group, VG for short) of memory space available that can generate logical volumes (LV) as needed. The operating system will then access the LVs instead of the physical partitions. Characteristics: • Several hard disks or partitions can be merged into one large logical partition. • If an LV (such as /usr) is filled up, enlarge it if configured properly. • Even add to LVs on a running system using LVM, if using “hot-swappable” hardware is suitable for such procedures. Using LVM is already quite beneficial for home PCs or small servers placed under high demand. If you have a growing data stock such as databases, MP3 archives, user directories, or mail directories on the SuSE Linux eMail Server, the Logical Volume Manager might be right for you. With this, you could have file systems, for instance, larger than a physical hard disk. Another advantage of the LVM is that you can create up to 256 LVs. Remember, however, that working with the LVM is quite different than working with conventional partitions. Further information on configuring the “Logical Volume Manager” (LVM) can be found in the official LVM Howto available at http://www.sistina.com/ lvm/Pages/howto.html.
5.8.1 Configuring LVM with YaST2 Activate the YaST2 LVM configuration by selecting ‘Custom partitioning with LVM’ while in the initial phase of preparing the hard disk then continuing the installation. In an installed system, the corresponding button can be found in the YaST2 Control Center under ‘System’.
Figure 5.10: YaST2: Activating LVM During Installation
25
5
Installation of SuSE Linux eMail Server with YaST2 5.8.2
LVM — Partitioner
First, you will reach a dialog where you can change the partitioning of your hard disk. Here, remove or change current partitions and create new ones. A partition to use for LVM must have the partition label 8E. These partitions are marked with the text “Linux LVM” in the partition list inside the window.
Figure 5.11: YaST2: LVM Partitioner It is not necessary to individually set each partition designated for LVM to the partition label 8E. When needed, YaST2 will automatically set the label of a partition assigned to an LVM volume group to 8E. If there are unpartitioned areas on your disks, add LVM partitions in this dialog for all these areas. These partitions should immediately be set to the partition label 8E. They do not need to be formatted and cannot be assigned a mount point.
Figure 5.12: YaST2: Creating a LVM Partition
26
5.8
Logical Volume Manager (LVM)
Note If a valid LVM configuration already exists on your system, it will automatically be applied at the start of the LVM configuration. If this configuration is activated, no disks containing a partition belonging to an activated volume group can be repartitioned. The Linux kernel will refuse to detect the modified partitioning of a hard disk as long as even a single partition on this drive is being used. Of course, repartitioning the disks not attributed to an LVM volume group is not a problem. If you already have a valid LVM configuration on your system, it is usually not necessary to repartition it. In this dialog, configure all the mount points not located on the LVM logical volumes. In YaST2, at least the root file system must be located on a normal partition. Select this partition from the list and define it as the root file system via the ‘Edit’ button. Due to the great degree of flexibility in LVM, we recommend assigning all other file systems to LVM logical volumes. After stating the root partition, exit this dialog.
5.8.3
LVM — Setting Up Physical Volumes
This dialog manages the LVM volume groups (often abbreviated to “VG”). If there is no volume group yet on your system, you will be prompted by a pop-up window to create one. “System” is the name suggested for the volume group where your SuSE Linux system files are located. The physical extent size (often abbreviated to PE size) defines the maximum size of a physical and logical volume in this volume group. This value is usually set to 4 megabytes. This allows for a maximum size of 256 gigabytes for a physical and logical volume. Only increase the physical extent size (e. g., to 8, 16 or 32 megabytes) if you need logical volumes larger than 256 gigabytes.
Figure 5.13: YaST2: Creating a Volume Group In the following dialog, all partitions are listed that either have "Linux LVM" or the "Linux native" types. Swap and DOS partitions will not be shown. If a
27
5
Installation of SuSE Linux eMail Server with YaST2
partition is already assigned to a volume group, the name of the volume group will be listed. Unassigned partitions bear the label "–".
Figure 5.14: YaST2: Overview of the Partitions The volume group currently being edited can be modified in the selection box above to the left. The buttons above to the right enable creation of additional volume groups and deletion of existing volume groups. However, only volume groups without any more partitions assigned to them can be removed. You do not need to create more than one volume group. A partition assigned to a volume group is also called a physical volume (often abbreviated to PV). To add a previously unassigned partition to the volume group selected, first select the partition then click on the button ‘Add volume’ below the selection list. Enter name of the volume group next to the partition selected. Assign all partitions meant for LVM to a volume group. Otherwise, the space on the partition will remain unused. Before exiting the dialog, assign at least one physical volume to each volume group.
5.8.4
Logical Volumes
This dialog manages the logical volumes (often just abbreviated to “LV”). Logical volumes are each assigned a volume group and each has a certain size. Normally, a file system is generated on a logical volume (e. g., reiserfs, ext2) that is also designated a mount point. On an installed system, the files stored on this logical volume can be found at this mount point. All the standard Linux partitions assigned a mount point, all swap partitions, and all already existing logical volumes are found in this list. If you have already configured LVM on your system, the available logical volumes should already be listed here. You will, however, still have to assign the appropriate mount point to these logical volumes. If you are configuring LVM on your system for the first time, there will not be any logical volumes yet in this screen and you will have to generate a logical volume for each mount point (with the ‘Add’ button), as well as define
28
5.8
Logical Volume Manager (LVM)
Figure 5.15: YaST2: Management of the Logical Volumes the size, the file system type (e. g., reiserfs or ext2), and the mount point (e. g., /var, /usr, /home).
Figure 5.16: YaST2: Creating Logical Volumes If you have created several volume groups, you can switch between the different volume groups in the selection list to the upper left. The new logical volumes are all located in the volume group shown in the upper left. After creating all the logical volumes required, the LVM configuration will be complete. Exit the dialog and continue to software selection, if in the process of installating the system.
Caution Implementing the LVM is also associated with increased risk factors such as data loss. Possible dangers are application crashes, power outages, and faulty commands. Backup your data before putting LVM to use and before reconfiguring volumes.
29
5
Installation of SuSE Linux eMail Server with YaST2
5.9
LILO — Introduction
The boot loader and boot manager LILO, the “LInux LOader” loads the Linux kernel. It can also start another operatiing system on your computer, if installed. LILO allows you to choose between different installed operating systems. YaST2 recognizes if you are using an operating system other than SuSE Linux. Depending on your machine’s environment, there are four alternative installation steps.
Note To start another operating system with LILO, make sure that you have a working boot disk for the other operating system, so that the it can be started with the floppy if necessary.
5.9.1
LILO — Background Information
When booting the computer, the kernel and the system files for the operating system have to be loaded and booted by the boot loader from the hard disk to the main memory. The boot loader can, therefore, only use the BIOS and not the operating system to access the hard disk. Since the BIOS only enables limited disk access, there should be a boot partition located on the first hard disk — at the beginning of it, if possible — to ensure the BIOS can access the necessary boot files. This is also the reason why Windows, for instance, normally uses the first partition on the first hard disk when it is installed. If LILO starts SuSE Linux, LILO will load the SuSE Linux kernel directly from the hard disk to the main memory then start it. In this capacity, LILO functions as a boot loader. If LILO starts another operating system, LILO will load the other operating system’s boot loader to the main memory then start it. The other operating system’s boot loader will then, in turn, load the operating system itself, since only the other boot loader knows for certain how to load its own operating system. LILO functions, in this case, as a boot manager, serving the purpose of loading another operating system as well as allowing a selection to be made between several boot loaders. The boot loader of the other operating system is located in the first sector of the partition where the other operating system is installed. Every hard disk partition has a boot sector — the first sector of each partition. Normally, a boot manager can only load another boot loader if it is located in the boot sector of a primary partition. Furthermore, the boot manager is, in certain circumstances, restricted to only the first hard disk, such as in the case of a DOS boot manager. The first sector of each hard disk is the boot sector. The boot sector of the first hard disk is known as the Master Boot Record (MBR). When booting, the BIOS
30
5.9
LILO — Introduction
loads the first sector of the first hard disk (the MBR) to the main memory then starts the respective application. If DOS or Windows is installed on the hard disk, the DOS boot manager is located in the MBR. As it is booting, the BIOS loads the DOS boot manager and starts it. The DOS boot manager loads the DOS/Windows boot loader from the boot sector of the partition recognized as active (in DOS/Windows, usually the first primary partition) and starts the DOS/Windows boot loader. The DOS/Windows boot loader loads the Windows system files and starts Windows in this manner. The DOS boot manager is, however, not an all-around boot manager, as it does not offer the user any selection options, but, rather, is defined strictly by each activated partition. If, during the installation of SuSE Linux, LILO is installed to the MBR (thus overwriting the DOS boot manager in the MBR), LILO may be able to act as boot manager and load the DOS/Windows boot loader or LILO will load the SuSE Linux kernel directly. Alternatively, LILO can be installed to the boot sector of the Linux boot partition, as long as it is a primary partition and if this partition, instead of the Windows partition, is now recognized as active. Then, the untouched DOS boot manager in the MBR will load and start LILO. LILO can then act as the boot manager in the manner already described above and might be able to load the DOS/Windows boot loader. Otherwise, LILO will load the SuSE Linux kernel directly. The advantage of this method is that the existing DOS/Windows boot mechanism remains nearly intact, because only the Linux boot partition is activated. Therefore, it is sufficient to reactive the Windows partition for the DOS/Windows boot mechanism to run exactly as described above.
5.9.2 LILO — Multiple Operating Systems If you already have another operating system installed, YaST2 will suggest saving the LILO to a floppy (see Figure 5.17 on the next page). This way, start Linux by first inserting this disk into the drive before switching on your computer. If the disk is not in the drive, the other operating system will start. Later, alternatively select the LILO expert installation in YaST2 and configure LILO so you can select the operating system should to start at system boot.
5.9.3 LILO — SuSE Linux Only If SuSE Linux is the only operating system existing on your computer, the dialog shown in Figure 5.18 on the following page will appear.
5.9.4
LILO — Multiple Hard Disks
If you have two or more hard disks on your computer, YaST2 cannot explicitly state, on its own, from which hard disk the operating system should be booted. The hard disks will be enumerated by YaST2 and the size of the disk space as
31
5
Installation of SuSE Linux eMail Server with YaST2
Figure 5.17: LILO Installation on Disk
Figure 5.18: LILO — SuSE as Single Operating System well as the drive label will be shown in Linux (e. g., /dev/hda). See Figure 5.19 on the next page. Drive labels such as C:, D:, and E: are irrelevant in Linux.
Note YaST2 suggests a hard disk to select. If problems arise when restarting the system, run YaST2 again and choose another hard disk in the item ‘Other configuration’.
5.9.5
LILO — When All Else Fails
In rare cases, the dialog will appear as shown in Figure 5.20 on the facing page. In such cases, LILO will not automatically be installed to your hard disk. SuSE
32
5.9
LILO — Introduction
Figure 5.19: LILO — Installation in the MBR Linux can, however, be booted from a start disk. YaST2 will not change the related start settings, but will suggest saving LILO to a floppy. This way, start Linux by first inserting this floppy into the disk drive before switching on your computer. If the floppy is not in the drive, your previous operating system will start. Once you are more comfortable using Linux, select ‘Other configuration’ in YaST2 and change these settings. Then you will have the option of selecting an operating system at system start via LILO.
Figure 5.20: LILO — The Most Complicated Scenario
5.9.6 LILO — Other Configuration If you chose ‘Other configuration’, a screen will appear as shown in Figure 5.21 on the next page. In this dialog, decide for yourself where LILO should be installed.
33
5
Installation of SuSE Linux eMail Server with YaST2
Four possibilities are open to you: 1. Install to /dev/hda (in the MBR of your hard disk) 2. Create a boot floppy 3. Install a boot manager other than LILO 4. Install to another partition To install SuSE Linux as a single operating system on your machine, select Option 1. With this, LILO will be installed to the Master Boot Record (MBR) of your hard disk. Also choose this option to use LILO as the boot manager for several operating systems. Make sure, however, that your other operating systems can be booted by LILO. If you are using several operating systems that you are not sure can be booted by LILO or if you do not want to make any changes to the previous start mechanism, choose ‘Create boot floppy’. This way, you can boot SuSE Linux from disk. If you have already installed a boot manager and want to include SuSE Linux in this boot manager, select ‘Do not install LILO’. After installing SuSE Linux you will have to reconfigure the existing boot manager and integrate SuSE Linux into the boot procedure.
Figure 5.21: LILO — Expert Mode
Tip Installing LILO on a boot floppy does not change anything with your previous boot mechanism. Start SuSE Linux from the floppy at any time. The option ‘Create boot floppy’ is the safest alternative when using multiple operating systems.
34
5.9
5.9.7
LILO — Introduction
LILO — Problem Cases
The boot loader LILO uses exclusively BIOS commands to load the kernel of the operating system from the hard disk to main memory and to start it. This can lead to several sources of error: • LILO hangs with the message L 01 01 01 ... or L 02 02 02 ... Causes: These error messages are BIOS error messages — the BIOS commands have failed and LILO is incapable of loading anything from the hard disk at all. If you have several hard disks, the BIOS can only access the first of the two EIDE hard disks and, for SCSI/EIDE mixed systems, may only be able to access the first one. Also, another cause of this problem could be that the order of multiple hard disks in the BIOS was switched around. Solution: Ascertain whether the boot partition is located on the first hard disk and, if possible, at the beginning of the disk space. • LILO hangs with the message LI. Causes: LILO can load some things from the hard disk, but it does not load what you
want, because the files in the boot partition are located outside the disk space accessible by the BIOS or because the disk geometry LILO acquired during installation is not the same as that the BIOS uses for booting. For example, for EIDE disks, the BIOS does not address the disk in LBA mode. Solution: Ascertain whether the boot partition is located on the first hard disk and at the beginning of the disk space, if possible. For EIDE disks, specifically set the disk geometry to LBA mode in the BIOS.
Caution A new installation of all operating systems on this hard disk is required after the disk geometry has been changed in the BIOS, because partitioning data will no longer be accurate.
LILO is most likely to function properly if the following requirements are met:
• The boot partition is located on the first hard disk at the beginning of the disk space. • If you have an EIDE disk, set the disk geometry explicitly to LBA mode in the BIOS.
35
5
Installation of SuSE Linux eMail Server with YaST2
5.10
Root Password
‘root’ is the name of the superuser or the system administrator. ‘root’ is per-
mitted to do all the things the normal user is not permitted to do. The superuser may make changes to the system, such as installing new applications or setting up new hardware. When users forget their passwords or have problems with software, ‘root’ is able to help them. As a general rule, only log in as root to carry out administrative tasks, such as system maintenance or repairs. ‘root’ is quite risky for everyday use, as ‘root’ can delete files that cannot subsequently be recovered or that could disable the system. Create the account for the superuser ‘root’ by entering a password and repeating it for verification purposes. See Figure 5.22. Select a secure password as the security of your system depends on it. A combination of letters and numbers is recommended. Be particularly careful not to forget the root password. It can not be retrieved at any later point in time.
Figure 5.22: Setting the Password for ‘root’
Caution The user ‘root’ has all the permissions needed to make changes to the system. You cannot carry out any administrative tasks without this password.
5.11
Confirming Installation
In the following dialog box (Figure 5.23 on the next page), you will see your previously chosen settings listed. You can also ‘Abort installation’ here. The installation of SuSE Linux will then be ended and your system will remain unchanged. To change some of your settings, click repeatedly on ‘Back’ until
36
5.12
Partitioning and Formatting the Hard Disk
you reach the dialog box in which to make changes. If you click on ‘Next’ instead, a dialog box will appear, asking if you are sure you want to proceed with the installation. If you answer ‘Yes - install’, the installation will begin. To save your selections for later retrieval, click ‘Save settings to floppy’.
Figure 5.23: List of Changes Made
Caution All data on the partitions chosen for SuSE Linux will, in the next step, be deleted irrevocably. If you have chosen the entire hard disk, all other operating systems and data will be erased.
5.12
Partitioning and Formatting the Hard Disk
YaST2 will now begin its work. It creates the selected partitions and formats
them. Depending on your system configuration, this may take some time.
5.13
Installation of Packages
Once you have started the installation process, the selected packages of the Linux base system are copied from CD or DVD to your hard disk. On this screen, monitor the progress of the various tasks (Figure 5.24 on the following page). Depending on the system configuration and size of the hard disk, the installation can be somewhat time consuming.
37
5
Installation of SuSE Linux eMail Server with YaST2
Figure 5.24: Package Installation
5.14
Monitor Settings
In the following dialog screen (Figure 5.25), define whether SuSE Linux should be operated in ‘Text mode only’ or in a ‘Graphical desktop environment’.
Figure 5.25: Monitor Settings When you click on ‘Change’, you have the option of configuring the graphical interface (Figure 5.26 on the facing page). Set the screen resolution and color depth for the graphical mode. Even define the image repetition rate. If you have a graphics card with a 3D chip, optionally select ‘3D acceleration’. By clicking on the ‘Test’ button, test the resolution selected. The installation program will issue a message that the screen will switch to the new resolution. If you do not see a steady screen, stop the test immediately by press-
38
5.14
Monitor Settings
Figure 5.26: Changing the Settings for the Graphical Interface ing ESC . Clicking on ‘Change Monitor’ will take you to the screen shown in Figure 5.27.
Figure 5.27: Selecting the Monitor Model Some technical data regarding your selected model and the horizontal (HSync) and the vertical (VSync) frequency deflection rates will appear in the bottom portion of the screen. If the preferred model is not included in the list, manually enter the data in the entry fields or choose predefined settings (VESA modes). Use the relevant values listed in your monitor manual. Otherwise, use a driver floppy. To do this, click ‘Driver disk’. Insert the disk into the drive and confirm with ‘OK’. If no file could be found or if the floppy is not readable, you will receive the respective warning. Otherwise, the monitor data will appear in the selection list. Alternatively, choose a standard resolution at this point. Select the item VESA and select 640 x 480 from the list.
39
5
Installation of SuSE Linux eMail Server with YaST2
5.15
Final Installation Steps
Finally, after it is installed, the SuSE Linux system must be initialized by ‘SuSEconfig’. When this is finished, browse the ‘Installation Log’ to see whether all the steps have been completed with ‘OK’.
5.16
Network Configuration
For network configuration, there is the ‘Automatic Address Assignment with DHCP’. This will only work for the SuSE Linux eMail Server if there is a DHCP server on your network configured in such a way that it can give the SuSE Linux eMail Server the same IP address and host name each time. The existence of a DHCP server in itself is not sufficient. To use DHCP, the checkbox ‘Change host name via DHCP’ also needs to be activated. See Figure 5.29 on the facing page.
5.16.1
Static Network Configuration
‘Static address configuration’ is the preferable way to set up your network. The following always must be configured: • IP address • subnet mask • host name (host name and domain name) In most cases, the following also needs to be configured: • Name server (IP address of the name server and optional domain search list) • Routing (normally just the IP address of the default gateway)
5.16.2
Dial-on-Demand Configuration
Consult the network manual for instructions for configuring a dial-on-demand Internet connection.
5.17
SuSE Linux eMail Server Basic Configuration
5.17.1
Part One
If you have a fully functional name server on your network and have specified its IP address in the network configuration, you will not need an additional DNS
40
5.17
SuSE Linux eMail Server Basic Configuration
Figure 5.28: Configuration of the Network Address
Figure 5.29: Configuration of the Host Name and Name Server server running on the SuSE Linux eMail Server. This item can then be deactivated. Leave the default values set for ‘LDAP BaseDN’. The default is the domain name specified in the network configuration. Here, the administrator password is not the root password for the system administrator specified previously, but, instead, refers to the password for the administrator responsible for the subsequent configuration of the SuSE Linux eMail Server mail system and for the mail administrator. These administrators are called cyrus and mailadmin. The same password is set for both.
5.17.2
Part Two
Enter your company name and select your country.
41
5
Installation of SuSE Linux eMail Server with YaST2
Figure 5.30: Configuring Internet Access After completing the SuSE Linux eMail Server basic configuration, the Linux system will reboot to its final mode of operation. As it is rebooting, more messages will appear on the screen.
5.18
Graphical Login
The SuSE Linux eMail Server is now installed and you can log in to the system as user ‘mailadmin’ by clicking on the icon or typing the user name in the field ‘Login:’. Give the password specified during the installation. For security reasons, what you type is not displayed. Even the length of the password is hidden.
42
6
The Administration System
6 The Administration System 6.1
The Home Page in the Browser
Once installation has been successfully completed, the SuSE Linux eMail Server will now provide all its functions. First, check to see if you can access the web front-end with a browser. To do this, open a browser on your client host and enter the URL http://IP_ADDRESS_OF_THE_SERVER. This will present the home page (see Figure 8.1 on page 71).
Figure 6.1: Home Page of the SuSE Linux eMail Server Provided that your client can resolve the SuSE Linux eMail Server name with the help of DNS (Domain Name Service), the server name can be entered as a URL along with the domain name: http://servername.domain.com
6.2
Introduction
The configuration system has been kept simple to allow easy and efficient navigation. It consists of a first row of tabs providing the main configuration menu and a second one forming a submenu. The latter will be enabled as needed by clicking on the main tab row, with the corresponding main tab being color-highlighted. When clicking on a submenu tab, the corresponding dialog will open. Temporarily change the language by clicking on the flag. This change will not be saved and is reset to the default for the next login. When clicking on the question mark in the upper right corner of each dialog, a separate help window will open. It contains explanations of the corresponding configuration options. After making changes, select ‘Log out’ to finish the configuration session. To make
43
6
The Administration System
further changes after logging out, provide the correct user name and password again.
6.3
Configuring the Server as the Administrator (‘cyrus’)
To administer the SuSE Linux eMail Server with the permissions of the mail administrator, log in as ‘cyrus’ and provide your administrator password in the configuration menu. After that, you have access to nearly all the options affecting the operation of the mail server. The following sections all refer to configuration conducted as ‘cyrus’.
Note To modify the configuration of the system itself, log in to a console as ‘root’. The graphical interface can also be started as ‘root’ to use YaST2 or other tools. All the system settings necessary for the operating system should be made as ‘root’, but you will not be able to change values pertaining to the SuSE Linux eMail Server.
6.4
User Administration
After installation of the SuSE Linux eMail Server, the first thing to do is create the necessary user accounts. So far, you will have created the accounts for ‘cyrus’, the server administrator for configuration, and ‘mailadmin’, the user authorized to read any e-mails sent to the administrator.
6.4.1
Creating a New User
To create the first user, select ‘User’ in the main menu then ‘New’. Now enter the new login name (UID) (see Figure 6.2 on the facing page). The UID can consist of up to eight characters, but must not contain any special characters or spaces. Also, each user name must be unique on your system. The mail address entered here will be used as the return address of that user if the mail client SKYRiXgreen is used. However, if another external mail client is used, the user’s e-mail address must be set in the client program’s configuration. For your users to have their proper names included in addresses, use the e-mail alias to fill in the address. By default, this alias is created using the syntax
[email protected]. Add more aliases later by selecting the menu entry ‘Edit’. Being the administrator, your next task is to provide a password for the new user. This password does not have to be a very secure one. The user will be required to change it at first login anyway. Choose between two encryption methods
44
6.4
User Administration
Figure 6.2: Creating a New User
for the password — either the older “crypt” method that allows for a password length of up to eight characters or the “SMD5” method allows passwords up to 255 characters long. Also specify the primary group to which the new user will belong. Additional group memberships can be assigned later using the ‘Groups’ dialog. If you have not created any groups on the system so far, you will only be able to specify ‘users’ at this point. Check the value given under Quota. This value specifies the maximum disk space available for the user to store messages in folders on the mail server. The user will not be able to receive new e-mails after this space is filled. The user must delete older messages to receive new messages again. This value can be changed at a later time if needed. If, however, you do not want to limit disk usage for a particular user, remove the value from the field. The default value used when creating a new user can be changed by selecting ‘Mail’ → ‘IMAP Configuration’ from the menus. The last thing to do is to tell the corresponding person about the user name and the password, at which point the user can log in to the mail server and change the password. There is no need for the administrator to remember user passwords, as he can provide a new password even without knowing the existing one.
45
6
The Administration System
6.4.2
Modifying User Accounts
Click on ‘Edit’ to modify user accounts. First select the users to be displayed. If you do not have many users, use the ‘Apply filter’ action without changing the value ‘*’ provided in the entry field to display all users. Select individual users from the list with a mouse click. The selected users will then be color-highlighted accordingly. By clicking on the buttons to the right, choose the following actions: ‘Delete’ Use this to completely remove the selected user from the server. Al-
ways proceed with great care when selecting this option. Using it will irretrievably delete all the user’s e-mails and other data. ‘Activate or Deactivate’ Disabling a user means deactivating an account
without deleting any user data. After disabling, the user will not be able to log in at the server and no e-mails can be received on that account. E-mails directed to such a user will be bounced by the server. Disabled users are marked with a ‘*’ to the right. ‘Create or Revoke certificate’ This dialog lets you create a certificate
for the corresponding user. However this will only work if a Certification Authority (CA) has been previously set up (see Section 6.9.1 on page 57). Creating a user certificate works similarly to server certificates. In the first dialog, you are prompted for the password set for creating a CA. In the next two fields, enter the password for the new client certificate twice. Confirm everything with ‘sign’. ‘Add to groups’ Users can be added to one or several (secondary) groups. Do
this by simply clicking on one or several of the available groups. ‘Edit user data’ This will display a dialog quite similar to the one shown
when a user is created. Any of the values displayed in the dialog can be changed. The dialog also gives the possibility of assigning aliases to users. To do so, enter the aliases as a space-separated list in the ‘E-mail aliases’ field. The user will then be reachable via e-mail under these aliases in addition to the regular user name. ‘Change password’ Use this dialog to define a new password for a user, some-
thing that will be necessary if a password is forgotten, for instance.
6.4.3
Changing the Password of ‘cyrus’
To change the administrator password (users ‘cyrus’ and ‘mailadmin’), select ‘Admin Password’ from the menu (see Figure 6.3 on the facing page). The new password can only be entered after supplying the old one (see Figure 6.3 on the next page). Be sure to memorize the new password, as your access to server administration will be lost if you forget it.
46
6.5
Arranging Users in Groups
Figure 6.3: Changing Administrator’s Password
6.4.4
Modifying Administrator Information
The administrator has access to the server through two different accounts: the user ID ‘cyrus’ used for configuration purposes only and the user ID ‘mailadmin’ used for reading administrator mail. These are predefined names that cannot be changed. Most of the values shown in the ‘Admin data’ dialog should be left untouched and rarely require any modification.
Note Making careless changes to some of the values in this dialog could make your e-mail server completely inoperative!
Limit changes to the following entries: ‘Last name’, ‘First name’, ‘Country’, and ‘Language’. Other values should be changed only if you really know what you are doing.
6.5
Arranging Users in Groups
In the ‘Groups’ dialog, arrange users in different groups to manage permission settings on your server better or to create a mailing list (see Section 6.6.2 on page 49).
6.5.1
Creating a Group
A new group can be created by selecting the submenu ‘New’ (see Figure 6.4 on the next page). A group name may only consist of lowercase letters and must not include any special characters or spaces. Try to give the new group a unique but descriptive name. To include users in the new group, first display a list of users. To see a list of all existing users, click
47
6
The Administration System
Figure 6.4: Creating a Group ‘Apply Filter’ without changing the value in the ‘Filter’ field. Otherwise, change the value under ‘Filter’ so the selection of users is limited according to your needs. After that, select one or several user for inclusion into the group with a mouse click. User names selected in this way will be color-highlighted. To finish off, select ‘Add’, which creates the group with the corresponding users.
6.5.2
Editing Groups
Use the ‘Edit’ dialog to edit and delete groups or to change the group description. To do so, select one group then the ‘Edit’ button to see the list of members and to change it as needed (see Figure 6.5 on the facing page). The complete list of all users on the system will be shown if you select ‘Apply filter’. Users already belonging to a group will be color-highlighted. Change group memberships to suit your needs by selecting with the mouse. To finish, select ‘Update’ which will save all changes to disk.
6.6
Managing Shared Folders
Use the ‘Folders’ dialog to create folders to share between several users or groups. If combined with the “Direct mail delivery” feature, this can be used to distribute e-mails among users who use POP so would not have access to shared folders. Also, shared folders allow set up of a mailing list without a lot of effort.
48
6.6
Managing Shared Folders
Figure 6.5: Editing Groups
6.6.1 Creating a Folder To create a new folder, select ‘New’ from the menu then enter the name of the folder. Folder names may only consist of lowercase letters and must not contain any special characters or spaces. Give the new folder a descriptive name. If you want the folder to have its own e-mail address, leave the corresponding option ‘Folder e-mail address?’ enabled. Finally, when you select ‘Add’, a new dialog opens for specifying the folder’s access rights.
6.6.2 Specifying Folder Rights The upper part of this dialog will display any rights assigned so far. By default, the owner of a folder will have maximum rights for it. This is something you should not change. To grant rights to other users, you will need a list of existing users. Just click ‘Filter’ or limit the selection of users by editing the ‘Filter’ field accordingly. Select individual users to grant or remove access rights. On the other hand, rights can also be granted to entire groups at once. For this reason, consider organizing users in groups first to grant these rights on a group basis. This will reduce the administrative overhead later when any changes need to be made. To complete your changes to access rights, select ‘Set’, which will also display any changes made in the upper section of the dialog. Continue to change other rights or leave the dialog. Access rights are defined as follows: (l)ookup: The folder is visible — it can be looked up by users. (r)ead: The folder and the e-mails stored in it can be read by users. (s)tore: The status flags new and read will be kept between different IMAP
sessions.
49
6
The Administration System
(w)rite: Status flags like new, replied, or draft may be changed. (i)nsert: The user is allowed to insert messages. (p)ost: E-mails can be sent to the folder’s receiving address. (c)reate: Subfolders may be added to this folder. (d)elete: Messages and entire folders may be deleted. (a)dminister: Grants administrator rights (e. g., to change rights of others).
The following combinations of rights should be the most reasonable for practical purposes: Reading (lrs): Folders can be looked up and their contents can be read. Adding (lrsip): In addition to the above, new messages may be added. Writing (lrswipcd): In addition to the above, this allows the creation and dele-
tion of subfolders and of the folder itself. Administration (lrswipcda): This comprises all access rights and thus also al-
lows the user to modify the rights of other users and groups.
6.6.3
Editing Folders and Rights
Use the menu ‘Edit’ to change folder attributes at any time after they have been created. To do so, first select a folder with the mouse, after which the folder should be color-highlighted. Click on ‘Edit’ to edit the folder’s description or to change the option ‘Folder e-mail address?’ by activating or deactivating it. To change access rights, select ‘Set permissions’. To completely delete the selected folder with all the mails in it, select ‘Delete’.
6.6.4
Direct Mail Delivery and Folder-Based Mailing Lists
The “Direct mail delivery” feature fulfills a special function. Enable ‘Direct mail delivery to user’ to tell the server that any e-mails sent to this folder should also be placed into the inbox of selected users. This will be necessary if these users access the server via POP to retrieve mail, because it is not possible to use folders with POP. Select ‘Apply filter’ to view a list of all the system’s users or edit the ‘Filter’ field first to limit the users shown. Users already selected are color-highlighted in the list. Select user names with a mouse click then save with ‘Save changes’. To revert to the settings present before changing the list, click ‘Reset selection’. By selecting ‘Back to folder selection’, go back to pick other folders for editing. In a similar way, configure the settings for ‘Mail delivery to groups’, only in this case all users in a group will receive a copy of incoming e-mails. This can be used as an easy way to set up a mailing list. Just put all users of the mailing list in their own group then create an incoming mail folder for it. Configure this folder to forward its contents to the members of the group.
50
6.7
6.7
Virtual Users and Domains
Virtual Users and Domains
It will often be the case that an organization uses several domain names. For instance, company.com could be used as the main domain with company.fr and my-company.fr as virtual domains. In many cases, these additional domains fulfill a functional role, as is the case when the organization wants to represent its foreign language presence on the Internet in a discernible way. The SuSE Linux eMail Server allows an unlimited number of virtual domains and users, including the ability to distinguish between users belonging to different domains. This means that an e-mail sent to a virtual user in a virtual domain (such as
[email protected]) is forwarded to a real user in the main domain (such as
[email protected]). As one can see, the local part of the address (sales in our example) can be used both in the main domain and in the virtual domain. The mail server can distinguish these addresses by their domain name part. The virtual address can also be used as sender address and be displayed in the “From:” line. To the outside world, it appears to be a separate domain.
6.7.1
Creating and Editing Virtual Domains
Before you can create a virtual user, create the virtual domain for this user. Click on ‘Virtual Users’ → ‘Virt. Domains’ and enter its name in the field to the right of ‘New domain’ then confirm with ‘Add’ (see Figure 6.6). Use these steps to add any number of virtual domains.
Figure 6.6: Creating and Editing Virtual Domains If there is no name server within your network to handle these domains, the same task can also performed by the SuSE Linux eMail Server. A name server (BIND8) configuration will be created automatically during installation, even if you did not choose to create it. In that case, the name server was configured, but
51
6
The Administration System
not started at all. To change this now, simply set the variable START_NAMED in /etc/rc.config to yes. Creating new virtual domains or deleting existing ones does not have any immediate effect on the name server configuration. Rather, to include any domains in the name server configuration, click the ‘Export’ button.
Note This action will overwrite the file /etc/named.conf as well as zone files for the domain name server stored in /var/named. To add special options to /etc/named.conf, use the template file /etc/named.conf.in. Include any additional parameters you need for the name server.
To include your own zone data in addition to the automatically generated main and virtual domain configuration of the SuSE Linux eMail Server, you can do so, but use names not identical to those automatically generated. Zone files will be named according to the following pattern: In the case of forward mapping, use /var/named/company.com.zone. In the case of reverse mapping, the “IN-ADDR.ARPA” address will be included in the file names.
6.7.2
Creating a Virtual User
After having created at least one virtual domain, create virtual users by selecting ‘New’ (see Figure 6.7 on the facing page). Click on ‘Apply filter’ to obtain a list of all users on the system or limit the selection of users first by editing the string in the ‘Filter’ input field. Enter a virtual e-mail address and select one of the available virtual domains. Then select one or several users and click on ‘Create’. From now on, these users will receive any mail sent to the virtual address.
6.7.3
Editing Virtual Users
To change the address of a virtual user, click ‘Edit’ then select the address to edit. Also give this address to another (real) user or entirely delete the virtual address.
6.7.4
Adding Clients to the Name Server
With the help of ‘DNS: create host’, configure the SuSE Linux eMail Server as the name server for the local network. This is recommended if you have no other name server running within your network. In this case, supplying the DNS of your ISP will not have any effect, because the ISP’s name service will not be able to resolve the addresses of your clients. To add a new client, enter its host name and IP address then confirm by clicking on ‘Create’.
52
6.8
Configuring the Components of the Mail System
Figure 6.7: Creating a Virtual User
Note The new entry will not be written to the configuration files immediately. To update the configuration files, select ‘Virt. domains’ → ‘Export’.
6.7.5
Removing Clients from the Name Server
To remove a client from the local network, select the option ‘DNS: delete host’. Even if you have only changed the IP address of a client, that client must first be removed then a new entry needs created. Such an entry will only take effect after you have selected ‘Virt. domains’ → ‘Export’.
6.8
Configuring the Components of the Mail System
Use the dialog found under the ‘Mail’ tab to configure all aspects of the mail system and set many important parameters needed for the operation of the SuSE Linux eMail Server. However, only change these values if you really know what effect they have.
53
6
The Administration System
6.8.1
Postfix: Basic Options
The Postfix interface allows you to influence the following functions (see Figure 6.8): Name of Relay Hosts: Enter the mail relay given by your ISP. Normally this
will be necessary if the server is not connected to the Internet through a dedicated line. Dial-on-demand: If you connect to your ISP using a dial-up line (e. g., ISDN),
specify whether the server should automatically establish a connection on demand. SASL: Enable this if users are allowed to log in via “secure SMTP” (authenti-
cated SMTP). TLS: This option will only be visible if you have set up a “CA” previously.
Enable this to have e-mails transmitted through an encrypted channel and to use certificate-based relaying.
Figure 6.8: Postfix Basic Configuration
6.8.2
Postfix: Expert Options
This dialog lets you modify, remove, and add nearly all parameters available for Postfix (see Figure 6.9 on the facing page).
Note Changing any values in this dialog without detailed knowledge can completely break your server. Only change those values where you are absolutely sure of the effects!
54
6.8
Configuring the Components of the Mail System
Figure 6.9: Postfix Advanced Configuration
6.8.3
Mail Retrieval: Fetch Mail
This functionality will not be needed as long as you are using a fixed, official IP address for your server and your mail server is “responsible” for your domain (i. e., an “MX record” has been made with an official name server). The functions under “Fetch Mail” are needed to retrieve e-mail from mail accounts with your ISP and to subsequently forward these messages to a local user. To add a new entry of this kind, select ‘New’. To change settings for an existing entry, select ‘Edit’ (see Figure 6.10 on the next page). Enter the data required to log on to the remote mail server. Under ‘Deliver to’, specify the complete e-mail address of the corresponding user on your local system, who will then receive all mails retrieved from this account. Under ‘Protocol’, select one of POP or IMAP. Normally, all ISPs should provide POP. By contrast, IMAP is not offered by all ISPs and you should therefore ask beforehand whether it is supported or not. If the account should be a multidrop account (mail to different users with the same domain is kept in one account), toggle the corresponding option. In this case, you will not have to specify a delivery address, because the SuSE Linux eMail Server will take care of the delivery of messages to users. In connection with this, specify whether the “QMail Prefix” should be used or not. This is because delivery addresses need to be in a special format if your ISP uses QMail for mail transport. For instance, if someone were to send a mail to your company, or more specifically to
[email protected], the QMail server of your ISP would write something like this into the mail header:
55
6
The Administration System
Figure 6.10: Fetch Mail “Delivered-To:
[email protected]”. In this case, “multidrop-” constitutes the QMail prefix. However, the exact form of the prefix will depend on your ISP’s server setup (so the best idea would be to ask the ISP). With the buttons under ‘At the following days’, configure whether mail shall be fetched on certain days only. For instance, you could specify the following to limit mail retrieval to your core business hours: “Mon Tue Wed Thu Fri, from 8 a. m. to 6 p. m., every 15 minutes”. The polling interval may be especially important if you rely on a dial-up connection (e. g., ISDN). To save some money, set longer polling intervals so the SuSE Linux eMail Server does not have to connect as often to the ISP.
6.8.4
IMAP Configuration: Access by Clients
This dialog allows setup of some basic preferences for how the SuSE Linux eMail Server should behave with regard to clients. In the entry field ‘Set default quota size’, set the value taken as the default quota when a new user is created. To configure after how long user must log in again if idle, set the desired value under ‘After the expiration of this time, idle IMAP users will automatically be logged out’. Logging users out automatically may be useful because some of them will forget to log out. Set the POP equivalent under ‘After the expiration of this time, idle POP3 users will automatically be logged out’. This will be useful mainly to sever any remaining open connections with the server. Normally, POP clients perform authentication each time they try to retrieve e-mail.
56
6.9
6.8.5
System: Additional Options
Mail Queue: Monitoring the Mail Transport
This dialog displays the mails processed by Postfix.Specify the refresh rate for the display in seconds (e. g., 5 seconds) then press ←- . After that, the dialog will be updated within the given interval. To disable sampling completely, select ‘Mail queue’ again. Normally, e-mails will not appear in this dialog for any longer period. However, if the Postfix mail system has stopped working or is not able to deliver mail for some other reason, mails yet to be delivered will be listed in this window. If you want Postfix to stop processing these queued mails altogether, click on the queue ID and select the ‘Flush Queue’ button. Note, however, that these mails will then be lost completely and cannot be recovered.
6.9
System: Additional Options
Here, change some additional system settings related to Apache, the handling of certificates, and modifications of the LDAP database. The dialog also gives the possibility to send a message to all users on the system.
6.9.1 Create or Remove a CA This is a front-end to help create your own CAs (Certification Authorities) and import certificates signed by “trust centers”. The latter require a fee to be paid, but are not strictly necessary for the mail server to function properly. ‘Create own certificate’: Use this to use the SuSE Linux eMail Server as a CA. Fill out all the required fields, but remember that the “CA password” will be needed later to create certificates for your clients and that it cannot be changed afterwards. The next dialog allows generation of the server certificate that will be signed by the CA created before. Use a password different from the previous one for this step. Note that ‘Host name of web server’ actually means the host name of your mail server. If the name stored in the server certificate does not correspond with this name, some browsers like Netscape will challenge the certificate each time they try to make a secure connection with your mail server. After having created the server certificate, you are ready to prepare certificates for your users and can also start using the SSL functions of Apache and Postfix. If you enter this dialog and a server certificate already exists, you will only be given the option to revoke it. To do so, enter the correct password. As soon as the certificate has been revoked, a new one can be created using the same dialog. Again you can either create your own certificate or import one. When creating a new one, use the existing CA or set up a new CA.
Note When an existing CA is revoked or a new one created, previously generated client certificates will no longer be valid.
57
6
The Administration System
6.9.2
Apache Configuration: Secure Access with SSL
You can enable a secure connection between your clients and the server with ‘Activate SSL’. This button can only be selected if a CA and a server certificate have already been created. The next step is to select one of these verification methods: none: No verification will be performed with regard to a valid certificate. optional: Verify whether a certificate is available, but give access even without
it. require: Give access only if a valid certificate is available. optional_no_ca: Verify whether a certificate is available, but not its validity.
CAs can have different hierarchies. In that case, a CA can be verified by another CA. The validity can be verified by an even higher CA in the hierarchy. The ‘verification depth’ sets the number of levels through which the Apache web server tracks the validity of CAs before rejecting them, if it does not get a verification. The default is 1, which means that you completely trust the CA that has signed your certificate. This value should not be changed.
6.9.3
LDAP Browser: Editing the LDAP Database
With the LDAP browser, you have direct access to the LDAP database, which holds nearly all user data. It is very important that you remember only to modify those elements about which you are absolutely sure. Making the wrong changes in the wrong place could completely break your mail server.
6.9.4
E-mail Newsletters: Sending a Message to All Users
There may be occasions when the mail administrator ‘cyrus’ wants to send a message to all users on the system. For instance, ‘cyrus’ wants all users to know that the SuSE Linux eMail Server will be down for maintenance for a given period. The dialog ‘Mail to all’ allows you to enter a subject line and a message to send such a mail (see Figure 6.11 on the facing page). It will go to all existing users regardless of whether they have exceeded their disk quota or not.
6.10
Resources: Managing Calender Resources
To manage and administer your resources (e.g., company cars and conference rooms) with SKYRiXgreen, specify them first in the dialog ‘Resources’.
58
6.10
Resources: Managing Calender Resources
Figure 6.11: An E-mail from the Administrator
6.10.1
Resources: Creating and Deleting Resources
Click ‘Resources’ then ‘New’ to create the resources to administer with SKYRiXgreen. Save your entries with ‘Confirm’. To remove obsolete entries, click on ‘Resources’ and then on the trash can symbol next to the resource to delete. Only resources that do not belong to a group can be deleted.
6.10.2
Creating Resource Groups
For easier management, organize the resources into groups in the dialog ‘Create Resource Groups’. First, define a name for the group. Then select the resources to go into this group from the list of already created resources. Finish by clicking ‘Commit’.
6.10.3
Resource Groups: Editing and Deleting Resource Groups
Defined groups can be changed anytime, with ‘Edit Resource Groups’. Resources can be removed from or added to the group by selecting or deselecting them from the list. When finished, click ‘Commit’ (see Figure 6.13 on the next page).
59
6
The Administration System
Figure 6.12: Creating and Deleting Resource Groups
Figure 6.13: Editing Resource Groups
60
7
Setting User Options
7 Setting User Options All users have access to a front-end to administer their own areas. The session can be closed with ‘Log out’. By logging out, nobody can access personal user data without logging in again — reentering the user name and password.
7.1
Settings
The ‘Settings’ dialog gives users the possiblity to enter personal data, change their passwords, and download a previously created certificate.
7.1.1
Personal Data: Entering and Modifying Personal Data
The dialog ‘Personal Data’ allows users to change data entered by the administrator and add some additional information, which is then available from the central address book (see Figure 7.1 on the following page). Users can also select among strings for the local part of their e-mail address, according to the possibilities allowed by the administrator. This will only be possible if SKYRiXgreen is used to write e-mails. You will not be able to configure external mail clients from this dialog. As another option, change the default language used for the display. The language can also be changed on a persession basis by clicking the flag in the upper right corner of the window. To save and update data according to your changes, press the ‘Update’ button.
7.1.2 Changing the Password For security reasons, change your password from time to time. To do so, select ‘Password’ and enter the old password in the field provided then the new one. Confirm the change by repeating it. See Figure 7.2 on page 63. Ask your administrator for help if you forget your password. Your administrator does not have to know your old password to provide a new one.
7.1.3 Certificate: Downloading a Certificate If your administrator has created a certificate for you to use, download it by selecting ‘Certificate’. Import it using your browser. The browser documentation should have information on how to do this.
61
7
Setting User Options
Figure 7.1: Personal User Data
7.2 Folders On an IMAP server, e-mails are stored in folders. By granting certain access rights for them, folders can be configured for shared use by several users, one of the advantages of the IMAP protocol. By contrast, there is no way to establish such folders when using POP.
7.2.1
New: Creating a New Folder
Clicking on ‘New’ will display a list of folders available for you to store mail messages. To add a new folder, first select an existing folder with a mouse click, for example, INBOX. Now enter the name for the new folder, for example, subfolder. See Figure 7.3 on the facing page).
Note Do not use special characters, uppercase letters, or spaces in folder names.
62
7.2
Folders
Figure 7.2: Changing the User Password
Figure 7.3: Create New Folder
The folder can now be created by selecting the ‘New’ button. Following the above example, its name would be INBOX.subfolder. The new folder may have subfolders of its own, for example, another_folder. If created, the complete folder name would thus be INBOX.subfolder.another_folder.
7.2.2 Edit: Folder Properties and Access Rights The folder INBOX with its subfolders INBOX.old, INBOX.public, and INBOX. sent-mail will always be present for any new user. These folders will normally be required and should not be deleted. In any case, deleting the complete INBOX folder will not be possible.
Note All mails contained in a folder are completely lost if that folder is deleted. The same applies to any subfolders (and their contents) in a folder.
63
7
Setting User Options
The ‘Edit’ dialog also allows you to rename folders. This can be done by entering the new name in the ‘Rename’ input field then clicking the corresponding button (see Figure 7.4).
Figure 7.4: Edit Folder You can change access rights for folders you own. If you select the ‘Permissions’ button, a dialog will appear that is similar to the folder creation dialog. Being the owner of the folder, you have full administrative rights over it. This setting itself should be left untouched, however. A detailed explanation of how to grant rights can be found in Section 6.6.2 on page 49. While that section describes how the mail administrator (‘cyrus’) has maximum access to the folder by default, the same applies here in the sense that the user who has created the folder will have these maximum access rights. Newly created subfolders will always inherit rights from the folder to which they belong.
7.3
SIEVE: Mail Filtering
The SuSE Linux eMail Server has a built-in mail filtering system based on SIEVE, which you can use to process incoming mail in an automated fashion.
7.3.1
Mail Filters
Use the ‘Mail Filter’ dialog to define conditions to process incoming mail in a specific way. To achieve this, define conditions then select an action to perform if the conditions are met. Conditions can be combined with each other using the operators and and or (see Figure 7.5 on the next page). Define any number of filters, which are then processed one after another. To configure such a mail filter, consider the following short example: A friend sends you e-mails regularly, but you do not want to receive all of them. Some of your friend’s e-mails, which are sent from
[email protected], are bigger than 1 Megabyte. Those are the ones you would like to discard. So you
64
7.3
SIEVE: Mail Filtering
Figure 7.5: Mail Filter
Figure 7.6: Limiting the Size of Incoming E-mails plan to reject these mails and to send a message back to your friend telling him about this. To achieve this, select ‘Add filter rule’ then click ‘Size restriction’. See Figure 7.6. Now specify the size limit for messages. In our example, you would set this to ‘Message is larger than 1 Megabyte’. Confirm this with ‘OK’. Next select ‘Filter for header fields’, then ‘From:’ and ‘contains’ and enter ‘
[email protected]’’ in the field. Confirm with ‘OK’ again. Having defined the conditions, you still need to select the action to be performed, which you can do now after selecting ‘Continue’. In this dialog, select ‘Reject message and reply with this explanation’, then write a clear message explaining the issue, for example, “This message is too big, please keep your messages smaller.” See Figure 7.7 on the next page. If you want the kind of mail specified to be filtered in any additional way (which is not likely in this case), enable the option ‘If filter applies also process the following filtering rules’. Now save all changes. When you reopen the ‘Mail filter’ dialog again, the rule defined will be shown in the form of a sentence. You now have the possibility to change this filter with the little symbols: sheet of paper and a pen: go back to the filter definition dialog.
65
7
Setting User Options
red crossmark or green checkmark: disable or enable the filter trashcan: delete the filter entirely.
To make another filter, select the button ‘Insert new filter’. The new filter will be inserted at the end of the filter list as long as you do not change anything in the field labeled ‘at position’. You can also specify another position for the filter. The order in which filters are processed does matter in some cases.
Figure 7.7: Defining Mail Filter Action
7.3.2
Vacation Notice: Sending Automatic Replies
The vacation note function allows you to tell the SuSE Linux eMail Server to automatically reply to any incoming mail. Click on ‘Create’ to write such a note. In the following dialog, enter the subject line and the text of the message to send. See Figure 7.8 on the facing page. For the subject line to be derived from each message as received, just leave the ‘Subject’ field empty. When someone sends you an e-mail when the vacation note option enabled, the sender will receive a reply with the message body as defined. At the same time, the sender will be added to a database. If you receive an e-mail from that sender again before the interval as defined with ‘Repeat after’ has elapsed, no automatic reply will be generated. Optionally, specify an e-mail address to which all your incoming mail should be forwarded under ‘Forward to’. Messages can be forwarded to an internal address (e. g., if you want a colleague to handle the message) or to an external address (e. g., to a mail account you can use from home). If you have created a vacation note, this will be indicated after you have selected the submenu ‘Vacation Notice’. Disable the vacation note by clicking on the green checkmark symbol or reenable it with the red crossmark.
66
7.3
SIEVE: Mail Filtering
Figure 7.8: Create Vacation Note
7.3.3
SIEVE Editor: Creating Custom Scripts
The SIEVE editor (see Figure 7.9) allows you to create your own scripts to process mail messages in an automatic fashion. It also allows you to insert your existing scripts. Any changes introduced here should be well thought-out, as a non-working script could completely interrupt all automatic mail handling.
Figure 7.9: SIEVE Editor to Write Scripts
67
7
68
Setting User Options
8
SKYRiXgreen — An Appointment, E-mail, and Task Manager
8 SKYRiXgreen — An Appointment, E-mail, and Task Manager 8.1 8.1.1
Introduction What is SKYRiXgreen?
The SuSE Linux eMail Server uses SKYRiXgreen as a web-based interface. It allows a user to read and write e-mails as well as manage addresses, tasks, and appointments. SKYRiXgreen is a fast and efficient managing tool for most of the daily tasks of a web-based groupware. The user interface is written purely in HTML (Hyper Text Markup Language), the page description language of the WWW (World Wide Web). No Java applets are necessary. The key advantage of all this is that SKYRiXgreen can be used on any platform. Using SKYRiXgreen is easy. Start any kind of Internet browser (e. g., Konqueror, Microsoft Internet Explorer, or Netscape Navigator) with any computer connected to the local network of the SuSE Linux eMail Server or, if permitted by the administrator, the Internet and you will be immediately able to work interactively with your data. The program offers a core of data that every user can access, depending on access rights. SKYRiXgreen is an intuitive tool — its functions are self-explainatory. However, it offers an online manual with an explanation of all available functions. The clear menus allow quick navigation inside the program to select the needed tool. Most of the time, a description is provided for interactive elements. Otherwise simply position the mouse pointer over an area and a help text will appear.
8.1.2
Features
SKYRiXgreen includes the following features:
• Sessions • Central data manager for all clients, partners, and colleagues • Worldwide data accessibility over the Internet • Worldwide organization and transparency of appointments and projects • Automatic messaging via e-mail • Different languages, time zones, and colors
69
8
SKYRiXgreen — An Appointment, E-mail, and Task Manager
• Easy maintenance and intuitive user management • Interfaces for data exchange
8.1.3
Program Differences
The main task of SKYRiXgreen is the efficient management of e-mails and appointments. The following characteristics of SKYRiXgreen • The program is intuitive and simple to use. • There are no unnecessary functional overloads. • Most users can apply Internet experience to SKYRiXgreen. • SKYRiXgreen can be adjusted to your individual requirements, with its numerous preconfiguration possibilities. • The interface appearance can be modified by the administrator. • It is fast and functional.
8.1.4
System Requirements
The program runs on following minimum system requirements: • Internet browser • Recommended Internet connection: at least ISDN or 56K Modem or local access to the SuSE Linux eMail Server • Recommended resolution: at least 800x600, 1024x768 preferred
8.2
Access
Logging in Before you can open your e-mails with SKYRiXgreen, log in. The following assumes that you have opened your browser and opened the address of the SuSE Linux eMail Server. The start screen as shown in Figure 8.1 on the facing page should be displayed. All buttons have a “Fast Help” (ToolTip). Move the mouse pointer over a button to display an explanatory message box. The start screen asks your user name and password. Enter both and either press ‘Configuration’ or ‘WebMail’. With Configuration, access an area of the SuSE Linux eMail Server in which to set different values for different settings. To access the interface of SKYRiXgreen, click ‘WebMail’. The typical SKYRiXgreen interface appears as shown in Figure 8.2 on the next page. To the top and
70
8.3
Mail
Figure 8.1: SuSE Linux eMail Server Home Page
Figure 8.2: SKYRiXgreen the left, find different menu bars to use to manage the different functions of the program. When already inside the configuration area of the SuSE Linux eMail Server, press ‘Mail/Calendar’ to access SKYRiXgreen. To return to the Configuration, press ‘Server Config’.
Logging out Sessions are automatically terminated when the interface remains idle for a certain period of time. However, you should always log out every time you leave the web interface of the SuSE Linux eMail Server. Select ‘Log out’, available inside Configuration and SKYRiXgreen.
8.3
Mail
SKYRiXgreen offers a powerful e-mail management system that allows you to
read, write, and manage your messages via a convenient web front-end. The
71
8
SKYRiXgreen — An Appointment, E-mail, and Task Manager
e-mail management system comprises the functions described in the following sections. In the upper left of the browser window, find SuSE’s mascot, Geeko. If Geeko is waving a flag, you have new messages. Click the flag to open your Inbox. If you do not see a flag, continue to the usual start page by clicking the first menu item, ‘SKYRiXgreen’.
8.3.1
Folder Management
Every e-mail is deposited in a folder on the eMail Server. New messages are saved in the directory /INBOX. Along with this standard directory for new messages, SKYRiXgreen also uses other directories. See Figure 8.3.
Figure 8.3: Folder Selection Use /INBOX/drafts to save your templates or unfinished messages to resume later. In the directory /INBOX/sent-mail, SKYRiXgreen saves a copy of all sent e-mails. Every time you write a message, you have the option to save a copy of the message automatically in this directory. You will then always be able to establish when and to whom it was sent. A trash bin is under the path /INBOX/trash. The trash contains deleted mails. If you need a deleted message again, extract it from the trash. Preconfigure whether to delete a message immediately or keep it for a while in the trash directory. The latter is recommended to prevent unintentional deletion of messages. The e-mail directories described so far are listed in the menu on the left of the SKYRiXgreen interface. Under the menu item ‘Mail’, find the directories Inbox, Drafts, Sent, and Trash. Click a name to show the contents of the directory. The above paths are standard. Set the directory represented in the preconfiguration section. If, for instance, you prefer to use the menu item Inbox to open something other than the directory /INBOX, assign it a different link under ‘Options’ → ‘Directories’. This is sensible if, for example, your drafts are saved in a different directory. Using the default settings, however, is recommended. The only way to manage directories on the SuSE Linux eMail Server is from the administration front-end of the server itself. Inside SKYRiXgreen, select ‘Server Config’ → ‘Folder’. Create new folders or edit existing directories.
72
8.3
8.3.2
Mail
Writing a Message
Figure 8.4: E-Mail Composition To write an e-mail, click on ‘Mail’ → ‘New Message’. A form will appear for the e-mail data. See Figure 8.4. In the insertion line ‘To’, insert the e-mail address of the receiver. It may be an address or a combination of name and address. In the latter case, it should look like this: "FirstName LastName"
Insert multiple addresses separated by commas. Directly underneath the ‘To’ line, find two more lines: ‘CC’ and ‘BCC’. These abbreviations stand for “carbon copy” and ‘blind carbon copy’. Use ‘CC’ to send copies of the mail to additional addresses. Every receiver can see the addresses indicated in ‘To’ and ‘CC’. Use ‘BCC’ to send a copy of the mail to someone without the ‘To’ and ‘CC’ recipients knowledge. Type a short, clear description of the topic of your mail in the ‘Subject’ line. Select the priority of your mail among 5 levels between ‘Very high’ and ‘Very low’. Remember, however, that many receivers do not look at these marks. It usually suffices to use the default level of ‘Normal’. In the following area, type the body text of your mail. The only required insertions are the message text and the receiver. A subject is recommended.
8.3.3
Reading Messages
To read a mail, switch to the relevant e-mail directory. Normally, new messages are deposited in the directory Inbox, sent mails in Sent, drafts in Drafts, and deleted mails in Trash. For example, click the directory Inbox in the left menu. It will open a standard directory with your e-mails, with new and read messages. They are kept in this directory until moved or deleted. The directory is loaded and a list of your mails is shown. Every message is characterized by a sender, subject, and date. Further information is provided about mail size and whether it has been read. With a click on the button at the top of the table, sort the list according to the item represented in the selected column. It is also possible to order the mails in ascending or descending sequence.
73
8
SKYRiXgreen — An Appointment, E-mail, and Task Manager
To delete a mail without reading it, check the chosen mail on the left edge of the page and click ‘Delete’ on the lower edge. To read a message, click its subject. It will open the e-mail viewer and show the message. The e-mail viewer is responsible for the representation of e-mails. The message text can be shown in HTML format if sent in HTML format. All pictures in usual formats are shown directly. Documents attached to a mail are separated by a green stripe with name, type, and size of the attachment. Click the yellow arrow to the extreme left to download the document. Alternatively, a click on the document name will open a new browser window showing the contents of the attachment. When downloading a file, if no dialog is shown, select an item from the context menu, depending on the browser, which will enable you to open the document correctly. In some cases, the browser does not know how to view a particular type of file and you will have to download it first.
8.3.4
Replying to a Message
To reply to a message click in the toolbar on ‘Reply’ or ‘Reply to all’. The mail will be loaded to the writing form with the message text indented and the sender inserted in the receiver line. If you choose ‘Reply to all’, the ‘CC’ line will be loaded as it is to also receive a copy of this mail. All addresses that have been inserted automatically can be edited.
8.3.5
Forwarding a Message
To forward an e-mail to another recipient, press ‘Forward’. It will load a writing form and a new e-mail will be created automatically to accompany the message to forward. All other functions work in the same way as the writing mode.
8.3.6
Bouncing Messages
Bouncing is a further forwarding tool. By simply forwarding, the mail to forward will be accompanied by a new mail. By bouncing a message, the message will be sent “as is” to another address. The previous address will be overwritten with the new forwarding address, without deleting the original data. It is thus possible to send wrongly addressed messages to the right receiver. To send a message a second time, activate ‘Send again’. Enter a new target address in the new page. Click ‘Okay’ and the letter will be sent.
8.3.7
Deleting messages
Delete a message in two ways: mark the message to delete on the left edge of the directory window (e.g., in the Inbox directory) and select the function ‘Delete’ from the toolbar at the lower edge of the window. Alternatively, open the mail first and delete it directly from the message viewer by clicking ‘Delete’ in the toolbar.
74
8.4
8.3.8
Address Books
Using address books
When filling in an e-mail-form, you might want to insert many different addresses in the receiver line. There is a more convenient alternative to the manual insertion: beside every insertion line for e-mail addresses, find a button with the picture of an address book. Click this button to open the address book in selection mode. The address book offers an additional table column at the right of the list. This column contains, for every address, a pop-up menu, that enables you to assign the chosen address to one of the three insertion lines (‘To’, ‘CC’, ‘BCC’). Select the receiver addresses then click ‘Okay’. The selected address will be loaded in the e-mail editor. Use ‘Back’ to return to the editor without selecting an address.
8.3.9
Attachments
To send a file together with an e-mail, link to it in the e-mail editor. It will then be attached to the mail sent. If, for example, you want to attach the file picture.gif, click underneath the e-mail on ‘Browse’. It will open a file viewing dialog, which may vary according to the operating system. Select the file and press ‘Okay’. The complete file name will be inserted in the line to the left of ‘Browse’. Further to the right is ‘Attach’. If you press this, the chosen file name will be linked to the message and appear as non-editable text under ‘Browse’. The insertion area will be emptied and will be available for the insertion of a second file. To detach an attachment from the mail, press ‘Delete Attachment’, shown after every existing attachment of the current mail. When everything is completed, send the mail as usual. The attachment will be sent automatically together with the mail
8.4 8.4.1
Address Books Overview
SKYRiXgreen offers three different address books: System, Public, and Private. In the address book ’System’, find users managed by the SuSE Linux eMail Server — those who possess a mail box on this server and read their mail from it.
The public address book is visible to all users. It contains all addresses needed by the users as a whole. In a company, it could contain customer details, for example. The private address book includes all private contacts — all addresses you inserted and do not want to share with others in the public folder. See Figure 8.5 on the following page.
75
8
SKYRiXgreen — An Appointment, E-mail, and Task Manager
Figure 8.5: Private Address Book
8.4.2
Selecting an Address
Access the address book by clicking ‘Address Books’. Simply select the name of the chosen book to open it. You will not see any data, yet. As the amount of data to viewed may be large, try to restrict this amount beforehand. To do that, make a search in the insertion line. Insert the name to search, whether a full name or a name with free definable parameters. To find the name “John Smith”, type “John Smith”, “John S*”, “*Smith”, or just “Smith”. Click on ‘Search’ to begin the search. The bar directly above the search insertion is easier to use. Click ‘All’ to view all data. Click a letter or a number to show only the people whose name begins with the chosen letter or number. According to the search criteria, the addresses found will be listed. Every list will show either all or a predetermined number of items. Set this under ‘Options’ → ‘Preferences’. If the output has been limited, find page buttons on the upper right edge of the table with which to scroll from one page to the next.
8.4.3
Adding an Address
Both private and public address books enable their proprietor to add addresses by pressing the button ‘New User’ in lower right corner. Press this button to open the address editor where you can insert a new set of data. In the editor, all insertion lines of the relevant data set are structured in a very clear way. Fill them in as completely as possible. Insert at least first name and last name. Scroll to the lower screen edge and save the set of data. As of now, the new address will appear in the address list.
8.4.4
Editing an Address
Open the relevant address book and click on the address so the address editor will appear in view mode. To edit the address, change into edit mode by clicking on the ‘Edit’ button along the lower edge of the page. The read-only lines will change into normal edit lines. Change the address and save it again.
76
8.5
8.4.5
Appointments
Deleting an Address
To delete an existing address, switch to the corresponding address book, open the address by clicking the name of the contact, and press ‘Delete’.
8.4.6
Moving Addresses
Save addresses in the address books for which you have writing rights. To move an address, open the source address book and load the set of data to copy or move by clicking on it. In the toolbar along the bottom, find the pop-up area with all possible target address books. Select the target book and use one of the buttons on the right to start the ‘Move’ or ‘Copy’.
8.5 8.5.1
Appointments Overview
The appointment manager of SKYRiXgreen is very extensive and, in a certain sense, very complicated. To prevent problems, read this chapter from the beginning to the very end and do not start somewhere in the middle. The diary differentiates appointments between Personal, Palm, and Resources. Personal Appointments are your own normal appointments — the appointments you will probably use the most. SKYRiXgreen also offers Palm Appointments: they are usually the same as your personal appointments, but they can also be deposited in a separate database. The reason for that is that Palm Appointments must be synchronized with those saved on your palm (if available) transferred without creating double registrations. This is the purpose of a separate database. A third sort of appointments is the Resource Appointment. Every resource (for example, a car) can be occupied or free. This status is shown in the category ‘Resource Appointments’. Recognize the kind of appointments viewed by looking at the colored mark-up of the index tab. All appointments can be represented in a daily, weekly, or monthly overview. Choose the overview by selecting one of the tabs on the right side of the window. All functions are available in all three overviews. However, some actions do adjust to the chosen overview. Directly underneath the tabs, find page arrows. If you are viewing a weekly overview, press these arrows to change to the next week. In a daily overview, change from day to day. With the button ‘Today’, the view will be returned to today. Left of this action bar, find a tool that enables you to extend or restrict the current selection. Choose a particular group out of a list of user groups or choose to have them all shown. The area ‘Mine too’ allows you to view your own diary together with the rest. In a weekly overview, select a certain week from a a popup menu, according to the number of weeks, and, when you wish to have your appointments adjusted to a different time zone, select a different time zone. At the end of the selection, click ‘Show’ and the selected data will appear in the overview.
77
8
SKYRiXgreen — An Appointment, E-mail, and Task Manager 8.5.2
Personal Appointments
>From your personal appointments, the program will plan your diary. Every single one of these appointments will be shown in this list.
8.5.3
Palm Appointments
A Palm Appointment is an appointment in or for your palm. It is separated from the normal appointments to avoid double registrations when transferring data to or from your palm. The list of palm appointments will then be transferred onto your palm device automatically. Synchronization
Palm appointments can be created manually (the usual Diary Editor opens) or by synchronizing the database of the palm with the normal personal appointments. To create an appointment manually, click ‘New’ in Palm Appointment mode. Fill in the form and save. Transfer a current personal appointment to the Palm Appointments by clicking ‘To Palm’ at the lower edge of the screen. The chosen appointment will now be created in the Palm Appointments. To synchronize the current appointments, for example, all personal appointments as of today, activate the button ‘Synchronize’. If all goes smoothly, the entire current diary is transferred into the Palm Appointments. Conflicts
Possible problems in the synchronization might occurr if the appointments to transfer already exist in the palm database (in modified form). If an appointment already exist in the parallel database or the relevant resource is already occupied in the chosen period of time, a conflict ensues. If it is only one appointment that conflicts with another in the other database, the two registrations will be shown together. Answer whether to transfer the appointment despite the conflict or ignore it. If several appointments conflict, these will be shown in a list, one under the other. Every kind of conflict will have to be solved individually and you will have to answer the question ‘Ignore and Copy or Cancel and Not Copy’ individually. Transferring Appointments to the Palm
Follow your palm’s directions for transferring the database. Before synchronizing, make the settings as described in the following section. The synchronization between palm and SKYRiXgreen works as follows: the palm establishes a connection to the desktop PC and the latter establishes a connection with a program running on the SuSE Linux eMail Server.
78
8.5
Appointments
On the SuSE Linux eMail Server, there must be a program called nhsd. It is shipped together with SKYRiXgreen. It establishes the connection between SKYRiXgreen and a palm over the Internet and allows it to communicate with SKYRiXgreen. As an administrator, switch in the right directory and start the program: cd ~/dev/SKYRiXgreen/ ./Tools/nhsd
Via the Internet, palms can access SKYRiXgreen and compare data. Current palms unfortunately do not have a direct Internet access. For this reason, you still need a normal PC to establish an Internet connection. Every palm uses software that must be installed on a PC and establishes the communication between a PC with Internet access and the palm. With Linux, you need to install the package SkyrixGreen-PalmClient.rpm series zima. Consult the documentation. This package is included with the SuSE Linux eMail Server. On newer Palms with Network HotSync, all the settings can be done in the menu ‘HotSync’. For Palms without NHS, a PalmOS Upgrade can be obtained from the Palm support. With Windows, the program “Palm-Desktop 4.0” is required. If not already installed, find it online at: http://palm.conxion.com/PalmDesktop_40_ENG.exe
After the installation, find some programs in \C:\palm\ that support the data exchange between palm and PC as well as the exchange between palm and a remote PC. The program to use is HotSync-Manager (HotSync.exe). Start it. In the task bar of Windows, a symbol will appear with which to open a window. Activate the items ‘Local’ and ‘Network’. Under ‘Setup’, configure the start behavior. Under ‘General’ and ‘Local’, configure the serial interfaces (COM1 or COM2). The page ‘Network’ should contain your unmarked name. Under ‘TCP/IP Settings’, your local PC should be indicated as main PC. Set up your palm. In the Memo application, create a new memo page. Insert the following 3 lines: SkyMail
As and , insert the same access data used to login to the web interface. Mark the memo as private, as only private memos can be browsed. In the HotSync Software on your palm, mark it as ‘Local’ and ‘Serial Direct’. In the menu item ‘LANsync Settings’, LANSync must be marked. Insert the name and IP address of the SuSE Linux eMail Server under ‘Main PC Name’. Connect the palm with your PC and HotSync-Manager. nhsd should automatically start a synchronization.
8.5.4
Resource Appointments
Resource Appointments are extracted from your personal diary. Resources cannot be manually and randomly marked as occupied or free, because they are always connected to your diary. To efficiently occupy a resource, use the function
79
8
SKYRiXgreen — An Appointment, E-mail, and Task Manager
‘Appointment Proposal’ or the Appointment Editor, if you already know the time. Before Resource Appointments are viewed, select the group of resources to view. For example, to view all cars belonging to your company, activate the check in front of the group ‘Cars’. In the overview, all cars will appear, together with the available information.
8.5.5
Creating a New Appointment
In all overviews, you can add new appointments. Click the shortcut ‘New’. The Appointment Editor will open and you can add new data. The important information is the time and a clear title.
Figure 8.6: Appointment Editor Every appointment can be connected with as many people as desired. You are automatically selected. To add additional people, insert a part of their names and click ‘Search’. The search results will be shown unmarked. Select the data of the people to link. You can link resources to every appointment. Click the insertion area called ‘Resources’. Insert the name or part of the name of the resource and click ‘Search’. You can also select the relevant resource category from the pop-up menu, restricting the search. All found resources will be viewed. Mark the resources to link with a simple mouse click. You can also adjust the reading and writing rights to the item in question. Selecting the people is like selecting the diary user. To assign reading rights to a whole user group, simply modify the read status corresponding to the name of the group. With ‘Private’, you will be the only one to be authorized to see the appointment. Reading rights may be assigned to whole groups of users, but the writing access to a certain appointment may be assigned only to certain users. When finished, click ‘Save’ and the appointment will be saved in the database. With ‘Cancel’, the inserted data will be cancelled. If you are inserting an appointment that already exists, a conflict will ensue. Check ‘Ignore Conflicts’ to save an appointment despite any conflicts.
80
8.5
8.5.6
Appointments
Modifying an Appointment
To modify an existing appointment, click the title of the appointment in one of the overviews. The appointment will be opened in view mode. At the lower edge of the browser, find (if your rights allow it) an ‘Edit’ button. The Appointment Editor changes its mode and allows you to edit the registration. The ‘Save’ button will save the appointment in the database.
8.5.7
Deleting an Appointment
To delete an existing appointment, click the title of the appointment in one of the overviews. The appointment will be opened in view mode. At the lower edge of the browser, find (if your rights allow it) a ‘Delete’ button. This command will eliminate the current appointment permanently.
8.5.8
Proposing an Appointment
The command ‘Propose Appointment’ opens the Appointment Editor and automatically inserts a time. Change the current data according to your needs and save. See Figure 8.7.
Figure 8.7: Propose Appointment
8.5.9
Print Preview
Print Preview creates a version of the current diary, optimized for printing. All colors are substituted with shades of black and gray and all unneeded buttons are eliminated.
81
8
SKYRiXgreen — An Appointment, E-mail, and Task Manager
8.6
Tasks
8.6.1
Tasks
SKYRiXgreen can manage your tasks and your to-do list. A tasks consists of a
title, a note, a resubmission date, and a settlement date. See Figure 8.8.
Figure 8.8: Tasks Every task has a “Done” flag. This flag looks like a check mark in the ‘Status’ column of the table. The attributes ‘Category’ and ‘Priority’ can be freely employed by the user. They are not used by the program. The task list is divided in three groups: ‘Current’, ‘All’, and ‘Archive’. Each group is represented by a tab on the table. In the group ‘All’, all open tasks are shown. Tasks that have been performed are immediately marked as done with a click on the status flag and archived. They will be saved in the ‘Archive’ list. In the list of the current tasks, find all sets of data whose resubmission date has come, together with completely new data. In this way, important tasks will not be forgotten accidentally. A task will be eliminated from the list of current or of all tasks if deleted or archived.
8.6.2
Creating a Task
To create a task, start the Task Editor, simply by clicking ‘New’. Fill in at least the line ‘Title’ and maybe also ‘Note’. All other data is not mandatory. With ‘Save’, leave the editor. The task will appear in the relevant task list.
8.6.3
Modifying a Task
Open the Task Editor by clicking, inside the task list, an existing task or its edit icon. Click the paper clip accompanying the task if a note is attached to it. The Task Editor will open. Make all necessary changes in it. Confirm your changes by pressing the ‘Save’ button.
82
8.7
8.6.4
Options
Marking a Task as Done
To mark a task as “done”, click the status icon. This will open an icon with a “Done” check and the task will be moved to the ‘Archive’ list.
8.7
Options
Many functions of SKYRiXgreen can be individually configured by the user. Use the submenu items of the menu item ‘Options’ or the menu items in the ‘Options’ menu. Click a shortcut and determine the behavior of the program. Use these menus to perform the adjustments necessary to make SKYRiXgreen meet your personal needs better.
8.7.1
Preferences
Behind the menu item ‘Preferences’, find different settings. Also use it to set important personal data. Every setting has a short and clear explanatory text and can be immediately edited.
Figure 8.9: Preferences
Page Size
Insert the number of items to show in each list. The value 0 shows entire lists. In all other cases — when a list is shown in more than one page — find page icons at the upper edge of the list. Automatic Mail Retrieval
Set the time in seconds after which SKYRiXgreen will retrieve new messages. If it finds new messages in the Inbox, it will show a flag in the upperleft corner of the browser.
83
8
SKYRiXgreen — An Appointment, E-mail, and Task Manager
Line Break
When using the Mail Viewer, this option will have an influence on the automatic insertion of a line break after n viewed characters. The value 0 shows the message without modifying its layout. Show Pictures in the Mail
This option allows you to show pictures sent together with the message, instead of links to them. Show Status Pages
If you have chosen this option, all important actions will communicate their results on a separate page. Without this option, you will only receive notices of errors and other essential events. Delete Mails Immediately
Allows the user to choose between the immediate deletion of a mail and its temporary deposit in the trash. The latter will have to manually emptied later by opening the trash directory and deleting items one by one or clicking ‘Delete all’. Reply-To
Insert an e-mail address to which reply e-mails should be sent. This address is only of importance if the receiver should send an answer to an address different than the one from which it is sent. If your Reply-To address is the same as your normal e-mail address, leave this line empty. Header
Insert all header abbreviations to show when mail is read. They should be in lowercase letters and separated by a comma. Only the selected headers will be viewed. However, when reading a mail, you can always click ‘Change View’ to make the program show all headers. No information will be lost. X-Accept-Language
Insert the language to use in a reply. For example, de or en. This information only serves to signal to the receiver in what languages you can communicate. Automatic Log Out
Insert the number of seconds after which you should be automatically logged out of your session. A value of 0 creates an uninterrupted session.
84
8.7
Options
No Inline HTML
With this switch, activate or eliminate the use of HTML in e-mails and attachments. This is sensible if you would like to avoid automatically loading HTML parts of an e-mail. Instead of that, receive a link that allows you to view the HTML page manually in a separate page. Time Zone
Set the time zone for SKYRiXgreen. Folders
This page allows you to link directory names with existing directories on the SuSE Linux eMail Server. For each name, create a path to use instead of the default path. If, for example, you want to change the inbox directory, insert a different path. The new path will be shown in the directory ’Mail’ when you click the Inbox link. See Figure 8.10.
Figure 8.10: Folder Options
8.7.2 Signature In this page, insert your signature. A signature is a text that is attached to your message. Use it by checking ‘Add signature’ when writing an e-mail. See Figure 8.11 on the following page. The signature text will be added to the message body as if written manually. You will not actually see anywhere that the signature has been added.
85
8
SKYRiXgreen — An Appointment, E-mail, and Task Manager
Figure 8.11: Signature Options
86
9
Configuring External Mail Applications
9 Configuring External Mail Applications In addition to the SKYRiXgreen methods previously described, your users can also use the SuSE Linux eMail Server over external mail clients featuring IMAP or POP3 mail server support. The Netscape Communicator, Versions 4.7x and 6.x, available for almost every operating system, and the mail client for the Open Source browser Mozilla are two possibilities. You also have the popular Linux mail client used in KDE KMail and the console-based program Pine. Outlook 2000 and Outlook Express feature parallel performance for Microsoft platforms. Other programs not described here can also be used, if they support IMAP or POP3 mail servers. To access the SuSE Linux eMail Server III global address book, your mail client must also have support for LDAP directory service queries. In the following, find information about configuring the clients described above for use in conjuction with the SuSE Linux eMail Server III. These descriptions consist of a basic explanation of setting up an IMAP client and configuring access to the global LDAP address book, if the client offers this feature. The clients can also be configured over the POP3 protocol, but it does not allow use of the full features of SuSE Linux eMail Server III, because, in this case, there is no commonly accessible folder. Furthermore, when you use POP3, your personal e-mails are downloaded from the server to your workstation, preventing your e-mails from being backed up by a centralized source. For these reasons, client-side configuration of POP3 will not be discussed here.
9.1
Preparing to Set Up an E-Mail Client
For expedient setup of an e-mail client with the SuSE Linux eMail Server III, some preparations need to be made first. A successful configuration requires the following information. If you do not have all this information available, consult your SuSE Linux eMail Server administrator. The information needed to configure the IMAP client is as follows: • Login name of the user (UID) • User password • E-mail address of the user • Fully qualified name of the SuSE Linux eMail Server The information needed to configure the LDAP address book is as follows:
87
9
Configuring External Mail Applications
• Fully qualified name of the SuSE Linux eMail Server • Search base and server root (LDAP BaseDN)
9.2
9.2.1
Configuration with Netscape Communicator Version 4.7x Configuring the IMAP Mail Client
To configure the IMAP mail client in Netscape Communicator Version 4.7x, open the ‘Edit’ menu after starting the browser and select the submenu item ‘Preferences’. You will now be taken to the settings menu in Netscape, where you can open the category ‘Mail & Newsgroups’ by clicking on the arrow in front of it. Then, select the submenu item ‘Identity’ and enter the corresponding user data in the designated fields. See Figure 9.1.
Figure 9.1: Identity and User Settings Next, to create a new entry for the IMAP server configuration, choose the category ‘Mail Server’ from the selection list by pressing ‘Add ...’. Enter the fully qualified name of your SuSE Linux eMail Server in the field ‘Server Name’, and click on the item IMAP in the field ‘Server Type’. As ‘User Name’, enter the login name (UID) of the user. For Netscape to save the password for accessing IMAP folders, also highlight the option ‘Remember password’. Refer to Figure 9.2 on the facing page. Finally, select the tab ‘Advanced’ in this dialog and deactivate the setting ‘Show only subscribed folders’ to show a list of all available SuSE Linux eMail Server folders.
88
9.3
Netscape Communicator Version 6.x and Mozilla 0.9x
Figure 9.2: IMAP Server Configuration Exit this dialog with ‘OK’ and enter the fully qualified name of the SuSE Linux eMail Server and your user name (UID) in the designated field in the section ‘Outgoing mail (SMTP) server’. See Figure 9.3 on the next page. After ending this dialog with ‘OK’, configuration will be complete and the user can establish a connection to the SuSE Linux eMail Server by opening Netscape Messenger.
9.2.2 Configuring the LDAP Address Book The following setup procedure is required to access the global LDAP address book of the SuSE Linux eMail Server with Netscape Communicator. Open Netscape and select the ‘Address Book’ item in the ‘Communicator’ menu. In the address book appearing next, select ‘File’ → ‘New Directory ...’ to add an entry for a new directory service server. The configuration screen, ‘Directory Info’, will follow. Enter the name of your organization in the field ‘Description’ and specify the fully qualified name of your SuSE Linux eMail Server as ‘LDAP Server’. As ‘Server Root’, enter the LDAP BaseDN values defined during the installation of the SuSE Linux eMail Server or provided by the administrator. Refer to Figure 9.4 on page 91. Then, confirm this dialog with ‘OK’. Use the ‘Search for ...’ button to query and implement the SuSE Linux eMail Server address book.
9.3
Netscape Communicator Version 6.x and Mozilla 0.9x
The configuration of Netscape Communicator Version 6.x is the same as that of the Open Source browser Mozilla, because both browsers use an identical “en-
89
9
Configuring External Mail Applications
Figure 9.3: Mail Server Configuration gine” for displaying web sites. For this reason, we will only use the example of Netscape Communicator to explain the configuration procedure, which is also applicable to Mozilla. However, since both browsers are currently under development, there could be slight differences from the screenshots shown here, depending on the version used.
9.3.1
Configuring the IMAP Mail Client
To configure the IMAP client, open Netscape Communicator and, after it starts, change to the Communicator menu client by selecting ‘Tasks’ in the menu panel and, subsequently, by clicking ‘Mail’ . If an e-mail account has not yet been set up, you will then be automatically greeted by an “assistant” that will guide you through the rest of the configuration. If this is not the case, manually start the assistant by opening the account settings. Choose ‘Edit’ → ‘Mail/News Account Settings ...’ in the menu panel. The assistant is started by clicking ‘New Account’ in the window that appears. In the first dialog field, select ‘ISP or email provider’ for account type and confirm your selection with ‘Next’. In the following window labeled ‘Identity’, enter the fully qualified user name and corresponding e-mail address in the designated fields. Refer to Figure 9.5 on page 92. After confirming with ‘Next’, a dialog will appear asking for server information. Enter the fully qualified name of your SuSE Linux eMail Server for the incoming and outgoing server. Choose IMAP as the server type for the incoming mail server. Refer to Figure 9.6 on page 92. During the last part of the configuration procedure, the ‘User Name’ window
90
9.3
Netscape Communicator Version 6.x and Mozilla 0.9x
Figure 9.4: Directory Info will appear, where the login name (UID) of the user on the SuSE Linux eMail Server should be entered in the corresponding field. In the ‘Account Name’ dialog, enter the name under which this newly created e-mail account should be managed in the Netscape e-mail client. Refer to Figure 9.7 on page 93. After entering this data, it will be displayed for confirmation and saved with ‘Finish’. Now open the dialog ‘Account Settings’ under ‘Edit’ → ‘Mail/News Account Settings ...’ and ‘Server’, located under the column shown to the left. By clicking the ‘Advanced...’ button, continue to the advanced IMAP settings dialog. Deactivate the option ‘Show only subscribed folders’. Refer to Figure 9.8 on page 93. Next, close this window by clicking ‘OK’. Select the option ‘Outgoing (SMTP) Server’ from the columns. Make sure that the server name given corresponds with the fully qualified name of your SuSE Linux eMail Server and that the name and password usage settings are disabled. Refer to Figure 9.9 on page 94. After closing this dialog with ‘OK’, return to the main menu of the Netscape mail client. Obtain an overview of SuSE Linux eMail Server folders available for each user to the left. View a list of the available folders by clicking in the menu panel on ‘File’ → ‘Subscribe ...’. This completes the configuration. The e-mail client is ready for use with the SuSE Linux eMail Server.
9.3.2 Configuring the LDAP Address Book Support for querying an LDAP address book with Netscape Communicator Version 6.x or Mozilla Version 0.9x is still in an early phase of development so is not featured by the current application versions.
91
9
Configuring External Mail Applications
Figure 9.5: Netscape v.6 Identity
Figure 9.6: Netscape v.6 Server Information
92
9.3
Netscape Communicator Version 6.x and Mozilla 0.9x
Figure 9.7: Netscape v.6 E-Mail Information
Figure 9.8: Netscape v.6 Advanced IMAP Server Settings
93
9
Configuring External Mail Applications
Figure 9.9: Netscape v.6: Outgoing Server Settings
94
9.4
9.4
Setting up KMail as of Version 1.3
Setting up KMail as of Version 1.3
An extremely sophisticated graphical mail client in Linux is KMail, which was developed as part of the KDE project and, as of Version 1.3, also enables use of IMAP mailboxes. Without this capability, an LDAP directory service cannot be accessed. Start KMail by clicking the corresponding icon or by entering ‘kmail’ in a terminal window. If you are starting KMail for the first time, the mail directory will automatically be added to your home directory. Confirm this with KMail by clicking ‘OK’. This local mail directory is, in itself, not needed for IMAP, but KMail will save your sent mail there. Click ‘Settings’ → ‘Configure KMail’ to carry out the configuration. Select ‘Identity’ to the left and fill out the required fields. Refer to Figure 9.10.
Figure 9.10: KMail Personal Information Now, click the next item in the left-hand column, ‘Network’. Click ‘Add’ and specify, in the following window, ‘IMAP’ as mailbox type and confirm with ‘OK’. In the following window, specify the required information regarding the IMAP mailbox. Refer to Figure 9.11 on the next page. After confirming with ‘OK’, proceed to the screen for configuration relating to sending and receiving messages. Refer to Figure 9.12 on the following page. Leave the values for ‘Port’ and ‘Folder Prefix’. Also, select ‘Show hidden folders’ and ‘Save IMAP password’ to activate these preferences. Confirm with ‘OK’ then enter the SMTP server for outgoing mail, leaving the port at 25. Confirm this window, too, with ‘OK’. This completes the configuration and, with that, KMail can already be used to read and write messages.
95
9
Configuring External Mail Applications
Figure 9.11: Creating KMail IMAP Mailbox
Figure 9.12: E-Mail Settings
96
9.5
9.5 9.5.1
Configuration with Pine Version 4.33
Configuration with Pine Version 4.33 Configuring the IMAP Mail Client
All mail program options for Pine are configured by way of the configuration file .pinerc, located in each user’s home directory. This configuration file is a pure ASCII text file and can be edited using a text editor. To make the changes described in the following, use only editors that do not generate line breaks, such as the Midnight Commander (mcedit) or vi. This configuration file will only be placed in your home directory after Pine has been started for the first time. To . Now start it, enter pine. Then close the resulting start screen by pressing E you will be automatically taken to the main menu in Pine (see Figure 9.13). The program can be ended by pressing Q then confirming with Y .
Figure 9.13: Main Menu in Pine Now you can edit the configuration file .pinerc, which was created with the default program values. To guarantee access to the SuSE Linux eMail Server’s IMAP folders, browse the options that appear next and make adjustments according to your configuration. Following each option is a short description of the values to set, beginning with ‘#’. Note the proper position of curly braces and angle brackets, as well as the uppercase and lowercase spellings infile names. Now save the file and start Pine by entering pine. By pressing L in Pine’s start window (see Figure 9.13), change to the ‘Collection List’, which displays the main folders set up in Pine. By selecting a folder using the arrow keys then pressing ←- , proceed to an overview of the IMAP folders of your SuSE Linux eMail Server stored there, after entering your password. See Figures 9.14 on page 99 and 9.15 on page 99. In the folder list, Pine differentiates between ingoing mail folders, the remaining personal folders, and the public folders. For this reason, the user’s incoming IMAP folder is not shown in the folder list, but, rather, is displayed in clickable ‘Incoming Folders’, located under the collection list (see Figure 9.16 on page 100).
97
9
Configuring External Mail Applications
personal-name=John Doe # The full name of the user to add smtp-server=imapserver.suse.com # The fully qualified name of your e-mail server for sending e-mail default-fcc=imapserver.suse.com/user=tuxINBOX.sent-mail # The IMAP folder in which copies of sent messages are saved. The # specification consists of the fully qualified server name and # the user’s login name on the eMail Server. In our example: # servername=imapserver.suse.com and loginname (UID)=tux incoming-folders=imapserver.suse.com/user=tuxINBOX # The incoming folder for each specified user. This specification, too, # consists of the fully qualified server name and the login name of # the user on the eMail Server. In our example, the server # name is imapserver.suse.com and the user name is (UID)=tux folder-collections="SuSE IMAP Folders" imapserver.suse.com/user=tux[*], "Personal IMAP Folders" imapserver.suse.com/user=tuxINBOX.[*] # # # # # # # #
This entry will create two meta-folders in Pine, each containing the publicly accessible (SuSE GmbH IMAP Folders) and the (Personal IMAP Folders) of the user on the eMail server. This specification, too, consists of the fully qualified server name and the login name of the user on the eMail Server. The names of these meta-folders ("SuSE GmbH IMAP Folder" and "personal IMAP folder") are arbitrary, but should reflect the actual folders on the SuSE Linux eMail Server.
rsh-open-timeout=0 # Time limit for Pine to set up an rsh connection to the eMail # server. Not needed in this configuration, so disabled by setting # it to 0.
disable-these-authenticators=CRAM-MD5 # List of authentication methods to disable. # In this case, CRAM-MD5
File 9.5.1: Configuration File .pinerc
98
9.5
Configuration with Pine Version 4.33
Figure 9.14: Collection List: Entering the Password
Figure 9.15: Personal IMAP Folder
9.5.2 Configuring the LDAP Address Book If you want to access the SuSE Linux eMail Server’s global address book with Pine, another entry will need to be made in the file .pinerc for each user. To do this, open the file as described in Section 9.5.1 on page 97 and change the option as shown in the following example. Following this final modification in .pinerc, the SuSE Linux eMail Server ’s global address book can be selected with the arrow keys and pressing ←- , after entering ‘A’ in Pine’s main menu (see Figures 9.13 on page 97). A detailed search in the address book can be started by pressing Ctrl + T . See Figure 9.17 on the following page.
99
9
Configuring External Mail Applications
Figure 9.16: Incoming Mail Folder
ldap-servers=imapserver.suse.com:389 "/base=dc=suse, dc=de/nick= SuSE GmbH Nürnberg"
# # # # # # #
Specification of the LDAP server and the name by which the LDAP address book is managed in Pine (SuSE GmbH Nürnberg). The entries consist of the fully qualified server name (imapserver.suse.com), followed by the port number, and the BaseDN values defined during the installation of the eMail Server (dc=suse, dc=de). The entry ’nick=SuSE GmbH Nürnberg’ defines the name of the address book under which it should be listed in Pine.
File 9.5.2: Address Book Configuration in .pinerc
Figure 9.17: Advanced Search in Address Book
100
9.6
9.6
Outlook Express Version 5.x and 6.0 and Outlook 2000
Outlook Express Version 5.x and 6.0 and Outlook 2000
An assistant will guide you through the configuration of the Microsoft Mail applications Outlook Express and Outlook 2000, which behave almost identically in both versions. The diagrams depicted in the following section correspond to Outlook Express Version 6.0.
9.6.1
Configuring the IMAP Mail Client
After starting Outlook via the menu items ‘Tools’ → ‘Accounts’, open the configuration dialog for the Internet accounts managed by Outlook and, after clicking the ‘Add’ button, select ‘Mail’ to start the assistant. In Outlook, open the ‘File’ menu and select ‘Identities’ → ‘Add New Identity’. In the window that opens next, enter a name for your new identity and choose a password for it. Confirm the identity change by clicking on ‘Yes’. Outlook will now prompt you to enter the user name and, in the dialog field which follows, the e-mail address. In the ‘E-mail Server Names’ dialog, choose the uppermost field ‘IMAP’ and enter the name of your SuSE Linux eMail Server in the ‘Incoming mail server’ and ‘Outgoing mail server’ fields. See Figure 9.18.
Figure 9.18: E-Mail Server Names Complete the configuration by entering the login name of the user for the SuSE Linux eMail Server III mail account in the ‘Account name’ field in the ‘Internet Mail Logon’ screen that follows. For your password to be permanently saved by Outlook, highlight the checkbox ‘Remember password’ then enter the necessary information in the ‘Password’ field. Refer to Figure 9.19.
101
9
Configuring External Mail Applications
Figure 9.19: Internet E-Mail Login With Outlook 2000, after the ‘Internet Mail Logon’, continue to a dialog where you can select the type of Internet connection to the SuSE Linux eMail Server. The selection to make at this point depends on your network environment. Consult the SuSE Linux eMail Server administrator if you have difficulties. Click the ‘Next’ button after choosing the option right for you. After configuration is complete, a special indicator will notify you that all recently setup e-mail account folders are currently deactivated. You will then be asked if you want to view a list of these folders. If you answer ‘Yes’ here, ‘Show/Hide IMAP Folders’ will appear in the dialog, where the selected folders can be activated for Outlook. See also Figure 9.20 on the next page. If a subdirectory is not shown, select ‘Reset List’ in this dialog window to reload the list of existing folders. This dialog can also be accessed at time via the ‘Tools’ → ‘IMAP Folders’.
9.6.2
Configuring the LDAP Address Book
The SuSE Linux eMail Server LDAP address book can be used with Outlook. To configure it, select the entry ‘Tools’ → ‘Address Book’ after starting Outlook. Then select ‘Tools’ and ‘Accounts’ in the emerging window. See Figure 9.21 on the facing page. Select ‘Add’. Enter the name of your SuSE Linux eMail Server in the ‘Internet directory (LDAP) server’ field. Exit the assistant by continuing to click ‘Next’ until you get to ‘Finish’. In the list of available directory service accounts, only one new entry will exist for your SuSE Linux eMail Server. Highlight this and select ‘Properties’ to the right. Under the ‘Advanced’ tab, enter the LDAP BaseDN values into the ‘Search base’ field, which were de-
102
9.6
Outlook Express Version 5.x and 6.0 and Outlook 2000
Figure 9.20: Activating and Deactivating IMAP Folders
Figure 9.21: Internet Accounts fined during the installation of the server or obtained from the SuSE Linux eMail Server administrator. See Figure 9.22 on the next page. These settings will bring the configuration for accessing the LDAP address book to a close.
103
9
Configuring External Mail Applications
Figure 9.22: Extended Properties of your Directory Service Account
104
10
Arkeia Backup of the SuSE Linux eMail Server
10 Arkeia Backup of the SuSE Linux eMail Server The following chapter describes how to backup the SuSE Linux eMail Server with Knox Software’s Arkeia.
10.1
Arkeia by Knox Software
Arkeia is one of the most widespread and well-known Linux backup solutions. Ideal for company-wide use in heterogeneous networks, Arkeia is popular with many system administrators and has been tried and tested a thousand times over in many companies.
10.1.1
Licensing Conditions
Knox Software provides a free version of Arkeia. This has no time limitations (its use is not restricted to a limited period of time) and may be used commercially. The license is valid for one Linux server and two clients (Linux, Windows 95/98, or Windows NT Workstation) and allows you to save your data to a single SCSI tape drive. This means that your SuSE Linux eMail Server and two additional clients can be backed up via the SuSE Linux eMail Server.
10.1.2
Expanding Your Use of Arkeia
You can back up more than just the SuSE Linux eMail Server with Arkeia. For information about expanding the use of Arkeia in your company, contact
[email protected].
10.2
Backing Up the SuSE Linux eMail Server
Backing up the SuSE Linux eMail Server while it is running can lead to problems. To prevent this, it must be guaranteed that write accesses to the LDAP server is disabled when the backup procedure is running. In the scripts included with this product (described later), the OpenLDAP and IMAPD services are stopped before configuration files are backed up. Postfix will be notified when user mails are being backed up, so no user mails will be delivered during the backup. IMAP components are handled the same way. Backups should be made
105
10
Arkeia Backup of the SuSE Linux eMail Server
at night, because no one can work with the system during the backup. Incoming mail is accepted and delivered after the backup is complete. No mail is lost. Delivery is just delayed until the backup is complete. The SuSE Linux eMail Server backup takes place in two stages. First the configuration files and the LDAP database are backed up. In the second stage, the users mail is backed up. The scripts to stop and start e-mail services can be found under /usr/sbin/.
10.3
Installation
10.3.1
Preparation
A backup medium (such as the SCSI tape drive used in the following examples) is needed for backups with Knox Arkeia. In addition, Arkeia needs 15 MB of hard drive space and 1 MB per 100MB of data to backed up for catalog entries. It also needs 15 MB in a temporary directory during installation on your SuSE Linux eMail Server. Arkeia consists of 3 components: • a client • the server • the GUI The three packages are all included in the Arkeia rpm.
Note In the installation description, the placeholder NULL is used in place of the backup drive and backup medium streamer or tape. When installing, choose the type (manufacturer, name) of your backup drive or backup medium from the selection list.
10.3.2
Explanation of Concepts
In the following installation description, some specific concepts are mentioned that you need to understand. Tape Individual removable backup medium (tape). Tape Drive Backup drive. Drivepack The tape drive (or drives) for the backup. Tape Pool The total number of tapes needed for a backup. Savepack Directories and files to back up. NULL Virtual, not really existing. A NULL tape drive is, for example, a virtual
tape drive.
106
10.3
10.3.3
Installation
Backup Server Installation
If you install the Arkeia software, the SuSE Linux eMail Server will also be the backup server. Carry out the following steps to install the Arkeia packages: 1. Mount the CD-ROM drive with the command: earth: # mount /cdrom
2. Install the client package via a terminal window with the command: earth: # rpm -Uvh /cdrom/suse/pay2/arkeia.rpm
You will see the output: arkeia ########################################## Update /etc/rc.config
Arkeia is now installed on the server in the directory /usr/knox. After the installation, the daemon is started. For test purposes, query the status of this daemon by typing the command rcarkeia status when logged in as the user ‘root’. To start the backup server automatically when the computer is rebooted, set the variable START_ARKEIA in /etc/rc.config to yes.
10.3.4
Configuration
Arkeia has a graphical interface, so you will need the X Window System. Start this with the command startx. Run Arkeia from a terminal window, using the command ARKEIA. A “Welcome to Arkeia” window appears, as shown in Figure 10.1.
Figure 10.1: Arkeia Welcome Screen In the ‘Login’ field, enter root. Leave the password field empty. Never enter the root password of the computer. Set a password later as described in the online documentation. Press the green check mark at the bottom right to register. The Arkeia main menu will appear as illustrated in Figure 10.2 on the next page.
107
10
Arkeia Backup of the SuSE Linux eMail Server
Figure 10.2: Arkeia Main Menu
Note During the installation, the host name is written to the file /usr/knox/ admin.cfg. If Arkeia cannot be started, look there first to see if the computer name is correct and, if necessary, change it using a text editor. Save the file and restart the Arkeia daemon with the command rcarkeia restart. Now Arkeia can be started again with ARKEIA.
Five steps must now be carried out before your first backup is completed.
Step 1: Setting up the Tape Drive
In the navigation bar, select ‘Devices’ → ‘Drive Management’ or press the ‘Drives Management’ button in the toolbar. See Figure 10.3).
Figure 10.3: Arkeia Drives Management Button In the ‘Drives Management’ menu click ‘NEW’. Fill out the fields as shown in Figure 10.4 on the next page.
108
10.3
Installation
Figure 10.4: Arkeia Drives Management Window
Caution Instead of ‘Type:’ NULL as shown in the screen shot, enter the type of your single SCSI tape drive (AIT, DLT, DAT, etc.). In the ‘Rewind device’ field, enter the correct device connection, such as /dev/st0, instead of /dev/null. To create the drive, confirm this with the green check mark in the status bar.
Click again on the check mark to leave the menu.
Step 2: Setting up a Drivepack
In the navigation bar, select ‘Devices’ → ‘Drivepacks’ or click the ‘Drivepacks’ button in the toolbar. See Figure 10.5.
Figure 10.5: Arkeia Drivespack Button Click ‘NEW’ and fill out the fields as shown in Figure 10.6 on the next page. Choose a name for your tape drive, for example, DAT PACK. Confirm this by clicking the green check mark in the status bar to create the drivepack. Click the check mark again to leave the menu.
109
10
Arkeia Backup of the SuSE Linux eMail Server
Figure 10.6: Arkeia Drivepacks Window Step 3: Setting up a Tape Pool
In the navigation bar, select ‘Tapes’ → ‘Pools Management’ or click the ‘Pools Management’ button in the toolbar. See Figure 10.7).
Figure 10.7: Arkeia Pools Management Button Click ‘NEW’ and enter a name, for example, DAT POOL. Add a short description of the tapes in the comment, for example, “Tapes for eMail Server”. See Figure 10.8 on the next page). To create the tape pool, click the green check mark in the status bar. Step 4: Setting up a Tape
The new tape pool is now created and is shown in the list. With a double click on the new tape pool ‘DAT POOL’, reach the tape menu. Click ‘NEW’ and fill out the fields as shown in Figure 10.9 on the facing page. ‘Last number’, specify how many tapes are needed to back up the required data.
Caution Instead of NULL in the ‘Type’ field, enter the type of tapes to use.
110
10.3
Installation
Figure 10.8: Arkeia Pool Creation
Figure 10.9: Arkeia Create Tapes Window To confirm your selection, click the green check mark in the status bar to create the tape pool. Click the check mark twice to return to the main menu. Step 5: Setting up the Savepacks
Two savepacks are now set up: one to back up the configuration files and the second to back up user mail (Accounts). In the navigation bar, select ‘Backup’ → ‘Savepacks’ or click the ‘Savepacks’ button in the toolbar. See Figure 10.10.
Figure 10.10: Arkeia Savepacks Button Savepack for configuration files:
111
10
Arkeia Backup of the SuSE Linux eMail Server
Click ‘NEW’ and enter a name, for example, config_savepack. Confirm this with the green check mark. The savepack config_savepack is now created and appears in a list. Double click to change the settings. In the ‘Command before savepack’ field, enter the computer and the path of the script that suppresses writing to the configuration files. The ‘Backup savepack if command fails’ field, as seen in Figure 10.11, must not be selected.
Figure 10.11: Arkeia Savepack Configuration In the ‘Command after savepack’ field, enter the computer and the path of the script that reenables writing to the configuration files. The field ‘Execute if savepack backup fails’ should be selected so the server starts working again if the backup was not ended properly. These are the scripts for the configuration savepack: localhost:/usr/sbin/pre_config_bak.sh (before the backup) localhost:/usr/sbin/post_config_bak.sh (after the backup)
Confirm this setting with the green check mark. Click the ‘Navigation’ button at the bottom of the toolbar. See Fig 10.12.
Figure 10.12: Arkeia Navigation Button In the ‘Navigation’ menu, find the SuSE Linux eMail Server icon. Click it twice. See Figure 10.13 on the facing page. You should now be in the file and directory selection dialog as shown in Figure 10.14 on the next page. Choose the following files and directories:
112
10.3
Installation
Figure 10.13: Arkeia Navigator /var/lib/ldap (LDAP database) /etc/ (general configuration files) /var/named (if using a name server)
Figure 10.14: Arkeia Directory Selection Confirm this with the green check mark. Savepack for User Mails: Click ‘NEW’ in the the Savepack Management menu and enter a name, for example, mail_savepack. See Figure 10.15 on the following page. Confirm this with the green check mark. The savepack mail_savepack is now created and appears in the list. Double click to change the settings. The ‘Command before savepack’ field must contain the computer and the path of the script that stops the SuSE Linux eMail Server. The field ‘Backup
113
10
Arkeia Backup of the SuSE Linux eMail Server
Figure 10.15: Arkeia Savepacks Management Window savepack if command fails’ may not be selected, as is shown in Figure 10.16
on the next page. The field ‘Command after savepack’ must contain the computer and the path of the script that returns the SuSE Linux eMail Server to its normal condition. The field ‘Execute if savepack backup fails’ should be selected so the server starts working again if the backup was not ended properly. The scripts for the mail savepack are: localhost:/usr/sbin/pre_data_bak.sh (before the backup) localhost:/usr/sbin/post_data_bak.sh (after the backup) Confirm the settings with the green check mark. Click the ‘Navigation’ button at the bottom of the toolbar. See Figure 10.17 on the facing page. Choose these directories for the mail_savepack: /var/spool/imap (control information) /var/imap (user mail) To leave the file and directory selection, click the green check mark. Confirm the windows with a green check mark until you return to the main menu. Step 6: Performing the Backup Interactive Backup
All the settings have now been made to start the first backup. It makes sense to label the individual tapes. Insert a new, empty tape into the tape drive. In the navigation bar, select ‘Backup’ → ‘Interactive Backup’ or press the ‘Interactive Backup’ button. See Figure 10.18 on page 116. Start with the config_savepack. It is already set up by default. Click the green check mark to start the backup. The data to save is written to tape. The
114
10.3
Installation
Figure 10.16: Arkeia Mail Savepack Settings
Figure 10.17: Arkeia Navigation Button Speedometer shows everything is running correctly (see Figure 10.19 on the following page). The light on the tape drive flashes when the tape is being written. Check if everything has run correctly in the ‘Log window’ in the bottom of the menu. Errors are highlighted with a red box. If no errors have occurred, leave the backup menu by clicking on the green check mark. In the navigation bar, select ‘Backup’ → ‘Interactive Backup’. This time, instead of config_savepack, enter ‘mail_savepack’. Proceed in the same way as with the first savepack. As soon as both savepacks have been correctly backed up, remove the tape and store it in a safe place. If there are problems or if you have questions, the extensive Arkeia documentation is available. Find the pdf files, which can be read with Acrobat Reader, in the directory /usr/share/doc/packages/arkeia. Time-controlled Backup
To have backups controlled automatically, do not choose the ‘Interactive Backup’ button. Choose the ‘Periodic Backup’ one. Click ‘NEW’ then enter a name for the periodic backup. At first, you will see the basic settings as shown in Figure 10.20 on page 117. • The status field shows either active or inactive.
115
10
Arkeia Backup of the SuSE Linux eMail Server
Figure 10.18: Arkeia Interactive Backup Button
Figure 10.19: Arkeia Speedometer • The ‘Use emails’ or ‘Don’t use emails’ field specifies if you want be informed by e-mail of a successful backup after the backup has been completed. In the ‘Savepack’ window, specify which savepack to periodically back up. With ‘Type’, choose to back up everything new or incrementally — only the differences from an old backup are saved. With ‘Pool’, choose the tape pool. In addition, specify if tapes that have been started can continue to be used (‘Complete existing tapes’) or if new tapes should always be used (‘Always use a new tape’). Via the ‘Validity’ field, define a period of time during which the tape cannot be overwritten with a new backup. Only when this period has expired can the tape be used again. Under ‘Periodicity’, adjust at what intervals backups should be performed. For a backup period, a number of levels can be defined. For this, click on ‘Add Level’. The following example shows a useful backup configuration with two levels: 1. For Level 1, select ‘Total Backup’. Under ‘Validity’, enter the value 3 month(s). Under ‘Periodicity’, 1 week(s). This means that a complete backup is carried out once per week. 2.
116
10.3
Installation
Figure 10.20: Arkeia Periodic Backup 2. Now change to Level 2. Under ‘Based on’, enter the name of the periodic backup and the output level (in our example, level 1). Select ‘Incremental Backup’. Under ‘Validity’, enter 1 month(s) and under ‘Periodicity’, 1 Day. With this, an incremental backup is performed once per day. 3. The ‘Schedule Viewer’ shows the schedule of the automatic backup (see Figure 10.21 on the following page).
10.3.5
Short Description
1. Start Arkeia by entering ARKEIA & 2. Log in (Login: root, leave password field empty) 3. Creating a drive a) Navigation bar: ‘Devices’ → ‘Drives Management’ b) Click ‘NEW’ c) Name: DAT DRIVE d) Type: the model of the SCSI single drive e) Rewind device: device driver (e.g., /dev/st0) f) Confirm this with the green check mark.
117
10
Arkeia Backup of the SuSE Linux eMail Server
Figure 10.21: Arkeia Schedule Viewer 4. Setting up a drivepack a) Navigation bar: ‘Devices’ → ‘Drivepacks’ b) Click ‘NEW’ c) Name: DAT PACK d) List of drives: Select DAT DRIVE e) Confirm this twice with the green check mark 5. Setting up a tape pool a) Navigation bar: ‘Tapes’ → ‘Pools Management’ b) Click ‘NEW’ c) Name: DAT POOL d) Comment: Tapes for eMail Server e) Confirm this with the green check mark 6. Setting up a tape a) Pools Management Menu: double click ‘DAT POOL’ b) Click ‘NEW’
118
10.3
Installation
c) Name: EMAIL TAPES d) First Number: 1 e) Last Number: number of your tapes f) Type: type of your tapes g) Confirm this twice with the green check mark 7. Setting up a savepack a) Savepack for configuration files i. Navigation bar: ‘Backup’ → ‘Savepacks’ ii. Click ‘NEW’ iii. Name: config_savepack iv. Insert the savepack and press the check mark v. Double click the new savepack vi. Command before savepack: localhost:/usr/sbin/pre_config_ bak.sh
vii. Command after savepack: localhost:/usr/sbin/post_config_ viii. ix. x. xi.
bak.sh Select ‘Execute if savepack backup fails’
Click the navigation button Select files and directories: /var/lib/ldap; /etc; /var/named Confirm this with the green check mark
b) Savepack for user mail i. Click ‘NEW’ ii. Name: mail_savepack iii. Insert the savepack then press the check mark iv. Double click the new savepack v. Command before savepack: localhost:/usr/sbin/pre_data_bak. sh
vi. Command after savepack: localhost:/usr/sbin/post_data_bak. sh
vii. viii. ix. x.
Select ‘Execute if savepack backup fails’ Click the navigation button Select files and directories: /var/spool/imap; /var/imap Confirm this with the green check mark
8. Conducting the backup a) Insert an empty tape b) Backing up the configuration files savepack i. Navigation bar: ‘Backup’ → ‘Interactive backup’ ii. Selection of savepack: config_savepack iii. Click the green check mark iv. Check the log window v. Confirm this with the green check mark
119
10
Arkeia Backup of the SuSE Linux eMail Server
c) Backing up the user mail savepack i. ii. iii. iv. v.
Navigation bar: ‘Backup’ → ‘Interactive backup’ Select savepack: mail_savepack Click the green check mark Check the log window The backup is now completed
d) Remove the tape from the tape drive
10.4
Recovery
The SuSE Linux eMail Server can be restored relatively easily with the help of Knox Arkeia. There are various types of recovery. On the one hand, there is the complete recovery, if files were damaged or deleted through hardware defects or errors in system administration. Here, either the complete files (configuration and user mail) or just the configuration files or user mail can be restored. On the other hand, there is the partial recovery if users want to recover mail that was accidentally deleted.
10.4.1
General Procedure During Recovery
During the recovery process, the SuSE Linux eMail Server should not be in operation. For this reason, run the script /usr/sbin/pre_data_bak.sh before a recovery. After a recovery, start the server again with the script /usr/sbin/ pre_data_bak.sh.
10.4.2
Complete Recovery
Open a terminal window and start the script pre_data_bak.sh in the directory /usr/sbin/ to stop the SuSE Linux eMail Server. In the shell, enter the following command as the user ‘root’: usr/sbin/pre_data_bak.sh. Click, in the navigation bar, ‘Recovery’ → ‘Restoration’. You will now be in the Recovery main menu. At the bottom of the status bar, select the ‘Navigation’ button. You are now in the database navigation menu. In the first two lines, choose which savepacks are the correct ones for your recovery. To access all data from the last backup, choose the last entry of config_savepack in the first line and the last entry of mail_savepack in the second line. Before you make your settings, see Figure 10.22 on the next page. To reach the file selection, click twice on the computer icon. To restore a complete backup, select all the directories displayed, as shown in Figure 10.23 on page 122. Confirm this with the green check mark to see an overview of all selected directories, as shown in Figure 10.24 on page 123.
120
10.4
Recovery
Figure 10.22: Arkeia Database Navigator Click the check mark. The required tape is displayed. Insert this into the tape drive and click the green check mark. The recovery will be conducted. Check in the log window to see if everything has been performed correctly. Open a terminal window and start the script post_data_bak.sh in the directory /usr/ sbin/ to restart the SuSE Linux eMail Server. As the user ‘root’, enter the following command in the shell: usr/sbin/post_data_bak.sh
10.4.3
Partial Recovery
To restore individual user accounts, it is not necessary to stop the entire eMail Server. All users other than those involved can continue working with the server. It must be guaranteed, however, that the user concerned may not access the server, so he must be deactivated in the SuSE Linux eMail Server Admin interface. To deactivate a single user select, in the SuSE Linux eMail Server Admin interface, under the item ‘User’, the user whose account will be restored. On the right, select the action ‘Deactivate’ and confirm the following window with ‘Yes’. The user is now deactivated and can no longer access his account. Proceed as far as the file selection, as described in Section 10.4.2 on the facing page. To restore mails of an individual user, select the mail data and the appropriate control file of the user. The files are stored according to the following pattern: /var/spool/imap/user/ /var/imap/user//.sub /var/imap/quota//user.
For the user in our example ‘are’, these are the following files and directories (see Figure 10.25 on page 123): /var/spool/imap/user/are /var/imap/user/a/are.sub
121
10
Arkeia Backup of the SuSE Linux eMail Server
Figure 10.23: Arkeia Directory Overview /var/imap/quota/a/user.are
Select all the required data for the user and click the check mark. You will now see an overview of all files. Click the check mark to start the recovery. Insert the requested tape into the tape drive and click the check mark. The recovery will now be performed. Check the log window to see that everything has been correctly completed. Open a terminal window and change to the user ‘cyrus’. For a complete reconstruction of the account, use the command: su - cyrus reconstruct -r user.
The output appears similar to our example as shown in Figure 10.26 on the facing page. The account is now completely restored. Reactivate the user in the admin interface of the SuSE Linux eMail Server.
Note More information on Arkeia can be found on the CD in the directory /usr/ share/doc/packages/arkeia/. The “Advanced Manual” advmanual. pdf and the “Administator Manual” admmanual.pdf will probably be of particular interest to you. Read these files with the Acrobat Reader by entering acroread advmanual.pdf.
122
10.4
Recovery
Figure 10.24: Arkeia Restoration Window
Figure 10.25: Database Navigator Directory Overview
Figure 10.26: Console Output of the Reconstruction
123
10
124
Arkeia Backup of the SuSE Linux eMail Server
11
Glossary
11 Glossary
alias The login name (UID) is essentially the local segment of the user’s e-mail address. A corresponding alias must be used for longer e-mail addresses or addresses with special characters (e.g., a period ‘.’). For example, ‘user’ and ‘a1234’ are permissable user names and firstname.lastname@ company.com is a possible alias e-mail address. CA (Certification Authority) A certification authority is authorized for issuing certificates for servers and clients. The SuSE Linux eMail Server features a CA. Certificates help verify the identity of the server or client. They are used, for example, to guarantee secure access to the server for a client located outside of the local network, if the client can prove his authenticity. For the client to authenticate the server, the certificate must be saved by the client. Otherwise, some clients will doubt the server’s validity or even completely refuse to set up the connection. certificate A certificate is a user’s “ID card,” which allows use of certain services on the SuSE Linux eMail Server. The user certificate is stored locally on the user’s client and should not be accessible to other users. Only users with certificates could be allowed to set up a secure connection to the server. Dial on Demand If SuSE Linux eMail Server is not connected to the Internet over a leased line, it is typically implemented “dial on demand”. This is used by the eMail Server to automatically set up a connection to the provider if mail is waiting in the queue to be sent or if Fetch Mail should retrieve mail from the provider. DNS (Domain Name Service) see name server Fetch Mail The Fetch Mail function is used for retrieving e-mails from a remote POP3 or IMAP server. This is normally only necessary if the SuSE Linux eMail Server does not have an official IP address reachable by the Internet or if it is not recognized by remote name servers by way of an mx entry. For experts: Fetch Mail is a special SuSE Linux eMail Server function and is not the same as the package fetchmail, although it has the same name. Fetch Mail manages the multidrop procedure. See also multidrop!
125
11
Glossary
filter A filter can be used to limit a listing. In the simplest scenario, the filter entry is ‘*’. * is a universal placeholder for one or more arbitrary characters. The filter entry sch*, for example, lists all names beginning with “sch”. The filter *sch* lists all names containing “sch”. Entering only * lists all names. folders A folder is essentially a mailbox where e-mails are stored. Allowing several users various permissions for different folders is made possible by assigning permissions to the folder itself (such as reading, writing, and deleting). Common folders can be created by the mail administrator and given respective access permissions. Each user has a “personal” folder. Generally, this is the INBOX folder with its subfolders. Users can even transform their INBOX to a common folder simply by assigning permissions (for example, read-only access for another user). However, it makes more sense to add another subfolder to the INBOX (e.g., INBOX.public, which often already exists) then share it with other users as a common folder. groups A group includes several users who obtain the same permissions or properties for any particular reason. A user belongs to at least one group. The default group name on the SuSE Linux eMail Server is ‘users’. This group is the primary group. Every user can also belong to other groups, known as secondary groups. This way, users from several groups can share different permissions to various files in the Unix world. Example: in your company (company.com), some coworkers belong to the sales department and others to the IT department. The groups ‘sales’ and ‘technology’ can be created and one of them assigned to your coworkers as a secondary group. A single user can exist in both groups. A mailing list can also be implemented using the ‘Direct mail delivery to groups’ function. To do this, create a folder (with mail reception) and call it ‘sales’. Now, in this folder, after setting up the ‘Direct mail delivery’ to the group ‘sales’, all group members will receive a copy of e-mails sent to
[email protected]. At the same time, e-mails are also stored in the sales folder, meaning that the administrator or a user with the right permissions should empty the folder periodically. IMAP (Internet Message Access Protocol) IMAP allows clients to access eMail Server folders. The advantage of this, as opposed to POP, is that many clients can access one mail folder at the same time. The data (e-mail) is still stored centrally on the server. This makes the use of common folders possible. The TCP/IP connection via IMAP takes place over port 143. Further specifications can be found in RFC 2060. LDAP (Lightweight Directory Access Protocol) LDAP is used to access the database that the SuSE Linux eMail Server uses for storing practically all types of user information. External clients can contact the server over port 389. BaseDN (Base Distinguished Name) is the
126
11
Glossary
“highest level” of the hierarchical directory structure in this process. Unless the administrator has not specified otherwise, this can be, for example, dc=company, dc=com for the domain company.com. More in-depth information can be found at http://www.openldap.org/ mailing list see groups multidrop A multidrop mailbox is a typical POP3 account where the e-mail of an entire domain is stored. Mail must be retrieved from there by way of POP3 and distributed on the target system. Information has been lost, because SMTP transport has already been taken care of by the provider. The most important data here is the “envelope recipient” address. An e-mail consists of an envelope, a header, and a body. The envelope is generated during the transfer from MTA (Mail Transfer Agent) to MTA. This is comparable to postal stamps on letters. Once the mail is deposited, the envelope disappears. This does not usually cause any problems, since mail is sent from one user to another. The recipient in the envelope corresponds to the recipient in the mail header (“To:”). However, if users are subscribed to a mailing list, for example, the target address would read To:
[email protected] for each user who receives this e-mail. The actual recipient is conferred during transport by the SMTP command RCPT TO. As soon as the e-mail has reached the target server, this information is lost. Not irrevocably lost, of course, because otherwise no software could to retrieve e-mail from the multidrop mailboxes at all. The target address leaves its “trail” in the form of “Received:” lines in the mail header. The actual recipient can be extracted from these lines. Unfortunately, this information is not standardized — every MTA writes these lines differently. This could lead to mail delivery errors, so multidrop mailboxes should be avoided whenever possible. name server (DNS) The purpose of a name server is to resolve host names into IP addresses and vice versa. The SuSE Linux eMail Server has its own name service for managing its domains. You can also leave this task up to a name server located on your network. The SuSE Linux eMail Server uses BIND8, the configuration files for which are stored under /var/named/ and in /etc/named.conf. These files are automatically created when installing the SuSE Linux eMail Server and when virtual domains are added (‘Export’). To make permanent changes, use the template file /etc/named.conf.in. Only for experts: note that flawed entries could crash your eMail Server! If your SuSE Linux eMail Server is the official delegate for your name service in the Internet as well, you will need at least one other name server and should enter another mail server as “backup mail server”. Additional NS (Name Service) and MX (MaileXchanger) entries are required to do this. Click the main menu item ‘System’ then ‘LDAP Browser’. Now click ‘Start search’. Afterwards, click the cross in front of ‘o=DNS’ then the link with the name ‘relativeDomainName=@’. Make changes in the screen that follows. As you can see, entries for nSRecord and mXRecord already exist. To insert an
127
11
Glossary
additional MX entry, write mXRecord in the smaller entry field under ‘New’ and the priority and name of the mail server in the long field next to it. Proceed with the the NS record accordingly. To make the changes effective, click in the main menu on ‘Virt. users’, then on ‘Virt. domains’, and, finally, on ‘Export’. POP3 (Post Office Protocol) POP3’s function is to retrieve e-mails from a mail server set up for this purpose. The respective TCP/IP connection to the server is set up over port 110 and is controlled by simple data transfer commands (e.g., HELO, USER, and PASS). The default configuration of the SuSE Linux eMail Server is for POP3, allowing clients to retrieve e-mails using this protocol. Also, Fetch Mail can use POP3 to retrieve e-mails from another server (such as from the provider). The description of this Internet standard can be found in RFC939. Postfix Postfix is an MTA (Mail Transfer Agent). Complete documentation on Postfix can be found at http://www.postfix.org/, including a question and answer list (FAQ). For experts: for security reasons, Postfix components on the SuSE Linux eMail Server run in a changeroot environment under /var/spool/postfix/. Whenever changes are made manually in configuration files under /etc/, these elements will have to be entered in /var/spool/postfix/etc/. Run SuSEconfig and it will take care of this for you. quotas Memory available for users can be limited with the help of quotas. This is recommended, because hard disk space can become scarce in the face of a growing user pool and an increasing number of stored e-mails. Example: you have created 200 users who consume an average of 5 MB space. The user’s e-mails alone already take up 1000 MB of the hard disk. The default quota is 10 MB. Hard disk requirements then reach a maximum of 2000 MB. relay host If you are not able to send e-mail “directly” to the Internet, specify a relay host. This is a machine of your provider, which receives and forwards e-mail destined for remote addresses via SMTP. A relay host usually needs to be specified whenever a dial-up Internet connection is used — the server cannot have a static IP address. Your provider can provide information about what relay host to access. RFC (Requests For Comments) RFCs describe protocols and somewhat define the default as well. A list of all RFCs can be found at http://the.rfceditor.org/. SASL (Simple Authentication and Security Layer) This function serves to authenticate mail clients for the server. More information can be found in the man page man sasl as well as RFC 2222.
128
11
Glossary
SIEVE SIEVE is a “standardized” language for creating mail filters. It is not necessary to understand the syntax of this language. That is taken care of by the configuration front-end. For experts: with the SIEVE editor, generate your own filter scripts or add already existing ones. A description of the script language SIEVE can be found in RFC 3028 or at http: //www.cyrusoft.com/sieve/. SMTP Simple Mail Transport Protocol E-mails are sent to the e-mail server via SMTP. Likewise, the eMail Server uses SMTP to send mail to other mail servers in the Internet (e.g., to a relay host). A TCP/IP connection over port 25 is used for this purpose. A more detailed description of SMTP can be found in RFC 2821. SSL (Secure Socket Layer) see TLS TLS (Transport Layer Security) TLS encrypts data to transfer. A relevant description can be found in RFC 2246. UID (User Identification) This is the login name with which the user logs into the system. This can be eight characters long, may not contain any special characters or spaces, can only consist of lowercase letters, and must be unique for each user. Abnormal e-mail addresses must be represented by aliases. Example user names are user and a1234. The login name is the same as the e-mail address, in this case
[email protected] and
[email protected].
129
11
130
Glossary
12
YaST and SuSE Linux License Terms
12 YaST and SuSE Linux License Terms YaST Copyright (c) 1995-2001 SuSE GmbH, Nürnberg (Germany) The object of this license is the YaST (Yet another Setup Tool) program, the name “YaST”, SuSE Linux the Linux Distribution of SuSE GmbH, all other programs of SuSE GmbH under this license, all programs derived from YaST or another program under this license, and all works or names derived in full or in part thereof together with the use, application, archiving, reproduction, and distribution of a program under this license, all programs derived from a program under this license, and all works derived in full or in part thereof. The YaST program, any other program under this license, and all sources are the intellectual property of SuSE GmbH within the meaning of the Copyright Law. The name YaST is a registered trademark of SuSE GmbH. In the following, SuSE GmbH is the licensor and every user or processor of YaST or any other program under this license, works derived in full or in part thereof, together with every person who reproduces, distributes, or archives YaST, SuSE Linux, or any other program under this license is the licensee of SuSE GmbH. The following license terms are recognized as a result of the processing, use, application, archiving, reproduction, and dissemination of the programs under this license. Only this license gives the Licensee the right to use, reproduce, to distribute, or to amend YaST, any other program under this license, or works derived thereof. These actions are forbidden by the copyright act, if this license is not recognized. If this license is recognized and complied with in full, it is also valid even without the written consent of the Licensee. 1. Usage YaST, SuSE Linux, and any other program under this license may be used for personal and commercial purposes if the copyright and license terms of the installed packages and programs are observed. The use of YaST or any other program under this license, even if a modified version is used, does NOT exempt in particular the Licensee from the duty to take due care with regard to the license terms of the packages or programs installed through YaST, any other program under this license, or works based on it. 2. Processing All programs derived from YaST, any other program under this license and all works derived thereof, in full or parts thereof, are to be provided on the opening screen with the clear information “Modified Version”. Moreover, the operator must give his name on the opening screen, stating that SuSE GmbH is not providing any support for the “Modified Version” and is excluded from
131
12
YaST and SuSE Linux License Terms
any liability whatsoever. Every amendment to the sources not conducted by SuSE GmbH are deemed a “Modified Version”. The Licensee is entitled to change his copy from the sources of YaST or any other program under this license, whereby a work based on one of these programs is created, provided that the following conditions are satisfied. a) Every amendment must have a note in the source with date and operator. The amended sources must be made available for the user in accordance with section 3) together with the unamended license. b) The Licensee is obliged to make all work distributed by him derived as a whole or in part from a program under this license or parts thereof to third parties as a whole under the terms of this license without royalties. c) The amendment of this license by a Licensee, even in part, is forbidden. SuSE GmbH reserves the right to accept parts or all amendments of a modified version of any program under this license into the official version of the concerned program free of charge. The Licensee has no bearing on this. 3. Dissemination It is forbidden to reproduce or distribute data carriers reproduced without authorization for payment without the prior written consent of SuSE GmbH or SuSE Linux. Distribution of programs under this license, their sources, whether amended or unamended in full or in part thereof, and the works derived thereof for a charge require the prior written consent of SuSE GmbH. All programs derived from programs under this license and all works derived thereof as a whole or parts thereof may only be disseminated with the amended sources and this license in accordance with 2b). Making YaST, any other program under this license, or works derived thereof available free of charge together with SuSE Linux on FTP Servers and mailboxes is permitted if the licenses on the software are observed. 4. Guarantee No guarantee whatsover is given for YaST, any other program under this license works derived thereof, and SuSE Linux. The SuSE GmbH guarantee only covers fault-free data carriers. SuSE GmbH will provide every program under this license and SuSE Linux AS IS, without any guarantee whatever that it is fit for a specific purpose or use. In particular, SuSE is not liable for lost profit, savings not made, or damages from the claims lodged by third parties against the Licensee. SuSE GmbH is not liable for other direct or indirect consequential losses, in particular not for the loss or production of recorded data. The observance of the respective licenses and copyrights of the installed software is incumbent solely upon the user of the relevant program and SuSE Linux.
132
12
YaST and SuSE Linux License Terms
5. Rights No other rights to YaST, any other program under this license, or to SuSE Linux are granted other than negotiated in this license. An infringement against this license automatically terminates the rights of the Licensee. However, the right of third parties who have received copies or rights under this license from the Licensee are not terminated as long as all parts of his license are recognized and observed. If the Licensee is subject to conditions or obligations as a result of a court judgement, patent terms, license terms, or another reason, and these conditions or obligations contradict this license as a whole or in part, the Licensee shall only be exempted in full or in part from this license and its terms with the express prior written consent of SuSE. SuSE is entitled to withhold its consent without giving reasons. 6. Additional restrictions If the distribution or use of YaST, any other program under this license, and SuSE Linux or parts of SuSE Linux is restricted in a state either by patents or by interfaces protected by copyright, SuSE GmbH can specify an explicit geographic restriction of the distribution of the concerned program or parts of SuSE Linux, in which these states are fully or partially excluded from distribution. In such a case, this license includes the whole or partial restriction as if it were written in this license.
133
12
134
YaST and SuSE Linux License Terms
Index
Index
A administering . . . . . . . . . . . 43–59 administration page . . . . . . . 43 cyrus . . . . . . . . . . . . . . . . . . . . 44 disk quotas . . . . . . . . . . . . . . 45 folders . . . . . . . . . . . . . . . 48–50 groups . . . . . . . . . . . . . . . 47–48 resources . . . . . . . . . . . . . . . . 58 users . . . . . . . . . . . . . . . . . 44–47 administrator e-mailing all users . . . . . . . . 58 information . . . . . . . . . . . . . . 47 password . . . . . . . . . . . . . 42, 46 alias . . . . . . . . . . . . . . . . . . . . . 125 Apache SSL . . . . . . . . . . . . . . . . . . . . . 58 Arkeia . . . . . . . . . . . . . . . 105–122 help . . . . . . . . . . . . . . . . . . . . 122 installing . . . . . . . . . . . . . . . 106 interactive backup . . . . . . . 114 password . . . . . . . . . . . . . . . 107 periodic backup . . . . . . . . . 115 recovery . . . . . . . . . . . 120–122 requirements . . . . . . . . . . . . 106 starting . . . . . . . . . . . . . . . . . 107
mounting . . . . . . . . . . . . . . . 107 CD-ROM drives ATAPI . . . . . . . . . . . . . . . . . . 15 EIDE . . . . . . . . . . . . . . . . . . . 15 SCSI . . . . . . . . . . . . . . . . . . . . 16 certificate . . . . . . . . . . . . . . . . . 125 certificates . . . . . . . . . . . . . . . . . 57 CAs . . . . . . . . . . . . . . . . . . . . . 57 downloading . . . . . . . . . . . . . 61 configuration files .pinerc . . . . . . . . . . . . . . . 97, 99 admin.cfg . . . . . . . . . . . . . . 108 named.conf . . . . . . . 12, 13, 52 named.conf.in . . . . . . . . . . . . 52 rc.config . . . . . . . . . . . . . . . 107 configuring eMail Server . . . . . 41–42, see administering IMAP . . . . . . . . . . . . . . . . . . . 56 mail applications . . . . . . . . . 87 mail system . . . . . . . . . . . . . . 53 network . . . . . . . . . . . . . . . . . 40 cyrus . . . . . . . . . . . . . . . . . . . . . . 47 administering the eMail Server 44 password . . . . . . . . . . . . . . . . 42
B backup . . . . . . . . . . . . . . . . . . . . . 8 restoring . . . . . . . . . . . . . . . . . . 9 backup server eMail server as . . . . . . . . . . 107 backups Arkeia . . . . . . . . . . . . . . . . . 105 BIOS setup . . . . . . . . . . . . . . . . 15, 16 booting CD-ROM, from . . . . . . . . . . 15 kernel parameters . . . . . . . . 17 LILO . . . . . . . . . . . . . . . . . . . 30
C CA . . . . . . . . . . . . . . . . . . . . . . 125 CD-ROM
D DHCP eMail Server and . . . . . . . . . 10 Dial on Demand . . . . . . . . . . . 125 DNS . . . . see name servers, 125 server . . . . . . . . . . . . . . . . . . . 42 domains virtual . . . . . . . . . . . . . . . 51–52 creating . . . . . . . . . . . . . . . . . . 51
IMAP . . . . . . . . . . . . . . . . . . . 56 protocol . . . . . . . . . . . . . . . . . 55 retrieving . . . . . . . . . . . . . . . . 55
F Fetch Mail . . . . . . . . . . . . . . . . 125 fetchmail . . . . . . . . . . . . . . 125 filter . . . . . . . . . . . . . . . . . . . . . 126 folders . . . . . . . . . . . . 48–50, 126 creating . . . . . . . . . . . . . . 49, 62 editing . . . . . . . . . . . . . . . . . . 50 mailing list . . . . . . . . . . . . . . 48 mailing lists . . . . . . . . . . . . . 50 permissions . . . . . . . . . . . . . . 63 properties . . . . . . . . . . . . . . . . 63 rights . . . . . . . . . . . . . . . . . . . 49 shared . . . . . . . . . . . . . . . . . . . 48 user . . . . . . . . . . . . . . . . . . . . . 62
G groups . . . . . . . . . . . . . 47–48, 126 creating . . . . . . . . . . . . . . . . . 47 editing . . . . . . . . . . . . . . . . . . 48 folders . . . . . . . . . . . . . . . 48, 49 resources . . . . . . . . . . . . . . . . 59
H hard disks preparing . . . . . . . . . . . . . . . . 19 help Arkeia . . . . . . . . . . . . . . . . . 122 SKYRiXgreen . . . . . . . . . . . 69 support . . . . . . . . . . . . . . . . . 3–6 YaST2 . . . . . . . . . . . . . . . . . . 17 host names selecting . . . . . . . . . . . . . . . . . . 7
I E e-mail aliases . . . . . . . . . . . . . . . 44, 46 all users . . . . . . . . . . . . . . . . . 58 automatic replies . . . . . . . . . 66 filtering . . . . . . . . . . . . . . 64–66
IMAP . . . . . . . . . . . . . . . . 56, 126 folders . . . . . . . . . . . . . . . . . . 62 installing Arkeia . . . . . . . . . . . . . . . . . 106 DHCP and . . . . . . . . . . . . . . . 10 preparing for . . . . . . . . . . . . . . 7
135
Index
configuring . . . . . . . . . . . . . . 40 layouts . . . . . . . . . . . . . . . 11–14 topology . . . . . . . . . . . . . 11–14
YaST2 and . . . . . . . . . . . 15–40
K keyboard YaST2 . . . . . . . . . . . . . . . . . . KMail . . . . . . . . . . . . . . . . . . . . . starting . . . . . . . . . . . . . . . . . . version . . . . . . . . . . . . . . . . . .
19 95 95 95
O Outlook . . . . . . . . . . . . . . 101–103 IMAP . . . . . . . . . . . . . 101–102 LDAP . . . . . . . . . . . . . 102–103
deleting . . . . . . . . . . . . . . . . . 59 groups . . . . . . . . . . . . . . . . . . 59 managing . . . . . . . . . . . . 58–59 RFC . . . . . . . . . . . . . . . . . . . . . 128 root administrator and . . . . . . . . . 42 password . . . . . . . . . . . . . . . . 36
S L
P
language changing . . . . . . . . . . . . . . . . 43 languages changing . . . . . . . . . . . . . . . . 61 selecting . . . . . . . . . . . . . . . . . 18 LDAP . . . . . . . . . . . . . . . . 58, 126 LILO . . . . . . . . . . . . . . . . . . 30–35 floppy . . . . . . . . . . . . . . . . . . . 32 multiple hard disks . . . . . . . 31 multiple OSs . . . . . . . . . . . . . 31 problems . . . . . . . . . . . . . . . . 35 Logical Volume Manager . . . see LVM login . . . . . . . . . . . . . . . . . . . . . . 42 administration page . . . . . . . 43 LVM . . . . . . . . . . . . . . . . . . 24–30 advantages . . . . . . . . . . . . . . . 25 configuring with YaST2 . . . 25
package
M mailadmin . . . . . . . . . . . . . . . . . 47 password . . . . . . . . . . . . . . . . 42 mailing list . . . . . . . . . . . . . . . 127 mailing lists folders as . . . . . . . . . . . . 48, 50 monitors configuring with YaST2 . . . 38 mouse YaST2 . . . . . . . . . . . . . . . . . . 18 Mozilla . . . . . . . . . . see Netscape Communicator multidrop . . . . . . . . . . . . . . . . . 127
quotas . . . . . . . . . . . . . . . . . . . . 128 assigning . . . . . . . . . . . . . . . . 45
SASL . . . . . . . . . . . . . . . . . . . . 128 scripts custom mail scripts . . . . . . . 67 port_config_bak.sh . . . . . . 112 post_data_bak.sh . . . 114, 121 pre_config_bak.sh . . . . . . . 112 pre_data_bak.sh . . . . 114, 120 restore.sh . . . . . . . . . . . . . . . . . 8 SuSEconfig . . . . . . . . . . . . . . 40 series zima . . . . . . . . . . . . . . . . . . . . 79 SIEVE . . . . . . . . . . . . . . . . 64, 129 editor . . . . . . . . . . . . . . . . . . . 67 SKYRiXgreen . . . . . . . . . . 69–85 address books . . . . . . . . 74–77 appointments . . . . . . . . . 77–81 attachments . . . . . . . . . . . . . . 75 bouncing e-mail . . . . . . . . . . 74 deleting e-mail . . . . . . . . . . . 74 e-mail . . . . . . . . . . . . . . . 71–75 features . . . . . . . . . . . . . . . . . 69 folders . . . . . . . . . . . . . . . . . . 72 forwarding e-mail . . . . . . . . 74 help . . . . . . . . . . . . . . . . . . . . . 69 login . . . . . . . . . . . . . . . . . . . . 70 logout . . . . . . . . . . . . . . . . . . . 71 options . . . . . . . . . . . . . . . 83–85 palms . . . . . . . . . . . . . . . . 78–79 reading e-mail . . . . . . . . 73–74 replying to e-mail . . . . . . . . 74 requirements . . . . . . . . . . . . . 70 tasks . . . . . . . . . . . . . . . . . 81–82 writing e-mail . . . . . . . . . . . . 72 SMTP . . . . . . . . . . . . . . . . . . . . 129 SSL . . . . . . . . . . . . . . . . . . . . . . 129 support . . . . . . . . . . . . . . . . . . . 3–6
R
T
relay host . . . . . . . . . . . . . . . . . 128 rescue system starting . . . . . . . . . . . . . . . . . . 17 resources appointments . . . . . . . . . . . . 79 creating . . . . . . . . . . . . . . . . . 59
time zones YaST2 . . . . . . . . . . . . . . . . . . 19 TLS . . . . . . . . . . . . . . . . . . . . . 129
fetchmail . . . . . . . . . . . . 125 palms . . . . . . . . . . . . . . . . . . 78–79 partitioning manual . . . . . . . . . . . . . . . 22–23 YaST2 . . . . . . . . . . . . . . . 19–24 partitions boot . . . . . . . . . . . . . . . . . 19, 22 required . . . . . . . . . . . . . . . . . 19 resizing Windows . . . . . . . . 23 root . . . . . . . . . . . . . . . . . . 20, 22 swap . . . . . . . . . . . . . . . . . 20, 22 var . . . . . . . . . . . . . . . . . . . . . . 22 passwords administrator . . . . . . . . . . . . . 46 changing . . . . . . . . . . . . . . . . 61 root . . . . . . . . . . . . . . . . . . . . . 36 users . . . . . . . . . . . . . . . . . 44, 46 Pine . . . . . . . . . . . . . . . . . . . 97–99 .pinerc . . . . . . . . . . . . . . . 97, 99 IMAP . . . . . . . . . . . . . . . . . . . 97 LDAP . . . . . . . . . . . . . . . . . . . 99 starting . . . . . . . . . . . . . . . . . . 97 POP3 . . . . . . . . . . . . . . . . . . . . 128 Postfix . . . . . . . . . . . . 53–54, 128 dial on demand . . . . . . . . . . . 54 expert options . . . . . . . . . . . . 54 queues . . . . . . . . . . . . . . . . . . 57 relay hosts . . . . . . . . . . . . . . . 54 SASL . . . . . . . . . . . . . . . . . . . 54 TLS . . . . . . . . . . . . . . . . . . . . . 54
Q N name server . . . . . . . . . . . . . . . 127 name servers adding clients . . . . . . . . . . . . 52 eMail Server as . . . . . . . . . . 51 removing clients . . . . . . . . . 53 Netscape Communicator . 88–91 IMAP . . . . . . . . . . . . . . . . 88–91 LDAP . . . . . . . . . . . . . . . 89, 91 networks
136
U UID . . . . . . . . . . . . . . . . . . . . . . 129
Index
updating . . . . . . . . . . . . . . . . 7–10 user configuration . . . . . . . 61–67 automatic replies . . . . . . . . . 66 certificates . . . . . . . . . . . . . . . 61 creating scripts . . . . . . . . . . . 67 folders . . . . . . . . . . . . . . . . . . 62 KMail . . . . . . . . . . . . . . . . . . . 95 language . . . . . . . . . . . . . . . . 61 mail applications . . . . . . . . . 87 mail filtering . . . . . . . . . 64–66 Mozilla . . . . . . . . . . . . . . . . . . 91 Netscape Communicator . . . . . 88–91 Outlook . . . . . . . . . . . 101–103 password . . . . . . . . . . . . . . . . 61 personal data . . . . . . . . . . . . . 61 Pine . . . . . . . . . . . . . . . . . 97–99 preparing for . . . . . . . . . . . . . 87
SKYRiXgreen . . . . . . . . 69–85 users adding to groups . . . . . . . . . 46 administering . . . . . . . . . 44–47 aliases . . . . . . . . . . . . . . . . . . . 46 certificates . . . . . . . . . . . . . . . 46 creating . . . . . . . . . . . . . . . . . 44 deleting . . . . . . . . . . . . . . . . . 46 disabling . . . . . . . . . . . . . . . . 46 e-mailing all . . . . . . . . . . . . . 58 passwords . . . . . . . . . . . . . . . 46 personal data . . . . . . . . . . . . . 61 virtual . . . . . . . . . . . . . . . 51–52 creating . . . . . . . . . . . . . . . . . . 52 editing . . . . . . . . . . . . . . . . . . . 52
Y YaST
starting . . . . . . . . . . . . . . . . . . 17 YaST2 graphics modes . . . . . . . . . . 16 hard disks . . . . . . . . . . . . 19–24 help . . . . . . . . . . . . . . . . . . . . . 17 installing eMail Server 15–40 kernel parameters . . . . . . . . 17 keyboard . . . . . . . . . . . . . . . . 19 language . . . . . . . . . . . . . . . . 18 LILO . . . . . . . . . . . . . . . . . . . 30 LVM . . . . . . . . . . . . . . . . 24–30 monitor . . . . . . . . . . . . . . . . . 38 mouse selection . . . . . . . . . . 18 partitioning . . . . . . . . . . . 19–24 resizing Windows partition 23 root password . . . . . . . . . . . . 36 time zones . . . . . . . . . . . . . . . 19
137
