Originally written in 1997 by Wietse Venema at the IBMThomas J. Watson Research Center in New York, and first released in December 1998,[3] Postfix continues as of 2022[update] to be actively developed by its creator and other contributors. The software is also known by its former names VMailer and IBM Secure Mailer.
The name Postfix is a compound of "post" (which is another word for "mail") and "fix"[citation needed] (which is for other software that inspired Postfix development).
In a study published on June 1, 2022 by E-Soft, Inc.,[4] approximately 34% of the 800 thousand reachable mail servers ran Postfix, making it the second most popular mail server behind Exim. However, this survey represents a much smaller sample than the 4 million domains that responded in a survey announced in December, 2021, by Lightmeter, Inc.[5] There, a scan of the IPv4 address space (excluding certain military ranges) found that of the 4 million domains that responded, 55% ran Postfix, 17% Exim. In a more recent Shodan census of 5 million services on port 25,[6] Postfix was detected 1.4 million times, Exim 0.4 million times (with Exim detected 1.1 million times on ports 465 and 587). Note: these surveys appear to sample different populations, and Shodan scans are often blocked.
Typical deployment
As an SMTP server, Postfix implements a first layer of defense against spambots and malware. Administrators can combine Postfix with other software that provides spam/virus filtering (e.g., Amavisd-new), message-store access (e.g., Dovecot), or complex SMTP-level access-policies (e.g., postfwd, milter-regex, policyd-weight).
As an SMTP client, Postfix implements a high-performance parallelized mail-delivery engine. Postfix is often combined with mailing-list software (such as Mailman).
This article or section uses color as the only way to convey important information. To meet Wikipedia's web accessibility guidelines, please help improve this article or section so it is easier to read by those with disabilities by adding an additional means for these readers to access the relevant information. See the guides to editing for accessibility at contrast and colors.
Postfix consists of a combination of server programs that run in the background, and client programs that are invoked by user programs or by system administrators.
The Postfix core consists of several dozen server programs that run in the background, each handling one specific aspect of email delivery. Examples are the SMTP server, the scheduler, the address rewriter, and the local delivery server. For damage-control purposes, most server programs run with fixed reduced privileges, and terminate voluntarily after processing a limited number of requests. To conserve system resources, most server programs terminate when they become idle.
Client programs run outside the Postfix core. They interact with Postfix server programs through mail delivery instructions in the user's ~/.forward file, and through small "gate" programs to submit mail or to request queue status information.
Other programs provide administrative support to start or stop Postfix, query status information, manipulate the queue, or to examine or update its configuration files.
Yellow ellipses
One of Postfix' many daemons serving exactly one purpose. This split-up into many smaller pieces of software is considered one of the reasons why Postfix is secure and stable.
Blue boxes
The blue boxes represent so-called lookup tables. A lookup table consists of two columns (key and value) containing information used for access control, e-mail routing etc.
Orange boxes
The orange boxes are either mail queues or files. In either case, e-mails are stored on persistent media (e.g., a hard disk).
White clouds
The clouds stand for points at which e-mails enter or leave Postfix. For example, smtpd receives mail from other mail servers or users whereas smtp relays mail to other MTAs.
Implementation
The Postfix implementation uses safe subsets of the C language and of the POSIX system API. These subsets are buried under an abstraction layer that contains about 50% of all Postfix source code, and that provides the foundation on which all Postfix programs are built. For example, the "vstring" primitive makes Postfix code resistant to buffer overflow[10]
attacks, and the "safe open" primitive makes Postfix code resistant to race condition attacks on systems that implement the POSIX file system
API. This abstraction layer does not affect the attack resistance of non-Postfix code, such as code in system libraries or in third-party libraries.
Robustness
Conceptually, Postfix manages pipelines of processes that pass the responsibility for message delivery and error notification from one process to the next. All message and notification "state" information is persisted in the file system. The processes in a pipeline operate mostly without centralized control; this relative autonomy simplifies error recovery. When a process fails before completing its part of a file or protocol transaction, its predecessor in the pipeline backs off and retries the request later, and its successor in the pipeline discards unfinished work. Many Postfix daemons can simply "die" when they run into a problem; they are automatically restarted when the next service request arrives. This approach makes Postfix highly resilient, as long as the operating system or hardware don't fail catastrophically.
Performance
One single Postfix instance has been clocked at ~300 message deliveries/second[11]
across the Internet, running on commodity hardware (a vintage-2003 Dell 1850 system with battery-backed MegaRAID controller and two SCSI
disks). This delivery rate is an order of magnitude below the "intrinsic" limit of 2500 message deliveries/second[11]
that was achieved with the mail queue on a RAM disk while delivering to the "discard" transport (with a dual-core Opteron system in 2007).
Mail systems such as Postfix and Qmail achieve high performance by delivering mail in parallel sessions. With mail systems such as Sendmail and Exim that do one delivery at a time, high performance can be achieved by submitting limited batches of mail in parallel, so that each batch is delivered by a different process. Postfix and Qmail require parallel submission into different MTA instances once they reach their intrinsic performance limit, or the performance limits of the hardware or operating system.
The delivery rates cited above are largely theoretical. With bulk mail delivery, the true delivery rate is primarily determined by the receiver's mail receiving policies and by the sender's reputation.
More complex Postfix implementations may include: integration with other applications such as SpamAssassin; support for multiple virtual domain names - and use databases such as MySQL to control complex configurations.
.png){kind=spacer}
