DOCSLIB.ORG

Tg-Olivera.Pdf

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Tg-Olivera.Pdf Universidad de la República Oriental del Uruguay Facultad de Ingeniería Carrera Ingeniería en Computación Sistema MailDB Integración de ee----mailmail y bases de datos Integrantes Elohim Olivera Marcelo Rodríguez Responsables Ing. Felipe Zipitría Ing. Alejandro Blanco Proyecto de grado Abril 2005 Resumen Este trabajo se basa en el estudio de formatos de almacenamientos de correo electrónico (e-mail). La principal motivación de este estudio es la sobrecarga de procesamiento que sufren los servidores de e-mails al trabajar con casillas (mailboxes) de gran tamaño. Por otro lado, es indudable el avance y potencia que han desarrollado las bases de datos, en consecuencia surgen naturalmente preguntas como: • ¿Alguna de las soluciones de almacenamiento existentes está aprovechando ese conocimiento? • ¿Se obtienen ventajas sobre los otros formatos de almacenamiento al utilizar bases de datos? En la primera parte del trabajo, se estudian los formatos y tecnologías más comúnmente utilizadas hoy en día para el almacenamiento de e-mails. Mediante un estudio cuantitativo se analiza que impacto tiene en el desempeño de los servicios de e-mails, la utilización de cada formato. En busca de mejoras en la calidad de los servicios, se analiza y diseña una API (Application Programming Interface, traducido del inglés: Interfaz de Programación de Aplicaciones) que se encarga de brindar las herramientas necesarias para trabajar con e-mails almacenados en una base de datos. Se desarrolla un prototipo de esta API y se la integra a un servidor de e-mails. Por último, se compara el desempeño de los servicios de e-mail utilizando la API con los datos obtenidos de servicios que utilizan otro tipo de formatos para almacenar e-mails. Palabras Clave: Servicio de correo electrónico, e-mail, mailbox, formato de almacenamiento de correo electrónico, base de datos, API, servidor de correo. Tabla de Contenido CAPÍTULO I INTRODUCCIÓN .......................................................................................................... 1 MOTIVACIÓN ......................................................................................................................................... 3 VIABILIDAD ........................................................................................................................................... 4 OBJETIVOS ............................................................................................................................................. 4 ORGANIZACIÓN DEL DOCUMENTO ......................................................................................................... 4 CAPÍTULO II ESTUDIO DE TECNOLOGÍAS EXISTENTES. ...................................................... 5 RESUMEN ............................................................................................................................................... 7 FUNDAMENTOS DEL SISTEMA DE E -MAILS ............................................................................................. 7 Agentes............................................................................................................................................. 8 MUA (Mail User Agent, Agente de Usuario de Correo)............................................................ 8 MTA (Mail Transfer Agent, Agente de Transferencia de Correo)............................................. 8 MDA (Mail Delivery Agent, Agente de Entrega de Correo)...................................................... 8 MRA (Mail Retrieval Agent, Agente de Recuperación de Correo)............................................ 9 Protocolos de comunicación............................................................................................................ 9 Depósito de e-mails.......................................................................................................................... 9 FORMATOS DE ALMACENAMIENTO DE E -MAILS ................................................................................... 10 Formatos basados en archivo........................................................................................................ 10 Mbox ......................................................................................................................................... 10 Mboxrd...................................................................................................................................... 10 Mmdf......................................................................................................................................... 11 Mbx ........................................................................................................................................... 11 Formatos basados en directorios................................................................................................... 12 Mh ............................................................................................................................................. 12 Mx ............................................................................................................................................. 12 Maildir....................................................................................................................................... 12 PRODUCTOS DEL MERCADO ................................................................................................................. 13 MTAs .............................................................................................................................................. 13 Sendmail............................................................................................................................... 13 Qmail .................................................................................................................................... 13 Postfix................................................................................................................................... 13 Exim ..................................................................................................................................... 13 MMDF.................................................................................................................................. 13 RLAs ............................................................................................................................................... 14 UW-Imap.............................................................................................................................. 14 Courier-Imap ........................................................................................................................ 14 Cyrus .................................................................................................................................... 14 Dovecot ................................................................................................................................ 14 Agentes mixtos (con almacenamiento en bases de datos) ............................................................. 14 Dbmail .................................................................................................................................. 14 Oryx Mailstore ..................................................................................................................... 14 James .................................................................................................................................... 15 Utilitarios para el almacenamiento en bases de datos.................................................................. 15 Mail2Db................................................................................................................................ 15 Mbox2mysql......................................................................................................................... 15 TRABAJOS RELACIONADOS AL PROYECTO ........................................................................................... 16 CAPÍTULO III ANÁLISIS DEL PROBLEMA Y SOLUCIÓN PROPUESTA ............................. 17 RESUMEN ............................................................................................................................................. 19 ANÁLISIS DE LA REALIDAD .................................................................................................................. 19 E-mail............................................................................................................................................. 19 Folder............................................................................................................................................. 19 Modelo conceptual de la realidad ................................................................................................. 20 El Problema ................................................................................................................................... 20 Requerimientos funcionales...................................................................................................... 20 Requerimientos no funcionales................................................................................................. 24 Actores y Casos de Uso.................................................................................................................. 24 Actores ...................................................................................................................................... 24 Casos de Uso
Load more

Recommended publications
  • Simple Mail Transfer Protocol (SMTP)
    Mail agents MUA = Mail User Agent Interacts directly with the end user Introduction to Internet Mail Pine, MH, Elm, mutt, mail, Eudora, Marcel, Mailstrom, Mulberry, Pegasus, Simeon, Netscape, Outlook, ... Multiple MUAs on one system - end user choice Philip Hazel MTA = Mail Transfer Agent University of Cambridge Receives and delivers messages Sendmail, Smail, PP, MMDF, Charon, Exim, qmail, Postfix, ... One MTA per system - sysadmin choice Message format (1) Message format (2) From: Philip Hazel <[email protected]> An address consists of a local part and a domain To: Julius Caesar <[email protected]> [email protected] Cc: Mark Anthony <[email protected]> Subject: How Internet mail works A basic message body is unstructured Julius, Other RFCs (MIME, 2045) add additional headers which I'm going to be running a course on ... define structure for the body Format was originally defined by RFC 822 in 1982 MIME supports attachments of various kinds and in Now superseded by RFC 2822 various encodings Message consists of Header lines Creating/decoding attachments is the MUA's job A blank line Body lines Authenticating senders MUA MTA Spool log Embedded MUA uses inter-process call to send to MTA in May use pipe, file, or internal SMTP over a pipe Folders Mailbox MTA knows the identity of the sender Normally inserts Sender: header if differs from From: SMTP MTA Spool Freestanding MUA uses SMTP to send mail MTA cannot easily distinguish local/remote clients SMTP No authentication in basic protocol Folders SMTP AUTH command in extended
    [Show full text]
  • Untersuchung Von Techniken Zur Persönlichen E-Mail-Postfachverschlüsselung
    Fachbereich VI - Informatik und Medien Master-Arbeit von Benjamin Fichtner zur Erlangung des akademischen Grades Master of Engineering im Studiengang Technische Informatik - Embedded Systems Untersuchung von Techniken zur persönlichen E-Mail-Postfachverschlüsselung Erstprüfer: Prof. Dr. rer. nat. Thomas Scheffler Gutachter: Prof. Dr. rer. nat. Rüdiger Weis Eingereicht am: 04.03.2019 Kurzfassung E-Mails enthalten häufig sensible und schützenswerte Inhalte, die nicht für Dritte be- stimmt sind. Obwohl die E-Mail ein weit verbreiteter Kommunikationsstandard ist, er- füllt sie viele aktuelle Sicherheitsanforderungen nicht [Foster et al., 2015]. Eines der Probleme ist, dass E-Mail-Inhalte im Klartext auf den Servern des E-Mail-Providers ge- speichert sind. Dort haben berechtigte und unberechtigte Dritte eine dauerhafte Möglich- keit, auf diese zuzugreifen. Um das zu verhindern, wurde die sogenannte persönliche E- Mail-Postfachverschlüsselung entwickelt. Diese neuartige, serverseitige Schutzmaßnah- me speichert eingehende E-Mails verschlüsselt ab. Sie sorgt dafür, dass die verschlüssel- ten E-Mails ausschließlich durch den Nutzer bzw. dessen Passwort entschlüsselt werden können. In dieser Masterarbeit soll untersucht werden, ob der Einsatz von Postfachverschlüs- selungstechniken Auswirkungen auf den E-Mail-Server-Betrieb hat und wie sich die- se darstellen. Hierbei werden die vier Postfachverschlüsselungstechniken GPG-Sieve- Filter, MailCrypt, Scrambler und TREES miteinander verglichen. Dazu werden die ver- schiedenen Techniken analysiert, eine Testumgebung entwickelt, sowie eine Messreihe konzipiert und durchgeführt. Abstract In digital communication, e-mail is an indispensable means of communication. They often contain sensitive and protective content that is not intended for third parties. Alt- hough e-mail is such an important and widespread communication standard, it it does not meet modern security requirements [Foster et al., 2015].
    [Show full text]
  • Exim the Mail Transfer Agent.Pdf
    ,Title.10724 Page 1 Tuesday, October 9, 2001 9:25 AM Exim The Mail Transfer Agent ,Title.10724 Page 2 Tuesday, October 9, 2001 9:25 AM ,Title.10724 Page 3 Tuesday, October 9, 2001 9:25 AM Exim The Mail Transfer Agent Philip Hazel Beijing • Cambridge • Farnham • Köln • Paris • Sebastopol • Taipei • Tokyo ,Copyright.10561 Page 1 Tuesday, October 9, 2001 9:25 AM Exim: The Mail Transfer Agent by Philip Hazel Copyright © 2001 O’Reilly & Associates, Inc. All rights reserved. Printed in the United States of America. Published by O’Reilly & Associates, Inc., 101 Morris Street, Sebastopol, CA 95472. Editor: Andy Oram Production Editor: Mary Brady Cover Designer: Ellie Volckhausen Printing History: June 2001: First Edition. Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of O’Reilly & Associates, Inc. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and O’Reilly & Associates, Inc. was aware of a trademark claim, the designations have been printed in caps or initial caps. The association between the image of an aye-aye and Exim is a trademark of O’Reilly & Associates, Inc. While every precaution has been taken in the preparation of this book, the publisher assumes no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein. Library of Congress Cataloging-in-Publication Data Hazel, Philip Exim: the mail transfer agent/by Philip Hazel p.cm. ISBN 0-596-00098-7 1. Exim (Computer program) 2.
    [Show full text]
  • Linux E-Mail Set Up, Maintain, and Secure a Small Office E-Mail Server
    Linux E-mail Set up, maintain, and secure a small office e-mail server Ian Haycox Alistair McDonald Magnus Bäck Ralf Hildebrandt Patrick Ben Koetter David Rusenko Carl Taylor BIRMINGHAM - MUMBAI This material is copyright and is licensed for the sole use by Jillian Fraser on 20th November 2009 111 Sutter Street, Suite 1800, San Francisco, , 94104 Linux E-mail Set up, maintain, and secure a small office e-mail server Copyright © 2009 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the authors, nor Packt Publishing, and its dealers and distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. First published: June 2005 Second edition: November 2009 Production Reference: 1051109 Published by Packt Publishing Ltd. 32 Lincoln Road Olton Birmingham, B27 6PA, UK. ISBN 978-1-847198-64-8 www.packtpub.com
    [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]
  • Computer System Administration. Topic 11. Secure E-Mail Service
    Computer System Design and Administration Topic 11. Secure e-Mail service: SMTP Postfix, IMAP Dovecot (over SSL) José Ángel Herrero Velasco Department of Computer and Electrical Engineering This work is published under a License: Creative Commons BY-NC-SA 4.0 Computer System Design and Administration Topic 11. Secure e-Mail service: SMTP Postfix, IMAP Dovecot (over SSL) Puzzle Secure Information Server Clients Active ISC Directory DHCP Open ISC client SSL SSL LDAP DNS OpenLDAP DB LDAP ISC SSL NTP SSH IMAP (mail client) NFSv4 CIFS Secure MAIL Server Network file server/ MS Windows-Linux/UNIX interoperability SMTP IMAP (Postfix) (Dovecot) RAID/LVM SAMBA NFSv4 SSL Secure Web Server Ganglia Apache2 Hosts Core (web data) User (web data) Virtual MailLISTs Webmail pool pool (MailMan) (squirrelmail) (public_html) SSL Webmin Nagios 2 (.html, php …) WordPress José Ángel Herrero Velasco Computer System Design and Administration Topic 11. Secure e-Mail service: SMTP Postfix, IMAP Dovecot (over SSL) Target: e-Mail services • Deployment and development of an INTERNET secure e-MAIL service based on SMTP/IMAP protocols: – Sending mail using SMTP protocol: Pos(ix. – Receiving mail using IMAP protocol: Dovecot. – Management of Maildrop: Maildirs. – MUA-MTA secure communicaon (encrypted): TLS/SSL. • Installaon, configuraon and start up of a Webmail client: – Roundcube. – Mailmain. José Ángel Herrero Velasco Computer System Design and Administration Topic 11. Secure e-Mail service: SMTP Postfix, IMAP Dovecot (over SSL) The e-Mail system HTTP SMTP IMAP • Definions and basics: TCP TCP UDP – E-Mail: the electronic mail system: • Network service that enables 2 users from different computers IP to send and receive (exchange) digital messages.
    [Show full text]
  • LNCS 2763, Pp
    A High Performance and Low Cost Cluster-Based E-mail System Woo-Chul Jeun1, Yang-Suk Kee1, Jin-Soo Kim2, and Soonhoi Ha1 1 School of Electrical Engineering and Computer Science, Seoul National University, San 56-1, Sinlim-dong, Gwanak-gu, Seoul 151-744, Korea {wcjeun, yskee, sha}@iris.snu.ac.kr 2 Division of Computer Science, KAIST, Daejeon 305-701, Korea [email protected] Abstract. A large-scale e-mail service provider requests a highly scal- able and available e-mail system to accommodate the increasing volume of e-mail traffic as well as the increasing number of e-mail users. To reduce the system development and maintenance cost, it is requested to make the system modular using off-the-shelf components. In this pa- per, we propose a cluster-based e-mail system architecture to achieve the goals of high scalability and availability, and low development and maintenance cost. We adopt the internal structure of a typical Internet e-mail system for a single server, called the MTA-MDA structure, to the proposed system architecture for the low cost requirements. We have implemented four different system configurations with the MTA-MDA structure and compare their performances. Experimental results show that the proposed system architecture achieves all the design objectives. 1 Introduction The growth of the Internet has led to an explosion in volumes of e-mail traffic and in number of the users of e-mail service. At the same time, large-scale e-mail service providers have appeared. They have hundreds of millions of subscribers and process billions of messages: for example, in May 2001, Hotmail had over 100 million users and Yahoo! Mail, in March 1999, served 45 million users with 3.6 billion mail messages [1][2].
    [Show full text]
  • Lecture Notes for Web Security 2019 Part 5 — E-Mail Security Martin Hell
    Lecture Notes for Web Security 2019 Part 5 | E-mail Security Martin Hell This chapter will discuss some different security aspects of emails. In order to understand these aspects, it is necessary to understand the SMTP protocol, i.e., how emails are sent from one user to another, and what the messages look like. 1 The SMTP Protocol SMTP (Simple Mail Transfer Protocol) is the most common protocol used to transfer emails. It was first defined in RFC 821 [6], which was obsoleted by RFC 2821 [4], which was again obsoleted by RFC 5321 [5]. The email architecture consists of several building blocks, see Figure 1. • MUA - Mail User Agent. This is the source and target of emails and is responsible for delivering the email to the MSA. Typical examples are Eudora, Outlook, Pine and Kmail. • MSA - Mail Submission Agent. This receives the message from the MUA and delivers it to the MTA. This is usually implemented together with the MTA instead of being a standalone program. The MSA can implement security checks on the email, e.g., checking that it is not spam, before sending it to the MTA. Message submission uses TCP port 587 and is discussed in RFC 4409 [3]. • MTA - Mail Transfer Agent. This is the building block that implements the SMTP protocol. It is responsible for both sending and receiving mes- sages. When the destination has been reached, the MTA at the end host sends the message to the MDA. Examples of MTAs are sendmail, postfix, qmail and Microsoft's Exchange Server. • MDA - Mail Delivery Agent.
    [Show full text]
  • A Sane Mail System Or: Fetchmail, Procmail, Courier-IMAP-SSL, Maildir, Exim and Spamassassin
    A Sane Mail System Or: fetchmail, procmail, Courier-IMAP-SSL, Maildir, exim and SpamAssassin ©2003 Stewart Smith Linux Australia Vice President http://www.linux.org.au http://www.flamingspork.com 1 Why? • Ever increasing amounts of email • Needs to be sorted or we go insane • Ever increasing amounts of SPAM • Needs to be filtered or we go insane • Needs to be efficient or we go insane! 2 Fetchmail • It’s job is to fetch mail from POP or IMAP servers • You only need to use it if you do not receive mail directly (i.e. people send mail to [email protected]) 3 What you need to know • The server you get mail from (e.g. mail.myisp.com.au) • Your username (e.g. fred) • Your password (e.g. azy68fie) • The type of server you’re connecting to (It’s probably POP3) 4 ~/.fetchmailrc • This is where you store your fetchmail configuration • Must have permissions of 0600 (u=rw,g=,o=) (think chmod 600 .fetchmailrc) • The man page is useful 5 Example .fetchmailrc set daemon 660 poll mail.myisp.com.au protocol pop3 user fred password azy68fie fetchall The ‘set daemon 660’ line tells fetchmail to check for mail every 660 seconds 6 Where does fetched mail go? • As each message is retrieved fetchmail normally delivers it via SMTP to port 25 on the machine it is running on (localhost), just as though it were being passed in over a normal TCP/IP link. The mail will then be delivered locally via your system's MDA (Mail Delivery Agent, usually sendmail(8) but your system may use a different one such as smail, mmdf, exim, or qmail).
    [Show full text]
  • (19) United States (12) Patent Application Publication (10) Pub
    US 20090164586A1 (19) United States (12) Patent Application Publication (10) Pub. No.: US 2009/0164586 A1 DOUGLAS et al. (43) Pub. Date: Jun. 25, 2009 (54) METHOD AND SYSTEM FOR MANAGING Publication Classi?cation THE RECEPTION OF MESSAGES IN A (51) Int Cl COMMUNICATION NETWORK G0 6F 15/16 (200601) (52) US. Cl. ...................................................... .. 709/206 (75) Inventors: PAUL B. DOUGLAS, SHARDLOW DERBY (GB); (57) ABSTRACT ANDREW I‘ THOMPSON’ A method and system for managing the reception of messages SOUTHAMPTON (GB) in a communication network (100) includes a ?rst client node (102) polling (404) a server node (110) to check for the arrival Correspondence Address: of a ?rst message that is related to a ?rst message account at MOTOROLA INC the server node (110). The ?rst client node has a pull-message 600 NORTH Us HIGHWAY 45, W4 _ 39Q con?guration for the ?rst message account. The method also LIBERTYVILLE, IL 600485343 (Us) includes receiving (410) a push-message at the ?rst client node. The push-message noti?es the ?rst client node of the . _ arrival of a second message at the server node that is related to (73) Asslgnee' ’ S the ?rst message account. Further, the method includes ’ (U ) changing (502) the ?rst client node from a pull-message con?guration to a push-message con?guration, based on the (21) Appl. NO-I 11/962,374 push-message. Furthermore, the method includes the ?rst client node terminating (506) the polling of the server node (22) Filed; Dec. 21, 2007 for the ?rst message account. r102 FIRST CLIENT NODE r202 MEMORY [204 206 110 PROCESSOR r SERVER r TRANSCEIVER 4 ' ' ' ' '> NODE r210 MESSAGE r203 RETR'EVER CONFIGURATION MANAGER Patent Application Publication Jun.
    [Show full text]
  • 리눅스 서버 Chapter 08 324 Page
    20 Linux fedora Server 리눅스 왕초보 실무를 익혀라! 김영훈ㆍ정거룡 지음 리눅스 서버 Chapter 08 324 page 메일 서버 8.1 Email 서비스의 구성 요소 8.2 메일 서버 구축 05 8.1 Email 서비스의 구성 요소 • mail 서비스 관련 프로토콜 – SMTP(Simple Mail Transfer Protocol) • 인터넷 상에서 전자 메일을 전송할 때 쓰이는 표준 프로토콜 – POP3(Post Office Protocol 3) • 메일서버로 수신된 메일을 사용자 자신의 PC 즉 메일 client 프로그램으로 다운 로드해주는 프로토콜 – IMAP(Internet Messaging Access Protocol) • POP3와 마찬가지로 메일을 사용자가 볼 수 있도록 해주는 프로토콜 • 서버에 메일 박스를 둘 수 있어서 메일을 사용자의 client로 다운로드 하지 않더라도 서버에서 메일 관리 가능 3 05 8.1 Email 서비스의 구성 요소 • mail 서비스 관련 프로그램 – MTA (Mail Transfer Agent) • SMTP 프로토콜을 이용하여 client에서 server로 메일 메시지 전송 • sendmail 등 – MUA (Mail User Agent) • 사용자PC(client)에서 메일을 보내고 받을 때 이용 • 윈도우의 아웃룩, Fedora Linux의 에볼루션 등 – MDA (Mail Delivery Agent) • 메일서버(MTA)에 도착한 메일을 사용자 메일박스(Mail Box)로 저장 • /bin/mail (mailx), procmail 등 – MRA (Mail Retrieval Agent) • 사용자 메일박스에서 Client프로그램(아웃룩 등)으로 메일을 받아오는 역할 • fetchmail, getmail, retchmail, dovecot 등 4 05 8.1 Email 서비스의 구성 요소 • 메일 송수신 과정 5 05 8.2 메일 서버 구축 • <실습 8-1> Fedora 20 서버 설치 – GUI 환경에서 메일서버를 설치 할 것이며 “Minimal Install” 모드 에서 실습을 원하는 경우 교재 324 ~367페이지 참조 6 05 8.2 메일 서버 구축 • 실습환경 예시 1 7 05 8.2 메일 서버 구축 • 실습환경 예시 2 8 05 8.2 메일 서버 구축 • 실습환경 예시 3 9 05 8.2 메일 서버 구축 • 실습환경 예시 4 1 0 05 8.2 메일 서버 구축 • <실습 8-2> yhkim.com DNS 서버 설치 – “실습환경 예시 4” 에서 구축(가상컴퓨터 램 용량을 적절히 조절) – DNS/MAIL Server 1 • yhkim.com 도메인 설정 – DNS/MAIL Server 2 • yh.com 도메인 설정 11 05 8.2 메일 서버 구축 • yhkim.com DNS 구축 – yum list bind – yum -y install bind.i686 – vi /etc/named.conf • listen-on port 53 { any; }; • allow-query { any; }; • recursion no; • zone “yhkim.com” IN { – type master; – file “yhkim.com.zone”; – allow-update {none;}; • }; 12 05 8.2 메일 서버 구축 • cd /var/named/ • ls • cp named.empty yhkim.com.zone • vi yhkim.com.zone – $TTL 3H – @ IN SOA @ root.
    [Show full text]
  • Bladecenter, Linux, and Open Source Blueprint for E-Business on Demand
    Front cover IBM Eserver BladeCenter, Linux, and Open Source Blueprint for e-business on demand Discover open source projects to reduce cost and improve reliability Install and configure Linux and critical open source network services Learn best practices to implement reliable services George Dolbier Peter Bogdanovic Dominique Cimafranca Yessong Johng Rufus Credle Jr. ibm.com/redbooks International Technical Support Organization IBM ^ BladeCenter, Linux, and Open Source: Blueprint for e-business on demand July 2003 SG24-7034-00 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. First Edition (July 2003) This edition applies to Red Hat Advanced Server 2.1. © Copyright International Business Machines Corporation 2003. 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 . vii Trademarks . viii Preface . ix The team that wrote this redbook. ix Become a published author . xi Comments welcome. xi Chapter 1. About the book: Blueprint for building an e-business application for BladeCenter. 1 1.1 Building an e-business infrastructure . 2 1.1.1 Materials . 2 1.1.2 Objectives . 3 1.2 IBM eServer™ BladeCenter . 3 1.3 FAStT SAN storage. 3 1.4 BladeCenter business value . 4 1.5 Linux business value. 4 1.6 Open source business value. 4 1.7 Other references . 5 Chapter 2. Architecture: Solution overview . 7 2.1 Open source e-business infrastructure a modular approach . 8 2.2 All construction projects start with a pattern . 8 2.2.1 Industry standard e-business pattern: A three-tier infrastructure .
    [Show full text]