DOCSLIB.ORG

Fusiondirectory User Manual Documentation Release 1.4

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Fusiondirectory User Manual Documentation Release 1.4 FusionDirectory User Manual Documentation Release 1.4 Benoit Mortier Paola Penati Sep 09, 2021 Contents 1 FusionDirectory 3 1.1 What is FusionDirectory ?........................................5 1.2 Prerequisites...............................................6 1.3 Certified distributions..........................................8 1.4 Buy a subscription............................................8 1.5 Activate a subscription..........................................8 1.6 Install FusionDirectory..........................................9 1.7 Update FusionDirectory......................................... 23 1.8 Core................................................... 112 1.9 Configuration............................................... 135 1.10 ACLs................................................... 149 1.11 Plugins.................................................. 170 1.12 Templates................................................. 345 1.13 Triggers.................................................. 356 1.14 Faq.................................................... 360 1.15 Bug report................................................ 361 1.16 Release Policy.............................................. 363 1.17 License.................................................. 365 2 Schema2ldif 367 2.1 What is schema2ldif ?.......................................... 367 2.2 Prerequisites............................................... 367 2.3 Install Schema2ldif............................................ 367 2.4 ldap-schema-manager.......................................... 369 2.5 Schema2ldif............................................... 370 2.6 License.................................................. 371 3 Argonaut 373 3.1 What is Argonaut ?............................................ 375 3.2 Argonaut Components.......................................... 375 3.3 Certified distributions.......................................... 377 3.4 Buy a subscription............................................ 377 3.5 Install Argonaut............................................. 377 3.6 Configure Argonaut........................................... 382 3.7 Argonaut-server............................................. 383 3.8 Argonaut Client............................................. 384 3.9 Applications............................................... 384 i 3.10 License.................................................. 388 4 Support 389 4.1 Professional paid support........................................ 389 4.2 Community support........................................... 390 5 Security 391 5.1 Digital signature............................................. 391 5.2 Security issues.............................................. 391 6 Authors 393 6.1 Original GOsa2 AUTHORS....................................... 393 6.2 FusionDirectory AUTHORS....................................... 394 6.3 FusionDirectory libraries......................................... 397 7 Contact Us 399 8 Code of Conduct 401 8.1 Our Pledge................................................ 401 8.2 Our Standards.............................................. 401 8.3 Our Responsibilities........................................... 402 8.4 Scope................................................... 402 8.5 Enforcement............................................... 402 8.6 Attribution................................................ 402 ii FusionDirectory User Manual Documentation, Release 1.4 Contents: Contents 1 FusionDirectory User Manual Documentation, Release 1.4 2 Contents 3 FusionDirectory User Manual Documentation, Release 1.4 CHAPTER 1 FusionDirectory 4 Chapter 1. FusionDirectory FusionDirectory User Manual Documentation, Release 1.4 Contents: 1.1 What is FusionDirectory ? FusionDirectory provides a solution to daily management of data stored in an LDAP directory. Becoming the cor- nerstone of the information system, the corporate directory becomes more complex offering more data and managing more infrastructure services. This interface is simple and can be used to delegate fully or partly the data management to non-specialists. 1.1.1 Features • Users, groups, mail, ssh, personal management. • Supann norm Management. • PARTAGE mail integration • Systems management : dhcp, dns, sudo, all kind of systems. • System deployment management : FAI, OPSI • Complex Roles Management. • Access to multiple LDAP trees. • FusionDirectory Triggers 1.1.2 Acls and roles • ACLs are only used by FusionDirectory and not the underlying ldap server. • ACLs can be assigned to roles. – Global administrator : Can do everything. – Local administrator : Can manage users and groups and also a branch. – Human resources : Can create users from template to optimize the arrival of new people. – User : Will only be able to change his data permitted by an administrator 1.1.3 FusionDirectory Triggers FusionDirectory incorporates a series of triggers that can launch a specific action based on a task FusionDirec- tory must run. These triggers are associated with a content type (LDAP user, group, server, password, service and the triggering ac- tion (create, edit, delete, change password . ) For example, when creating a user, a script generation form can be executed automatically with informa- tion from the LDAP server. This can be useful for generating badges with photo, a form of access to the canteen or sending an email to warn other services of the actual arrival of the person. This system is also convenient when we want to deploy the account of that person on an application that does not sup- port LDAP. 1.1. What is FusionDirectory ? 5 FusionDirectory User Manual Documentation, Release 1.4 Another example is when a user leaves, you must: • archive and delete his mailbox • archive and remove its network space • delete him from third party applications not connected to LDAP. All of this can be easily done by shell scripts (at least in UNIX environment) and run automatically after the suppres- sion of the person by the administrator in FusionDirectory 1.1.4 The interaction with non-LDAP applications FusionDirectory stores information of a service or a server on an LDAP server. How about when this service does not have the opportunity to interact with LDAP? This question can be solved by creating: • LDAP schema suitable for application to the LDAP server • A plugin for its management in FusionDirectory with the simple plugin API • An Argonaut module for the client installed on the server 1.2 Prerequisites FusionDirectory is a Web application that will need: • a webserver; • PHP; • an ldap server; • perl 1.2.1 Web server FusionDirectory requires a web server that supports PHP, like: • Apache 2 (or more recent); • Nginx; • Microsoft IIS. 1.2.2 PHP As of 1.4 release, FusionDirectory requires PHP 7.0 or more recent. Note: We recommand to use the most recent stable PHP release for better performances. 6 Chapter 1. FusionDirectory FusionDirectory User Manual Documentation, Release 1.4 Mandatory extensions Following PHP extensions are required for the app to work properly: • cas: for CAS authentication; • curl: to communicate with different types of servers and protocols • filter: to filters a variable with a specified filter; • fpdf: to export data in pdf format; • gd: to generate images; • iconv : for the samba integration; • imagick : to handle images; • imap: to handle imap servers management; • json: to get support for JSON data format; • mbstring: to manage multi bytes characters; • ldap: to connect and query the ldap server; • openssl: secured communications and generation of secure tokens; • session: to get user sessions support; • simplexml; • xml. Optional extensions Note: Even if those extensions are not mandatory, we advise you to install them anyways. Following PHP extensions are required for some extra features of FusionDirectory : • gettext : for an internationalized interface. • mhash : to make use of SSHA encryption • sha1 : to make use of SSHA encryption • zlib: to handle snapshots; Configuration PHP configuration file (php.ini) must be adapted to reflect following variables: expose_php= Off; implicit_flush= Off; memory_limit= 128M ; // max memory limit max_execution_time= 30 ; // not mandatory but adviced session.auto_start= off ; 1.2. Prerequisites 7 FusionDirectory User Manual Documentation, Release 1.4 1.2.3 LDAP server For FusionDirectory to work you need an ldap server. Servers know to work are : • OpenLDAP • 389DS 1.3 Certified distributions We certify FusionDirectory with all the most common distributions, here is a table which summarizes the level of support by distribution and version. Fusiondirectory need at least PHP 5.6. • Fusiondirectory 1.3 need >= PHP 5.6 • Fusiondirectory 1.4 need >= PHP 7.0 DISTRIBUTION FusionDirectory 1.2 FusionDirectory 1.3 Debian Jessie need a support contract need a support contract Debian Stretch not supported supported Debian Buster not supported supported Ubuntu 16.04 LTS need a support contract supported Ubuntu 18.04 LTS not supported supported Ubuntu 20.04 LTS not supported work in progress Centos 7 need a support contract supported Centos 8 not supported not supported 1.4 Buy a subscription FusionDirectory source code is published under the free software licence GPL 2+ and thus is freely available for download, use and share. You use your distribution package manager or inspect the code in the public code repository A FusionDirectory Subscription is an additional service program designed to help IT professionals and businesses to keep your FusionDirectory deployments up-to-date. A
Load more

Recommended publications
  • Selektiv Verteilen Auswertung, Ob Und Wie Der Kunde Die Kunde Der Wie Und Ob Auswertung, Kann
    04/2011 Open-Source-Tools fürs E-Mail-Marketing Titelthema Selektiv verteilen Mailings 34 Funktionierendes E-Mail-Marketing ist nicht auf proprietäre Software beschränkt. Eine Vielzahl von Open- Source-Produkten nimmt es beim Versand professionell anmutender Nachrichten durchaus mit kommerziellen Varianten auf. Dieser Artikel vergleicht fünf freie Mailer für Unternehmen. Peer Heinlein www.linux-magazin.de »approve Listenpassword [un]subscribe Liste E-Mail-Adresse«, eine Übersicht der eingetragenen Adressen liefert »approve Listenpassword who Liste«. Weil aber solche E-Mail-Kommandos erfahrungsgemäß viele nicht-technische Anwender überfordern, braucht es ein GUI für die Bedienung per Mausklick. Zwar bringt Majordomo selbst keine Weboberfläche mit, über das Tool Ma- jorcool [2] lässt sich die jedoch unpro- blematisch anbauen. Majordomo und Majorcool treten heute fast immer im Doppelpack auf, auch in vielen Confixx- Installationen bei großen Hostern. Leider haben die Entwickler den Ma- jordomo-Code seit über 10 Jahren nicht © Thorsten Rust, 123RF.com Rust, © Thorsten mehr wirklich verbessert ([3], [4]) ,auch der Rewrite Majordomo 2 hat sei- „Wer nicht wirbt stirbt.“ Diese alte Weis- E-Mail gelesen hat, wichtige Rückmel- nen Alpha-Status nie verlassen [5]. In heit haben gute Geschäftsleute stets im dung über dessen Interessen. Auch das Sachen Usability und Technik ist Ma- Hinterkopf. Wer die technischen Mög- hilft, die Qualität zu steigern – schließ- jordomo daher hoffnungslos veraltet. lichkeiten des Internets für seine Zwecke lich soll das Mailing ja nicht als plumpe Selbst grundlegende Funktionen wie ein nutzt, schafft sich neue Wege, die Kunden Werbe-Massenmail rüberkommen, son- Bounce-Management zum Austragen un- zu binden und spart eine Menge Geld. dern die Probleme und Bedürfnisse der zustellbarer Empfänger fehlt – von vielen Freie Software wie Mailman, Majordomo, Angesprochenen treffen.
    [Show full text]
  • Toward an Automated Vulnerability Comparison of Open Source IMAP Servers Chaos Golubitsky – Carnegie Mellon University
    Toward an Automated Vulnerability Comparison of Open Source IMAP Servers Chaos Golubitsky – Carnegie Mellon University ABSTRACT The attack surface concept provides a means of discussing the susceptibility of software to as-yet-unknown attacks. A system’s attack surface encompasses the methods the system makes available to an attacker, and the system resources which can be used to further an attack. A measurement of the size of the attack surface could be used to compare the security of multiple systems which perform the same function. The Internet Message Access Protocol (IMAP) has been in existence for over a decade. Relative to HTTP or SMTP, IMAP is a niche protocol, but IMAP servers are widely deployed nonetheless. There are three popular open source UNIX IMAP servers – UW-IMAP, Cyrus, and Courier-IMAP – and there has not been a formal security comparison between them. In this paper, I use attack surfaces to compare the relative security risks posed by these three products. I undertake this evaluation in service of two complementary goals: to provide an honest examination of the security postures and risks of the three servers, and to advance the study of attack surfaces by performing an automated attack surface measurement using a methodology based on counting entry and exit points in the code. Introduction Contributions and Roadmap System administrators frequently confront the The paper makes two major contributions. First, problem of selecting a software package to perform a I undertake an in-depth discussion of the relative secu- desired function. Many considerations affect this deci- rity postures of the three major open source IMAP sion, including functionality, ease of installation, soft- servers in use today.
    [Show full text]
  • Design and Management of Email Service
    Design and Management of Email Service Source : homepage.ntu.edu.tw/~jsc/2005-mail.ppt Outline Introduction to the architecture and operation of SMTP Design of a suitable email system – Webmail solutions Postfix and simple configuration samples Spam and virus filtering Conclusion 2 Overview Electronic mail service has already evolved into one of the major Internet applications. It is not only fundamental, but also a must. Users may become impatient when mails were delayed, not to mention failed to access their emails. – Imagine we meet the situation of power failure or cut of water supply 3 Architecture of a Simple Mail System Consists of the following components – MTA - Mail transfer agent Sending and forwarding emails Server end – MDA - Mail delivery agent Delivering emails to recipients’ mailbox Server end – Pop3/Imap4 Daemons For users to download their mailboxs Server end – MUA - Mail user agent Reading and composing emails 4 Client end Architecture of a Simple Mail System Protocols Used for Mail System Protocols – For computer programs to communicate with each other – Similar to languages that human beings speak SMTP – Simple Mail Transfer Protocol – Too simple to provide any “advanced features” Authentication Authorization POP3 – Post Office Protocol version 3 – Simple IMAP4 – Internet Message Access Protocol version 4 – Fully compatible with internet message standards, e.g. MIME. – Allow messages to be accessed from more than one computer. – Provide support for online, offline, and disconnected modes. 6 – Multiple and share folders. Mail Forwarding Between Servers How to Find the Way to the Destination? How do we find the way to [email protected]? 8 DNS: The Key to All Internet Services Query DNS server by the address part of email address.([email protected]) 1.
    [Show full text]
  • Tomenet-Guide.Pdf
    .==========================================================================+−−. | TomeNET Guide | +==========================================================================+− | Latest update: 17. September 2021 − written by C. Blue ([email protected]) | | for TomeNET version v4.7.4b − official websites are: : | https://www.tomenet.eu/ (official main site, formerly www.tomenet.net) | https://muuttuja.org/tomenet/ (Mikael’s TomeNET site) | Runes & Runemastery sections by Kurzel ([email protected]) | | You should always keep this guide up to date: Either go to www.tomenet.eu | to obtain the latest copy or simply run the TomeNET−Updater.exe in your | TomeNET installation folder (desktop shortcut should also be available) | to update it. | | If your text editor cannot display the guide properly (needs fixed−width | font like for example Courier), simply open it in any web browser instead. +−−− | Welcome to this guide! | Although I’m trying, I give no guarantee that this guide | a) contains really every detail/issue about TomeNET and | b) is all the time 100% accurate on every occasion. | Don’t blame me if something differs or is missing; it shouldn’t though. | | If you have any suggestions about the guide or the game, please use the | /rfe command in the game or write to the official forum on www.tomenet.eu. : \ Contents −−−−−−−− (0) Quickstart (If you don’t like to read much :) (0.1) Start & play, character validation, character timeout (0.1a) Colours and colour blindness (0.1b) Photosensitivity / Epilepsy issues (0.2) Command reference
    [Show full text]
  • (GNU Mailman) Mailing Lists
    Usability and efficiency improvements of the (GNU Mailman) mailing lists Rudy Borgstede ([email protected]) System and Network Engineering University of Amsterdam July 5, 2008 Versions Version Date Changes 0.0.1 18 May 2008 First setup of the report 0.0.2 9 June 2008 Release Candidate 1 of the project proposal 0.1.1 17 June 2008 A rewrite of the document because of the change of project result. The project will deliver an advice rather then a product like a patch or add-on for GNU Mailman. This means that the report becomes an consultancy report instead of a project proposal. 1.0.0 30 June 2008 Final version 1 of the report. 1.0.1 1 July 2008 A spelling check of the report. 1.0.2 5 July 2008 Extending the conclusion en future work chapters. Participants Name Contact Information University of Amsterdam Rudy Borgstede (Student) [email protected] Cees de Laat (Supervisor) [email protected] NLnet Michiel Leenaars (Supervisor) [email protected] Abstract This report is the result of a research project of four weeks at the NLnet Foundation1 in Amster- dam. The NLnet Foundation is a foundation who financially supports the open-source community and their projects. The purpose of the project is to improve the usability and the administration of the mailing lists (of the foundation) and giving a more clear view on mailing list server software to anyone who is interested in using mailing list server software or developing new mail or mail- ing list server software. The report describes the research of the usability of several open-source mailing list server software for scalable environments with several well known mail servers.
    [Show full text]
  • Set up Mail Server Documentation 1.0
    Set Up Mail Server Documentation 1.0 Nosy 2014 01 23 Contents 1 1 1.1......................................................1 1.2......................................................2 2 11 3 13 3.1...................................................... 13 3.2...................................................... 13 3.3...................................................... 13 4 15 5 17 5.1...................................................... 17 5.2...................................................... 17 5.3...................................................... 17 5.4...................................................... 18 6 19 6.1...................................................... 19 6.2...................................................... 28 6.3...................................................... 32 6.4 Webmail................................................. 36 6.5...................................................... 37 6.6...................................................... 38 7 39 7.1...................................................... 39 7.2 SQL.................................................... 41 8 43 8.1...................................................... 43 8.2 strategy.................................................. 43 8.3...................................................... 44 8.4...................................................... 45 8.5...................................................... 45 8.6 Telnet................................................... 46 8.7 Can postfix receive?..........................................
    [Show full text]
  • S/MIME and Sympa Mailing Lists Manager Using Signature and Encryption with a Mailing List Manager
    S/MIMEand Sympa mailing lists manager Using signature and encryption with a mailing list manager Serge Aumont and Olivier Salaün ComitØ RØseaux des UniversitØs [email protected] http://www.sympa.org Keywords: Signature, Encryption, S/MIME, Mailing list A few original features Abstract: Sympa is a modern mailing list manager that include many Using internal RDBMS features such as a complete web interface, associated groupware tools, Firt goal is to support large services with high performances and scal- fine tuning for access control etc. Current Sympa version provides also ability relying on RDBMS 3MySQL, PostgreSQL, Oracle, Sybase sup- original secure way based on S/MIME: digital signature and messages ported ). Sympa has been tested with 300.000 subscribers in a single distribution process using encryption. In addition Sympa`s web interface list on a medium server 3bi PII 550mhz with 512 Mega RAM) and can use HTTPS authentication based on user X509 certificates. This pa- some users already have real usage with more than 100.000 subscri- per describes how Sympa uses S/MIMEand HTTPS standards for secure bers using MySQL. The database allows high performances. It also group messaging. resolves data acces conflict between Sympa`s mail and web interface that share the same datas. Preface The web interface is a portal for all lists : WWSympa is the name given to Sympa`s web interface. It is a direc- The development was initiated in 1997. The goal was to replace a tory of lists provided by Sympa. Non-authenticated users can access previous mailing lists server ªTULPª, initiated in 1992 to organize public information but they can also login to access to their private the Bitnet services migration and was used essentially by French uni- list environment.
    [Show full text]
  • PONENCIAS Sympa, Un Gestor De Listas De
    03.Maq.IMPAR_S1-5.qxd 1/3/07 17:26 Página 29 Sympa, un gestor de listas de distribución PONENCIAS para las universidades Sympa, a mailing list software for universities S. Aumont y O. Salaün Resumen Este artículo describe las funcionalidades de Sympa, un gestor de listas de correo desarrollado por el CRU, una agencia que presta servicios a las instituciones académicas francesas. La descripción de Sympa se concentra esencialmente en las necesidades específicas del entorno universitario y en cómo Sympa puede satisfacerlas. Muchas de estas necesidades requieren una buena interacción con el middleware instalado en los sistemas de la universidad, como directorios LDAP, portales web y sistemas de single sign-on. Sympa es capaz de interaccionar con estos servicios a diferentes niveles: autenticación y autorización de usuarios, definición dinámica de listas, definición de grupos e integración de servicios Palabras clave: Lista de correo, groupware, colaboración, integración, middleware, LDAP, Single Sign-On, Shibboleth, PAPI, S/MIME, SOAP. Summary Sympa es un gestor The article describes functionalities of Sympa, a mailing list software, developed by the CRU, an agency working for French higher education institutions. The description of Sympa highly focuses on universities de listas de correo specific needs and how the mailing list software fulfils them. Most of these needs require interaction with a desarrollado por el university middleware; this includes the LDAP directory, a web portal, Single Sign-On systems. Sympa CRU, una agencia interacts with these services at different levels : user authentication and authorization, mailing lists definition, groups definition, service integration. que presta servicios a las instituciones Keywords: Mailing list, groupware, middleware integration, LDAP, Single Sign-On, Shibboleth, PAPI, académicas S/MIME, SOAP.
    [Show full text]
  • Server Administration
    Server administration Remo Suppi Boldrito PID_00148466 GNUFDL • PID_00148466 Server administration Copyright © 2009, FUOC. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License" GNUFDL • PID_00148466 Server administration Index Introduction............................................................................................... 5 1. Domain name system (DNS)............................................................ 7 1.1. Cache names server .................................................................... 7 1.2. Forwarders ................................................................................... 10 1.3. Configuration of an own domain .............................................. 11 2. NIS (YP)................................................................................................. 14 2.1. ¿How do we initiate a local NIS client in Debian? ..................... 14 2.2. What resources must be specified in order to use NIS? .............. 15 2.3. How should we execute a master NIS server? ............................ 16 2.4. How should we configure a server? ............................................ 17 3. Remote connection services: telnet and ssh............................... 19 3.1. Telnet and telnetd
    [Show full text]
  • An Open Source, Middleware-Enabled Mailing List Server
    An Open Source, Middleware-enabled Mailing list server Serge Aumont & Olivier Salaün September 2004 Internet2 Austin/Texas 1 CRU brief presentation, why Sympa Sympa overview The web document repository Sympa organization, virtual robots The template format The SOAP interface Dynamic mailing lists Lists families Privacy S/Mime and Sympa Authentication in Sympa Access control management Perspective Internet2 Austin/Texas 2 What is the CRU • CRU stands for « Comité Réseau des Universités » (network committee for French universities) • We do NOT operate a national academic network (=> Renater) • The CRU is responsible for coordinating actions among universities and between universities and the ministry Internet2 Austin/Texas 3 Institutional view Ministry in charge of Research and HE CNRS INRIA Universities Research (83) Engineer schools institutions (80) CEA … Internet2 Austin/Texas 4 Working forces in our environment • Renater is operating the national academic and research network • UREC, working for CNRS laboratories • CRU, working for Universities Internet2 Austin/Texas 5 CRU activities / Training • Training for universities technical staff : – Tutorials on targeted technologies (directories, groupware, video conferencing,…) – Yearly camps for security officers and network managers – Networking conference, held every two years (> 1000 participants, http://www.jres.org) Internet2 Austin/Texas 6 CRU activities / Working Groups • Working groups coordination for topics such as : – Directories – Security of information systems – Authentication
    [Show full text]
  • Number 1, May 2020
    May 2020 Volume 23, Number 1 A Quarterly Technical Publication for From The Editor Internet and Intranet Professionals In This Issue In mid-February, I traveled to Melbourne, Australia, to attend the Asia Pacific Regional Internet Conference on Operational Technologies (APRICOT). I normally attend around 10 or 12 similar Internet- From the Editor ...................... 1 related events in a year, be they Network Operator Group (NOG) conferences, Regional Internet Registry (RIR) events, or meetings of Network Buffer Sizes .............. 2 The Internet Engineering Task Force (IETF). This year, most of these events have either been cancelled or have “gone virtual” as the world tackles the COVID-19 pandemic. Mail Security with DMARC and ARC ............... 21 The pandemic has clearly demonstrated the resilience and flexibil- ity of the Internet and the people and organizations that rely on it for work, education, and entertainment. The various lock-downs or Letter to the Editor ............... 35 shelter-in-place orders have also given many of us an opportunity to take a closer look at some of the underlying technologies of the Fragments ............................. 37 Internet, as we participate in online events or perhaps read more books and articles. This journal continues to receive many interesting articles on all aspects of networking, and in addition to the normal Thank You! .......................... 40 issues in print (and PDF format), we are also planning to expand our online presence in the near future. Call for Papers ...................... 42 Buffering is a central concept in packet-switched networks. Appli- cations such as streaming audio or video rely on buffers to com- pensate for the fact that packets do not arrive at a fixed rate or even Supporters and Sponsors .....
    [Show full text]
  • The Qmail Handbook by Dave Sill ISBN:1893115402 Apress 2002 (492 Pages)
    < Free Open Study > The qmail Handbook by Dave Sill ISBN:1893115402 Apress 2002 (492 pages) This guide begins with a discussion of qmail s history, architecture and features, and then goes into a thorough investigation of the installation and configuration process. Table of Contents The qmail Handbook Introduction Ch apt - Introducing qmail er 1 Ch apt - Installing qmail er 2 Ch apt - Configuring qmail: The Basics er 3 Ch apt - Using qmail er 4 Ch apt - Managing qmail er 5 Ch apt - Troubleshooting qmail er 6 Ch apt - Configuring qmail: Advanced Options er 7 Ch apt - Controlling Junk Mail er 8 Ch apt - Managing Mailing Lists er 9 Ch apt - Serving Mailboxes er 10 Ch apt - Hosting Virtual Domain and Users er 11 Ch apt - Understanding Advanced Topics er 12 Ap pe ndi - How qmail Works x A Ap pe ndi - Related Packages x B Ap pe ndi - How Internet Mail Works x C Ap pe ndi - qmail Features x D Ap pe - Error Messages ndi x E Ap pe - Gotchas ndi x F Index List of Figures List of Tables List of Listings < Free Open Study > < Free Open Study > Back Cover • Provides thorough instruction for installing, configuring, and optimizing qmail • Includes coverage of secure networking, troubleshooting issues, and mailing list administration • Covers what system administrators want to know by concentrating on qmail issues relevant to daily operation • Includes instructions on how to filter spam before it reaches the client The qmail Handbook will guide system and mail administrators of all skill levels through installing, configuring, and maintaining the qmail server.
    [Show full text]