Share E-Book
Scan to open this page

Scan with your phone to open this page

Author: Dianna Mullet, Kevin Mullet

Rating No ratings yet

Virtually everything--not just computers, but every kind of device--is coming on board the Internet, and the two principal applications are the World Wide Web and email. The POP3 model for online-only messaging is being taxed to its limit, and users clearly would like mail servers with more "oomph." More specifically, the demand is for email servers that take advantage of centralized resources to manage mail, rather than heap more tasks on end-user computers. This clamor has resulted in the IMAP protocol being incorporated into virtually every major email server on the market. Those who haven't already installed IMAP are probably planning to do so.Managing IMAP is a movable feast of IMAP help. It is a handy guide for everyday tasks common to most IMAP servers as well as a concise reference to help navigate the sometimes sparsely and obtusely documented open source software. Whether the goal is more insight into the IMAP server and client or utility software, or big-picture strategic suggestions to get off a legacy system, Managing IMAP is here to help.This book is both a conceptual and a mechanical IMAP road map. Managers, system integrators, and system administrators on the front lines of Internet messaging will find it a valuable tool for IMAP system provision, maintenance and support. It is also useful if you're considering IMAP for your messaging system. Managing IMAP covers the IMAP protocol, setting up a client, IMAP security, performance monitoring, and tools. Several chapters are devoted specifically to two of the most popular servers: the University of Washington server and Cyrus, and detailed appendixes cover topics such as TCL, procmail, Sieve, and sendmail.

AI Reading Assistant

Whole-book reading guide from stratified index samples; jump to passages in the text

AI guide
【One-Line Pitch】 A practical, hands-on guide for system administrators and integrators who need to deploy, secure, and maintain IMAP-based email systems, covering both the University of Washington and Cyrus servers with real-world configuration advice. 【Book Arc】 - **Opening (~0%–9%)**: Introduces the Internet mail model, explaining the roles of MTA, MDA, and MUA, and why IMAP is replacing POP3 for centralized mail management. - **Early (~9%–28%)**: Explores IMAP’s three interaction models—online, offline, and disconnected—and compares them with POP, highlighting IMAP’s scalability for multi-device access and webmail backends. - **Early (~28%–38%)**: Profiles the two dominant open source servers—University of Washington’s reference implementation and Carnegie Mellon’s Cyrus—and begins client configuration with feature comparison tables. - **Middle (~38%–47%)**: Walks through setting up popular IMAP clients like PINE, Netscape Messenger, and Eudora, including folder subscriptions, expunging deleted mail, and remote configuration storage. - **Late (~47%–75%)**: Covers server administration for UW and Cyrus, including security, performance tuning, and monitoring, with practical advice on I/O, memory, and kernel adjustments. - **Ending (~75%–100%)**: Discusses advanced topics like remote configuration storage (IMSP, ACAP, LDAP), filtering tools (Sieve, procmail), and scaling strategies, plus appendices on TCL and sendmail integration. 【Key Takeaways】 - **IMAP’s core advantage is centralized mail storage** (Early): Unlike POP, which downloads mail to a single device, IMAP keeps archives on the server, enabling access from any platform—critical for multi-device users and webmail gateways. - **The disconnected model is a game-changer for mobile users** (Early): Clients sync mailboxes, cache messages, and queue actions offline, then replay them on reconnect—ideal for travelers or metered wireless connections. - **POP vs. IMAP is a user-constituency decision** (Early): POP suits single-computer users; IMAP shines when users access mail from multiple machines, though it demands far more server resources per read. - **Two open source servers dominate the landscape** (Early): The University of Washington server is the reference implementation by IMAP’s inventor, while Cyrus offers robust, time-tested alternatives—both rival commercial options. - **Client choice hinges on feature support** (Middle): A detailed comparison table shows that clients vary widely in SSL, Kerberos, disconnected mode, and remote configuration support—so matching client to server capabilities is essential. - **Configuration is often counterintuitive** (Middle): For example, Netscape Messenger hides expunge behind “Compact This Folder,” and PINE requires explicit folder-collection settings for multiple IMAP accounts—small details that trip up new users. - **Performance tuning is a systematic process** (Late): The book breaks down tuning by platform, I/O subsystem, memory, and kernel/network drivers, with clear signs for when to scale up and how to present metrics to management. 【Reading Tips】 - **Skim the early protocol chapters** (~0%–28%) if you already know IMAP basics; focus instead on the interaction models and POP comparison, which frame all later decisions. - **Deep-read the client configuration sections** (~38%–47%) if you support end users; the step-by-step guides for PINE, Messenger, and Eudora are practical and immediately applicable. - **Pay special attention to the server-specific chapters** (~47%–75%) if you’re deploying UW or Cyrus; these contain the most actionable administration and security advice. - **Treat the appendices as reference material**—TCL, procmail, Sieve, and sendmail are covered for integration scenarios, not as tutorials; skim them when you hit a specific need. - **Watch for dated specifics** (e.g., 2000-era client versions); focus on the underlying concepts and configuration patterns, which remain relevant even as software evolves. 【Coverage Limits】 This guide synthesizes excerpts covering roughly the first half of the book (protocols, clients, and early server topics); later chapters on advanced security, performance tuning, and remote configuration are only partially represented in the source material.
Page 8
............................................................................................. 234 Authentication ...............................................
View in text
Excerpt 2
inconvenienced by having to download them all to read them. If he gets 100 messages a day with sizable attachments, he’s going to wish he’d never heard of em...
View in text
Excerpt 3
ve stored your mail in a given format on a Unix system over * A reference to The Wizard of Oz. This is the Title of the Book, eMatter Edition Copyright © 200...
View in text
Excerpt 4
developed by Steve Dorner at the University of Illinois and began its life as a freeware POP client for the Macintosh. Qualcomm bought the rights to Eudora i...
View in text
Excerpt 5
ially become a problem if the underlying system is not well optimized (see Chapter 16, Server Performance Tuning, before planning your WING installation). Ev...
View in text
Excerpt 6
gn is a quite different approach to IMAP than the UW server. The UW server emphasizes personal mailboxes, while Cyrus supports both personal mailboxes and sh...
View in text
Excerpt 7
would look like this: 0 2 * * * /usr/cyrus/bin/deliver –E 3 The –E 3 argument, for example, tells deliver to prune the delivered database of entries older th...
View in text
Excerpt 8
named after the quota root, contains the quota root’s quota usage (in bytes) and quota limit (in kilobytes). Here is an example of a quota file: $ cd /var/im...
View in text
Tags
AI categories
Cloud NativeDevOpsTechnology
ISBN: 059600012X
Publisher: O'Reilly Media
Publish Year: 2000
Language: English
Pages: 408
File Format: PDF
File Size: 2.0 MB
Text Preview (First 20 pages)
Registered users can read the full content for free

Register as a Gaohf Library member to read the complete e-book online for free and enjoy a better reading experience.

Generating text preview…