70 lines
3.3 KiB
HTML
70 lines
3.3 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||
<HTML>
|
||
<HEAD>
|
||
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
|
||
<TITLE>mini-HOWTO install qmail with MH: Introduction</TITLE>
|
||
<LINK HREF="Qmail+MH-2.html" REL=next>
|
||
|
||
<LINK HREF="Qmail+MH.html#toc1" REL=contents>
|
||
</HEAD>
|
||
<BODY>
|
||
<A HREF="Qmail+MH-2.html">Next</A>
|
||
Previous
|
||
<A HREF="Qmail+MH.html#toc1">Contents</A>
|
||
<HR>
|
||
<H2><A NAME="s1">1. Introduction</A></H2>
|
||
|
||
<P>
|
||
<P>My thanks to all netizens who have helped me, especially Tony Nugent
|
||
(tony@trishul.sci.gu.edu.au), David Summers (david@summersoft.fay.ar.us)
|
||
and S.u.S.E ( Linux distribution) who has made installing Linux so much easier,
|
||
and the authors of the above excellent programs.
|
||
<P>What is qmail and why should I use it? Here is the author´s (Dan Bernstein)
|
||
blurb:
|
||
<P>qmail is a secure, reliable, efficient, simple message transfer agent.
|
||
It is meant as a replacement for the entire sendmail-binmail system on
|
||
typical Internet-connected UNIX hosts.
|
||
<P>Secure: Security isn't just a goal, but an absolute requirement. Mail
|
||
delivery is critical for users; it cannot be turned off, so it must be
|
||
completely secure. (This is why I started writing qmail: I was sick of
|
||
the security holes in sendmail and other MTAs.)
|
||
<P>Reliable: qmail's straight-paper-path philosophy guarantees that a
|
||
message, once accepted into the system, will never be lost. qmail also
|
||
supports maildir, a new, super-reliable user mailbox format. Maildirs,
|
||
unlike mbox files and mh folders, won't be corrupted if the system
|
||
crashes during delivery. Even better, not only can a user safely read
|
||
his mail over NFS, but any number of NFS clients can deliver mail to him
|
||
at the same time.
|
||
<P>Efficient: On a Pentium under BSD/OS, qmail can easily sustain 200000
|
||
local messages per day---that's separate messages injected and delivered
|
||
to mailboxes in a real test! Although remote deliveries are inherently
|
||
limited by the slowness of DNS and SMTP, qmail overlaps 20 simultaneous
|
||
deliveries by default, so it zooms quickly through mailing lists. (This
|
||
is why I finished qmail: I had to get a big mailing list set up.)
|
||
<P>Simple: qmail is vastly smaller than any other Internet MTA. Some
|
||
reasons why: (1) Other MTAs have separate forwarding, aliasing, and
|
||
mailing list mechanisms. qmail has one simple forwarding mechanism that
|
||
lets users handle their own mailing lists. (2) Other MTAs offer a
|
||
spectrum of delivery modes, from fast+unsafe to slow+queued. qmail-send
|
||
is instantly triggered by new items in the queue, so the qmail system
|
||
has just one delivery mode: fast+queued. (3) Other MTAs include, in
|
||
effect, a specialized version of inetd that watches the load average.
|
||
qmail's design inherently limits the machine load, so qmail-smtpd can
|
||
safely run from your system's inetd.
|
||
<P>Replacement for sendmail: qmail supports host and user masquerading,
|
||
full host hiding, virtual domains, null clients, list-owner rewriting,
|
||
relay control, double-bounce recording, arbitrary RFC 822 address lists,
|
||
cross-host mailing list loop detection, per-recipient checkpointing,
|
||
downed host backoffs, independent message retry schedules, etc. In
|
||
short, it's up to speed on modern MTA features. qmail also includes a
|
||
drop-in ``sendmail'' wrapper so that it will be used transparently by
|
||
your current UAs.
|
||
<P>
|
||
<P>
|
||
<HR>
|
||
<A HREF="Qmail+MH-2.html">Next</A>
|
||
Previous
|
||
<A HREF="Qmail+MH.html#toc1">Contents</A>
|
||
</BODY>
|
||
</HTML>
|