DOCSLIB.ORG

IBM Z/OS V1R13 Communications Server TCP/IP Implementation: Volume 2 Standard Applications

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
IBM Z/OS V1R13 Communications Server TCP/IP Implementation: Volume 2 Standard Applications Front cover IBM z/OS V1R13 Communications Server TCP/IP Implementation: Volume 2 Standard Applications Provides information about z/OS Communications Server TCP/IP standard applications Discusses how to take advantage of TCP/IP standard applications for your needs Includes TCP/IP application implementation examples Mike Ebbers Rama Ayyar Octavio L Ferreira Yohko Ojima Gilson Cesar de Oliveira Mike Riches Maulide Xavier ibm.com/redbooks International Technical Support Organization IBM z/OS V1R13 Communications Server TCP/IP Implementation: Volume 2 Standard Applications December 2011 SG24-7997-00 Note: Before using this information and the product it supports, read the information in “Notices” on page ix. First Edition (December 2011) This edition applies to Version 1, Release 13 of IBM z/OS Communications Server (product number 5694-A01). © Copyright International Business Machines Corporation 2011. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . ix Trademarks . .x Preface . xi The team who wrote this book . xii Now you can become a published author, too! . xiii Comments welcome. xiv Stay connected to IBM Redbooks . xiv Chapter 1. The syslog daemon . 1 1.1 Conceptual overview of syslogd . 2 1.1.1 What is syslogd. 2 1.1.2 How syslogd works . 3 1.1.3 How can syslogd be deployed . 3 1.2 Log messages to different files and to a single file . 5 1.2.1 Description of logging to multiple files and to a single file. 5 1.2.2 Configuration of multiple files and a single file . 5 1.2.3 Verification of multiple files and a single file . 13 1.3 Starting two syslogd instances . 14 1.3.1 Description of two syslogd instances . 14 1.3.2 Configuring two syslogd instances . 14 1.3.3 Verification for running two syslogd instances . 17 1.4 The syslogd functions . 18 1.4.1 The syslogd operator commands . 19 1.4.2 Description of syslogd automatic archival. 19 1.4.3 The syslogd browser and search facility . 25 1.5 Problem determination for syslogd logging . 33 1.6 Additional information sources for syslogd . 34 Chapter 2. TN3270E Telnet server . 35 2.1 Conceptual overview of the TN3270E server . 36 2.1.1 What is the TN3270E server. 36 2.1.2 How does the TN3270E server work . 37 2.1.3 Possible uses for the TN3270E server . 42 2.2 TN3270E server in a single image . 43 2.2.1 Description of our TN3270E server scenario . 44 2.2.2 Configuration of the TN3270E server . 44 2.2.3 Activation of the TN3270E server . 53 2.2.4 Verification of the TN3270E server . 53 2.2.5 Administration and management of the TN3270E server . 66 2.3 Multiple TN3270E servers in a multiple image environment . 77 2.3.1 Multiple TN3270E servers within the sysplex . 78 2.3.2 Configuration of multiple TN3270E servers within the sysplex . 80 2.3.3 Activation and verification of multiple TN3270E servers in the sysplex . 86 2.4 Multiple TN3270E servers using LU name server and LU name requester . 95 2.4.1 Description of TN3270E servers using LU name server and requester . 96 2.4.2 Configuration of TN3270E servers within sysplex using LU name server and requester. 102 2.4.3 Activation and verification of LU name server and requester within sysplex . 109 © Copyright IBM Corp. 2011. All rights reserved. iii 2.4.4 Scenario: LU name server automated takeover when active name server fails . 124 2.5 TN3270E server in a single image using SHAREACB . 128 2.5.1 Overview of SHAREACB utilization . 128 2.5.2 Configuration of the TN3270E server with SHAREACB option. 129 2.5.3 Activation of the TN3270E server . 130 2.5.4 Verification of the TN3270E server with SHAREACB defined . 131 2.6 TN3270 support of TSO logon reconnect . 132 2.7 Problem determination for the TN3270E servers . 132 2.7.1 Review the definition statements within the profile . 132 2.7.2 Use TCP/IP and Telnet commands. 133 2.7.3 Use the MSG07 statement in the TN3270 profile . 138 2.7.4 Use SMF records to capture TN3270 connection activity. 139 2.7.5 Use trace data. 139 2.7.6 Tips for multiple TN3270E servers in a Parallel Sysplex environment . 140 2.7.7 Tips for LU name server and LU name requester diagnosis. 140 2.8 Additional information sources for the TN3270E server . 141 Chapter 3. File Transfer Protocol. 143 3.1 Conceptual overview of FTP . 144 3.1.1 What is FTP . 144 3.1.2 How does FTP work . 145 3.1.3 How can FTP be used . 146 3.2 Basic FTP without security . 148 3.2.1 Description of basic FTP without security . 148 3.2.2 Planning for the basic FTP environment without security . 149 3.2.3 Configuration of basic FTP without security . 162 3.2.4 Activation and verification for basic FTP without security . 165 3.3 Multiple FTP servers in a sysplex . 173 3.3.1 Description of multiple FTP servers in a sysplex . 173 3.3.2 Configuration for multiple FTP servers in the sysplex. 175 3.3.3 Activation and verification of FTP servers within sysplex . 178 3.4 FTP client using batch. 187 3.4.1 Description of FTP client using batch . 187 3.4.2 Configuration of FTP client using batch . 188 3.4.3 Activation and verification of FTP client batch job. 189 3.5 FTP client application program interface. 190 3.5.1 FTP client API for REXX . 190 3.5.2 FTP client API for Java . 191 3.6 FTP access to UNIX named pipes . 192 3.6.1 What are UNIX named pipes . 192 3.6.2 Description of FTP access to UNIX named pipes. ..
Load more

Recommended publications
  • SMTP (Simple Mail Transfer Protocol)
    P1: JsY JWBS001A-60.tex WL041/Bidgoli WL041-Bidgoli.cls May 12, 2005 3:27 Char Count= 0 SMTP (Simple Mail Transfer Protocol) Vladimir V. Riabov, Rivier College Introduction 1 SMTP Security Issues 12 SMTP Fundamentals 1 SMTP Vulnerabilities 12 SMTP Model and Protocol 2 SMTP Server Buffer Overflow Vulnerability 15 User Agent 4 Mail Relaying SMTP Vulnerability 15 Sending e-Mail 4 Mail Relaying SMTP Vulnerability in Microsoft Mail Header Format 4 Windows 2000 15 Receiving e-Mail 4 Encapsulated SMTP Address Vulnerability 15 The SMTP Destination Address 4 Malformed Request Denial of Service 16 Delayed Delivery 4 Extended Verb Request Handling Flaw 16 Aliases 5 Reverse DNS Response Buffer Overflow 16 Mail Transfer Agent 5 Firewall SMTP Filtering Vulnerability 16 SMTP Mail Transaction Flow 5 Spoofing 16 SMTP Commands 6 Bounce Attack 16 Mail Service Types 6 Restricting Access to an Outgoing Mail SMTP Service Extensions 8 Server 17 SMTP Responses 8 Mail Encryption 17 SMTP Server 8 Bastille Hardening System 17 On-Demand Mail Relay 8 POP and IMAP Vulnerabilities 17 Multipurpose Internet Mail Extensions Standards, Organizations, and (MIME) 8 Associations 18 MIME-Version 10 Internet Assigned Numbers Authority 18 Content-Type 10 Internet Engineering Task Force Working Content-Transfer-Encoding 10 Groups 18 Content-Id 11 Internet Mail Consortium 18 Content-Description 11 Mitre Corporation 18 Security Scheme for MIME 11 Conclusion 18 Mail Transmission Types 11 Glossary 18 Mail Access Modes 11 Cross References 19 Mail Access Protocols 11 References 19 POP3 11 Further Reading 22 IMAP4 12 INTRODUCTION and IMAP4), SMTP software, vulnerability and security issues, standards, associations, and organizations.
    [Show full text]
  • Understanding Post Office Protocol (POP3)
    Understanding Post Office Protocol (POP3) Author: Conrad Chung, 2BrightSparks Introduction Most Internet users with email accounts would have used some form of “client” software (Outlook, Thunderbird etc.) to access and manage their email at one point or another. To retrieve emails, these email clients may require the configuration of Post Office Protocol (or POP3) before messages can be downloaded from the server. This article will help readers understand what POP3 is and how it works. What is Post Office Protocol? The Post Office Protocol (POP3) is an Internet standard protocol used by local email software clients to retrieve emails from a remote mail server over a TCP/IP connection. Since the first version was created in 1984, the Post Office Protocol (currently at Version 3) has since became one of the most popular protocols and is used by virtually every email client to date. Its popularity lies in the protocol’s simplicity to configure, operate and maintain. Email servers hosted by Internet service providers also use POP3 to receive and hold emails intended for their subscribers. Periodically, these subscribers will use email client software to check their mailbox on the remote server and download any emails addressed to them. Once the email client has downloaded the emails, they are usually deleted from the server, although some email clients allow users to specify that mails be copied or saved on the server for a period of time. Email clients generally use the well-known TCP port 110 to connect to a POP3 server. If encrypted communication is supported on the POP3 server, users can optionally choose to connect either by using the STLS command after the protocol initiation stage or by using POP3S, which can use the Transport Layer Security (TLS) or Secure Sockets Layer (SSL) on TCP port 995 to connect to the server.
    [Show full text]
  • What Is the Difference Between Email Protocols
    What Is The Difference Between Email Protocols Interactions between email servers and users are governed by email protocols. The most common incoming email protocols are POP, and IMAP. Most email applications/programs support one or more of these. This article is to help users understand and choose which protocol should be selected for each user’s situation. Outgoing Incoming POP (Post Office Protocol): IMAP (Internet Message Access Protocol): SSL (Secure Socket Layer): Differences Between POP and IMAP Backups / Email Loss Outgoing SMTP (Simple Mail Transfer Protocol) is the protocol used in sending (outgoing) emails. SMTP is the protocol always used for sending (outgoing) emails. Incoming POP (Post Office Protocol) and IMAP (Internet Message Access Protocol) are two different protocols that do the same thing differently. They are both used in receiving emails from a mail server and can both are available for standard and secure (?) connections. POP (Post Office Protocol): POP is an email accessing protocol used to download emails from a mail server. Applications like Outlook and Outlook Express using POP will download all emails from the server to the user’s computer, and then delete them on the server. Generally POP server uses port 110 to listen to the POP requests or securely using SSL (Secure Socket Layer) (?) POP uses port number 995. The POP protocol assumes that there is only one client/computer that will be connecting to the mailbox. Even though there is an option in most mail applications to leave the copies of the emails in the server, it is not generally used due to various reasons.
    [Show full text]
  • Ii Jacobs Rp316
    !II JACOBS RP316 RACIBORZ FLOOD RESERVOIR Public Disclosure Authorized Resettlement Action Plan Public Disclosure Authorized DRAFT Public Disclosure Authorized Public Disclosure Authorized March 2005 JACOBS Document control sheet Form IP180/B Client: PCU Project: Odra Flood Mitigation Job No: J24201A Title: Draft Resettlement Action Plan Prepared by Reviewed by Approved by ORIGINAL0 NAME NAME NAME P Devitt L J S Attewill see list of authors H Fiedler-Krukowicz J Loch | DATfE SIGNATURE SIGNATURE SIGNATURE REVISION NAME NAME NAME DATE SIGNATURE SIGNATURE SIGNATURE REVISION NAME NAME NAME DATE SIGNATURE SIGNATURE SIGNATURE REVISION NAME NAME NAME DATE SIGNATURE SIGNATURE SIGNATURE This report, and infonnabon or advice which it contains, is provided by JacobsGIBB Ltd solely for internal use and reliance by its Cient in performance of JacobsGIBB Ltd's duties and liabilities under its contract with the Client Any advice, opinions, or recomrnendatons within this report should be read and retied upon only in the context of the report as a whole. The advice and opinions in this report are based upon the information nmadeavailable to JacobsGIBB Ltd at the date of this report and on current UK standards, codes, technology and constnuction practices as at the date of this report. Folloving final delvery of this report to the Client, JacobsGIBB Ltd will have no further obligations or duty to advise She Client on any mafters, including developrrient affecting the information or advice provided in ths report This report has been prepared by JacobsGIBB Ltd in their professional capaaty as Consuhing Engineers The contents of the report do not, in any way, purport to include any mranner of legal advice or opinion This report is prepared in accordance wrth the terms and conditions of JacobsGIBB Ltd's contract with the Client.
    [Show full text]
  • HTTP Cookie - Wikipedia, the Free Encyclopedia 14/05/2014
    HTTP cookie - Wikipedia, the free encyclopedia 14/05/2014 Create account Log in Article Talk Read Edit View history Search HTTP cookie From Wikipedia, the free encyclopedia Navigation A cookie, also known as an HTTP cookie, web cookie, or browser HTTP Main page cookie, is a small piece of data sent from a website and stored in a Persistence · Compression · HTTPS · Contents user's web browser while the user is browsing that website. Every time Request methods Featured content the user loads the website, the browser sends the cookie back to the OPTIONS · GET · HEAD · POST · PUT · Current events server to notify the website of the user's previous activity.[1] Cookies DELETE · TRACE · CONNECT · PATCH · Random article Donate to Wikipedia were designed to be a reliable mechanism for websites to remember Header fields Wikimedia Shop stateful information (such as items in a shopping cart) or to record the Cookie · ETag · Location · HTTP referer · DNT user's browsing activity (including clicking particular buttons, logging in, · X-Forwarded-For · Interaction or recording which pages were visited by the user as far back as months Status codes or years ago). 301 Moved Permanently · 302 Found · Help 303 See Other · 403 Forbidden · About Wikipedia Although cookies cannot carry viruses, and cannot install malware on 404 Not Found · [2] Community portal the host computer, tracking cookies and especially third-party v · t · e · Recent changes tracking cookies are commonly used as ways to compile long-term Contact page records of individuals' browsing histories—a potential privacy concern that prompted European[3] and U.S.
    [Show full text]
  • Migrationsleitfaden
    Migrationsleitfaden Leitfaden für die Migration der Basissoftwarekomponenten auf Server- und Arbeitsplatz-Systemen Version 1.0 – Juli 2003 Schriftenreihe der KBSt ISSN 0179-7263 Band 57 Juli 2003 Schriftenreihe der KBSt Band 57 ISSN 0179 - 7263 Nachdruck, auch auszugsweise, ist genehmigungspflichtig Dieser Band wurde erstellt von der KBSt im Bundesministeri- um des Innern in Zusammenarbeit mit dem Bundesamt für Sicherheit in der Informationstechnik (BSI), dem Bundesver- waltungsamt (BVA) und der C_sar Consulting, solutions and results AG Redaktion: C_sar AG, Berlin Interessenten erhalten die derzeit lieferbaren Veröffentlichungen der KBSt und weiterführende Informationen zu den Dokumenten bei Bundesministerium des Innern Referat IT 2 (KBSt) 11014 Berlin Tel.: +49 (0) 1888 681 - 2312 Fax.: +49 (0) 1888 681 - 523121 Homepage der KBSt: http://www.kbst.bund.de 1Frau Monika Pfeiffer (mailto: [email protected]) Migrationsleitfaden Leitfaden für die Migration der Basissoftwarekomponenten auf Server- und Arbeitsplatz-Systemen Version 1.0 Juli 2003 Herausgegeben vom Bundesministerium des Innern INHALTSVERZEICHNIS 1 Einleitung ........................................................................ 8 1.1 Über das Vorhaben 8 1.2 Über diesen Leitfaden 9 1.3 Hinweise zur Benutzung des Leitfadens 10 1.4 Hinweise an die Entscheider 12 1.4.1 Grundsätzliche Empfehlungen 12 1.4.2 Fortführende und ablösende Migration 13 1.4.3 Migrationswege 14 1.4.4 Vergleichbarkeit von Alternativen 14 1.4.5 Künftige Schwerpunte 15 1.4.6 Wirtschaftlichkeit 16
    [Show full text]
  • [MS-STANOPOP3]: Outlook Post Office Protocol Version 3 (POP3) Standards Compliance
    [MS-STANOPOP3]: Outlook Post Office Protocol Version 3 (POP3) Standards Compliance Intellectual Property Rights Notice for Open Specifications Documentation . Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages, standards as well as overviews of the interaction among each of these technologies. Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you may make copies of it in order to develop implementations of the technologies described in the Open Specifications and may distribute portions of it in your implementations using these technologies or your documentation as necessary to properly document the implementation. You may also distribute in your implementation, with or without modification, any schema, IDL’s, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. Patents. Microsoft has patents that may cover your implementations of the technologies described in the Open Specifications. Neither this notice nor Microsoft's delivery of the documentation grants any licenses under those or any other Microsoft patents. However, a given Open Specification may be covered by Microsoft's Open Specification Promise (available here: http://www.microsoft.com/interop/osp) or the Community Promise (available here: http://www.microsoft.com/interop/cp/default.mspx). If you would prefer a written license, or if the technologies described in the Open Specifications are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting [email protected].
    [Show full text]
  • NBG6515 User's Guide
    NBG6515 AC750 Dual-Band Wireless Gigabit Router Version 1.00 Edition 1, 01/2016 Quick Start Guide User’s Guide Default Details LAN IP Address - Router Mode http://192.168.1.1 (Default mode) - AP/Repeater http://192.168.1.2 Mode www.zyxel.com User Name admin Password 1234 2.4G SSID ZyXEL + Last 6 digits of the 2.4G MAC address (ZyXEL734916) 5G SSID ZyXEL+ Last 6 digits of the 5G MAC address + .speed (ZyXEL734917.speed) Pre-shared Key Serial number + Random key Copyright © 2016 ZyXEL Communications Corporation IMPORTANT! READ CAREFULLY BEFORE USE. KEEP THIS GUIDE FOR FUTURE REFERENCE. Screenshots and graphics in this book may differ slightly from your product due to differences in your product firmware or your computer operating system. Every effort has been made to ensure that the information in this manual is accurate. Related Documentation •Quick Start Guide The Quick Start Guide shows how to connect the NBG and access the Web Configurator. Note: It is recommended you use the Web Configurator to configure the NBG. •More Information Go to support.zyxel.com to find other information on the NBG. NBG6515 User’s Guide 2 Contents Overview Contents Overview User’s Guide ....................................................................................................................................... 11 Getting to Know Your NBG .....................................................................................................................12 Connection Wizard ..................................................................................................................................17
    [Show full text]
  • Table of Contents
    Table of Contents Preface .................................................................................................... xiii Part I: The Web Environment Chapter 1—Designing for a Variety of Browsers ...................... 3 Browsers ................................................................................................. 3 Design Strategies .................................................................................... 9 Writing Good HTML ............................................................................. 11 Knowing Your Audience ..................................................................... 12 Considering Your Site’s Purpose ......................................................... 13 Test! Test! Test! ..................................................................................... 13 Chapter 2—Designing for a Variety of Displays .................... 14 Dealing with Unknown Monitor Resolutions ..................................... 14 Fixed versus Flexible Web Page Design ............................................. 19 Accessibility .......................................................................................... 23 Alternative Displays .............................................................................. 26 Chapter 3—Web Design Principles for Print Designers ...................................................................... 28 Color on the Web ................................................................................. 28 Graphics on the Web ..........................................................................
    [Show full text]
  • Groupwise Internet Agent
    GroupWise Internet Agent April 7, 2000 Novell Confidential Manual Rev 99a24 8 February 00 Legal Notices Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. This product may require export authorization from the U.S. Department of Commerce prior to exporting from the U.S. or Canada. Copyright © 1993-1999 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher. U.S. Patent Nos. 4,555,775; 4,580,218; 5,412,772; 5,701,459; 5,717,912; 5,760,772; 5,870,739; 5,873,079; 5,884,304; 5,903,755; 5,913,209; 5,924,096; 5,946,467; D393,457 and U.S. Patents Pending. Novell, Inc. 122 East 1700 South Provo, UT 84606 U.S.A. www.novell.com GroupWise Internet Agent February 2000 104-001304-001 Online Documentation: To access the online documentation for this and other Novell products, and to get updates, see www.novell.com/documentation.
    [Show full text]
  • System I: Poczta Elektroniczna
    System i Poczta elektroniczna Wersja 6 wydanie 1 System i Poczta elektroniczna Wersja 6 wydanie 1 Uwaga Przed skorzystaniem z tych informacji oraz z produktu, którego dotyczą, należy przeczytać informacje zawarte w sekcji “Uwagi”, na stronie 55. To wydanie dotyczy systemu operacyjnego IBM i5/OS (numer produktu 5761-SS1) wersja 6, wydanie 1, modyfikacja 0, a także wszystkich kolejnych wydań i modyfikacji, chyba że w nowych wydaniach zostanie określone inaczej. Wersja ta nie działa na wszystkich modelach komputerów z procesorem RISC ani na modelach z procesorem CISC. © Copyright International Business Machines Corporation 1998, 2008. Wszelkie prawa zastrzeżone. Spis treści Poczta elektroniczna . .1 Zabezpieczanie poczty elektronicznej . .24 Wysyłanie poczty elektronicznej przez router lub || Co nowego w wersji V6R1 . .1 zaporę firewall . .24 Plik PDF z informacjami na temat poczty elektronicznej . .2 Wymagania wstępne dla routera poczty Koncepcje poczty elektronicznej . .2 elektronicznej . .25 Protokół SMTP w systemie i5/OS . .3 Uwierzytelnianie lokalnej i przekazywanej poczty Serwer POP w systemie i5/OS . .4 | elektronicznej . .25 Scenariusze: poczta elektroniczna . .4 | Śledzenie nadawcy poczty elektronicznej . .26 Scenariusz: wysyłanie i odbieranie poczty elektronicznej | Ograniczanie przekazywania wiadomości . .27 lokalnie . .4 Akceptowanie wiadomości przekazywanych od | Scenariusz: konfigurowanie funkcji API klientów POP . .28 || QtmsCreateSendEmail do używania standardu S/MIME .7 Równoczesne korzystanie z funkcji ograniczenia Planowanie korzystania z poczty elektronicznej . .10 przekazywania i ograniczenia połączeń . .29 Kontrolowanie dostępu do poczty elektronicznej . .10 Ograniczanie połączeń . .29 Kontrola dostępu do serwera SMTP . .11 Filtrowanie poczty elektronicznej w celu zapobiegania Kontrola dostępu do serwera POP . .11 rozprzestrzenianiu się wirusów . .30 Blokowanie dostępu do poczty elektronicznej . .12 Wysyłanie i pobieranie poczty elektronicznej . .30 Blokowanie dostępu za pomocą protokołu SMTP 12 Konfigurowanie klientów poczty POP .
    [Show full text]
  • Vmware Zimbra Collaboration Server Administrator's
    VMware Zimbra Collaboration Server Administrator’s Guide Release 7.1 Open Source Edition May 2011 Legal Notices Copyright ©2005-2011 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents. VMware and Zimbra are registered trademarks or trademarks of VMware, Inc. in the United states and/ or other jurisdiction. All other marks and names mentioned herein may be trademarks of their respective companies. VMware, Inc. 3401 Hillview Avenue Palo Alto, California 94304 USA www.zimbra.com ZCS 7.1 Rev 2 for 7.1.2 July 2011 Table of Contents 1 Introduction . 9 Intended Audience . 9 Available Documentation . 9 Support for Recommended Third-Party Components . 10 Support and Contact Information . 10 2 Product Overview . 11 Core Functionality . 11 Zimbra Components . 13 System Architecture . 13 Zimbra Packages . 15 Zimbra System Directory Tree . 17 Example of a Typical Multi-Server Configuration . 19 3 Zimbra Mailbox Server . 23 Incoming Mail Routing . 23 Disk Layout . 23 Message Store . 24 Data Store. 24 Index Store . 24 Log . 25 4 Zimbra Directory Service. 27 Directory Services Overview . 27 LDAP Hierarchy . 28 Zimbra Schema . 29 Account Authentication . 30 Internal Authentication Mechanism. 30 External LDAP and External Active Directory Authentication Mechanism 30 Custom Authentication - zimbraCustomAuth . 31 Kerberos5 Authentication Mechanism . 33 Zimbra Objects . 33 Company Directory/GAL . 36 Flushing LDAP Cache . 38 Themes and Locales . 38 Accounts, COS, Domains, and Servers . 38 Global Configuration . 39 5 Zimbra MTA. 41 Zimbra MTA Deployment . 41 Postfix Configuration Files .
    [Show full text]