DOCSLIB.ORG

Copyrighted Material

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Copyrighted Material Index Note to the reader: Throughout this index boldfaced page numbers indicate primary discussions of a topic. Italicized page numbers indicate illustrations. Symbols and Numbers access database, 156–161, 197 action field in, 159–161 ! (exclamation point) for UUCP bang address field in, 157–159 addressing, 188 address formats, 158 $: symbol in rewrite rules, 235–236 to block mail, 309–312 $@ symbol in rewrite rules, 235 creation, 311–312 $&x syntax, 184 linuxconf to create, 311, 312 $(database-spec$) syntax, 239 for relay controls, 304 $#discard mailer, 244 TLS actions in, 355 $#error mailer, 244, 313 access_db feature, 130, 132, 143, 157, $[hostname$] syntax, 238 376, 388 $>name syntax, 236–237 action field in access database, 159–161 to call rulesets, 221 AddDomain ruleset, 225 $#OK mailer, 244 address field in access database, 157–159 $v command syntax, 296 address test mode . (dot) character, 188–189, 228 commands, 281 =M command, 291 configuration file, 290–291 =S command, 291–292 debug setting during, 292–293 [ (bracket) character, 188–189 alias 7bit encoding, 19 defining personal mail, 153–154 8bit encoding, 19 for e-mail recipient, 46 8BITMIME, 21 in Sendmail, 47–48 aliases database, 138, 149–154 A input address processing through, 271 COPYRIGHTED MATERIALlocation for, 200 acceptable use policy, 300 preventing modification, 341 accept_unqualified_senders feature, for Red Hat, 150–151 376, 389 Sendmail instructions to rebuild, 126 accept_unresolvable_domains feature, 131, vs. user database, 155–156 306, 376, 389 aliases file, 47 436 AliasFile option in sendmail.cf – CANONIFY_DOMAIN command (m4) AliasFile option in sendmail.cf, 418 B ALIAS_FILE variable, 127, 132, 150 background daemon, starting sendmail AliasWait option in sendmail.cf, 418 as, 398 allmasquerade feature, 252, 376, 388 backup mail exchange server, 34 AllowBogusHELO option in base64 encoding, 19 sendmail.cf, 418 bestmx_is_local feature, 377, 381, 390 always_add_domain feature, 129–130, 132, binary encoding, 19 377, 381, 390 BIND software, 74 anonymous FTP to download RPM bitdomain database, 380 software, 64–65 bitdomain feature, 143, 144, 171, 377 anti-spam rule, defining, 311 .BITNET pseudo-domain, 125–126 APOP command (POP), 23, 329 BITNET_RELAY variable, 125–126, APPEND command (IMAP4), 27 265, 386 application media type (MIME), 16 blacklist_recipients feature, 130–131, 132, arguments for m4 macros, quoted strings, 96 158–159, 377, 388 Argv (A) field, in mailer definition, 209, 211 BlankSub option in sendmail.cf, 418 arith database, defining, 197 BSD-style Linux system, running Sendmail ASCII, e-mail support, 19 on, 53 asymmetric cryptography, 343 buffers for sendmail.cf file data, 93 audio media type (MIME), 16 bug fixes, 326 AUTH DIGEST-MD5, 22 Build command, to compile sendmail, 72–73 AUTH extension to SMTP, 344 build script, in cf/cf directory, 87–88 AUTH protocol, 342 auth server (identd), 300 AUTHENTICATE command (IMAP4), 26 C authentication, 343–344, 344–350 in relaying, 349–350 C.. command, 188 authentication client, 347–349 C[[ command, 188 authid (authentication identity), 347 C (define class) command, 182, 186– AuthMechanisms option in sendmail.cf, 418 190, 215 AuthOptions option in sendmail.cf, 418 CACERTFile option in sendmail.cf, 418 AutoRebuildAliases option in CACERTPath option in sendmail.cf, 418 sendmail.cf, 418 Caldera, 54. See also System-V-style Linux canon command, 290 canonify ruleset, 44, 220, 222, 223, 228, 243, 280 CANONIFY_DOMAIN command (m4), 362, 390 CANONIFY_DOMAIN_FILE command (m4) – comments 437 CANONIFY_DOMAIN_FILE command class variable O, 188 (m4), 362, 390 class variable P, 187–188 CAPABILITY command (IMAP4), 26 class variables, 416–417 case sensitivity, 153, 173, 195 loading from file, 190–191 certificate, 350 in pattern matching, 229 self-signed, 352 class w, 127 Index certificate authority adding value to, 187 locating, 352 failed test, 147–148 and public key cryptography, 350 class w variable, loading from file, 115–116 cf directory structure, 82–91 classes cf/cf directory, 85–88 in Sendmail, 186 contents, 86 setting and viewing, 287–288 cf/cf directory, build script, 87–88 ClassFactor option in sendmail.cf, 418 cf/domain directory, 85 ClassTest ruleset, 230 cf/feature directory, 90 cleanup after RPM software, 69–71 cf/hack directory, 83–84 client cf/m4 directory, 90–91 authentication, 347–349 cf/mailer directory, 89 mail, 38 cf/ostype directory, 88–89 problems from blocking relaying, 302 cf/sh directory, 84 Properties box for configuring, 38–39, 39 cf/siteconfig directory, 84 Sendmail as, 49 .cf file extension, 86 client-only.mc macro configuration file, 262 cfhead.m4 file, 92 client_addr variable, placing test value cf.m4 file, 91 in, 308 changes, dealing with, 117 ClientCertFile option in sendmail.cf, 419 Charset (C) field, in mailer definition, 210 ClientKeyFile option in sendmail.cf, 419 CHECK command (IMAP4), 27 ClientPortOptions option in CheckAliases option in sendmail.cf, 418 sendmail.cf, 419 check_mail ruleset, 222, 223 CLOSE command (IMAP4), 27, 29 CheckpointInterval option in ColonOkInAddr option in sendmail.cf, 419 sendmail.cf, 418 command-line options to test Sendmail, check_recpt ruleset, 222, 223 269–280 check_relay ruleset, 222, 223 -bv option, 270–271 chkconfig, to enable Sendmail, 58 hoststat command, 273–276 class E, 118 mailq command, 276–280 class M, 252 verbose option, 271–273 class R, 146, 191, 302, 303 comments class t, users in, 202 in m4 macro language, 94 438 compatibility of Sendmail configuration – Cyrus mailers in Red Hat aliases database, 151 confMAPDEF database, available from script lines, 53 options, 139 in sendmail.cf file, 182 confMAX_DAEMON_CHILDREN compatibility of Sendmail configuration, parameter, 335–336 75–76 confMAX_HEADERS_LENGTH compiling Sendmail variable, 132 with Build command, 72–73 confMAX_MESSAGE_SIZE, 337 checking options, 141 confSERVER_CERT parameter, 351 conditionals confSERVER_KEY parameter, 351 in D (define macro) command, 185–186 confTO_CONNECT variable, 126, 132 in m4 macro language, 110 confTRUSTED_USERS parameter, 202 in pattern matching, 231 confTRY_NULL_MX_LIST variable, 126– in procmail recipe, 317 127, 132 confAUTH_MECHANISMS parameter, 345 confUSERDB_SPEC variable, 127, 132, confAUTO_REBUILD variable, 126, 132 142, 154 confBINDIR parameter, 110 ConnectionCacheSize option in confCLIENT_CERT parameter, 351 sendmail.cf, 419 confCLIENT_KEY parameter, 351 ConnectionCacheTimeout option in confCONNECTION_RATE_THROTTLE, sendmail.cf, 419 336–337 ConnectionRateThrottle option in confCR_FILE variable, 142, 146 sendmail.cf, 419 confCW_FILE variable, 115 ConnectOnlyTo option in sendmail.cf, 419 confDEF_USER_ID variable, 125, 132, 338 Content-Transfer-Encoding header (MIME), confDONT_PROBE_INTERFACES vari- 19–20 able, 127, 132 Content:Type: header (MIME), 16–19 confEBINDIR variable, 128 ControlSocketName option in confFORWARD_PATH variable, 113–114 sendmail.cf, 420 confHOST_STATUS_DIRECTORY, COPY command (IMAP4), 27 273, 274 copyright notice in .m4 files, 109 config keyword for Sendmail error code, 244 cr file, 145 configuration file. See also sendmail.cf file cracked address, 284 build script to create multiple, 88 CREATE command (IMAP4), 26 forcing reload, 59 cryptography, 343–344 configuration variables for sendmail.cf ct file, 144 file, 96 Ctrl+Alt+Del, disabling, 323 confLDAP_DEFAULT_SPEC, 394 Cyrus mailers, 113–114, 392 D (define macro) command – deleting messages, with POP command 439 D virtusertable feature, 161–166. See also virtusertable feature D (define macro) command, 182–186, 215 database records in DNS, 33 conditional format, 185–186 DataFileBufferSize option in daemon mode for Sendmail, 51 sendmail.cf, 420 DAEMON variable for Sendmail script, 54 datagrams, 4 DAEMON_OPTIONS command (m4), 362, Index Date: header, 14 393–394 DeadLetterDrop option in sendmail.cf, 420 DaemonPortOptions option in Debian packages, 61 sendmail.cf, 420 debug levels, 293–297, 399–410 DATA command (SMTP), 5, 12 output of level 0.10, 294–295 data field in DNS database record, 33 output of level 35.9, 295 database files output of level 37.1, 296–297 access database, 156–161 DECNET_RELAY variable, 264, 386 adding support, 138–144 dedicated servers, 326 compiler options, 138–142 DefaultAuthInfo option in sendmail.cf, aliases database, 149–154. See also aliases 347, 420 database DefaultCharSet option in sendmail.cf, 420 bitdomain feature, 143, 144, 171, DefaultUser option in sendmail.cf, 338, 420 377, 380 defense in depth, 322 cr file, 145 define class (C) command, 182, 186– ct file, 144 190, 215 domaintable feature, 143, 171, 377, 380 define command (m4), 92, 362, 365 genericstable database, 169–171 to configure databases, 142–144 information retrieval using rewrite and FEATURE macros, 97 rules, 239 format for, 96 local-host-names file, 115, 116, 147–149 parameters, 367–376 mailertable, 128, 143, 166–169, 377, 380 in redhat.mc file, 125–127 defining, 197 to set directory path, 110 makemap command, 172–174. See also define header (H) command, 215 makemap command define macro (D) command, 182–186, 215 relay-domains file, 145–146, 191, conditional format, 185–186 302–303 define rule (R) command, 215, 226–242 role in Sendmail, 137 delay_checks feature, 377 user database, 154–156, 256 DELE command (POP), 23 uucpdomain feature, 143, 144, 171, DELETE command (IMAP4), 26 379, 380 deleting messages, with POP command, 25 440 deliverability of mail – DSN (Delivery Status Notifications) deliverability of mail, processing address to dnl command (m4), 92, 94, 362, 365 determine, 270
Load more

Recommended publications
  • Exchange Server Is a Microsoft S Messaging D Collaboration System
    What is Exchange Server? Exchange Server is a Microsoft͛s Messaging d collaboration system which provides Industry leading Email, calendaring and unified Messaging Solutions. What are the minimum hardware requirements for Exchange Server 2003? Processor ʹ Pentium 133 MHz Operating System ʹ Windows 2000 SP3 Memory ʹ 256 MB Disk Space ʹ 200 MB for system files and 500 MB where Exchange Server installation. File System ʹ NTFS What are the steps involved in Exchange Server installation? Prerequisites Installation ʹ ASP .Net, IIS, SMTP, NNTP and WWW services Installation Forest Preparation Domain Preparation Exchange Server 2003 Installation What are the differences between Exchange Sever 2003 Standard and Enterprise Editions? Standard Edition : 1 Storage group 2 Database per Storage Group 16 GB Limit per Database. Exchange Cluster is Not Supported. X.400 Connector is not included. Enterprise Edition 4 Storage Group 5 Databases per Storage Group 16 TB or limited to hardware Exchange Clustering is Supported. X.400 Connector is included. 5. What are the main differences between Exchange 5.5 and Exchange 2000/2003? - Exchange 2000 does not uses its own Directory Service as Exchange 5.5 but rely on Active Directory. - Exchange 2000/2003 uses native components of windows (SMTP, NNTP,Asp.net. IIS, W3SVC and many more) for many core functions. - Active/Active Clustering is now supported in Exchange 2000/2003 - It now provided better Conferencing and Instant Messaging Solution. Name a Few Configuration options for Exchange Recipients ? Exchange Recipient parameters are values/attributes which can change exchange recipients message behaviour. 1. MicrosoftExchangeRecipientEmailAddresses: This parameter specifies one or more email address for the same user, maybe internal email associated with external email.
    [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]
  • Concept of Mail Protocols Format of an Email Email Addressing
    Concept of Mail Protocols Format of an Email Email Addressing A unique addressing system ,has two parts in addressing. Local part defines user mailbox and domain name mention the destination [email protected] Email alias:Create a group email to send email to many people like multicast. Email message fields Here are the meanings of the fields to be filled in when you send an email: ● From: this is your email address; most of the time you will not have to fill in this field, because it is generally set by the email client according to your preferences. ● To: This field is used for the recipient's email address. ● Subject: this is the title that your recipients will see when they want to read the email ● Cc (carbon copy): this allows an email to be send to a large number of people by writing their respective addresses separated by commas ● Bcc (blind carbon copy): This is a Cc, except that the recipient does not see the list of people in the Bcc field ● Message: This is the body of your message Other email functions are: ● Attached Files, Attachments: A file can be attached to an email by specifying its location on the hard drive. ● Signature: If the email client allows it, you are often able to set a signature, meaning a few lines of text which will be added to the end of the document. Email Delivery Queue Unlike ftp/http it is not necessarily to deliver email in real time.Delivery not instantaneous ,It will wait in the queue of outgoing,incoming ,intermediate MTA message queue.
    [Show full text]
  • Exchange Server Fundamentals Every Email Administrator Should Know
    EXCHANGE SERVER FUNDAMENTALS EVERY EMAIL ADMINISTRATOR SHOULD KNOW Read this Guide to get essential knowledge on Exchange Server architecture, Exchange mail flow mechanism, Exchange planning & deployment, Exchange mailbox management, maintenance and more. © Copyright Stellar Information Technology Pvt. Ltd. All Trademarks Acknowledged. www.stellarinfo.com CONTENTS EXECUTIVE SUMMARY 01 WHAT IS EXCHANGE SERVER? 02 HOW DOES EXCHANGE SERVER WORK? 02 EXCHANGE SERVER ARCHITECTURE: AN OVERVIEW 04 EXCHANGE SERVER PLANNING 08 EXCHANGE SERVER DEPLOYMENT 13 MAILBOX SERVER MANAGEMENT IN EXCHANGE 14 EXCHANGE SERVER MAINTENANCE CHECKLIST 16 CLOSING NOTES 19 REFERENCES 19 EXCHANGE SERVER FUNDAMENTALS — GUIDE 00 EXECUTIVE SUMMARY Email is widely used in business communication to facilitate an immediate exchange of messages with a systematic trail across different email platforms. Unlike personal communication, where individuals may also use instant messengers, business communication mostly needs to rely on a “centralized email service” such as on-premises server to allow sending out messages, calendar invites, etc., daily. These email services allow 24x7 exchange of messages and data files among all users with valid email addresses, irrespective of their physical location, email platform, and network. Such global transmission of messages through any network is enabled and managed using a mail server such as Microsoft Exchange Server in the backend. A mail server or Message Transfer Agent (MTA) is a software that uses a communication protocol called Simple Mail Transfer Protocol (SMTP) to transmit the messages to and from other mail servers in the network. An enterprise mail server technology such as Exchange Server allows the frontend users to readily access the emails through an email client such as Microsoft Outlook, a web service, or mobile devices apart from other applications.
    [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]
  • ICS 451: Today's Plan
    ICS 451: Today's plan ● email – overview – structure ● protocols: – SMTP – POP – IMAP Email overview ● A mail client is used to prepare and read email – Message User Agent, MUA ● A mail server forwards and stores email – Message Transfer Agent, MTA – providing Message Handling Service, MHS ● Global service providing user-to-user transmission of messages – everything, including multimedia, encoded using 7-bit ASCII Email structure ● Email consists of a header and a body, separated by an empty line – similar to HTTP, but structure visible to user ● Each line in the header has the form field-name: field value – From, To, Subject, Date ● Received fields indicate the path of the message (see book, p. 39) ● Message-id unique for each message MIME ● Multipurpose Internet Mail Extension ● A way to send non-ASCII data across email – non-English text: 江戸 – multimedia: images, sounds, video ● Mime-Version, Content-Type ● Content-Transfer-Encoding: – quoted-printable (=xx is char xx, =3D is =) – base64 (6 bits per character A-Za-z0-9+/) ● padded with = to make multiple of 3 chars – 7bit Email Clients ● Used to prepare email and send it to the first server, and used to read email – local application or webmail ● Once email is composed, sent using Simple Mail Transfer Protocol, SMTP – server may be default server for machine – server may be given by MX record Typical email transmission ● Sender's MUA sends to local MTA (Mail Submission Agent, MSA) ● MSA sends to MTA indicated by MX record ● MTA sends to receiver's local MTA (Mail Delivery Agent, MDA,
    [Show full text]
  • Zimbra™ Collaboration Suite Administrator's Guide
    Zimbra™ Collaboration Suite Administrator’s Guide Release 6.0 Network Edition Rev: July 2010 Legal Notices Copyright 2005-2010 Zimbra. All rights reserved. No part of this document may be reproduced, in whole or in part, without the express written permission of Zimbra. Trademark and Licensing MySQL is a registered trademark of MySQL AB in the United States, the European Union and other countries. OpenLDAP is a registered trademark of the OpenLDAP Foundation. Postfix is copyright © 1999 International Business Machines Corporation and others and it was created by Wietse Venema <[email protected]>. SpamAssassin is a trademark of Deersoft, Inc. This product includes software developed by the Apache Software Foundation (http://www.apache.org/). All other marks are the property of their respective owners. Building Better Products within the Open Source Community Zimbra Collaboration Suite leverages many great technologies from the open source community: MySQL, OpenLDAP, Postfix, SpamAssassin, and Apache. Zimbra believes that great products come from contributing to and leveraging open source technologies. We are thankful for the great contributions that led to the creation of MySQL, OpenLDAP, Postfix, SpamAssassin, and Apache software. Zimbra, a division of VMware, Inc. 3401 Hillview Avenue Palo Alto , California 94304 USA www.Zimbra.com September 2009 - ZCS 6.0 Revised for 6.0.8 July 12, 2010 Table of Contents Chapter 1 Introduction. 11 Intended Audience . 11 Zimbra Collaboration Suite License . 11 Available Documentation . 12 Support for Recommended Third-Party Components . 12 Support and Contact Information . 12 Chapter 2 Product Overview . 15 Core Functionality . 15 Zimbra Components . 17 System Architecture . 17 Zimbra Packages .
    [Show full text]
  • Linux Sendmail Installation/Configuration
    Sendmail Installation & Configuration: (26 Jan 2006) SMTP (Simple Mail Transfer Protocol) Email Primer: An email address: emailId@domainà [email protected] à bms is email Id & iitk.ac.in is domain Mail client: A system from where a sender (person) can send an email using any email client like mail, mh, elm, pine, Netscape messenger, Mozilla, Outlook Express, Eudora, Horde, Squirrelmail etc. Mail host: It is able to decode any address and reroutes the mail within the domain. Relay Host: It manages communication with network outside the domain. If you want a local mail system for your organization then relay host is not required. A good system for relay host is a router to internet. Gateway: It is a system between differing communication networks, like a mail from a Unix user must pass through a gateway to reach a VMS user. Mail Server: A mail storage system. This server keeps all mail boxes in /var/spool/mail (Linux) or /var/mail (Solaris) Standard Practice: Practically only one machine can act as: (Mailhost + MailRelay+ MailServer). Another configuration: Use separate servers for incoming & outgoing mails. Email Address resolution: When email sender sends an email. Destination address will be match with sender’s local aliases kept in .mailrc|.addressbook (pine uses it)|.elm/aliases.text etc. In second step it will try to expand/resolve destination address using local /etc/mail/aliases In third step it will try to expand/resolve the address using NIS aliases (If NIS is running and aliases are kept in NIS database) In fourth step it will use /etc/mail/aliases of mailhost to expand the destination Address.
    [Show full text]
  • Rfc4409.Txt.Pdf
    Network Working Group R. Gellens Request for Comments: 4409 QUALCOMM Obsoletes: 2476 J. Klensin Category: Standards Track April 2006 Message Submission for Mail Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2006). Abstract This memo splits message submission from message relay, allowing each service to operate according to its own rules (for security, policy, etc.), and specifies what actions are to be taken by a submission server. Message relay and final delivery are unaffected, and continue to use SMTP over port 25. When conforming to this document, message submission uses the protocol specified here, normally over port 587. This separation of function offers a number of benefits, including the ability to apply specific security or policy requirements. Gellens & Klensin Standards Track [Page 1] RFC 4409 Message Submission for Mail April 2006 Table of Contents 1. Introduction ....................................................3 2. Document Information ............................................4 2.1. Definitions of Terms Used in This Memo .....................4 2.2. Conventions Used in This Document ..........................5 3. Message Submission ..............................................5
    [Show full text]
  • Email Authentication Via Domainkeys Identified Mail (DKIM)
    IronPort Email Authentication W H I T E P A P ER Executive Summary The problems of spam, viruses, phishing and most email denial-of-service attacks can all be traced back to a single common cause – lack of authentication in the email protocol SMTP. TABLE OF CONTENTS 1 Executive Summary This lack of authentication means that a receiving mail server cannot reliably 2 Definitions verify that a particular message is in fact from the sender it purports to be from, making it harder to identify friend from foe. 2 History 3 The Authentication Problem The industry has recognized this shortcoming, and a great deal of effort 4 Sender ID and DomainKeys has been put into developing a new standard that will “overlay” SMTP Identified Mail and provide the sender authentication that is so desperately needed. This 9 Adoption Status paper will present a brief history of how this problem evolved, explore the pluses and minuses of the leading standards proposals, and highlight some 10 Why Authenticate? recommendations. 11 The Solution To Bounce Attacks 11 IronPort Systems’ Adoption Recommendations 12 Appendix D O C R E V 0 2 . 0 8 1 IRONPORT EMAIL AUTHENTICATION WHITE PAPER DEFINITIONS Email nomenclature can be a bit confusing, so it is useful to start with some definitions. An email message has an addressing scheme similar to a postal message: HELO/EHLO: The initial contact command between a sending and a receiving mail server, indicating an SMTP conversation. Envelope sender: The address of the sending mail server; not exposed to the end-user, used for managing bounces.
    [Show full text]
  • Protecting Your Zimbra Collaboration Environment Zimbra Security and Privacy White Paper Table of Contents
    Protecting Your Zimbra Collaboration Environment Zimbra Security and Privacy White Paper Table of Contents The Zimbra Approach to Security and Data Privacy Open Source Commitment Adherence to Open Standards Flexible, Open Architecture Tour of the Security Life Cycle Identity and Access Management Information Security and Privacy Administration Zimbra Partner Ecosystem MTA-Level Integration Zimlets Conclusion Acronyms Protecting Your Zimbra Collaboration Environment The Zimbra Approach to Security and Data Privacy for improvements to security is no longer an option. Normal modes of businessWith the risecommunication of mobile and have cloud shifted computing, from personal sacrificing computers user experience to mobile devices. With this shift, organizations must update legacy messaging and collaboration systems to better address the changing threat and technology landscape. As a messaging and collaboration platform, Zimbra Collaboration is at the core of business communication, a mission-critical component of the organization’s information infrastructure. Since no two organizations are of any information security and technology program. the same, the need for flexible, extensible software is critical to the success What is open source software? Software licensed with a copyright Collaboration. As organizations look to create comprehensive compliance license compliant with the andThis governance paper explores practices, the native and proactivelysecurity and mitigate privacy maliciousfeatures of activity, Zimbra Zimbra’s approach to security and privacy will help guide evaluations of SoftwareOpen is distributed Source Definition. with its source Zimbra Collaboration as a cornerstone of your information infrastructure. code in a human readable format. Software is developed in an open and Open Source Commitment collaborative way by groups of developers. As a commercial open source vendor, Zimbra offers customers and partners accountability as well as transparency.
    [Show full text]
  • Zimbra Collaboration Administrator Guide
    Zimbra Collaboration Administrator Guide Zimbra Collaboration 8.7 Open Source Edition Legal Notices Copyright © 2016 Synacor, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. ZIMBRA is a trademark of Synacor, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. Synacor, Inc. 40 La Riviere Drive, Suite 300 Buffalo, New York 14202 www.synacor.com Zimbra Collaboration 8.7 April 2016 Table of Contents 1 Introduction . 13 Audience . 13 Third-Party Components . 13 Support and Contact Information . 13 2 Product Overview . 15 Architectural Overview . 15 Core Email, Calendar and Collaboration Functionality . 16 Zimbra Components . 16 Zimbra Application Packages . 17 Mail Flow—Multi-Server Configuration . 19 Zimbra System Directory Tree . 20 Zimbra Web Clients . 22 Security Measures . 23 Identity and Access Management . 23 Information Security and Privacy . 24 System Logs . 24 3 Licensing . 27 License Types . 27 License Requirements . 28 License Usage by Account Type . 28 License Activation . 29 Automatic License Activation . 29 Manual License Activation . 29 When Licenses are not Installed or Activated . 29 Obtain a License . 30 Managing Licenses . 30 License Information . 30 License Expiration . 31 Renewal . 31 Updating Your License . 32 4 Zimbra Mailbox Server . 33 Mailbox Server . 33 Message Store . 33 Data Store . 34 Index Store . 34 Web Application Server . 35 Mailstore Services . 35 User Interface Services . 35 Web Application Server Split . 35 Installation and Configuration of the Web Application Server Split . 35 Mailbox Server Logs . 36 5 Zimbra LDAP Service . .37 LDAP Traffic Flow .
    [Show full text]