DOCSLIB.ORG

Simple Mail Transfer Protocol

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Simple Mail Transfer Protocol SIMPLE MAIL TRANSFER PROTOCOL Иванов В.В.1, Черкасов Д.Ю.2 1Иванов Вадим Вадимович – студент института кибернетики, Российский Технологический Университет (Московский Институт Радиотехники Электроники и Автоматики) 2Черкасов Денис Юрьевич – студент института кибернетики, Российский Технологический Университет (Московский Институт Радиотехники Электроники и Автоматики) г. Москва, Российская Федерация Аннотация: SMTP является протоколом для передачи электронной почты. В отличие от стандартного POP3, данный сервер ориентирован преимущественно на передачу, хотя имеется возможность и получения письма по определенному адресу в рамках протокола. SMTP широко применяется большинством современных почтовых сервисов. Ключевые слова: SMTP, почта, протокол, сервер, информация. SIMPLE MAIL TRANSFER PROTOCOL Ivanov V.V.1, Cherkasov D.Y.2 1Ivanov Vadim Vadimovich– student of the Institute of Cybernetics, Russian Technological University (Moscow Institute of Radio Engineering of Electronics and Automation) 2Cherkasov Denis Yurievich– student of the Institute of Cybernetics, Russian Technological University (Moscow Institute of Radio Engineering of Electronics and Automation) Moscow, Russian Federation Annotation: SMTP server is a protocol for sending e-mail. Unlike standard POP3, this server is oriented mainly to the transfer, although it is possible to receive a letter to a certain address within the protocol. SMTP is widely used by most modern mail services. Key words: SMTP, mail, protocol, server, information.. УДК 004 Электронный журнал «Столица Науки» СЕНТЯБРЬ 2(2) SMTP (Simple Mail Transfer Protocol) is a widely used network protocol for sending e-mail on TCP / IP networks. While e-mail servers and other messaging agents use SMTP to send and receive e-mail messages, user-level mail client applications typically use SMTP only to send messages to the mail server for relaying. To receive messages, client applications typically use either POP (Post Office Protocol), or IMAP (Internet Message Access Protocol), or proprietary systems (such as Microsoft Exchange and Lotus Notes / Domino) to access the accounting write your mailbox on the server. In the 1960s, various types of electronic communication were used. People connected with each other using systems designed for certain mainframes. When more and more computers became connected, especially in the US Government network, ARPANET, standards were developed to allow users on different systems to write electronic messages to each other. These standards, developed in the 1970s, became the basis for SMTP. Further implementations include FTP Mail and Mail Protocol, developed in 1973. Development continued throughout the 1970s until ARPANET was transformed into a modern Internet around 1980. In the same year, John Postel proposed the Mail Transport Protocol, , through which FTP has ceased to be the basis for the transfer of mail. SMTP is published in RFC 821 (also written by Postel) in August 1982. The SMTP standard was developed around the same time as Usenet, a data network that has some similarities with SMTP. SMTP became widely used in the early 1980s. At that time, it was a complement to Unix Unix to Unix CoPy (UUCP), which was more suitable for processing the transfer of electronic messages between periodically connected devices. On the other hand, SMTP works fine when both sending and receiving devices are connected on the network all the time. Both devices use the storage and forwarding mechanism and are an example of push-technology (pushing technology). Although the Usenet newsgroups are still distributed between the servers using UUCP, the UUCP mail actually disappeared along with the "bang path" route (the host machine sequence on the network that the message should reach the destination) that were used as the routing headers. The article about rewriting the Электронный журнал «Столица Науки» СЕНТЯБРЬ 2(2) sender contains technical background information on the history of early SMTP and routing from source to RFC 1123. Sendmail was one of the first (if not the first) message forwarding agent in which SMTP was implemented. Other popular server programs supporting SMTP include Postfix, qmail, Novell GroupWise, Exim, Novell NetMail, Microsoft Exchange Server, Sun Java System Messaging Server. The provision of messages (RFC 2476) and SMTP-AUTH (RFC 2554) were introduced in 1998 and 1999. and described new trends in the transmission of electronic messages. Initially, SMTP servers were usually internal to the organization, receiving messages from organizations from outside and relaying the organization's messages to the external environment. But over time, SMTP servers (messaging agents), in fact, expanded their functions and eventually became messaging agents for custom email applications, some of which now relayed mail from outside the organization (for example, the company manager, while on a trip , wants to send an e-mail message using a corporate SMTP server) [1]. This issue, being a consequence of the rapid development and popularity of the World Wide Web, means that SMTP should have included special rules and methods for relaying messages and authorizing users to prevent abuses such as junk mail (spam) relaying [2]. Since this protocol was initially with a text (ASCII) interface, it did not work well with binary files and symbols of many non-English languages. Standards such as Multipurpose Internet Mail Extensions (MIME) have been developed to encode binary files for transmission over SMTP. Sendmail agents developed after Sendmail, as a rule, also implemented the option of pure 8 bits, so that the "just send eight" alternative strategy can be used to transfer arbitrary text data (in any eight-bit ASCII-like character encoding) via SMTP. However, there was still the problem of krakozabr [en], caused by the different display of character sets from manufacturers, although the mail addresses themselves still allowed to use exclusively ASCII. Today, transfer agents that work with clean 8 bits tend to support the 8BITMIME extension, which allows the transfer of binary files almost as easily as plain text. Recently, an SMTPUTF8 Электронный журнал «Столица Науки» СЕНТЯБРЬ 2(2) extension was created to support UTF-8 encoded text, which made it possible to include international content and addresses using alphabets such as Cyrillic or Chinese. Many outstanding people have contributed to the specification of the main SMTP, including John Postel, Eric Ollman, Dave Crocker, Ned Fried, Randall Gellens, John Clensin and Keith Moore. SMTP function is implemented in modern TCP / IP networks. For the first time information about the use of the protocol appeared in 1982. Despite the fact that the SMTP server can be used for receiving messages, today most mail clients use it only for sending, preferring other technologies (for example, POP or IMAP) to receive information. The protocol is one of the most popular and is used by an overwhelming number of mail programs and servers. The function of SMTP is to check the correctness of the settings and parameters for sending a message. This protocol verifies the settings of the user's computer trying to send messages, and then the delivery is performed, if all the settings were performed correctly. After that, the SMTP operation does not end and the server waits for a message on the successful delivery of the data. If the message can not be delivered for some reason, a corresponding message is sent to the sender. SMTP setup The SMTP setup consists of installing the necessary software and determining the address of the server used for sending. To send from the user's side, it is required to install a client program that can send messages and communicate with the SMTP server via TCP / IP. After that, the program is launched and configured to work with the service to send and receive mail by specifying the desired settings. Then the user tries to send a message. If the setting is correct, the message will be delivered to the recipient. Most modern email services already have customized servers for sending messages. If you do not use third-party email software, you can send an email without making any additional settings on the site of the service where you have an account. Modern SMTP server administrators require users to authenticate before they can send their message. The user must first specify his login and password on the server, and only then go to the shipment. This protection is used to block the possibility of sending spam using simple SMTP protocols. Previously, for the identification in the SMTP protocol, the unique IP address of the sender was used. Электронный журнал «Столица Науки» СЕНТЯБРЬ 2(2) Bibliography 1. Johnson, K. Internet Email Protocols: A Developer's Guide. — Addison-Wesley Professional, 2000. — ISBN 0-201-43288-9. 2. Hughes, L. Internet e-mail Protocols, Standards and Implementation. — Artech House Publishers, 1998. — ISBN 0-89006-939-5. Электронный журнал «Столица Науки» СЕНТЯБРЬ 2(2) .
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]