PUBLIC MARKS with tags postfix & mail

Tiger = sudo service smtp start, Leopard = sudo postfix start

The configuration described here is not very complicated but still needs to be done carefully. You are expected to have at least basic knowledge of: * MySQL (creating a database, granting access to users, basic SQL queries) * SMTP (what it is and what a basic SMTP dialog looks like) * POP3, IMAP (what they do and what the differences are) * basic Postfix configuration (understand the default settings in your main.cf, have read through the basic configuration document and know that your mail log file is at /var/log/mail.log) * Debian/Linux (general system administration, using a text editor, reading log files)

his document is derived from Christoph Haas’ tutorial “Howto: ISP-style Email Server with Debian-Etch and Postfix” (http://workaround.org) and Falko Timme’s tutorial “Virtual Users And Domains With Postfix, Courier, MySQL And SquirrelMail (Ubuntu 8.04 LTS)” (http://www.howtoforge.com). The associated Mailfix Drupal module must be installed as part of this tutorial. It will guide you through the necessary steps to configure a Drupal driven Mail server. Provided features: * Drupal managed email accounts * Support for virtual domains * Automatic forwarding * Postfix quota support * Silent BCC monitoring * Other features: anti-spam, anti-virus

To test and benchmark several common SMTP servers for Unix. This is inspired by the work done by Matthias Andree at his Postfix vs. qmail - Performance page. His information, while likely still highly relevant is based heavily around file system I/O and not overall performance of the MTA. Additionally, more MTAs and OSs will eventually be tested here.

You are not a Linux expert, Artica for Postfix allows you to install a full solution by one single command line: * Postfix: Main MTA * Kaspersky Anti-spam: powerfull Anti-spam provided by Kaspersky Inc * Kaspersky Anti-Virus * Bogofilter : Bayesian anti-spam * OpenLDAP: Database for main configuration and user management * emailrelay: little SMTP server (used as a content-filter) * SQLite library: zeroconf sql database engine with high perfomances. * Cyrus-imap: powerfull MDA System * Procmail: MDA Filter * Fetchmail: Email retreival * DnsMasq:DNS forwarder and DHCP server * Mailman:Mailing List manager * Sieve: End-user mail filters * Yorel script: Statistics of yorel * QueueGraph: Statistics for postfix * MailGraph: Statistics for postfix * AWSTats and geoip plugin: Statistics set for postfix * renattach: attachments filter

Ce billet explique rapidement comment installer un serveur mail secondaire ou appellé aussi MX (Mail eXchanger) secondaire, serveur de relai avec Postfix.

La série d'articles de cette rubrique est entièrement dédiée à la mise en oeuvre d'un serveur de mail basé sur Postfix et Cyrus-Imap. Ces deux éléments sont tout simplement ce qui ce fait de mieux actuellement dans leur domaine respectif: * Postfix : protocole smpt ou smtps pour le mode sécurisé * Cyrus imap : protocole POP3 ou POP3S (mode sécurisé) ou IMAP ou IMAPS (mode sécurisé).

This document requires Postfix version 2.0 or later. This document gives an overview of how Postfix can be used for hosting multiple Internet domains, both for final delivery on the machine itself and for the purpose of forwarding to destinations elsewhere. The text not only describes delivery mechanisms that are built into Postfix, but also gives pointers for using non-Postfix mail delivery software.

This HOWTO enables you to build a complete open source turn-key email server in a matter of hours (instead of days or weeks). In one sense it is more like one big script that requires intervention. It can be considered a howto if one reads the contents of each patch and script I provide.

This document describes how to integrate ASSP (Anti-Spam SMTP Proxy) with embedded ClamAV into a mail server based on Postfix featuring virtual users and domains, i.e. users and domains that are in a MySQL database.

n this tutorial I will show how you can set up a Postfix mailserver as a backup mail exchanger for a domain so that it accepts mails for this domain in case the primary mail exchanger is down or unreachable, and passes the mails on to the primary MX once that one is up again.

J'ai donc décidé de prendre le taureau par les cornes, et j'ai mis en place du greylisting [3] Le principes et simple: chaque mail qui arrive est d'abord refusé par postfix, qui stocke dans une base de donnée l'adresse IP de l'expéditeur, l'adresse email de l'expéditeur, et l'adresse email du destinataire. Tout serveur SMTP "réglo" va tenter plus tard un nouvel envoi, qui sera alors accepté. Les spammeurs, eux, majoritairement, ne feront pas de nouvel envoi.

This tutorial shows how to set up a Debian Etch (Debian 4.0) based server that offers all services needed by ISPs and hosters: Apache web server (SSL-capable), Postfix mail server with SMTP-AUTH and TLS, BIND DNS server, Proftpd FTP server, MySQL server, Courier POP3/IMAP, Quota, Firewall, etc. This tutorial is written for the 32-bit version of Debian Etch, but should apply to the 64-bit version with very little modifications as well.