DOCSLIB.ORG

Postfixpostfix 2 /Usr/Ports/Mail/Postfix • • Postfix V2.9.2 Postfix   Postfix Postfix

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Postfixpostfix 2 /Usr/Ports/Mail/Postfix • • Postfix V2.9.2 Postfix   Postfix Postfix PostfixPostfix 2 /usr/ports/mail/postfix http://www.postfix.org/documentation.html • • http://www.postfix.org Postfix v2.9.2 Postfix Postfix Postfix Computer Center, CS, NCTU 2 http://www.postfix.org/OVERVIEW.html Receive and deliverover email the network via SMTP Local delivery directly or use deliveryother agentmail • • • MTA that MTA Role Postfix of Role Postfix of Computer Center, CS, NCTU 3 C o m Postfix Architecture p Postfix Architecture u t e r C Modular-design MTA e n • Not like sendmail of monolithic system t e • Decompose into several individual program that each one handle r , specific task C S • The most important daemon: master daemon , Reside in memory N Get configuration information from master.cf and main.cf C T Invoke other process to do jobs U Major tasks • Receive mail and put in queue • Queue management • Delivery mail from queue 4 C o m PostfixPostfix ArchitectureArchitecture –– p u t MessageMessage ININ e r C Four ways e • Local submission n t postdrop command e r maildrop queue , C pickup daemon S cleanup daemon Local submission , – Header validation N – address translation C T incoming queue U • Network submission smtpd daemon • Local forwarding Resubmit for such as .forward Envelope “to” is changed • Notification 5 Network submission C o m PostfixPostfix ArchitectureArchitecture –– p u t QueueQueue e r C Five different queues e • incoming n t The first queue that every incoming email will stay e r • active , C Queue manager will move message into active queue whenever there is enough S system resources , Queue manager then invokes suitable DA to delivery it N C • deferred T Messages that cannot be delivered are moved here U These messages are sent back either with bounce or defer daemons • corrupt Used to store damaged or unreadable message • hold 6 http://www.postfix.org/QSHAPE_README.html#queues C o m PostfixPostfix ArchitectureArchitecture –– p u t MessageMessage OUTOUT –– PartPart II e r C Address classes e • Used to determine which destinations to accept for delivery n t e • How the delivery take place r , Main address classes C S • Local delivery , Domain names in “mydestination” is local delivered N C Ex: T – mydestination = nasa.cs.nctu.edu.tw localhost U It will check alias and .forward file to do further delivery • Relay Transfer mail for others to not your domain It is common for centralize mail architecture to relay trusted domain • Deliver mail to other domains for authorized user The queue manager will invoke the smtp DA to deliver this mail • Virtual alias • 7 Virtual mailbox s sendmail command command sendmail s ’ [email protected] ([email protected]) [email protected] Helene compose mail using her MUA, and then call postfix and then call MUA, using her mail compose Helene to it send [email protected] [email protected] Phase1: • • Example Message Flow in (1) Message Flow Postfix Message Flow in (1) Message Flow Postfix Computer Center, CS, NCTU 8 [email protected] The smtpd on postfix.org takes this The message and smtpd on invoke postfix.org cleanup then put in incoming queue find that frank is an alias,The so localit resubmits it DA through cleanup daemon for further delivery [email protected] [email protected] Phase2: • • Example Message Flow in (2) Message Flow Postfix Message Flow in (2) Message Flow Postfix Computer Center, CS, NCTU 9 [email protected] The smtpd on onlamp.com takes this message and invoke cleanup then put in incoming queue Local delivery to message store [email protected] [email protected] Phase3 • • Example Message Flow in (3) Message Flow Postfix Message Flow in (3) Message Flow Postfix Computer Center, CS, NCTU 10 C o m Message Store Format p Message Store Format u t e r C The Mbox format e • n Store messages in single file for each user t e • Each message start with ªFrom º line and continued with message headers r , and body C • Mbox format has file-locking problem S , The Maildir format N C • Use structure of directories to store email messages T U • Each message is in its owned file • Three subdirectories - cur, new, and tmp • Maildir format has scalability problem locate and delete mails quickly, but waste amounts of fd, inodes, space Problems of quota and backup Related parameters (in main.cf) • mail_spool_directory = /var/mail (Mbox) • mail_spool_directory = /var/mail/ (Maildir) 11 C o m Postfix & POP3/IMAP p Postfix & POP3/IMAP u t e r C POP3 vs. IMAP e n • Both are used to retrieve mail from server for remote clients t e • POP3 has to download entire message, while IMAP can download r , C headers only S • POP3 can download only single mailbox, while IMAP can let you , N maintain multiple mailboxes and folders on server C T Postfix works together with POP3/IMAP U • Postfix and POP3/IMAP must agree on the type of mailbox format and style of locking Standard message store Non-standard message store (using LMTP) – Such as Cyrus IMAP or Dovecot 12 C o m Postfix Configuration p Postfix Configuration u t e r C Two most important configuration files e n • /usr/local/etc/postfix/main.cf – postconf(5) t e Core configuration r , C • /usr/local/etc/postfix/master.cf – master(5) S Which postfix service should invoke which program , N C Edit main.cf T • U Using text editor • postconf % postconf [–e] "myhostname = nasa.cs.nctu.edu.tw" % postconf –d myhostname (print default setting) % postconf myhostname (print current setting) Reload postfix whenever there is a change • # postfix reload 13 C o m PostfixPostfix ConfigurationConfiguration –– p u t LookupLookup tablestables (1)(1) e r C Parameters that use external files to store values e • n Such as mydestination, mynetwork, relay_domains t e • Text-based table is ok, but time-consuming when table is large r , Lookup tables syntax C S • Key values % postconf -m , btree N Database format cidr C • % postconf ±m environ T hash U List all available database format internal • In main.cf proxy regexp default_database_type static % postconf default_database_type tcp default_database_type = hash texthash % postconf -h default_database_type unix hash • http://www.postfix.org/DATABASE_README.html 14 C o m PostfixPostfix ConfigurationConfiguration –– p u t LookupLookup tablestables (2)(2) e r C Use databased-lookup table in main.cf e • n syntax t parameter = type:name e r , • Ex: C In main.cf S , canonical_maps = hash:/usr/local/etc/postfix/canonical N After execute postmap C /usr/local/etc/postfix/canonical.db T U postmap command • Generate database # postmap hash:/usr/local/etc/postfix/canonical • Query % postmap ±q nctu.edu.tw hash:/usr/local/etc/postfix/canonical 15 C o m PostfixPostfix ConfigurationConfiguration –– p u t LookupLookup tablestables (3)(3) e r C Regular expression tables e n • More flexible for matching keys in lookup tables t e Sometimes you cannot list all the possibilities r , C • Two regular expression libraries used in Postfix S POSIX extended regular expression (regexp, default) , N Perl-Compatible regular expression (PCRE) C T • Usage U /pattern/ value Do some content checks, such as – header_checks – body_checks Design some features – /(\S+)\.(\S+)@nasa\.cs\.nctu\.edu\.tw/ [email protected] 16 C o m PostfixPostfix ConfigurationConfiguration –– p u t CategoriesCategories e r C Categories e • n Server identities t my... e r , • Mail rewriting C for incoming/outgoing mails S , • Access control N restrictions C T • Mail processing U filter • Operation details … 17 C o m PostfixPostfix ConfigurationConfiguration –– p u t MTAMTA IdentityIdentity e r C Four related parameters e • n myhostname t myhostname = nasa.cs.nctu.edu.tw e r , If un-specified, postfix will use ‘hostname’ command C • mydestination S , List all the domains that postfix should accept for local delivery N mydestination = $myhostname, localhost.$mydomain $mydomain C T – This is the CS situation that mx will route mail to mailgate U mydestination = $myhostname www.$mydomain, ftp.$mydomain • mydomain mydomain = cs.nctu.edu.tw If un-specified, postfix use myhostname minus the first component • myorigin myorigin = $mydomain (default is $myhostname) 18 C o m PostfixPostfix ConfigurationConfiguration –– p u t System-wideSystem-wide aliasesaliases filesfiles e r C Using aliases in Postfix (first-matching) e • n alias_maps = hash:/etc/aliases t e • alias_maps = hash:/etc/aliases, nis:mail.aliases r , • alias_database = hash:/etc/aliases C Tell newaliases command which aliases file to build S , To Build alias database file N C • % postalias /etc/aliases T U Alias file format (same as sendmail) • RHS can be Email address, filename, |command, :include: Alias restriction • allow_mail_to_commands = alias, forward • allow_mail_to_files = alias, forward 19 C o m PostfixPostfix ConfigurationConfiguration –– p u t VirtualVirtual AliasAlias MapsMaps e r C Virtual Alias Map e n • It recursively rewrites envelope recipient addresses for all local, all t e virtual, and all remote mail destinations. r , • C virtual_alias_domains = $virtual_alias_maps (default) S • virtual_alias_maps = hash:/usr/local/etc/postfix/virtual , N src-address dst-address C [email protected] @chbsd.cs.nctu.edu.tw T U chwong [email protected] @csie.nctu.edu.tw @cs.nctu.edu.tw • Applying regular expression virtual_alias_maps = pcre:/usr/local/etc/postfix/virtual /^root(\..+)?@(t)?(cs|np)?bsd\d*\.cs\.nctu\.edu\.tw$/ [email protected] /^root(\..+)?@(t)?(cs|np)?linux\d*\.cs\.nctu\.edu\.tw$/ [email protected] /^root(\..+)?@(t)?csmail\w*\d*\.cs\.nctu\.edu\.tw$/ [email protected] 20 C o m PostfixPostfix ConfigurationConfiguration –– p u t RelayRelay ControlControl (1)(1) e r C Open relay e n • A mail server that permit anyone to relay mails t e • By default, postfix is not an open relay r , C S , N A mail server should C • Relay mail for trusted user T U Such as [email protected] • Relay mail for trusted domain Ex.
Load more

Recommended publications
  • Unit 13 E-Mail and E-Messaging
    UNIT 13 E-MAIL AND E-MESSAGING Structure 13.0 Objectives 13.1 Introduction 13.2 E-mail 13.2.1 Defining Email 13.2.2 Need of Email 13.2.3 Email Address 13.3 Types of Email Services 13.3.1 Free Web-based Email Services 13.3.2 Priced Web-based Email Services 13.3.3 Private Email Services 13.4 Types of Email Account 13.4.1 POP/IMAP Account 13.4.2 Email Forwarder 13.4.3 Mailing List 13.4.4 Auto Responder 13.4.5 Email Bouncer 13.4.6 Email Blackhole 13.5 Structure and Features of Email 13.5.1 Header 13.5.2 Body 13.5.3 Features 13.6 Functioning of Email Systems 13.6.1 Protocols 13.6.2 Delivery Agent 13.6.3 Access Client 13.6.4 Setting up Account 13.6.5 Folder Management 13.7 Messaging 13.7.1 Instant Messaging 13.7.2 Unified Messaging 13.8 Issues with Messaging 13.8.1 Spamming 13.8.2 Privacy 13.8.3 Security 13.9 Widgets and Utilities 13.10 Summary 13.11 Answers to Self Check Exercises 13.12 Keywords 13.13 References and Further Reading 5 Internet Tools and Services 13.0 OBJECTIVES After reading this Unit, you will be able to: provide a detailed account about Email and Email service Providers; explain in detail various Protocols used in Email service; and discuss about Web 2.0 tools in Email. 13.1 INTRODUCTION Electronic Mail is one of the most prominent uses of networked communication technology.
    [Show full text]
  • Set up Mail Server Documentation 1.0
    Set Up Mail Server Documentation 1.0 Nosy 2014 01 23 Contents 1 1 1.1......................................................1 1.2......................................................2 2 11 3 13 3.1...................................................... 13 3.2...................................................... 13 3.3...................................................... 13 4 15 5 17 5.1...................................................... 17 5.2...................................................... 17 5.3...................................................... 17 5.4...................................................... 18 6 19 6.1...................................................... 19 6.2...................................................... 28 6.3...................................................... 32 6.4 Webmail................................................. 36 6.5...................................................... 37 6.6...................................................... 38 7 39 7.1...................................................... 39 7.2 SQL.................................................... 41 8 43 8.1...................................................... 43 8.2 strategy.................................................. 43 8.3...................................................... 44 8.4...................................................... 45 8.5...................................................... 45 8.6 Telnet................................................... 46 8.7 Can postfix receive?..........................................
    [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]
  • Groupware Enterprise Collaboration Suite
    Groupware Enterprise Collaboration Suite Horde Groupware ± the free, enterprise ready, browser based collaboration suite. Manage and share calendars, contacts, tasks and notes with the standards compliant components from the Horde Project. Horde Groupware Webmail Edition ± the complete, stable communication solution. Combine the successful Horde Groupware with one of the most popular webmail applications available and trust in ten years experience in open source software development. Extend the Horde Groupware suites with any of the Horde modules, like file manager, bookmark manager, photo gallery, wiki, and many more. Core features of Horde Groupware Public and shared resources (calendars, address books, task lists etc.) Unlimited resources per user 40 translations, right-to-left languages, unicode support Global categories (tags) Customizable portal screen with applets for weather, quotes, etc. 27 different color themes Online help system Import and export of external groupware data Synchronization with PDAs, mobile phones, groupware clients Integrated user management, group support and permissions system User preferences with configurable default values WCAG 1.0 Priority 2/Section 508 accessibility Webmail AJAX, mobile and traditional browser interfaces IMAP and POP3 support Message filtering Message searching HTML message composition with WYSIWIG editor Spell checking Built in attachment viewers Encrypting and signing of messages (S/MIME and PGP) Quota support AJAX Webmail Application-like user interface Classical
    [Show full text]
  • Subnet Routing Replace Logo
    Outline INFOTECH Lecture IP Based Networks and Applications Manuscript: Edition Summer 2004 Additional material and information on the course is available at http://www.jcho.de/jc/IPNA/ Dr.-Ing. Joachim Charzinski [email protected] © Joachim Charzinski This slide set is distributed to support students of the University of Stuttgart who attend the IPNA lecture http://www.jcho.de/IPNA/ during summer term 2004. All other use requires written permission by Joachim Charzinski. IPNA – IP based Networks and Applications IPNA – IP based Networks and Applications Table of Contents (2) 2004 Edition Table of Contents 2004 Edition 4. Applications and Application Layer Protocols 4-1 4.1 Introduction 4-5 4.1.1 Design Principles 4-5 1. Introduction 1-1 4.1.2 Contents Delineation 4-6 1.1 Overview of the lecture 1-6 4.1.3 Client-Server Paradigm 4-9 4.1.4 Reply Codes 4-11 1.2 Internet History 1-26 4.1.5 Socket Concept 4-15 1.3 IP Standardisation 1-46 4.2 DNS 4-20 1.4 Networking Basics Refresher 1-55 4.3 E-Mail 4-28 1.4.1 Reference Model 1-56 4.3.1 SMTP 4-32 1.4.2 Circuit Switching and Packet Switching 1-59 4.3.2 MIME 4-37 1.4.3 Local Area Networks 1-65 4.3.3 POP3 4-39 1.4.4 Network Elements 1-76 4.3.4 IMAP 4-42 Questions 1-94 4.4 HTTP 4-43 4.5 Telnet 4-55 2. Network Layer et.
    [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]
  • Secure Your E-Mail Server on IBM Eserver I5 with Linux
    IBM Front cover Secure Your E-mail Server on IBM Eserver i5 with Linux Understanding security issues for network and e-mail server Linux open source solutions to secure your e-mail server Linux-based ISV solutions to secure your e-mail server Yessong Johng Alex Robar Colin McNaught Senthil Kumar ibm.com/redbooks Redpaper International Technical Support Organization Secure Your E-mail Server on IBM Eserver i5 with Linux October 2005 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. First Edition (October 2005) This edition applies to IBM i5/OS V5R3, SUSE LINUX Enterprise Server 9, and Red Hat Enterprise Linux AS Version 4. © Copyright International Business Machines Corporation 2005. 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 Redpaper . ix Become a published author . xi Comments welcome. xi Part 1. Open Source Solutions for Network Security . 1 Chapter 1. Understanding and planning e-mail server security. 3 1.1 Concepts: Securing e-mail servers . 4 1.1.1 Linux-based firewall . 6 1.1.2 E-mail security . 7 1.2 Scenarios: Securing e-mail server . 8 1.2.1 Open source protection and open source mail delivery . 8 1.2.2 Open source protection and Domino . 9 1.2.3 ISV protection, open source filtering, and open source mail delivery . 10 1.3 Planning: Securing e-mail server . 11 1.3.1 OSS versus ISV solutions for network security mechanisms .
    [Show full text]
  • Oracle Communications Unified Communications Suite Certificate Authentication Guide, Release 7.0.6
    Oracle® Communications Unified Communications Suite Certificate Authentication Guide Release 7.0.6 July 2015 Oracle Communications Unified Communications Suite Certificate Authentication Guide, Release 7.0.6 Copyright © 2007, 2015, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
    [Show full text]
  • How Qmail Works
    APPENDIX A How qmail Works You DON'T NEED TO UNDERSTAND how qmail works to install or use qmail. And you don't have to be an auto mechanic to operate a car or a watchmaker to tell time. Eut if you really want to master qmail, knowing exactly how it does what it does is crucial. Luckily, qmail's simple, modular design makes understanding how it works easy for a system as complex as a Mail Transfer Agent (MTA). This appendix takes a top-down approach: first looking at how the modules interact with each other, then looking at how each module does its job. High-Level Overview The grand division in qmail is between the modules that accept new messages and place them into the queue and the modules that deliver them from the queue. We'll call these functions receivingand sending. The separation between receiving and sending is complete: Either of these functions can be fully oper­ ational while the other is shut down. Figure A-l shows the high-level organization of qmail. Incoming Receiving Queue Sending Delivered Messages Messages Figure A -1. High-level qmail organization Receiving Messages enter the queue through two main routes: local injection using qmail-inject or sendmail and network injection using qmail-smtpd, qmail-qmtpd 417 AppendixA or qmail-qmqpd. Both ofthese routes use qmail-queue to actually inject their mes­ sages into the queue. Figure A-2 shows the organization ofthe receiving function. QMQP tcpserver QMTP tcpserver SMTP tcpserver Queue Local------------­ MUA Figure A-2. The receivingfunction Sending Messages are delivered from the queue through two main routes: local delivery using qma il-loca 1 and remote delivery using qma il-remote.
    [Show full text]
  • Network Security & Auditing BSD Magazine
    CONTENTS Dear Readers, The January issue opens another year with BSD Magazine. We hope you enjoyed the last few. We start with a second part of our new light-hearted and non- Editor in Chief: technical column. Its aim is not to learn but to entertain and to Ewa Dudzic [email protected] inspire some reflection and (maybe) action. In Developers Corner Dru Lavigne reviewed the 2012 of BSD. Supportive Editor Read it to recall the most important events, publications and Patrycja Przybyłowicz releases of the last year. [email protected] This time the flag article is about panoramic photography. You Contributing: will have an opportunity to try it out with tools available under a Dru Lavigne, Rob Somerville, Luca Ferrari, William Olson, BSD or any Unix like system, using only free open source software. Carlos E. G. Carvalho In the ‘How To’ section you have a chance to read another part Top Betatesters & Proofreaders: of PostgreSQL series about users and permissions managements. Barry Grumbine, Darren Pilgrim, Eric Geissinger, From the tutorials you will also learn how to ignore spam in Henrik Andersén, Imad Soltani, Luca Ferrari, Luiz Claudio 2013, since we get it more and more with each year. Pacheco, Mani Kanth, Rob Cabrera, Zander Hill Especially for administrators we start a new series, where Rob Somerville will look at the tools, processes and methods involved Special Thanks: in writing software, including developing a Content Management Denise Ebery System (CMS) which will run under an AMP stack on FreeBSD, Art Director: OpenBSD and Linux. Ireneusz Pogroszewski We wish you a good read! DTP: Ireneusz Pogroszewski [email protected] Post Scriptum Senior Consultant/Publisher: Many thanks to iXsystems Company and its employees for their Paweł Marciniak [email protected] support and contribution.
    [Show full text]
  • Mini-HOWTO Install Qmail with MH
    mini−HOWTO install qmail with MH mini−HOWTO install qmail with MH Table of Contents mini−HOWTO install qmail with MH..............................................................................................................1 Christopher Richardson ([email protected]).......................................................................................1 1. Introduction..........................................................................................................................................1 2. My System Details...............................................................................................................................1 3. Qmail Installation................................................................................................................................1 4. MH Installation....................................................................................................................................1 5. Fetchmail.............................................................................................................................................1 6. Exmh....................................................................................................................................................1 7. Procmail...............................................................................................................................................1 8. ISDN....................................................................................................................................................1
    [Show full text]
  • Mail Server for a VPS: Postfix, Dovecot, Spamassassin, Policyd-Weight
    Mail server for a VPS: Postfix, Dovecot, Spamassassin, policyd-weight Full featured mail server with memory footprint small enough even for a VPS, with dovecot, postfix, spamassassin, clamav, policyd-weight with all the configs you need. UPDATE, 2014-12-18 I've recently wrote an updated version of a similar, better setup[^1]. UPDATE, 2012-02-25 I've updated my system to Dovecot 2, and removed ClamAV from the whole line. I haven't received any virus mails in the last 4 years, also they usually end up as spam, and ClamAV was eating up ~300 MB memory total (50 RAM, 250 swap). For nearly 5 years, I always used Virtualmin GPL[^2] everywhere I could, because I did not had to configure many features myself, it came with pre-configs and really good backend scripts. But as always, it had a price: memory and CPU usage, what is luxury in the world of VPS[^3]'. I tried to look for the best solution to handle emails, filtering them for spam and virus, and the only system I came across with was always Amavisd[^4]. amavisd is basically a wrapper for spam and virus filtering: it can simultaneously use more than one for both purpose, and most people say it's a nice program. Unfortunately, I tried to configure it, not just use it, and for me it was hell. I've known that Perl is somewhat evil[^5], but configuring amavisd is a mess at all, so I searched for a way to bypass it. It wasn't easy, but in the depth of the postfix forums, I've found out, that postfix is able to pass the mail to a program than catch the output and pass to another program and so on.
    [Show full text]