|
|
|
| Description |
La messagerie lectronique est une application trs importante et des plus utiles des rseaux. Plus rapide et moins onreuse que la plupart des autres moyens de communication (tlcopie, tlphone, courrier postal, coursier...) la messagerie lectronique est un vecteur de plus en plus important dans la communication aussi bien interne qu'externe. Dans l'univers des rseaux TCP/IP, la messagerie SMTP est de loin la plus utilise, notamment avec l'outil Unix sendmail.
Le logiciel libre Postfix est un gestionnaire de messagerie simple configurer et conu pour une scurit optimale. De plus il est peu gourmand en ressources systme et constitue donc une vritable alternative Sendmail. Le choix de Postfix est lgitime tant pour le traitement de flux importants de messages que pour de petites installations. L'objectif de ce cours est de prparer l'installation et la mise en exploitation de Postfix en lieu et place de Sendmail. |
| Nature | Support de cours - 40 transparents (HTML). |
| Contexte |
Support de notre formation Postfix. Le support disponible ici est celui utilis le 12 octobre 1999 lors de la formation effectue au CRU ; les futures sessions de cette formation pourront utiliser une version revue du support. |
| Auteurs | Alain Thivillon (Alain.Thivillon@hsc.fr) |
| Sur le mme sujet... |
Prsentation publiques : "Postfix : une nouvelle gnration de MTA sous Unix" (juin 1999) "La scurit du MTA Postfix" (mars 1999) |
| Table des matires |
Page de garde
Agenda : matin
Architecture (1)
Compilation (1)
Installation (1)
Configuration de base (1)
Configuration avance (1) : spam
Maintenance de postfix (1)
Migration depuis sendmail
Exemple 1 : configuration sur un firewall |
| Droits d'auteur | © 1999, Herv Schauer Consultants, tous droits rservs. |
|
Dernire modification le 10 dcembre 1999
Informations sur ce serveur - webmaster@hsc.fr Copyright © 1999 Herv Schauer Consultants |
|
Postfix Configuration - UCE ControlsBy default, the Postfix SMTP server will accept mail only from or to the local network or domain, so that your system can't be used as a mail relay to forward bulk mail from random strangers.
The text in this document describes how you can set up more detailed anti-UCE policies that prevent delivery of unwanted email altogether, for example with sendmail-style access lists or with RBL (real-time blackhole list) name servers.
Unless indicated otherwise, all parameters described here are in the main.cf file. If you change parameters of a running Postfix system, don't forget to issue a postfix reload command.
A rule ending in OK affects only the header being matched. The next header may still result in a REJECT match, causing the mail still to be rejected.
In addition to restrictions that are specific to HELO (EHLO)
command parameters, you can also specify restrictions based
on the client hostname or network address.
In addition to restrictions that are specific to sender mail
addresses, you can also specify restrictions based on the information
passed with the HELO/EHLO command, and on the client hostname or
network address.
In addition to restrictions that are specific to recipient mail
addresses, you can also specify restrictions based on the sender mail
address, on the information passed with the HELO/EHLO command, and
on the client hostname or network address.
In addition to restrictions that are specific to ETRN domain names,
you can also specify restrictions based on the information passed
with the HELO/EHLO command, and on the client hostname or network
address.
Note: RBL lookups are disabled by default.
A host or destination address matches $relay_domains when
its name or parent domain matches any of the names, files or lookup
tables listed in $relay_domains.
Client name/address restrictions
The smtpd_client_restrictions parameter restricts what
clients this system accepts SMTP connections from.
Require HELO (EHLO) command
The smtpd_helo_required parameter determines if clients must
send a HELO (EHLO) command at the beginning of an
SMTP session. Requiring this will stop some UCE software.
HELO (EHLO) hostname restrictions
The smtpd_helo_restrictions parameter restricts what hostnames
clients may send with the HELO (EHLO) command. Some
UCE software can be stopped by being strict here.
Sender address restrictions
The smtpd_sender_restrictions parameter restricts what sender
addresses this system accepts in MAIL FROM commands.
Recipient address restrictions
The smtpd_recipient_restrictions parameter restricts what
recipient addresses this system accepts in RCPT TO commands.
ETRN command restrictions
Not really an UCE restriction, the smtpd_etrn_restrictions
parameter restricts what domains may be specified in ETRN commands,
and what clients may issue ETRN commands.
Generic restrictions
The following restrictions can use used for client hostnames or
addresses, for HELO (EHLO) hostnames, for sender mail addresses
and for recipient mail addresses.
Restrictions:
Additional UCE control parameters
Up one level | Basic
Configuration | UCE Controls | Rate
Controls | Resource Controls | Address Manipulation
postfix/doc/trivial-rewrite.8.html 100664 1751 146 12146 7017475553 16507 0 ustar thivillo www
TRIVIAL-REWRITE(8) TRIVIAL-REWRITE(8)
NAME
trivial-rewrite - Postfix address rewriting and resolving
daemon
SYNOPSIS
trivial-rewrite [generic Postfix daemon options]
DESCRIPTION
The trivial-rewrite daemon processes two types of client
service requests:
rewrite
Rewrite an address to standard form. The trivial-
rewrite daemon by default appends local domain
information to unqualified addresses, swaps bang
paths to domain form, and strips source routing
information. This process is under control of sev-
eral configuration parameters (see below).
resolve
Resolve an address to a (transport, nexthop, recip-
ient) triple. The meaning of the results is as fol-
lows:
transport
The delivery agent to use. This is the first
field of an entry in the master.cf file.
nexthop
The host to send to. For local delivery this
is an empty string.
recipient
The envelope recipient address that is
passed on to nexthop.
The trivial-rewrite daemon by default only distin-
guishes between local and non-local mail. For finer
control over mail routing, use the optional trans-
port(5) lookup table.
This program expects to be run from the master(8) process
manager.
STANDARDS
None. The command does not interact with the outside
world.
SECURITY
The trivial-rewrite daemon is not security sensitive. By
default, this daemon does not talk to remote or local
users. It can run at a fixed low privilege in a chrooted
environment.
1
TRIVIAL-REWRITE(8) TRIVIAL-REWRITE(8)
DIAGNOSTICS
Problems and transactions are logged to syslogd(8).
BUGS
CONFIGURATION PARAMETERS
The following main.cf parameters are especially relevant
to this program. See the Postfix main.cf file for syntax
details and for default values. Use the postfix reload
command after a configuration change.
Miscellaneous
inet_interfaces
The network interfaces that this mail system
receives mail on. This information is used to
determine if user@[net.work.addr.ess] is local or
remote.
mydestination
List of domains that this machine considers local.
myorigin
The domain that locally-posted mail appears to come
from.
Rewriting
allow_percent_hack
Rewrite user%domain to user@domain.
append_at_myorigin
Rewrite user to user@$myorigin.
append_dot_mydomain
Rewrite user@host to user@host.$mydomain.
swap_bangpath
Rewrite site!user to user@site.
Routing
default_transport
The default transport to use when no transport is
explicitly given in the transport(5) table.
relayhost
The default host to send mail to when no entry is
matched in the transport(5) table.
When no relayhost is specified, mail is routed
directly to the destination's mail exchanger.
transport_maps
List of tables with domain to (transport, nexthop)
mappings.
2
TRIVIAL-REWRITE(8) TRIVIAL-REWRITE(8)
SEE ALSO
master(8) process manager
syslogd(8) system logging
transport(5) transport table format
LICENSE
The Secure Mailer license must be distributed with this
software.
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
3
postfix/doc/transport.5.html 100664 1751 146 12177 7017475553 15413 0 ustar thivillo www
TRANSPORT(5) TRANSPORT(5)
NAME
transport - format of Postfix transport table
SYNOPSIS
postmap /etc/postfix/transport
DESCRIPTION
The optional transport file specifies a mapping from
domain hierarchies to message delivery transports and/or
relay hosts. The mapping is used by the trivial-rewrite(8)
daemon.
The file serves as input to the postmap(1) command. The
result, an indexed file in dbm or db format, is used for
fast searching by the mail system. After updating this
table, issue the postfix reload command to make the change
visible.
The format of the transport table is as follows:
blanks and comments
Blank lines are ignored, as are lines beginning
with `#'.
domain transport:nexthop
Mail for domain is delivered through transport to
nexthop.
.domain transport:nexthop
Mail for any subdomain of domain is delivered
through transport to nexthop.
The interpretation of the nexthop field is trans-
port dependent. In the case of SMTP, specify
host:service for a non-default server port, and use
[host] or [host:port] in order to disable MX (mail
exchanger) DNS lookups. The [] form can also be
used with IP addresses instead of hostnames.
EXAMPLES
In order to send mail for foo.org and its subdomains
via the uucp transport to the UUCP host named foo:
foo.org uucp:foo
.foo.org uucp:foo
When no nexthop host name is specified, the destination domain
name is used instead. For example, the following directs mail for
user@foo.org via the slow transport to a mail
exchanger for foo.org. The slow transport could be
something that runs at most one delivery process at a time:
foo.org slow:
1
TRANSPORT(5) TRANSPORT(5)
When no transport is specified, the default transport is
used, as specified via the default_transport configuration
parameter. The following sends all mail for foo.org and its
subdomains to host gateway.foo.org:
foo.org :[gateway.foo.org]
.foo.org :[gateway.foo.org]
In the above example, the [] are used to suppress MX lookups.
The result would likely point to your local machine.
In the case of delivery via SMTP, one may specify
hostname:service instead of just a host:
foo.org smtp:bar.org:2025
This directs mail for user@foo.org to host bar.org
port 2025. Instead of a numerical port a symbolic name may be
used. Specify [] around the destination in order to disable MX lookups.
The error mailer can be used to bounce mail:
.foo.org error:mail for *.foo.org is not deliverable
This causes all mail for user@anythingfoo.org
to be bounced.
CONFIGURATION PARAMETERS
The following main.cf parameters are especially relevant
to this topic. See the Postfix main.cf file for syntax
details and for default values. Use the postfix reload
command after a configuration change.
transport_maps
List of transport lookup tables.
Other parameters of interest:
default_transport
The transport to use when no transport is explic-
itly specified.
relayhost
The default host to send to when no transport table
entry matches.
SEE ALSO
postmap(1) create mapping table
trivial-rewrite(8) rewrite and resolve addresses
LICENSE
The Secure Mailer license must be distributed with this
software.
2
TRANSPORT(5) TRANSPORT(5)
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
3
postfix/doc/smtpd.8.html 100664 1751 146 24005 7017475553 14502 0 ustar thivillo www
SMTPD(8) SMTPD(8)
NAME
smtpd - Postfix SMTP server
SYNOPSIS
smtpd [generic Postfix daemon options]
DESCRIPTION
The SMTP server accepts network connection requests and
performs zero or more SMTP transactions per connection.
Each received message is piped through the cleanup(8) dae-
mon, and is placed into the incoming queue as one single
queue file. For this mode of operation, the program
expects to be run from the master(8) process manager.
Alternatively, the SMTP server takes an established con-
nection on standard input and deposits messages directly
into the maildrop queue. In this so-called stand-alone
mode, the SMTP server can accept mail even while the mail
system is not running.
The SMTP server implements a variety of policies for con-
nection requests, and for parameters given to HELO, MAIL
FROM, VRFY and RCPT TO commands. They are detailed below
and in the main.cf configuration file.
SECURITY
The SMTP server is moderately security-sensitive. It talks
to SMTP clients and to DNS servers on the network. The
SMTP server can be run chrooted at fixed low privilege.
STANDARDS
RFC 821 (SMTP protocol)
RFC 1123 (Host requirements)
RFC 1651 (SMTP service extensions)
RFC 1652 (8bit-MIME transport)
RFC 1854 (SMTP Pipelining)
RFC 1870 (Message Size Declaration)
RFC 1985 (ETRN command) (partial)
DIAGNOSTICS
Problems and transactions are logged to syslogd(8).
Depending on the setting of the notify_classes parameter,
the postmaster is notified of bounces, protocol problems,
policy violations, and of other trouble.
BUGS
RFC 1985 is implemented by forcing delivery of all
deferred mail.
CONFIGURATION PARAMETERS
The following main.cf parameters are especially relevant
to this program. See the Postfix main.cf file for syntax
details and for default values. Use the postfix reload
1
SMTPD(8) SMTPD(8)
command after a configuration change.
Miscellaneous
always_bcc
Address to send a copy of each message that enters
the system.
command_directory
Location of Postfix support commands (default:
$program_directory).
debug_peer_level
Increment in verbose logging level when a remote
host matches a pattern in the debug_peer_list
parameter.
debug_peer_list
List of domain or network patterns. When a remote
host matches a pattern, increase the verbose log-
ging level by the amount specified in the
debug_peer_level parameter.
error_notice_recipient
Recipient of protocol/policy/resource/software
error notices.
hopcount_limit
Limit the number of Received: message headers.
notify_classes
List of error classes. Of special interest are:
policy When a client violates any policy, mail a
transcript of the entire SMTP session to the
postmaster.
protocol
When a client violates the SMTP protocol or
issues an unimplemented command, mail a
transcript of the entire SMTP session to the
postmaster.
smtpd_banner
Text that follows the 220 status code in the SMTP
greeting banner.
smtpd_recipient_limit
Restrict the number of recipients that the SMTP
server accepts per message delivery.
smtpd_timeout
Limit the time to send a server response and to
receive a client request.
2
SMTPD(8) SMTPD(8)
Resource controls
line_length_limit
Limit the amount of memory in bytes used for the
handling of partial input lines.
message_size_limit
Limit the total size in bytes of a message, includ-
ing on-disk storage for envelope information.
queue_minfree
Minimal amount of free space in bytes in the queue
file system for the SMTP server to accept any mail
at all.
Tarpitting
smtpd_error_sleep_time
Time to wait in seconds before sending a 4xx or 5xx
server error response.
smtpd_soft_error_limit
When an SMTP client has made this number of errors,
wait error_count seconds before responding to any
client request.
smtpd_hard_error_limit
Disconnect after a client has made this number of
errors.
UCE control restrictions
smtpd_client_restrictions
Restrict what clients may connect to this mail sys-
tem.
smtpd_helo_required
Require that clients introduce themselves at the
beginning of an SMTP session.
smtpd_helo_restrictions
Restrict what client hostnames are allowed in HELO
and EHLO commands.
smtpd_sender_restrictions
Restrict what sender addresses are allowed in MAIL
FROM commands.
smtpd_recipient_restrictions
Restrict what recipient addresses are allowed in
RCPT TO commands.
smtpd_etrn_restrictions
Restrict what domain names can be used in ETRN com-
mands, and what clients may issue ETRN commands.
3
SMTPD(8) SMTPD(8)
maps_rbl_domains
List of DNS domains that publish the addresses of
blacklisted hosts.
relay_domains
Restrict what domains or networks this mail system
will relay mail from or to.
UCE control responses
access_map_reject_code
Server response when a client violates an access
database restriction.
invalid_hostname_reject_code
Server response when a client violates the
reject_invalid_hostname restriction.
maps_rbl_reject_code
Server response when a client violates the
maps_rbl_domains restriction.
reject_code
Response code when the client matches a reject
restriction.
relay_domains_reject_code
Server response when a client attempts to violate
the mail relay policy.
unknown_address_reject_code
Server response when a client violates the
reject_unknown_address restriction.
unknown_client_reject_code
Server response when a client without address to
name mapping violates the reject_unknown_clients
restriction.
unknown_hostname_reject_code
Server response when a client violates the
reject_unknown_hostname restriction.
SEE ALSO
cleanup(8) message canonicalization
master(8) process manager
syslogd(8) system logging
LICENSE
The Secure Mailer license must be distributed with this
software.
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
4
SMTPD(8) SMTPD(8)
P.O. Box 704
Yorktown Heights, NY 10598, USA
5
postfix/doc/smtp.8.html 100664 1751 146 21435 7017475553 14342 0 ustar thivillo www
SMTP(8) SMTP(8)
NAME
smtp - Postfix remote delivery via SMTP
SYNOPSIS
smtp [generic Postfix daemon options]
DESCRIPTION
The SMTP client processes message delivery requests from
the queue manager. Each request specifies a queue file, a
sender address, a domain or host to deliver to, and recip-
ient information. This program expects to be run from the
master(8) process manager.
The SMTP client updates the queue file and marks recipi-
ents as finished, or it informs the queue manager that
delivery should be tried again at a later time. Delivery
problem reports are sent to the bounce(8) or defer(8) dae-
mon as appropriate.
The SMTP client looks up a list of mail exchanger
addresses for the destination host, sorts the list by
preference, and connects to each listed address until it
finds a server that responds.
Once the SMTP client has received the server greeting ban-
ner, no error will cause it to proceed to the next address
on the mail exchanger list. Instead, the message is either
bounced, or its delivery is deferred until later.
SECURITY
The SMTP client is moderately security-sensitive. It talks
to SMTP servers and to DNS servers on the network. The
SMTP client can be run chrooted at fixed low privilege.
STANDARDS
RFC 821 (SMTP protocol)
RFC 1651 (SMTP service extensions)
RFC 1870 (Message Size Declaration)
RFC 2197 (Pipelining)
DIAGNOSTICS
Problems and transactions are logged to syslogd(8). Cor-
rupted message files are marked so that the queue manager
can move them to the corrupt queue for further inspection.
Depending on the setting of the notify_classes parameter,
the postmaster is notified of bounces, protocol problems,
and of other trouble.
BUGS
CONFIGURATION PARAMETERS
The following main.cf parameters are especially relevant
to this program. See the Postfix main.cf file for syntax
details and for default values. Use the postfix reload
1
SMTP(8) SMTP(8)
command after a configuration change.
Miscellaneous
best_mx_transport
Name of the delivery transport to use when the
local machine is the most-preferred mail exchanger
(by default, a mailer loop is reported, and the
message is bounced).
debug_peer_level
Verbose logging level increment for hosts that
match a pattern in the debug_peer_list parameter.
debug_peer_list
List of domain or network patterns. When a remote
host matches a pattern, increase the verbose log-
ging level by the amount specified in the
debug_peer_level parameter.
disable_dns_lookups
Disable DNS lookups. This means that mail must be
forwarded via a smart relay host.
error_notice_recipient
Recipient of protocol/policy/resource/software
error notices.
fallback_relay
Hosts to hand off mail to if a message destination
is not found or if a destination is unreachable.
ignore_mx_lookup_error
When a name server fails to respond to an MX query,
search for an A record instead of assuming that the
name server will recover.
inet_interfaces
The network interface addresses that this mail sys-
tem receives mail on. When any of those addresses
appears in the list of mail exchangers for a remote
destination, the list is truncated to avoid mail
delivery loops.
notify_classes
When this parameter includes the protocol class,
send mail to the postmaster with transcripts of
SMTP sessions with protocol errors.
smtp_skip_4xx_greeting
Skip servers that greet us with a 4xx status code.
smtp_skip_quit_response
Do not wait for the server response after sending
QUIT.
2
SMTP(8) SMTP(8)
Resource controls
smtp_destination_concurrency_limit
Limit the number of parallel deliveries to the same
destination. The default limit is taken from the
default_destination_concurrency_limit parameter.
smtp_destination_recipient_limit
Limit the number of recipients per message deliv-
ery. The default limit is taken from the
default_destination_recipient_limit parameter.
Timeout controls
smtp_connect_timeout
Timeout in seconds for completing a TCP connection.
When no connection can be made within the deadline,
the SMTP client tries the next address on the mail
exchanger list.
smtp_helo_timeout
Timeout in seconds for receiving the SMTP greeting
banner. When the server drops the connection with-
out sending a greeting banner, or when it sends no
greeting banner within the deadline, the SMTP
client tries the next address on the mail exchanger
list.
smtp_helo_timeout
Timeout in seconds for sending the HELO command,
and for receiving the server response.
smtp_mail_timeout
Timeout in seconds for sending the MAIL FROM com-
mand, and for receiving the server response.
smtp_rcpt_timeout
Timeout in seconds for sending the RCPT TO command,
and for receiving the server response.
smtp_data_init_timeout
Timeout in seconds for sending the DATA command,
and for receiving the server response.
smtp_data_xfer_timeout
Timeout in seconds for sending the message content.
smtp_data_done_timeout
Timeout in seconds for sending the "." command, and
for receiving the server response. When no response
is received, a warning is logged that the mail may
be delivered multiple times.
smtp_quit_timeout
Timeout in seconds for sending the QUIT command,
and for receiving the server response.
3
SMTP(8) SMTP(8)
SEE ALSO
bounce(8) non-delivery status reports
master(8) process manager
qmgr(8) queue manager
syslogd(8) system logging
LICENSE
The Secure Mailer license must be distributed with this
software.
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
4
postfix/doc/small-picture.gif 100664 1751 146 622 7017475553 15526 0 ustar thivillo www GIF89as - ! , s - ڋH扦j.! þ4}A7D$h9gbc7k*6h/2kc. _GQ(xd1PC7HG(ٹyxI51g9Y1"hhٛ S[)W,6Jsl|K@{[]z= *; {)[N> NXi ~
ǎX?t ր{%B4 DWddQz&M͘%MHJI|D1$GLR[&jS4s
+CJSD)bť+%UxiMXW5رd˚=6ڵlۺ} 7. ; postfix/doc/small-picture.fig 100664 1751 146 10334 7017475553 15567 0 ustar thivillo www #FIG 3.1
Landscape
Center
Inches
1200 2
1 2 0 1 -1 6 1 0 20 0.000 1 0.0000 11850 2250 600 300 11250 1950 12450 2550
1 2 0 1 -1 6 1 0 20 0.000 1 0.0000 13500 4350 600 300 12900 4050 14100 4650
1 2 0 1 -1 6 1 0 20 0.000 1 0.0000 13500 3300 600 300 12900 3000 14100 3600
1 2 0 1 -1 6 1 0 20 0.000 1 0.0000 11850 3300 600 300 11250 3000 12450 3600
1 2 0 1 -1 6 1 0 20 0.000 1 0.0000 13500 2250 600 300 12900 1950 14100 2550
1 2 0 1 -1 6 1 0 20 0.000 1 0.0000 2700 2775 600 300 2100 2475 3300 3075
1 2 0 1 -1 6 1 0 20 0.000 1 0.0000 5700 2775 600 300 5100 2475 6300 3075
1 2 0 1 -1 6 1 0 20 0.000 1 0.0000 5700 3825 600 300 5100 3525 6300 4125
1 2 0 1 -1 6 1 0 20 0.000 1 0.0000 7350 3300 600 300 6750 3000 7950 3600
1 2 0 1 -1 6 1 0 20 0.000 1 0.0000 7350 2250 600 300 6750 1950 7950 2550
2 1 0 1 -1 7 0 0 -1 0.000 0 0 -1 0 0 2
10800 3300 11250 3300
2 1 0 1 -1 7 0 0 -1 0.000 0 0 -1 0 0 2
12450 3300 12900 3300
2 1 0 1 -1 7 0 0 -1 0.000 0 0 -1 0 0 2
12225 3075 13125 2475
2 1 0 1 -1 7 0 0 -1 0.000 0 0 -1 0 0 2
12138 3542 13038 4142
2 1 0 1 -1 7 0 0 -1 0.000 0 0 -1 0 0 2
14100 2250 14550 2250
2 1 0 1 -1 7 0 0 -1 0.000 0 0 -1 0 0 2
14100 3300 14550 3300
2 1 0 1 -1 7 0 0 -1 0.000 0 0 -1 0 0 2
14100 4350 14550 4350
2 2 0 0 -1 7 0 0 -1 0.000 0 0 -1 0 0 5
14587 4050 15487 4050 15487 4650 14587 4650 14587 4050
2 2 0 0 -1 7 0 0 -1 0.000 0 0 -1 0 0 5
14550 3000 15450 3000 15450 3600 14550 3600 14550 3000
2 1 0 1 -1 7 0 0 -1 0.000 0 0 -1 0 0 2
11850 1500 11850 1950
2 1 0 1 -1 7 0 0 -1 0.000 0 0 -1 0 0 2
11850 2550 11850 3000
2 1 0 1 -1 7 0 0 -1 0.000 0 0 -1 0 0 2
13500 1500 13500 1950
2 1 0 1 -1 7 2 0 -1 0.000 0 0 -1 0 0 2
14700 1350 13950 2025
2 1 0 1 -1 7 0 0 -1 0.000 0 0 -1 0 0 4
10800 3450 11100 3450 11100 4350 10800 4350
2 1 0 1 -1 7 0 0 -1 0.000 0 0 -1 0 0 2
11850 3600 11850 4050
2 2 0 1 -1 6 1 0 20 0.000 0 0 7 0 0 5
9900 3000 10800 3000 10800 3600 9900 3600 9900 3000
2 2 0 1 -1 6 1 0 20 0.000 0 0 7 0 0 5
9900 4050 10800 4050 10800 4650 9900 4650 9900 4050
2 2 0 1 -1 6 1 0 20 0.000 0 0 7 0 0 5
14550 1950 15450 1950 15450 2550 14550 2550 14550 1950
2 2 0 1 -1 3 1 0 20 0.000 0 0 -1 0 0 5
11400 900 12300 900 12300 1500 11400 1500 11400 900
2 2 0 1 -1 3 1 0 20 0.000 0 0 -1 0 0 5
13050 900 13950 900 13950 1500 13050 1500 13050 900
2 2 0 1 -1 3 1 0 20 0.000 0 0 -1 0 0 5
14550 900 15450 900 15450 1500 14550 1500 14550 900
2 2 0 1 -1 3 1 0 20 0.000 0 0 -1 0 0 5
11400 4050 12300 4050 12300 4650 11400 4650 11400 4050
2 1 0 1 -1 7 0 0 -1 0.000 0 0 -1 0 0 2
9300 3300 9900 3300
2 1 0 1 -1 7 0 0 -1 0.000 0 0 -1 0 0 4
9900 3450 9600 3450 9600 4350 9900 4350
2 1 0 1 -1 7 0 0 -1 0.000 0 0 -1 0 0 2
6225 3675 6825 3450
2 1 0 1 -1 7 0 0 -1 0.000 0 0 -1 0 0 2
7950 3300 8400 3300
2 1 0 1 -1 7 0 0 -1 0.000 0 0 -1 0 0 2
6225 2925 6825 3150
2 1 0 1 -1 7 0 0 -1 0.000 0 0 -1 0 0 2
3300 2775 3750 2775
2 1 0 1 -1 7 0 0 -1 0.000 0 0 -1 0 0 2
1650 2775 2100 2775
2 1 0 1 -1 7 0 0 -1 0.000 0 0 -1 0 0 2
4650 2775 5100 2775
2 1 0 1 -1 7 0 0 -1 0.000 0 0 -1 0 0 2
4650 3825 5100 3825
2 2 0 0 -1 7 0 0 -1 0.000 0 0 -1 0 0 5
3750 3525 4650 3525 4650 4125 3750 4125 3750 3525
2 1 0 1 -1 7 0 0 -1 0.000 0 0 -1 0 0 2
5700 4125 5700 4500
2 1 0 1 -1 7 2 0 -1 0.000 0 0 -1 0 0 2
4500 4650 5250 4050
2 1 0 1 -1 7 0 0 -1 0.000 0 0 -1 0 0 2
7350 2550 7350 3000
2 1 0 1 -1 7 0 0 -1 0.000 0 0 -1 0 0 2
7350 3600 7350 4050
2 1 0 1 -1 7 2 0 -1 0.000 0 0 -1 1 0 2
0 0 1.00 60.00 120.00
8550 4200 7800 3525
2 2 0 0 -1 7 0 0 -1 0.000 0 0 -1 0 0 5
750 2475 1650 2475 1650 3075 750 3075 750 2475
2 2 0 1 -1 6 1 0 20 0.000 0 0 -1 0 0 5
3750 2475 4650 2475 4650 3075 3750 3075 3750 2475
2 2 0 1 -1 6 1 0 20 0.000 0 0 7 0 0 5
8400 3000 9300 3000 9300 3600 8400 3600 8400 3000
2 2 0 1 -1 3 1 0 20 0.000 0 0 -1 0 0 5
3750 4500 4650 4500 4650 5100 3750 5100 3750 4500
2 2 0 1 -1 3 1 0 20 0.000 0 0 -1 0 0 5
5250 4500 6150 4500 6150 5100 5250 5100 5250 4500
2 2 0 1 -1 3 1 0 20 0.000 0 0 -1 0 0 5
6900 4050 7800 4050 7800 4650 6900 4650 6900 4050
2 2 0 1 -1 3 1 0 20 0.000 0 0 -1 0 0 5
8400 4050 9300 4050 9300 4650 8400 4650 8400 4050
4 0 -1 0 0 0 15 0.0000 4 150 690 14655 3375 Internet\001
4 0 -1 0 0 0 15 0.0000 4 150 930 14647 4425 UUCP etc.\001
4 0 -1 0 0 0 15 0.0000 4 150 690 3840 3892 Internet\001
4 0 -1 0 0 0 15 0.0000 4 150 405 952 2850 local\001
postfix/doc/showq.8.html 100664 1751 146 3524 7017475553 14477 0 ustar thivillo www
SHOWQ(8) SHOWQ(8)
NAME
showq - list the Postfix mail queue
SYNOPSIS
showq [generic Postfix daemon options]
DESCRIPTION
The showq daemon reports the Postfix mail queue status.
It is the program that emulates the sendmail `mailq' com-
mand.
The showq daemon can also be run in stand-alone mode by
the super-user. This mode of operation is used to emulate
the `mailq' command while the Postfix mail system is down.
SECURITY
The showq daemon can run in a chroot jail at fixed low
privilege, and takes no input from the client. Its service
port is accessible to local untrusted users, so the ser-
vice can be susceptible to denial of service attacks.
STANDARDS
None. The showq daemon does not interact with the outside
world.
DIAGNOSTICS
Problems and transactions are logged to syslogd(8).
BUGS
The showq daemon runs at a fixed low privilege; conse-
quently, it cannot extract information from queue files in
the maildrop directory.
SEE ALSO
cleanup(8) canonicalize and enqueue mail
pickup(8) local mail pickup service
qmgr(8) mail being delivered, delayed mail
syslogd(8) system logging
LICENSE
The Secure Mailer license must be distributed with this
software.
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
1
postfix/doc/sendmail.1.html 100664 1751 146 27415 7017475553 15150 0 ustar thivillo www
SENDMAIL(1) SENDMAIL(1)
NAME
sendmail - Postfix to Sendmail compatibility interface
SYNOPSIS
sendmail [option ...] [recipient ...]
mailq
sendmail -bp
newaliases
sendmail -I
DESCRIPTION
The sendmail program implements the Postfix to Sendmail
compatibility interface. For the sake of compatibility
with existing applications, some Sendmail command-line
options are recognized but silently ignored.
By default, sendmail reads a message from standard input
and arranges for delivery. sendmail attempts to create a
queue file in the maildrop directory. If that directory is
not world-writable, the message is piped through the post-
drop(1) command, which is expected to execute with suit-
able privileges.
Specific command aliases are provided for other common
modes of operation:
mailq List the mail queue. Each entry shows the queue
file ID, message size, arrival time, sender, and
the recipients that still need to be delivered. If
mail could not be delivered upon the last attempt,
the reason for failure is shown. This mode of oper-
ation is implemented by connecting to the showq(8)
daemon.
newaliases
Initialize the alias database. If no alias database
type is specified, the program uses the type speci-
fied in the database_type configuration parameter;
if no input file is specified, the program pro-
cesses the file(s) specified with the
alias_database configuration parameter. This mode
of operation is implemented by running the postal-
ias(1) command.
Note: it may take a minute or so before an alias
database update becomes visible. Use the postfix
reload command to eliminate this delay.
These and other features can be selected by specifying the
appropriate combination of command-line options. Some fea-
tures are controlled by parameters in the main.cf configu-
ration file.
1
SENDMAIL(1) SENDMAIL(1)
The following options are recognized:
-B body_type (ignored)
The message body MIME type. Currently, Postfix
implements just-send-eight.
-C config_file (ignored :-)
The path name of the sendmail.cf file. Postfix con-
figuration files are kept in /etc/postfix.
-F full_name
Set the sender full name. This is used only with
messages that have no From: message header.
-I Initialize alias database. See the newaliases com-
mand above.
-N dsn (ignored)
Delivery status notification control. Currently,
Postfix does not implement DSN.
-R return_limit (ignored)
Limit the size of bounced mail. Use the
bounce_size_limit configuration parameter instead.
-X log_file (ignored)
Log mailer traffic. Use the debug_peer_list and
debug_peer_level configuration parameters instead.
-bd Go into daemon mode. This mode of operation is
implemented by executing the postfix start command.
-bi Initialize alias database. See the newaliases com-
mand above.
-bm Read mail from standard input and arrange for
delivery. This is the default mode of operation.
-bp List the mail queue. See the mailq command above.
-bs Stand-alone SMTP server mode. Read SMTP commands
from standard input, and write responses to stan-
dard output. This mode of operation is implemented
by running the smtpd(8) daemon.
-f sender
Set the envelope sender address. This is the
address where delivery problems are sent to, unless
the message contains an Errors-To: message header.
-h hop_count (ignored)
Hop count limit. Use the hopcount_limit configura-
tion parameter instead.
2
SENDMAIL(1) SENDMAIL(1)
-i (ignored)
Lines beginning with "." get special treatment only
with -bs.
-m (ignored)
Backwards compatibility.
-n (ignored)
Backwards compatibility.
-oAalias_database
Non-default alias database. Specify pathname or
type:pathname. See postalias(1) for details.
-o7 (ignored)
-o8 (ignored)
The message body type. Currently, Postfix imple-
ments just-send-eight.
-om (ignored)
The sender is never eliminated from alias etc.
expansions.
-o x value (ignored)
Set option x to value. Use the equivalent configu-
ration parameter in main.cf instead.
-r sender
Set the envelope sender address. This is the
address where delivery problems are sent to, unless
the message contains an Errors-To: message header.
-q Flush the mail queue. This is implemented by kick-
ing the qmgr(8) daemon.
-qinterval (ignored)
The interval between queue runs. Use the
queue_run_delay configuration parameter instead.
-t Extract recipients from message headers. This
requires that no recipients be specified on the
command line.
-v Enable verbose logging for debugging purposes. Mul-
tiple -v options make the software increasingly
verbose.
SECURITY
By design, this program is not set-user (or group) id.
However, it must handle data from untrusted users or
untrusted machines. Thus, the usual precautions need to
be taken against malicious inputs.
3
SENDMAIL(1) SENDMAIL(1)
DIAGNOSTICS
Problems are logged to syslogd(8) and to the standard
error stream.
ENVIRONMENT
MAIL_CONFIG
Directory with Postfix configuration files.
MAIL_VERBOSE
Enable verbose logging for debugging purposes.
MAIL_DEBUG
Enable debugging with an external command, as spec-
ified with the debugger_command configuration
parameter.
FILES
/var/spool/postfix, mail queue
/etc/postfix, configuration files
CONFIGURATION PARAMETERS
See the Postfix main.cf file for syntax details and for
default values. Use the postfix reload command after a
configuration change.
alias_database
Default alias database(s) for newaliases. The
default value for this parameter is system-spe-
cific.
bounce_size_limit
The amount of original message context that is sent
along with a non-delivery notification.
database_type
Default alias etc. database type. On many UNIX sys-
tems the default type is either dbm or hash.
debugger_command
Command that is executed after a Postfix daemon has
initialized.
debug_peer_level
Increment in verbose logging level when a remote
host matches a pattern in the debug_peer_list
parameter.
debug_peer_list
List of domain or network patterns. When a remote
host matches a pattern, increase the verbose log-
ging level by the amount specified in the
debug_peer_level parameter.
4
SENDMAIL(1) SENDMAIL(1)
fork_attempts
Number of attempts to fork() a process before giv-
ing up.
fork_delay
Delay in seconds between successive fork()
attempts.
hopcount_limit
Limit the number of Received: message headers.
mail_owner
The owner of the mail queue and of most Postfix
processes.
command_directory
Directory with Postfix support commands (default:
$program_directory).
daemon_directory
Directory with Postfix daemon programs (default:
$program_directory).
queue_directory
Top-level directory of the Postfix queue. This is
also the root directory of Postfix daemons that run
chrooted.
queue_run_delay
The time between successive scans of the deferred
queue.
SEE ALSO
pickup(8) mail pickup daemon
postalias(1) maintain alias database
postdrop(1) privileged posting agent
postfix(1) mail system control
postkick(1) kick a Postfix daemon
qmgr(8) queue manager
showq(8) list mail queue
smtpd(8) SMTP server
syslogd(8) system logging
LICENSE
The Secure Mailer license must be distributed with this
software.
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
5
postfix/doc/security.html 100664 1751 146 14605 7017475554 15062 0 ustar thivillo www
Postfix
Overview - SecurityPostfix is a complex system. The initial release has about 30,000 lines of code (after deleting the comments). With a system that complex, the security of the system should not depend on a single mechanism. If it did, one single error would be sufficient to compromise the entire mail system. Therefore, Postfix uses multiple layers of defense to control the damage from software and other errors.
By default, the maildrop queue directory is world-writable, so that local processes can submit mail without assistance from a set-uid or set-gid command or from a mail daemon process. The maildrop directory is not used for mail coming in via the network, and queue files are not readable for other users.
A writable directory opens up opportunities for annoyance: a local user can make hard links to someone else's maildrop files so they don't go away and/or are delivered multiple times; a local user can fill the maildrop directory with garbage and try to make the mail system crash; and a local user can hard link someone else's files into the maildrop directory and try to have them delivered as mail. However, Postfix queue files have a specific format; less than one in 10^12 non-Postfix files would be recognized as a valid Postfix queue file.
If a world-writable maildrop directory is not acceptable, sites can revoke world write permission, and enable set-gid privileges for a small helper program that is provided for this purpose.
Of course, Postfix programs do not trust data received from the network, either. In particular, Postfix filters sender-provided data before exporting it via environment variables. If there is one lesson that people have learned from Web site security disasters it is this one: don't let any data from the network near a shell. Filtering is the best we can do.
Postfix Configuration - Address ManipulationUnless indicated otherwise, all parameters described here are in the main.cf file. If you change parameters of a running Postfix system, don't forget to issue a postfix reload command.
All mail:
Local delivery:
You probably should never turn off this feature, because a lot of
Postfix components expect that all addresses have the form
user@domain.
If your machine is not the main machine for $myorigin and
you wish to have some users delivered locally without going via
that main machine, make an entry in the virtual
table that redirects user@$myorigin to user@$myhostname.
Some will argue that rewriting host to host.$mydomain
is bad. That is why it can be turned off. Others like the convenience of having
the local domain appended automatically.
Canonical mapping is disabled by default. To enable, edit the canonical_maps parameter in the main.cf file and specify one or more lookup tables, separated by whitespace or commas. For example:
In addition to the canonical maps which are applied to both sender and recipient addresses, you can specify canonical maps that are applied only to sender addresses or to recipient addresses. For example:
The sender and recipient canonical maps are applied before the common canonical maps.
Sender-specific rewriting is useful when you want to rewrite ugly
sender addresses to pretty ones, and still want to be able to
send mail to the those ugly address without creating a mailer loop.
Address masquerading is disabled by default. To enable, edit the
masquerade_domains parameter in the main.cf
file and specify one or more domain names separated by whitespace
or commas. For example:
In this example, addresses of the form user@host.$mydomain
would be rewritten to user@$mydomain.
The masquerade_exceptions configuration parameter specifies
what user names should not be subjected to address masquerading.
Specify one or more user names separated by whitespace or commas.
For example,
By default, Postfix makes no exceptions.
Subtle point: address masquerading is applied only to message
headers and envelope sender addresses, not to envelope recipients.
Virtual mapping is disabled by default. To enable, edit the
virtual_maps parameter in the main.cf file and
specify one or more lookup tables, separated by whitespace or
commas. For example:
Addresses found in virtual maps are subjected to another iteration
of virtual mapping, but are not subjected to canonical mapping, in
order to avoid loops.
Lookups of relocated users are disabled by default. To enable, edit
the relocated_maps parameter in the main.cf
file and specify one or more lookup tables, separated by whitespace
or commas. For example:
Address masquerading
Address masquerading is a method to hide all hosts below a domain
behind their mail gateway, and to make it appear as if the mail
comes from the gateway itself, instead of from individual machines.
Virtual address mapping
After applying the canonical and masquerade mappings, the cleanup daemon uses the virtual table to redirect mail for all
recipients, local or remote. The mapping affects only envelope
recipients; it has no effect on message headers or envelope senders.
Virtual lookups are useful to redirect mail for virtual domains to
real user mailboxes, and to redirect mail for domains that no longer
exist. Virtual lookups can also be used to transform
Firstname.Lastname back into UNIX login names, although it
seems that local aliases are a more appropriate
vehicle.
Relocated users table
Next, the queue manager runs each recipient name through the
relocated database. This table
provides information on how to reach users that no longer have an
account, or what to do with mail for entire domains that no longer
exist. When mail is sent to an address that is listed in this
table, the message is bounced with an informative message.
Mail transport switch
Once the queue manager has established the destination of a message,
the optional transport table controls
how the message will be delivered (this table is used by the address
rewriting and resolving daemon). By default, everything is sent
via the smtp transport. The transport
table can be used to send mail to specific sites via UUCP,
or to send mail to a really broken mail system that can handle only
one SMTP connection at a time (yes, such systems exist and people
used to pay real money for them).
Transport table lookups are disabled by default. To enable, edit the transport_maps parameter in the main.cf file and specify one or more lookup tables, separated by whitespace or commas. For example:
Alias lookups are enabled by default. The default configuration depends on the system environment, but it is typically one of the following:
The path to the alias database file is controlled via the alias_database configuration parameter. The value is system dependent. Usually it is one of the following:
For security reasons, deliveries to command and file destinations
are performed with the rights of the alias database owner. A
default userid, default_privs, is used for deliveries to
commands/files in root-owned aliases.
Alternatively, mail for non-existent recipients can be delegated
to an entirely different message transport, as specified with the
fallback_transport configuration parameter. For details,
see the local delivery agent.
luser_relay can specify one address. It is subjected to
$name expansions. The most useful examples are:
Per-user .forward files
Users can control their own mail delivery by specifying destinations
in a file called .forward in their home directories. The
syntax of these files is the same as with system aliases, except
that the lookup key and colon are not present.
Non-existent users
When the local delivery agent finds that a message recipient does
not exist, the message is normally bounced to the sender ("user
unknown"). Sometimes it is desirable to forward mail for non-existing
recipients to another machine. For this purpose you can specify
an alternative destination with the luser_relay configuration
parameter.
Up one level |
Basic Configuration | UCE
Controls | Rate Controls | Resource Controls | Address Manipulation
postfix/doc/resource.html 100664 1751 146 17247 7017475554 15047 0 ustar thivillo www
Postfix Configuration - Resource Controls
The following parameters restrict the use of file system storage:
The general approach taken in the face of disaster is to terminate with a fatal run-time error (or with a panic in case of software problems), and to try again after some time (the master daemon will restart processes after some delay). Each failed attempt is logged; hopefully, someone will notice the problem and fix it.
Some recovery strategies were implemented very early during Postfix development, and haven't been made configurable yet. What follows is the beginning of a growing list of recovery control parameters:
RELOCATED(5) RELOCATED(5)
NAME
relocated - format of Postfix relocated table
SYNOPSIS
postmap /etc/postfix/relocated
DESCRIPTION
The optional relocated file provides the information that
is used in "user has moved to new_location" bounce mes-
sages.
The file serves as input to the postmap(1) command. The
result, an indexed file in dbm or db format, is used for
fast searching by the mail system. After an update issue a
postfix reload command to make the change visible.
Table lookups are case insensitive.
The format of the table is as follows:
o Blank lines are ignored, as are lines beginning
with `#'.
o An entry has one of the following form:
key new_location
Where new_location specifies contact information
such as an email address, or perhaps a street
address or telephone number.
The key field is one of the following:
user@domain
Matches user@domain. This form has precedence over
all other forms.
user Matches user@site when site is $myorigin, when site
is listed in $mydestination, or when site is listed
in $inet_interfaces.
@domain
Matches every address in domain. This form has the
lowest precedence.
ADDRESS EXTENSION
When the search fails, and the address localpart contains
the optional recipient delimiter (e.g., user+foo@domain),
the search is repeated for the unextended address (e.g.
user@domain).
BUGS
The table format does not understand quoting conventions.
CONFIGURATION PARAMETERS
The following main.cf parameters are especially relevant
1
RELOCATED(5) RELOCATED(5)
to this topic. See the Postfix main.cf file for syntax
details and for default values. Use the postfix reload
command after a configuration change.
relocated_maps
List of lookup tables for relocated users or sites.
Other parameters of interest:
inet_interfaces
The network interface addresses that this system
receives mail on.
mydestination
List of domains that this mail system considers
local.
myorigin
The domain that is appended to locally-posted mail.
SEE ALSO
postmap(1) create lookup table
LICENSE
The Secure Mailer license must be distributed with this
software.
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
2
postfix/doc/receiving.html 100664 1751 146 7361 7017475554 15147 0 ustar thivillo www
Postfix
Anatomy - Receiving MailWhen a message enters the Postfix mail system, the first stop on the inside is the incoming queue. The figure below shows the main components that are involved with new mail. For an explanation of the symbols used, click on the icon in the upper left-hand corner of this page.
Postfix Rate ControlsOn the inbound side, the Postfix SMTP server has defenses in place against malicious or confused clients. They won't protect against an all-out denial of service attack on your infrastructure, but then nothing will except pulling the plug.
Unless indicated otherwise, all parameters described here are in the main.cf file. If you change parameters of a running Postfix system, don't forget to issue a postfix reload command.
You can override this setting for specific Postfix daemons by editing the master.cf file. For example, if you do not wish to receive 50 SMTP messages at the same time, you could specify:
# ========================================================================== # service type private unpriv chroot wakeup maxproc command + args # (yes) (yes) (yes) (never) (50) # ========================================================================== . . . smtp inet n - - - 5 smtpd . . .
The Postfix queue manager comes to the rescue. This program implements the analog of the TCP slow start flow control strategy: when delivering to a site, send a small number of messages first, then increase the rate as long as all goes well; back off in the face of congestion.
The initial_destination_concurrency parameter (default: 2) controls how many messages are initially sent to the same destination before adapting delivery concurrency. Of course, this setting is effective only as long as it does not exceed the process limit and the destination concurrency limit for the specific mail transport channel.
The default_destination_concurrency_limit parameter (default: 10) controls how many messages may be sent to the same destination simultaneously. You can override this setting for specific delivery channels (local, smtp, uucp etc.). The main.cf file recommends the following:
A destination concurrency limit of 10 for SMTP delivery seems enough
to noticeably load a system without bringing it to its knees. Be
careful when changing this to a much larger number.
You can override this setting for specific Postfix delivery agents
(smtp, uucp, etc.). For example:
You must be careful when increasing the recipient limit; some SMTP
servers abort the connection when they run out of memory or when
a hard recipient limit is reached, so the mail won't get through.
The smtpd_recipient_limit parameter (default: 1000)
controls how many recipients the SMTP server will take per delivery.
That's more than any reasonable SMTP client would send. The limit
exists just to protect the local mail system against a malicious
or confused client.
A small site that is on-line only part of the time, and
that wants to defer all deliveries until the command sendmail
-q is executed (e.g., from a PPP dialout script) would use:
An ISP can use the defer_transports feature for customers
that are off-line most of the time. The customer can trigger delivery
by issuing an ETRN command at the SMTP port. The following
examples show how to configure such a customer:
You can specify any number of transports here. The example gives
just one.
The [] are necessary to avoid MX lookups, which might point to your
local machine. The second entry is necessary only if you want to
relay mail for customer subdomains.
This is just the master.cf entry for regular SMTP, with the
first field changed to hold.
As you would expect, this whole process is governed by a bunch of
little parameters.
Some defenses are part of a more general strategy: for example,
how long a line of text may be before it is broken up into pieces,
and how much text may be carried in a multi-line message header.
See the resource controls documentation
for details.
The Postfix SMTP server increments a
per-session error counter whenever a client request is unrecognized
or unimplemented, or whenever a client request violates UCE restrictions or other reasons. The error
counter is reset when a message is transferred successfully.
As the per-session error count increases, the SMTP server changes
behavior. The idea is to limit the damage by slowing down the
client. The behavior is controlled by the following parameters:
Unfortunately, the Postfix SMTP server does not yet know how to
limit the number of connections from the same client,
other than by limiting the total number of SMTP server processes
(see process limit). Things could be worse:
some mailers don't even implement an SMTP server process limit.
That's of course no excuse. I'm still looking for a good solution.
Recipient limits
The default_destination_recipient_limit parameter (default:
50) controls how many recipients a Postfix delivery agent (smtp,
uucp, etc.) will send with each copy of an email message.
If an email message has more than
$default_destination_recipient_limit recipients at the same
destination, the list of recipients will be broken up into smaller lists,
and multiple copies of the message will be sent.
would limit the number of recipients per UUCP delivery to 100.
Always postponing delivery
The defer_transports parameter allows you to specify what
mail should always be deferred until Postfix is explicitly asked
to deliver.
Backoff from unreachable hosts
When a Postfix delivery agent (smtp, local, uucp, etc.)
is unable to deliver a message it may blame the message itself or
the receiving party.
Slowing down bad clients
First of all, no defense will protect against an all-out denial of
service attack. I just don't want to raise impossible expectations.
But there are a few simple things one can do in order to deal with
confused or malicious client programs.
Up one level |
Basic Configuration | UCE
Controls | Rate Controls | Resource
Controls | Address Manipulation
postfix/doc/queuing.html 100664 1751 146 10354 7017475554 14665 0 ustar thivillo www
Postfix Overview - Queue Management
Up one level | Introduction | Goals
and features | Global architecture
| Queue Management | Security
The queue manager keeps information in memory about the active queue only. The active queue size is limited on purpose: the queue manager should never run out of working memory because of a peak message workload. Whenever there is space in the active queue, the queue manager lets in one message from the incoming queue and one from the deferred queue. This guarantees that new mail will get through even when there is a large backlog.
Postfix tries to be a good network neighbor. When delivering mail to a site, Postfix will initially make no more than two simultaneous connections. As long as deliveries succeed, the concurrency slowly increases up to some configurable limit (or until the host or network is unable to handle the load); concurrency is decreased in the face of trouble. For those familiar with TCP/IP implementation details, Postfix implements its own analog of the TCP slow start algorithm
On the average, Postfix will do simultaneous deliveries to the same domain only when there is not enough work to keep all outbound SMTP channels busy. So, when AOL goes off-line and comes back, it should not stop the system from delivering to other sites.
When mail arrives faster than Postfix can deliver it, Postfix will favor new mail over delayed mail. The idea is that new mail should be delivered with as little delay as possible; delayed mail can be delivered while the system would otherwise be idle.
Whenever a repeat delivery attempt fails, the queue file time stamp is moved into the future by an amount of time equal to the age of the message. Thus, the time between delivery attempts doubles each time. This strategy effectively implements exponential backoff.
QMGR(8) QMGR(8)
NAME
qmgr - Postfix queue manager
SYNOPSIS
qmgr [generic Postfix daemon options]
DESCRIPTION
The qmgr daemon awaits the arrival of incoming mail and
arranges for its delivery via Postfix delivery processes.
The actual mail routing strategy is delegated to the triv-
ial-rewrite(8) daemon. This program expects to be run
from the master(8) process manager.
Mail addressed to the local double-bounce address is
silently discarded. This stops potential loops caused by
undeliverable bounce notifications.
Mail addressed to a user listed in the optional relocated
database is bounced with a "user has moved to new_loca-
tion" message. See relocated(5) for a precise description.
MAIL QUEUES
The qmgr daemon maintains the following queues:
incoming
Inbound mail from the network, or mail picked up by
the local pickup agent from the maildrop directory.
active Messages that the queue manager has opened for
delivery. Only a limited number of messages is
allowed to enter the active queue (leaky bucket
strategy, for a fixed delivery rate).
deferred
Mail that could not be delivered upon the first
attempt. The queue manager implements exponential
backoff by doubling the time between delivery
attempts.
corrupt
Unreadable or damaged queue files are moved here
for inspection.
DELIVERY STATUS REPORTS
The qmgr daemon keeps an eye on per-message delivery sta-
tus reports in the following directories. Each status
report file has the same name as the corresponding message
file:
bounce Per-recipient status information about why mail is
bounced. These files are maintained by the
bounce(8) daemon.
defer Per-recipient status information about why mail is
1
QMGR(8) QMGR(8)
delayed. These files are maintained by the
defer(8) daemon.
The qmgr daemon is responsible for asking the bounce(8) or
defer(8) daemons to send non-delivery reports.
STRATEGIES
The queue manager implements a variety of strategies for
either opening queue files (input) or for message delivery
(output).
leaky bucket
This strategy limits the number of messages in the
active queue and prevents the queue manager from
running out of memory under heavy load.
fairness
When the active queue has room, the queue manager
takes one message from the incoming queue and one
from the deferred queue. This prevents a large mail
backlog from blocking the delivery of new mail.
slow start
This strategy eliminates "thundering herd" problems
by slowly adjusting the number of parallel deliver-
ies to the same destination.
round robin
The queue manager sorts delivery requests by desti-
nation. Round-robin selection prevents one desti-
nation from dominating deliveries to other destina-
tions.
exponential backoff
Mail that cannot be delivered upon the first
attempt is deferred. The time interval between
delivery attempts is doubled after each attempt.
destination status cache
The queue manager avoids unnecessary delivery
attempts by maintaining a short-term, in-memory
list of unreachable destinations.
TRIGGERS
On an idle system, the queue manager waits for the arrival
of trigger events, or it waits for a timer to go off. A
trigger is a one-byte message. Depending on the message
received, the queue manager performs one of the following
actions (the message is followed by the symbolic constant
used internally by the software):
D (QMGR_REQ_SCAN_DEFERRED)
Start a deferred queue scan. If a deferred queue
scan is already in progress, that scan will be
2
QMGR(8) QMGR(8)
restarted as soon as it finishes.
I (QMGR_REQ_SCAN_INCOMING)
Start an incoming queue scan. If an incoming queue
scan is already in progress, that scan will be
restarted as soon as it finishes.
A (QMGR_REQ_SCAN_ALL)
Ignore deferred queue file time stamps. The request
affects the next deferred queue scan.
F (QMGR_REQ_FLUSH_DEAD)
Purge all information about dead transports and
destinations.
W (TRIGGER_REQ_WAKEUP)
Wakeup call, This is used by the master server to
instantiate servers that should not go away for-
ever. The action is to start an incoming queue
scan.
The qmgr daemon reads an entire buffer worth of triggers.
Multiple identical trigger requests are collapsed into
one, and trigger requests are sorted so that A and F pre-
cede D and I. Thus, in order to force a deferred queue
run, one would request A F D; in order to notify the queue
manager of the arrival of new mail one would request I.
STANDARDS
None. The qmgr daemon does not interact with the outside
world.
SECURITY
The qmgr daemon is not security sensitive. It reads sin-
gle-character messages from untrusted local users, and
thus may be susceptible to denial of service attacks. The
qmgr daemon does not talk to the outside world, and it can
be run at fixed low privilege in a chrooted environment.
DIAGNOSTICS
Problems and transactions are logged to the syslog daemon.
Corrupted message files are saved to the corrupt queue for
further inspection.
Depending on the setting of the notify_classes parameter,
the postmaster is notified of bounces and of other trou-
ble.
BUGS
A single queue manager process has to compete for disk
access with multiple front-end processes such as smtpd. A
sudden burst of inbound mail can negatively impact out-
bound delivery rates.
3
QMGR(8) QMGR(8)
CONFIGURATION PARAMETERS
The following main.cf parameters are especially relevant
to this program. See the Postfix main.cf file for syntax
details and for default values. Use the postfix reload
command after a configuration change.
Miscellaneous
relocated_maps
Tables with contact information for users, hosts or
domains that no longer exist. See relocated(5).
queue_directory
Top-level directory of the Postfix queue.
Active queue controls
qmgr_message_active_limit
Limit the number of messages in the active queue.
qmgr_message_recipient_limit
Limit the number of in-memory recipients.
This parameter also limits the size of the short-
term, in-memory destination cache.
Timing controls
min_backoff
Minimal time in seconds between delivery attempts
of a deferred message.
This parameter also limits the time an unreachable
destination is kept in the short-term, in-memory
destination status cache.
max_backoff
Maximal time in seconds between delivery attempts
of a deferred message.
maximal_queue_lifetime
Maximal time in days a message is queued before it
is sent back as undeliverable.
queue_run_delay
Time in seconds between deferred queue scans. Queue
scans do not overlap.
transport_retry_time
Time in seconds between attempts to contact a bro-
ken delivery transport.
Concurrency controls
In the text below, transport is the first field in a mas-
ter.cf entry.
4
QMGR(8) QMGR(8)
initial_destination_concurrency
Initial per-destination concurrency level for par-
allel delivery to the same destination.
default_destination_concurrency_limit
Default limit on the number of parallel deliveries
to the same destination.
transport_destination_concurrency_limit
Limit on the number of parallel deliveries to the
same destination, for delivery via the named mes-
sage transport.
Recipient controls
default_destination_recipient_limit
Default limit on the number of recipients per mes-
sage transfer.
transport_destination_recipient_limit
Limit on the number of recipients per message
transfer, for the named message transport.
SEE ALSO
master(8), process manager
relocated(5), format of the "user has moved" table
syslogd(8) system logging
trivial-rewrite(8), address routing
LICENSE
The Secure Mailer license must be distributed with this
software.
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
5
postfix/doc/postsuper.1.html 100664 1751 146 5210 7017475555 15367 0 ustar thivillo www
POSTSUPER(1) POSTSUPER(1)
NAME
postsuper - Postfix super intendent
SYNOPSIS
postsuper [-p] [-s] [-v] [directory ...]
DESCRIPTION
The postsuper command does small maintenance jobs on the
named Postfix queue directories (default: all). Directory
names are relative to the Postfix top-level queue direc-
tory.
By default, postsuper performs the operations requested
with the -s and -p command-line options. postsuper always
tries to remove objects that are neither files nor direc-
tories. Use of this command is restricted to the super-
user.
Options:
-s Structure check. Move queue files that are in the
wrong place in the file system hierarchy and remove
subdirectories that are no longer needed. File
rearrangements are necessary after a change in the
hash_queue_names and/or hash_queue_depth configura-
tion parameters. It is highly recommended to run
this check once before Postfix startup.
-p Purge stale files (files that are left over after
system or software crashes).
-v Enable verbose logging for debugging purposes. Mul-
tiple -v options make the software increasingly
verbose.
DIAGNOSTICS
Problems are reported to the standard error stream and to
syslogd.
CONFIGURATION PARAMETERS
See the Postfix main.cf file for syntax details and for
default values.
hash_queue_depth
Number of subdirectory levels for hashed queues.
hash_queue_names
The names of queues that are organized into multi-
ple levels of subdirectories.
LICENSE
The Secure Mailer license must be distributed with this
software.
1
POSTSUPER(1) POSTSUPER(1)
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
2
postfix/doc/postmap.1.html 100664 1751 146 11160 7017475555 15027 0 ustar thivillo www
POSTMAP(1) POSTMAP(1)
NAME
postmap - Postfix lookup table management
SYNOPSIS
postmap [-c config_dir] [-i] [-v] [-w]
[file_type:]file_name
DESCRIPTION
The postmap command creates a new Postfix lookup table, or
updates an existing one. The input and output formats are
expected to be compatible with:
makemap file_type file_name < file_name
While the table update is in progress, signal delivery is
postponed, and an exclusive, advisory, lock is placed on
the entire table, in order to avoid surprises in spectator
programs.
The format of a lookup table input file is as follows:
o Blank lines are ignored. So are lines beginning
with `#'.
o A table entry has the form
key whitespace value
o A line that starts with whitespace continues the
preceding line.
The key and value are processed as is, except that sur-
rounding white space is stripped off. Unlike with Postfix
alias databases, quotes cannot be used to protect lookup
keys that contain special characters such as `#' or
whitespace. The key is mapped to lowercase to make mapping
lookups case insensitive.
Options:
-c config_dir
Read the main.cf configuration file in the named
directory.
-i Incremental mode. Read entries from standard input
and do not truncate an existing database. By
default, postmap creates a new database from the
entries in file_name.
-v Enable verbose logging for debugging purposes. Mul-
tiple -v options make the software increasingly
verbose.
B-w Do not warn about duplicate entries; silently
1
POSTMAP(1) POSTMAP(1)
ignore them.
Arguments:
file_type
The type of database to be produced.
btree The output file is a btree file, named
file_name.db. This is available only on
systems with support for db databases.
dbm The output consists of two files, named
file_name.pag and file_name.dir. This is
available only on systems with support for
dbm databases.
hash The output file is a hashed file, named
file_name.db. This is available only on
systems with support for db databases.
When no file_type is specified, the software uses
the database type specified via the database_type
configuration parameter.
file_name
The name of the lookup table source file when
rebuilding a database.
DIAGNOSTICS
Problems and transactions are logged to the standard error
stream. No output means no problems. Duplicate entries are
skipped and are flagged with a warning.
ENVIRONMENT
MAIL_CONFIG
Directory with Postfix configuration files.
MAIL_VERBOSE
Enable verbose logging for debugging purposes.
CONFIGURATION PARAMETERS
database_type
Default output database type. On many UNIX sys-
tems, the default database type is either hash or
dbm.
LICENSE
The Secure Mailer license must be distributed with this
software.
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
2
POSTMAP(1) POSTMAP(1)
Yorktown Heights, NY 10598, USA
3
postfix/doc/postlog.1.html 100664 1751 146 3550 7017475555 15017 0 ustar thivillo www
POSTLOG(1) POSTLOG(1)
NAME
postlog - Postfix-compatible logging utility
SYNOPSIS
postlog [-i] [-p priority] [-t tag] [-v] [text...]
DESCRIPTION
The postlog command implements a Postfix-compatible log-
ging interface for use in, for example, shell scripts.
By default, postlog logs the text given on the command
line as one record. If no text is specified on the command
line, postlog reads from standard input and logs each
input line as one record.
Logging is sent to syslogd(8); when the standard error
stream is connected to a terminal, logging is sent there
as well.
The following options are implemented:
-i Include the process ID in the logging tag.
-p priority
Specifies the logging severity: info (default),
warn, error, fatal, or panic.
-t tag Specifies the logging tag, that is, the identifying
name that appears at the beginning of each logging
record.
-v Enable verbose logging for debugging purposes. Mul-
tiple -v options make the software increasingly
verbose.
SEE ALSO
syslogd(8) syslog daemon.
LICENSE
The Secure Mailer license must be distributed with this
software.
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
1
postfix/doc/postlock.1.html 100664 1751 146 6624 7017475555 15173 0 ustar thivillo www
POSTLOCK(1) POSTLOCK(1)
NAME
postlock - lock mail folder and execute command
SYNOPSIS
postlock [-c config_dir] [-v] file command...
DESCRIPTION
The postlock command locks file for exclusive access, and
executes command. The locking method is compatible with
the Postfix UNIX-style local delivery agent.
Options:
-c config_dir
Read configuration information from main.cf in the
named configuration directory.
-v Enable verbose logging for debugging purposes. Mul-
tiple -v options make the software increasingly
verbose.
Arguments:
file A mailbox file. The user should have read/write
permission.
command...
The command to execute while file is locked for
exclusive access. The command is executed
directly, i.e. without interpretation by a shell
command interpreter.
DIAGNOSTICS
The result status is 75 (EX_TEMPFAIL) when the file is
locked by another process, 255 (on some systems: -1) when
postlock could not perform the requested operation. Oth-
erwise, the exit status is the exit status from the com-
mand.
BUGS
With remote file systems, the ability to acquire a lock
does not necessarily eliminate access conflicts. Avoid
file access by processes running on different machines.
ENVIRONMENT
MAIL_CONFIG
Directory with Postfix configuration files.
MAIL_VERBOSE
Enable verbose logging for debugging purposes.
CONFIGURATION PARAMETERS
The following main.cf parameters are especially relevant
to this program. See the Postfix main.cf file for syntax
1
POSTLOCK(1) POSTLOCK(1)
details and for default values.
Locking controls
deliver_lock_attempts
Limit the number of attempts to acquire an exclu-
sive lock.
deliver_lock_delay
Time in seconds between successive attempts to
acquire an exclusive lock.
stale_lock_time
Limit the time after which a stale lock is removed.
Resource controls
fork_attempts
Number of attempts to fork() a process before giv-
ing up.
fork_delay
Delay in seconds between successive fork()
attempts.
LICENSE
The Secure Mailer license must be distributed with this
software.
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
2
postfix/doc/postkick.1.html 100664 1751 146 5236 7017475555 15162 0 ustar thivillo www
POSTKICK(1) POSTKICK(1)
NAME
postkick - kick a Postfix service
SYNOPSIS
postkick [-c config_dir] [-v] class service request
DESCRIPTION
The postkick command sends request to the specified ser-
vice over a local transport channel. This command makes
Postfix private IPC accessible for use in, for example,
shell scripts.
Options:
-c config_dir
Read configuration information from main.cf in the
named configuration directory.
-v Enable verbose logging for debugging purposes. Mul-
tiple -v options make the software increasingly
verbose.
Arguments:
class Name of a class of local transport channel end-
points, either public (accessible by any local
user) or private (administrative access only).
service
The name of a local transport endpoint within the
named class.
request
A string. The list of valid requests is service-
specific.
DIAGNOSTICS
Problems and transactions are logged to the standard error
stream.
ENVIRONMENT
MAIL_CONFIG
Directory with Postfix configuration files.
MAIL_VERBOSE
Enable verbose logging for debugging purposes.
CONFIGURATION PARAMETERS
The following main.cf parameters are especially relevant
to this program. See the Postfix main.cf file for syntax
details and for default values.
queue_directory
Location of the Postfix queue, and of the local IPC
1
POSTKICK(1) POSTKICK(1)
communication endpoints.
SEE ALSO
qmgr(8) queue manager trigger protocol
pickup(8) local pickup daemon
LICENSE
The Secure Mailer license must be distributed with this
software.
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
2
postfix/doc/postfix.1.html 100664 1751 146 11421 7017475556 15041 0 ustar thivillo www
POSTFIX(1) POSTFIX(1)
NAME
postfix - Postfix control program
SYNOPSIS
postfix [-c config_dir] [-D] [-v] command
DESCRIPTION
The postfix command controls the operation of the Postfix
mail system: start or stop the master daemon, do a health
check, and other maintenance. The command sets up a stan-
dardized environment and runs the postfix-script shell
script to do the actual work.
The following commands are implemented:
check Validate the Postfix mail system configuration.
Warn about bad directory/file ownership or permis-
sions, and create missing directories.
start Start the Postfix mail system. This also runs the
configuration check described above.
stop Stop the Postfix mail system in an orderly fashion.
Running processes are allowed to terminate at their
earliest convenience.
Note: in order to refresh the Postfix mail system
after a configuration change, do not use the start
and stop commands in succession. Use the reload
command instead.
abort Stop the Postfix mail system abruptly. Running pro-
cesses are signaled to stop immediately.
flush Force delivery: attempt to deliver every message in
the deferred mail queue. Normally, attempts to
deliver delayed mail happen at regular intervals,
the interval doubling after each failed attempt.
reload Re-read configuration files. Running processes ter-
minate at their earliest convenience.
The following options are implemented:
-c config_dir
The absolute path to a directory with Postfix con-
figuration files. Use this to distinguish between
multiple Postfix instances on the same host.
-D (with postfix start only)
Run each Postfix daemon under control of a debugger
as specified via the debugger_command configuration
parameter.
1
POSTFIX(1) POSTFIX(1)
-v Enable verbose logging for debugging purposes. Mul-
tiple -v options make the software increasingly
verbose.
ENVIRONMENT
The postfix command sets the following environment vari-
ables:
MAIL_CONFIG
Directory with Postfix configuration files.
MAIL_VERBOSE
This is set when the -v command-line option is pre-
sent.
MAIL_DEBUG
This is set when the -D command-line option is pre-
sent.
The following configuration parameters are made available
as process environment variables with the same names:
command_directory
Directory with Postfix support commands (default:
$program_directory).
daemon_directory
Directory with Postfix daemon programs (default:
$program_directory).
config_directory
Directory with Postfix configuration files and with
administrative shell scripts.
queue_directory
The directory with the Postfix queue directory (and
with some files needed for programs running in a
chrooted environment).
mail_owner
The owner of the Postfix queue and of most Postfix
processes.
FILES
$config_directory/postfix-script, administrative commands
SEE ALSO
master(8) Postfix master program
LICENSE
The Secure Mailer license must be distributed with this
software.
2
POSTFIX(1) POSTFIX(1)
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
3
postfix/doc/postdrop.1.html 100664 1751 146 5157 7017475556 15210 0 ustar thivillo www
POSTDROP(1) POSTDROP(1)
NAME
postdrop - Postfix mail posting agent
SYNOPSIS
postdrop [option ...]
DESCRIPTION
The postdrop command creates a file in the maildrop direc-
tory and copies its standard input to the file.
The command is designed to run with set-gid privileges,
and with group write permission to the maildrop queue
directory.
The postdrop command is automatically invoked by the send-
mail(1) mail posting agent when the maildrop queue direc-
tory is not world-writable.
Options:
-v Enable verbose logging for debugging purposes. Mul-
tiple -v options make the software increasingly
verbose.
SECURITY
This program is designed so that it can run with set-user
(or group) id privileges.
DIAGNOSTICS
Fatal errors: malformed input, I/O error, out of memory.
Problems are logged to syslogd(8) and to the standard
error stream. When the input is incomplete, or when the
process receives a HUP, INT, QUIT or TERM signal, the
queue file is deleted.
ENVIRONMENT
The program deletes all environment information, because
the C library can't be trusted.
FILES
/var/spool/postfix, mail queue
/etc/postfix, configuration files
CONFIGURATION PARAMETERS
See the Postfix main.cf file for syntax details and for
default values. Use the postfix reload command after a
configuration change.
queue_directory
Top-level directory of the Postfix queue. This is
also the root directory of Postfix daemons that run
chrooted.
1
POSTDROP(1) POSTDROP(1)
SEE ALSO
sendmail(1) compatibility interface
syslogd(8) system logging
LICENSE
The Secure Mailer license must be distributed with this
software.
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
2
postfix/doc/postconf.1.html 100664 1751 146 2752 7017475556 15167 0 ustar thivillo www
POSTCONF(1) POSTCONF(1)
NAME
postconf - Postfix configuration utility
SYNOPSIS
postconf [-c config_dir] [-d] [-h] [-n] [-v] [parameter
...]
DESCRIPTION
The postconf command prints the actual value of parameter
(all known parameters by default), one parameter per line.
Options:
-c config_dir
The main.cf configuration file is in the named
directory.
-d Print default parameter settings instead of actual
settings.
-h Show parameter values only, not the ``name = ''
label that normally precedes the value.
-n Print non-default parameter settings only.
-v Enable verbose logging for debugging purposes. Mul-
tiple -v options make the software increasingly
verbose.
DIAGNOSTICS
Problems are reported to the standard error stream.
LICENSE
The Secure Mailer license must be distributed with this
software.
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
1
postfix/doc/postcat.1.html 100664 1751 146 2130 7017475556 14777 0 ustar thivillo www
POSTCAT(1) POSTCAT(1)
NAME
postcat - show Postfix queue file contents
SYNOPSIS
postcat [-v] [files...]
DESCRIPTION
The postcat command prints the contents of the named Post-
fix queue files in human-readable form. If no files are
specified on the command line, the program reads from
standard input.
Options:
-v Enable verbose logging for debugging purposes. Mul-
tiple -v options make the software increasingly
verbose.
DIAGNOSTICS
Problems are reported to the standard error stream.
LICENSE
The Secure Mailer license must be distributed with this
software.
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
1
postfix/doc/postalias.1.html 100664 1751 146 10365 7017475556 15352 0 ustar thivillo www
POSTALIAS(1) POSTALIAS(1)
NAME
postalias - Postfix alias database maintenance
SYNOPSIS
postalias [-c config_dir] [-i] [-v] [-w]
[file_type:]file_name ...
DESCRIPTION
The postalias command creates a new Postfix alias
database, or updates an existing one. The input and output
file formats are expected to be compatible with Sendmail
version 8, and are expected to be suitable for the use as
NIS alias maps.
While a database update is in progress, signal delivery is
postponed, and an exclusive, advisory, lock is placed on
the entire database, in order to avoid surprises in spec-
tator programs.
Options:
-c config_dir
Read the main.cf configuration file in the named
directory.
-i Incremental mode. Read entries from standard input
and do not truncate an existing database. By
default, postalias creates a new database from the
entries in file_name.
-v Enable verbose logging for debugging purposes. Mul-
tiple -v options make the software increasingly
verbose.
-w Do not warn about duplicate entries; silently
ignore them.
Arguments:
file_type
The type of database to be produced.
btree The output is a btree file, named
file_name.db. This is available only on
systems with support for db databases.
dbm The output consists of two files, named
file_name.pag and file_name.dir. This is
available only on systems with support for
dbm databases.
hash The output is a hashed file, named
file_name.db. This is available only on
systems with support for db databases.
1
POSTALIAS(1) POSTALIAS(1)
When no file_type is specified, the software uses
the database type specified via the database_type
configuration parameter. The default value for
this parameter depends on the host environment.
file_name
The name of the alias database source file when
rebuilding a database.
DIAGNOSTICS
Problems are logged to the standard error stream. No out-
put means no problems were detected. Duplicate entries are
skipped and are flagged with a warning.
ENVIRONMENT
MAIL_CONFIG
Directory with Postfix configuration files.
MAIL_VERBOSE
Enable verbose logging for debugging purposes.
CONFIGURATION PARAMETERS
The following main.cf parameters are especially relevant
to this program. See the Postfix main.cf file for syntax
details and for default values.
database_type
Default alias database type. On many UNIX systems,
the default type is either dbm or hash.
STANDARDS
RFC 822 (ARPA Internet Text Messages)
SEE ALSO
aliases(5) format of alias database input file.
sendmail(1) mail posting and compatibility interface.
LICENSE
The Secure Mailer license must be distributed with this
software.
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
2
postfix/doc/pipe.8.html 100664 1751 146 21114 7017475556 14311 0 ustar thivillo www
PIPE(8) PIPE(8)
NAME
pipe - Postfix delivery to external command
SYNOPSIS
pipe [generic Postfix daemon options] command_attributes...
DESCRIPTION
The pipe daemon processes requests from the Postfix queue
manager to deliver messages to external commands. Each
delivery request specifies a queue file, a sender address,
a domain or host to deliver to, and one or more recipi-
ents. This program expects to be run from the master(8)
process manager.
The pipe daemon updates queue files and marks recipients
as finished, or it informs the queue manager that delivery
should be tried again at a later time. Delivery problem
reports are sent to the bounce(8) or defer(8) daemon as
appropriate.
COMMAND ATTRIBUTE SYNTAX
The external command attributes are given in the master.cf
file at the end of a service definition. The syntax is as
follows:
flags=FR> (optional)
Optional message processing flags. By default, a
message is copied unchanged.
F Prepend a "From sender time_stamp" envelope
header to the message content. This is
expected by, for example, UUCP software. The
F flag also causes an empty line to be
appended to the message.
R Prepend a Return-Path: message header with
the envelope sender address.
> Prepend > to lines starting with "From ".
This is expected by, for example, UUCP soft-
ware.
user=username (required)
user=username:groupname
The external command is executed with the rights of
the specified username. The software refuses to
execute commands with root privileges, or with the
privileges of the mail system owner. If groupname
is specified, the corresponding group ID is used
instead of the group ID of of username.
argv=command... (required)
The command to be executed. This must be specified
1
PIPE(8) PIPE(8)
as the last command attribute. The command is exe-
cuted directly, i.e. without interpretation of
shell meta characters by a shell command inter-
preter.
In the command argument vector, the following
macros are recognized and replaced with correspond-
ing information from the Postfix queue manager
delivery request:
${extension}
This macro expands to the extension part of
a recipient address. For example, with an
address user+foo@domain the extension is
foo. A command-line argument that contains
${extension} expands into as many command-
line arguments as there are recipients.
${mailbox}
This macro expands to the complete local
part of a recipient address. For example,
with an address user+foo@domain the mailbox
is user+foo. A command-line argument that
contains ${mailbox} expands into as many
command-line arguments as there are recipi-
ents.
${nexthop}
This macro expands to the next-hop hostname.
${recipient}
This macro expands to the complete recipient
address. A command-line argument that con-
tains ${recipient} expands into as many com-
mand-line arguments as there are recipients.
${sender}
This macro expands to the envelope sender
address.
${user}
This macro expands to the username part of a
recipient address. For example, with an
address user+foo@domain the username part is
user. A command-line argument that contains
${user} expands into as many command-line
arguments as there are recipients.
In addition to the form ${name}, the forms $name and
$(name) are also recognized. Specify $$ where a single $
is wanted.
DIAGNOSTICS
Command exit status codes are expected to follow the
2
PIPE(8) PIPE(8)
conventions defined in <sysexits.h>.
Problems and transactions are logged to syslogd(8). Cor-
rupted message files are marked so that the queue manager
can move them to the corrupt queue for further inspection.
SECURITY
This program needs a dual personality 1) to access the
private Postfix queue and IPC mechanisms, and 2) to exe-
cute external commands as the specified user. It is there-
fore security sensitive.
CONFIGURATION PARAMETERS
The following main.cf parameters are especially relevant
to this program. See the Postfix main.cf file for syntax
details and for default values. Use the postfix reload
command after a configuration change.
Miscellaneous
mail_owner
The process privileges used while not running an
external command.
Resource controls
In the text below, transport is the first field in a mas-
ter.cf entry.
transport_destination_concurrency_limit
Limit the number of parallel deliveries to the same
destination, for delivery via the named transport.
The default limit is taken from the default_desti-
nation_concurrency_limit parameter. The limit is
enforced by the Postfix queue manager.
transport_destination_recipient_limit
Limit the number of recipients per message deliv-
ery, for delivery via the named transport. The
default limit is taken from the default_destina-
tion_recipient_limit parameter. The limit is
enforced by the Postfix queue manager.
transport_time_limit
Limit the time for delivery to external command,
for delivery via the named transport. The default
limit is taken from the command_time_limit parame-
ter. The limit is enforced by the Postfix queue
manager.
SEE ALSO
bounce(8) non-delivery status reports
master(8) process manager
qmgr(8) queue manager
syslogd(8) system logging
3
PIPE(8) PIPE(8)
LICENSE
The Secure Mailer license must be distributed with this
software.
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
4
postfix/doc/pickup.8.html 100664 1751 146 6054 7017475557 14636 0 ustar thivillo www
PICKUP(8) PICKUP(8)
NAME
pickup - Postfix local mail pickup
SYNOPSIS
pickup [generic Postfix daemon options]
DESCRIPTION
The pickup daemon waits for hints that new mail has been
dropped into the world-writable maildrop directory, and
feeds it into the cleanup(8) daemon. Ill-formatted files
are deleted without notifying the originator. This pro-
gram expects to be run from the master(8) process manager.
STANDARDS
None. The pickup daemon does not interact with the outside
world.
SECURITY
The pickup daemon runs with superuser privileges so that
it 1) can open a queue file with the rights of the submit-
ting user and 2) can access the Postfix private IPC chan-
nels. On the positive side, the program can run chrooted,
opens no files for writing, is careful about what files it
opens for reading, and does not actually touch any data
that is sent to its public service endpoint.
DIAGNOSTICS
Problems and transactions are logged to syslogd(8).
BUGS
The pickup daemon copies mail from file to the cleanup(8)
daemon. It could avoid message copying overhead by send-
ing a file descriptor instead of file data, but then the
already complex cleanup(8) daemon would have to deal with
unfiltered user data.
CONFIGURATION PARAMETERS
The following main.cf parameters are especially relevant
to this program. See the Postfix main.cf file for syntax
details and for default values. Use the postfix reload
command after a configuration change.
Miscellaneous
always_bcc
Address to send a copy of each message that enters
the system.
mail_owner
The process privileges used while not opening a
maildrop file.
queue_directory
Top-level directory of the Postfix queue.
1
PICKUP(8) PICKUP(8)
SEE ALSO
cleanup(8) message canonicalization
master(8) process manager
syslogd(8) system logging
LICENSE
The Secure Mailer license must be distributed with this
software.
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
2
postfix/doc/outbound.gif 100664 1751 146 7745 7017475557 14645 0 ustar thivillo www GIF89a
! ,
ڋH扦ʶ L
ĢL*̦ JԪj N
xm%hxCxXHY 29iY):dJډĪK*t[ԻR') wYl 0 -=M]m}
==Nݬ\>.O ?~>.ឿv X` H D8=
6xHB
C`̈E M$q_G Q҃E-cF۸M0w4ie9w)k3 h֒:Zi)/J4խ\iMeԯ6Ң V:2Z4bӝZJeW%߾4淋YɎoF8` C5x wԪ3OxgwtҶg` hGF[Snyq }zAt *pcC,Sv߾x}v
`w)<$`xC aWaGYxqu 5֞oQVsi
HAgg~), YIe[|:Hր"HvSh68a #EQYVu Ld\uXY^bnY%
UBBce k~ RWp@tЛd?Dz9柀Ph>m6Ϟn袗(Χi iy
%i9) jjR:OAuJPHm%zvK,ɸA̳l ml_ws( I~k϶9 `L)Tn~pK%7R5n#{0 /1 ? ^gѰ_,q1!CB%r ] jZ *Z42 #缐ƌC:s1C 4/m$;K/2G" %ǪA7g !5̶O([lX{R'F+i؍1:mk`kH Nxc6/^8?84Eyc^)/^l_$y蛏Vgz) zw1 ^y0nz;q{N$] |OAߞo?߃/=17_.O9/S{?9{ c{.Nw
N ;8
= * aF&aa6"!|(dyXw
-b^X ndx& L!=,^[Lc>Uψ A
8ю#t". <<&nS'H.R<" ).pvm d'?YDP~1W)CJO2 *_yOΣN T2ߓ` )HJBRd1˨GW2| nLA
r&g;\syl%2WYCq<#7YMv+_K8=ihs%XH ҟhY
x2t(=EQ3)]ҙ&BBP 5R3sT'IlaBSh 3BudDӞբf\TrH(FZDb5PjVHU&UNBh֭B{1 +Y*/Qe[-ʕ|^W=u{%M~*dbEZ1 -[Yj-䱓GWKg|6U`h>085&`/mJ;GVCxZWЊֶíi
We k祸8.w>mtMr؝.oqZd
jzy=q}XX}_ϱ%>l]2.n-i
02bIx+1;aC,'Ո-z.N΅{d1Fql
j{w̥$٭HZj^@,8q@)_B`r#¬Y j2_ +fȶ-_2&lZ f7*ufdJVMnF\r>ځu;iIetmvML vZijJWke1@/:gUs&տ
kFp2BDעVZXfѿ6bSa;֮4 X^]L[ݰfO ңt ]W{FKH
SENDMAIL(1) SENDMAIL(1)
NAME
sendmail - Postfix to Sendmail compatibility interface
SYNOPSIS
sendmail [option ...] [recipient ...]
mailq
sendmail -bp
newaliases
sendmail -I
DESCRIPTION
The sendmail program implements the Postfix to Sendmail
compatibility interface. For the sake of compatibility
with existing applications, some Sendmail command-line
options are recognized but silently ignored.
By default, sendmail reads a message from standard input
and arranges for delivery. sendmail attempts to create a
queue file in the maildrop directory. If that directory is
not world-writable, the message is piped through the post-
drop(1) command, which is expected to execute with suit-
able privileges.
Specific command aliases are provided for other common
modes of operation:
mailq List the mail queue. Each entry shows the queue
file ID, message size, arrival time, sender, and
the recipients that still need to be delivered. If
mail could not be delivered upon the last attempt,
the reason for failure is shown. This mode of oper-
ation is implemented by connecting to the showq(8)
daemon.
newaliases
Initialize the alias database. If no alias database
type is specified, the program uses the type speci-
fied in the database_type configuration parameter;
if no input file is specified, the program pro-
cesses the file(s) specified with the
alias_database configuration parameter. This mode
of operation is implemented by running the postal-
ias(1) command.
Note: it may take a minute or so before an alias
database update becomes visible. Use the postfix
reload command to eliminate this delay.
These and other features can be selected by specifying the
appropriate combination of command-line options. Some fea-
tures are controlled by parameters in the main.cf configu-
ration file.
1
SENDMAIL(1) SENDMAIL(1)
The following options are recognized:
-B body_type (ignored)
The message body MIME type. Currently, Postfix
implements just-send-eight.
-C config_file (ignored :-)
The path name of the sendmail.cf file. Postfix con-
figuration files are kept in /etc/postfix.
-F full_name
Set the sender full name. This is used only with
messages that have no From: message header.
-I Initialize alias database. See the newaliases com-
mand above.
-N dsn (ignored)
Delivery status notification control. Currently,
Postfix does not implement DSN.
-R return_limit (ignored)
Limit the size of bounced mail. Use the
bounce_size_limit configuration parameter instead.
-X log_file (ignored)
Log mailer traffic. Use the debug_peer_list and
debug_peer_level configuration parameters instead.
-bd Go into daemon mode. This mode of operation is
implemented by executing the postfix start command.
-bi Initialize alias database. See the newaliases com-
mand above.
-bm Read mail from standard input and arrange for
delivery. This is the default mode of operation.
-bp List the mail queue. See the mailq command above.
-bs Stand-alone SMTP server mode. Read SMTP commands
from standard input, and write responses to stan-
dard output. This mode of operation is implemented
by running the smtpd(8) daemon.
-f sender
Set the envelope sender address. This is the
address where delivery problems are sent to, unless
the message contains an Errors-To: message header.
-h hop_count (ignored)
Hop count limit. Use the hopcount_limit configura-
tion parameter instead.
2
SENDMAIL(1) SENDMAIL(1)
-i (ignored)
Lines beginning with "." get special treatment only
with -bs.
-m (ignored)
Backwards compatibility.
-n (ignored)
Backwards compatibility.
-oAalias_database
Non-default alias database. Specify pathname or
type:pathname. See postalias(1) for details.
-o7 (ignored)
-o8 (ignored)
The message body type. Currently, Postfix imple-
ments just-send-eight.
-om (ignored)
The sender is never eliminated from alias etc.
expansions.
-o x value (ignored)
Set option x to value. Use the equivalent configu-
ration parameter in main.cf instead.
-r sender
Set the envelope sender address. This is the
address where delivery problems are sent to, unless
the message contains an Errors-To: message header.
-q Flush the mail queue. This is implemented by kick-
ing the qmgr(8) daemon.
-qinterval (ignored)
The interval between queue runs. Use the
queue_run_delay configuration parameter instead.
-t Extract recipients from message headers. This
requires that no recipients be specified on the
command line.
-v Enable verbose logging for debugging purposes. Mul-
tiple -v options make the software increasingly
verbose.
SECURITY
By design, this program is not set-user (or group) id.
However, it must handle data from untrusted users or
untrusted machines. Thus, the usual precautions need to
be taken against malicious inputs.
3
SENDMAIL(1) SENDMAIL(1)
DIAGNOSTICS
Problems are logged to syslogd(8) and to the standard
error stream.
ENVIRONMENT
MAIL_CONFIG
Directory with Postfix configuration files.
MAIL_VERBOSE
Enable verbose logging for debugging purposes.
MAIL_DEBUG
Enable debugging with an external command, as spec-
ified with the debugger_command configuration
parameter.
FILES
/var/spool/postfix, mail queue
/etc/postfix, configuration files
CONFIGURATION PARAMETERS
See the Postfix main.cf file for syntax details and for
default values. Use the postfix reload command after a
configuration change.
alias_database
Default alias database(s) for newaliases. The
default value for this parameter is system-spe-
cific.
bounce_size_limit
The amount of original message context that is sent
along with a non-delivery notification.
database_type
Default alias etc. database type. On many UNIX sys-
tems the default type is either dbm or hash.
debugger_command
Command that is executed after a Postfix daemon has
initialized.
debug_peer_level
Increment in verbose logging level when a remote
host matches a pattern in the debug_peer_list
parameter.
debug_peer_list
List of domain or network patterns. When a remote
host matches a pattern, increase the verbose log-
ging level by the amount specified in the
debug_peer_level parameter.
4
SENDMAIL(1) SENDMAIL(1)
fork_attempts
Number of attempts to fork() a process before giv-
ing up.
fork_delay
Delay in seconds between successive fork()
attempts.
hopcount_limit
Limit the number of Received: message headers.
mail_owner
The owner of the mail queue and of most Postfix
processes.
command_directory
Directory with Postfix support commands (default:
$program_directory).
daemon_directory
Directory with Postfix daemon programs (default:
$program_directory).
queue_directory
Top-level directory of the Postfix queue. This is
also the root directory of Postfix daemons that run
chrooted.
queue_run_delay
The time between successive scans of the deferred
queue.
SEE ALSO
pickup(8) mail pickup daemon
postalias(1) maintain alias database
postdrop(1) privileged posting agent
postfix(1) mail system control
postkick(1) kick a Postfix daemon
qmgr(8) queue manager
showq(8) list mail queue
smtpd(8) SMTP server
syslogd(8) system logging
LICENSE
The Secure Mailer license must be distributed with this
software.
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
5
postfix/doc/motivation.html 100664 1751 146 3241 7017475557 15361 0 ustar thivillo www
Postfix
Overview - IntroductionPostfix is the freeware project that I started during my sabattical year in the USA while visiting IBM T.J. Watson Research. I am grateful to IBM for the opportunity to write this software and for their permission to give it away.
Postfix is my attempt to provide an alternative to the widely-used Sendmail program. Postfix attempts to be fast, easy to administer, and hopefully secure, while at the same time being sendmail compatible enough to not upset your users.
The original plan was to release this software under a different name, VMailer. With the release in sight, IBM's lawyers discovered that VMailer was too similar to an existing trade mark. So, the program will go through its life as Postfix instead.
Postfix is a direct competitor to the qmail by Dan Bernstein. That's competitor, not enemy. I'm sure that friendly competition will help to improve both programs.
MASTER(8) MASTER(8)
NAME
master - Postfix master process
SYNOPSIS
master [-c config_dir] [-D] [-t] [-v]
DESCRIPTION
The master daemon is the resident process that runs Post-
fix daemons on demand: daemons to send or receive messages
via the network, daemons to deliver mail locally, etc.
These daemons are created on demand up to a configurable
maximum number per service.
Postfix daemons terminate voluntarily, either after being
idle for a configurable amount of time, or after having
serviced a configurable number of requests. The exception
to this rule is the resident Postfix queue manager.
The behavior of the master daemon is controlled by the
master.cf configuration file. The table specifies zero or
more servers in the UNIX or INET domain, or servers that
take requests from a FIFO. Precise configuration details
are given in the master.cf file, and in the manual pages
of the respective daemons.
Options:
-c config_dir
Read the main.cf and master.cf configuration files
in the named directory.
-D After initialization, run a debugger on the master
process. The debugging command is specified with
the debugger_command in the main.cf global configu-
ration file.
-t Test mode. Return a zero exit status when the mas-
ter.pid lock file does not exist or when that file
is not locked. This is evidence that the master
daemon is not running.
-v Enable verbose logging for debugging purposes. This
option is passed on to child processes. Multiple -v
options make the software increasingly verbose.
Signals:
SIGHUP Upon receipt of a HUP signal (e.g., after postfix
reload), the master process re-reads its configura-
tion files. If a service has been removed from the
master.cf file, its running processes are termi-
nated immediately. Otherwise, running processes
are allowed to terminate as soon as is convenient,
so that changes in configuration settings affect
1
MASTER(8) MASTER(8)
only new service requests.
SIGTERM
Upon receipt of a TERM signal (e.g., after postfix
abort), the master process passes the signal on to
its child processes and terminates. This is useful
for an emergency shutdown. Normally one would ter-
minate only the master (postfix stop) and allow
running processes to finish what they are doing.
DIAGNOSTICS
Problems are reported to syslogd(8).
BUGS
ENVIRONMENT
MAIL_DEBUG
After initialization, start a debugger as specified
with the debugger_command configuration parameter
in the main.cf configuration file.
MAIL_CONFIG
Directory with Postfix configuration files.
CONFIGURATION PARAMETERS
The following main.cf parameters are especially relevant
to this program. See the Postfix main.cf file for syntax
details and for default values. Use the postfix reload
command after a configuration change.
Miscellaneous
mail_owner
The owner of the mail queue and of most Postfix
processes.
command_directory
Directory with Postfix support programs.
daemon_directory
Directory with Postfix daemon programs.
queue_directory
Top-level directory of the Postfix queue. This is
also the root directory of Postfix daemons that run
chrooted.
Resource controls
default_process_limit
Default limit for the number of simultaneous child
processes that provide a given service.
max_idle
Limit the time in seconds that a child process
waits between service requests.
2
MASTER(8) MASTER(8)
max_use
Limit the number of service requests handled by a
child process.
service_throttle_time
Time to avoid forking a server that appears to be
broken.
FILES
/etc/postfix/main.cf: global configuration file.
/etc/postfix/master.cf: master process configuration file.
/var/spool/postfix/pid/master.pid: master lock file.
SEE ALSO
qmgr(8) queue manager
pickup(8) local mail pickup
syslogd(8) system logging
LICENSE
The Secure Mailer license must be distributed with this
software.
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
3
postfix/doc/mailq.1.html 100664 1751 146 27415 7017475557 14463 0 ustar thivillo www
SENDMAIL(1) SENDMAIL(1)
NAME
sendmail - Postfix to Sendmail compatibility interface
SYNOPSIS
sendmail [option ...] [recipient ...]
mailq
sendmail -bp
newaliases
sendmail -I
DESCRIPTION
The sendmail program implements the Postfix to Sendmail
compatibility interface. For the sake of compatibility
with existing applications, some Sendmail command-line
options are recognized but silently ignored.
By default, sendmail reads a message from standard input
and arranges for delivery. sendmail attempts to create a
queue file in the maildrop directory. If that directory is
not world-writable, the message is piped through the post-
drop(1) command, which is expected to execute with suit-
able privileges.
Specific command aliases are provided for other common
modes of operation:
mailq List the mail queue. Each entry shows the queue
file ID, message size, arrival time, sender, and
the recipients that still need to be delivered. If
mail could not be delivered upon the last attempt,
the reason for failure is shown. This mode of oper-
ation is implemented by connecting to the showq(8)
daemon.
newaliases
Initialize the alias database. If no alias database
type is specified, the program uses the type speci-
fied in the database_type configuration parameter;
if no input file is specified, the program pro-
cesses the file(s) specified with the
alias_database configuration parameter. This mode
of operation is implemented by running the postal-
ias(1) command.
Note: it may take a minute or so before an alias
database update becomes visible. Use the postfix
reload command to eliminate this delay.
These and other features can be selected by specifying the
appropriate combination of command-line options. Some fea-
tures are controlled by parameters in the main.cf configu-
ration file.
1
SENDMAIL(1) SENDMAIL(1)
The following options are recognized:
-B body_type (ignored)
The message body MIME type. Currently, Postfix
implements just-send-eight.
-C config_file (ignored :-)
The path name of the sendmail.cf file. Postfix con-
figuration files are kept in /etc/postfix.
-F full_name
Set the sender full name. This is used only with
messages that have no From: message header.
-I Initialize alias database. See the newaliases com-
mand above.
-N dsn (ignored)
Delivery status notification control. Currently,
Postfix does not implement DSN.
-R return_limit (ignored)
Limit the size of bounced mail. Use the
bounce_size_limit configuration parameter instead.
-X log_file (ignored)
Log mailer traffic. Use the debug_peer_list and
debug_peer_level configuration parameters instead.
-bd Go into daemon mode. This mode of operation is
implemented by executing the postfix start command.
-bi Initialize alias database. See the newaliases com-
mand above.
-bm Read mail from standard input and arrange for
delivery. This is the default mode of operation.
-bp List the mail queue. See the mailq command above.
-bs Stand-alone SMTP server mode. Read SMTP commands
from standard input, and write responses to stan-
dard output. This mode of operation is implemented
by running the smtpd(8) daemon.
-f sender
Set the envelope sender address. This is the
address where delivery problems are sent to, unless
the message contains an Errors-To: message header.
-h hop_count (ignored)
Hop count limit. Use the hopcount_limit configura-
tion parameter instead.
2
SENDMAIL(1) SENDMAIL(1)
-i (ignored)
Lines beginning with "." get special treatment only
with -bs.
-m (ignored)
Backwards compatibility.
-n (ignored)
Backwards compatibility.
-oAalias_database
Non-default alias database. Specify pathname or
type:pathname. See postalias(1) for details.
-o7 (ignored)
-o8 (ignored)
The message body type. Currently, Postfix imple-
ments just-send-eight.
-om (ignored)
The sender is never eliminated from alias etc.
expansions.
-o x value (ignored)
Set option x to value. Use the equivalent configu-
ration parameter in main.cf instead.
-r sender
Set the envelope sender address. This is the
address where delivery problems are sent to, unless
the message contains an Errors-To: message header.
-q Flush the mail queue. This is implemented by kick-
ing the qmgr(8) daemon.
-qinterval (ignored)
The interval between queue runs. Use the
queue_run_delay configuration parameter instead.
-t Extract recipients from message headers. This
requires that no recipients be specified on the
command line.
-v Enable verbose logging for debugging purposes. Mul-
tiple -v options make the software increasingly
verbose.
SECURITY
By design, this program is not set-user (or group) id.
However, it must handle data from untrusted users or
untrusted machines. Thus, the usual precautions need to
be taken against malicious inputs.
3
SENDMAIL(1) SENDMAIL(1)
DIAGNOSTICS
Problems are logged to syslogd(8) and to the standard
error stream.
ENVIRONMENT
MAIL_CONFIG
Directory with Postfix configuration files.
MAIL_VERBOSE
Enable verbose logging for debugging purposes.
MAIL_DEBUG
Enable debugging with an external command, as spec-
ified with the debugger_command configuration
parameter.
FILES
/var/spool/postfix, mail queue
/etc/postfix, configuration files
CONFIGURATION PARAMETERS
See the Postfix main.cf file for syntax details and for
default values. Use the postfix reload command after a
configuration change.
alias_database
Default alias database(s) for newaliases. The
default value for this parameter is system-spe-
cific.
bounce_size_limit
The amount of original message context that is sent
along with a non-delivery notification.
database_type
Default alias etc. database type. On many UNIX sys-
tems the default type is either dbm or hash.
debugger_command
Command that is executed after a Postfix daemon has
initialized.
debug_peer_level
Increment in verbose logging level when a remote
host matches a pattern in the debug_peer_list
parameter.
debug_peer_list
List of domain or network patterns. When a remote
host matches a pattern, increase the verbose log-
ging level by the amount specified in the
debug_peer_level parameter.
4
SENDMAIL(1) SENDMAIL(1)
fork_attempts
Number of attempts to fork() a process before giv-
ing up.
fork_delay
Delay in seconds between successive fork()
attempts.
hopcount_limit
Limit the number of Received: message headers.
mail_owner
The owner of the mail queue and of most Postfix
processes.
command_directory
Directory with Postfix support commands (default:
$program_directory).
daemon_directory
Directory with Postfix daemon programs (default:
$program_directory).
queue_directory
Top-level directory of the Postfix queue. This is
also the root directory of Postfix daemons that run
chrooted.
queue_run_delay
The time between successive scans of the deferred
queue.
SEE ALSO
pickup(8) mail pickup daemon
postalias(1) maintain alias database
postdrop(1) privileged posting agent
postfix(1) mail system control
postkick(1) kick a Postfix daemon
qmgr(8) queue manager
showq(8) list mail queue
smtpd(8) SMTP server
syslogd(8) system logging
LICENSE
The Secure Mailer license must be distributed with this
software.
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
5
postfix/doc/local.8.html 100664 1751 146 51363 7017475557 14460 0 ustar thivillo www
LOCAL(8) LOCAL(8)
NAME
local - Postfix local mail delivery
SYNOPSIS
local [generic Postfix daemon options]
DESCRIPTION
The local daemon processes delivery requests from the
Postfix queue manager to deliver mail to local recipients.
Each delivery request specifies a queue file, a sender
address, a domain or host to deliver to, and one or more
recipients. This program expects to be run from the mas-
ter(8) process manager.
The local daemon updates queue files and marks recipients
as finished, or it informs the queue manager that delivery
should be tried again at a later time. Delivery problem
reports are sent to the bounce(8) or defer(8) daemon as
appropriate.
SYSTEM-WIDE AND USER-LEVEL ALIASING
The system adminstrator can set up one or more system-wide
sendmail-style alias databases. Users can have sendmail-
style ~/.forward files. Mail for name is delivered to the
alias name, to destinations in ~name/.forward, to the
mailbox owned by the user name, or it is sent back as
undeliverable.
The system administrator can specify a comma/space sepa-
rated list of ~/.forward like files through the for-
ward_path configuration parameter. Upon delivery, the
local delivery agent tries each pathname in the list until
a file is found. The forward_path parameter is subject to
interpolation of $user (recipient username), $home (recip-
ient home directory), $shell (recipient shell), $recipient
(complete recipient address), $extension (recipient
address extension), $domain (recipient domain), local
(entire recipient address localpart) and $recipient_delim-
iter. The forms ${name?value} and ${name:value} expand
conditionally to value when $name is (is not) defined.
Characters that may have special meaning to the shell or
file system are replaced by underscores. The list of
acceptable characters is specified with the forward_expan-
sion_filter configuration parameter.
An alias or ~/.forward file may list any combination of
external commands, destination file names, :include:
directives, or mail addresses. See aliases(5) for a pre-
cise description. Each line in a user's .forward file has
the same syntax as the right-hand part of an alias.
When an address is found in its own alias expansion,
delivery is made to the user instead. When a user is
listed in the user's own ~/.forward file, delivery is made
1
LOCAL(8) LOCAL(8)
to the user's mailbox instead. An empty ~/.forward file
means do not forward mail.
In order to prevent the mail system from using up unrea-
sonable amounts of memory, input records read from
:include: or from ~/.forward files are broken up into
chunks of length line_length_limit.
While expanding aliases, ~/.forward files, and so on, the
program attempts to avoid duplicate deliveries. The dupli-
cate_filter_limit configuration parameter limits the num-
ber of remembered recipients.
MAIL FORWARDING
For the sake of reliability, forwarded mail is re-submit-
ted as a new message, so that each recipient has a sepa-
rate on-file delivery status record.
In order to stop mail forwarding loops early, the software
adds an optional Delivered-To: header with the envelope
recipient address. If mail arrives for a recipient that is
already listed in a Delivered-To: header, the message is
bounced.
MAILBOX DELIVERY
The default per-user mailbox is a file in the UNIX mail
spool directory (/var/mail/user or /var/spool/mail/user);
the location can be specified with the mail_spool_direc-
tory configuration parameter.
Alternatively, the per-user mailbox can be a file in the
user's home directory with a name specified via the
home_mailbox configuration parameter. Specify a relative
path name. Specify a name ending in / for qmail-compatible
maildir delivery.
Mailbox delivery can be delegated to an external command
specified with the mailbox_command configuration parame-
ter. The command executes with the privileges of the
recipient user (exception: in case of delivery as root,
the command executes with the privileges of
default_privs).
Mailbox delivery can be delegated to alternative message
transports specified in the master.cf file. The mail-
box_transport configuration parameter specifies a message
transport that is to be used for all local recipients,
regardless of whether they are found in the UNIX passwd
database. The fallback_transport parameter specifies a
message transport for recipients that are not found in the
UNIX passwd database.
In the case of UNIX-style mailbox delivery, the local dae-
mon prepends a "From sender time_stamp" envelope header to
2
LOCAL(8) LOCAL(8)
each message, prepends an optional Delivered-To: header
with the envelope recipient address, prepends a Return-
Path: header with the envelope sender address, prepends a
> character to lines beginning with "From ", and appends
an empty line. The mailbox is locked for exclusive access
while delivery is in progress. In case of problems, an
attempt is made to truncate the mailbox to its original
length.
In the case of maildir delivery, the local daemon prepends
an optional Delivered-To: header with the envelope recipi-
ent address and prepends a Return-Path: header with the
envelope sender address.
EXTERNAL COMMAND DELIVERY
The allow_mail_to_commands configuration parameter
restricts delivery to external commands. The default set-
ting (alias, forward) forbids command destinations in
:include: files.
The command is executed directly where possible. Assis-
tance by the shell (/bin/sh on UNIX systems) is used only
when the command contains shell magic characters, or when
the command invokes a shell built-in command.
A limited amount of command output (standard output and
standard error) is captured for inclusion with non-deliv-
ery status reports. A command is forcibly terminated if
it does not complete within command_time_limit seconds.
Command exit status codes are expected to follow the con-
ventions defined in <sysexits.h>.
A limited amount of message context is exported via envi-
ronment variables. Characters that may have special mean-
ing to the shell are replaced by underscores. The list of
acceptable characters is specified with the command_expan-
sion_filter configuration parameter.
SHELL The recipient user's login shell.
HOME The recipient user's home directory.
USER The bare recipient name.
EXTENSION
The optional recipient address extension.
DOMAIN The recipient address domain part.
LOGNAME
The bare recipient name.
LOCAL The entire recipient address localpart (text to the
left of the rightmost @ character).
3
LOCAL(8) LOCAL(8)
RECIPIENT
The entire recipient address.
The PATH environment variable is always reset to a system-
dependent default path, and the TZ (time zone) environment
variable is always passed on without change.
The current working directory is the mail queue directory.
The local daemon prepends a "From sender time_stamp" enve-
lope header to each message, prepends an optional Deliv-
ered-To: header with the recipient envelope address,
prepends a Return-Path: header with the sender envelope
address, and appends an empty line.
EXTERNAL FILE DELIVERY
The allow_mail_to_files configuration parameter restricts
delivery to external files. The default setting (alias,
forward) forbids file destinations in :include: files.
Specify a pathname ending in / for qmail-compatible
maildir delivery.
The local daemon prepends a "From sender time_stamp" enve-
lope header to each message, prepends an optional Deliv-
ered-To: header with the recipient envelope address,
prepends a > character to lines beginning with "From ",
and appends an empty line. The envelope sender address is
available in the Return-Path: header. When the destina-
tion is a regular file, it is locked for exclusive access
while delivery is in progress. In case of problems, an
attempt is made to truncate a regular file to its original
length.
In the case of maildir delivery, the local daemon prepends
an optional Delivered-To: header with the envelope recipi-
ent address. The envelope sender address is available in
the Return-Path: header.
ADDRESS EXTENSION
The optional recipient_delimiter configuration parameter
specifies how to separate address extensions from local
recipient names.
For example, with "recipient_delimiter = +", mail for
name+foo is delivered to the alias name+foo or to the
alias name, to the destinations listed in ~name/.for-
ward+foo or in ~name/.forward, to the mailbox owned by the
user name, or it is sent back as undeliverable.
In all cases the local daemon prepends an opional `Deliv-
ered-To: name+foo' header line.
DELIVERY RIGHTS
Deliveries to external files and external commands are
4
LOCAL(8) LOCAL(8)
made with the rights of the receiving user on whose behalf
the delivery is made. In the absence of a user context,
the local daemon uses the owner rights of the :include:
file or alias database. When those files are owned by the
superuser, delivery is made with the rights specified with
the default_privs configuration parameter.
STANDARDS
RFC 822 (ARPA Internet Text Messages)
DIAGNOSTICS
Problems and transactions are logged to syslogd(8). Cor-
rupted message files are marked so that the queue manager
can move them to the corrupt queue afterwards.
Depending on the setting of the notify_classes parameter,
the postmaster is notified of bounces and of other trou-
ble.
BUGS
For security reasons, the message delivery status of
external commands or of external files is never check-
pointed to file. As a result, the program may occasionally
deliver more than once to a command or external file. Bet-
ter safe than sorry.
Mutually-recursive aliases or ~/.forward files are not
detected early. The resulting mail forwarding loop is
broken by the use of the Delivered-To: message header.
CONFIGURATION PARAMETERS
The following main.cf parameters are especially relevant
to this program. See the Postfix main.cf file for syntax
details and for default values. Use the postfix reload
command after a configuration change.
Miscellaneous
alias_maps
List of alias databases.
expand_owner_alias
When delivering to an alias that has an owner- com-
panion alias, set the envelope sender address to
the right-hand side of the owner alias, instead
using of the left-hand side address.
forward_path
Search list for .forward files. The names are sub-
ject to $name expansion.
local_command_shell
Shell to use for external command execution (for
example, /some/where/smrsh -c). When a shell is
specified, it is invoked even when the command
5
LOCAL(8) LOCAL(8)
contains no shell built-in commands or meta charac-
ters.
owner_request_special
Give special treatment to owner-xxx and xxx-request
addresses.
prepend_delivered_header
Prepend an optional Delivered-To: header upon
external forwarding, delivery to command or file.
Specify zero or more of: command, file, forward.
Turning off Delivered-To: when forwarding mail is
not recommended.
recipient_delimiter
Separator between username and address extension.
Mailbox delivery
fallback_transport
Message transport for recipients that are not found
in the UNIX passwd database. This parameter over-
rides luser_relay.
home_mailbox
Pathname of a mailbox relative to a user's home
directory. Specify a path ending in / for maildir-
style delivery.
luser_relay
Destination (@domain or address) for non-existent
users. The address is subjected to $name expan-
sion.
mail_spool_directory
Directory with UNIX-style mailboxes. The default
pathname is system dependent.
mailbox_command
External command to use for mailbox delivery. The
command executes with the recipient privileges
(exception: root). The string is subject to $name
expansions.
mailbox_transport
Message transport to use for mailbox delivery to
all local recipients, whether or not they are found
in the UNIX passwd database. This parameter over-
rides all other configuration parameters that con-
trol mailbox delivery, including luser_relay.
Locking controls
deliver_lock_attempts
Limit the number of attempts to acquire an exclu-
sive lock on a mailbox or external file.
6
LOCAL(8) LOCAL(8)
deliver_lock_delay
Time in seconds between successive attempts to
acquire an exclusive lock.
stale_lock_time
Limit the time after which a stale lock is removed.
Resource controls
command_time_limit
Limit the amount of time for delivery to external
command.
duplicate_filter_limit
Limit the size of the duplicate filter for results
from alias etc. expansion.
line_length_limit
Limit the amount of memory used for processing a
partial input line.
local_destination_concurrency_limit
Limit the number of parallel deliveries to the same
user. The default limit is taken from the
default_destination_concurrency_limit parameter.
local_destination_recipient_limit
Limit the number of recipients per message deliv-
ery. The default limit is taken from the
default_destination_recipient_limit parameter.
Security controls
allow_mail_to_commands
Restrict the usage of mail delivery to external
command.
allow_mail_to_files
Restrict the usage of mail delivery to external
file.
command_expansion_filter
What characters are allowed to appear in $name
expansions of mailbox_command. Illegal characters
are replaced by underscores.
default_privs
Default rights for delivery to external file or
command.
forward_expansion_filter
What characters are allowed to appear in $name
expansions of forward_path. Illegal characters are
replaced by underscores.
7
LOCAL(8) LOCAL(8)
HISTORY
The Delivered-To: header appears in the qmail system by
Daniel Bernstein.
The maildir structure appears in the qmail system by
Daniel Bernstein.
SEE ALSO
aliases(5) format of alias database
bounce(8) non-delivery status reports
postalias(1) create/update alias database
syslogd(8) system logging
qmgr(8) queue manager
LICENSE
The Secure Mailer license must be distributed with this
software.
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
8
postfix/doc/index.html 100664 1751 146 2334 7017475557 14301 0 ustar thivillo www
Wietse's Postfix Project
All programmers are optimists -- Frederick P. Brooks, Jr.
First of all, thank you for your interest in the Postfix project.
What is Postfix? It is Wietse Venema's attempt to provide an alternative to the widely-used Sendmail program. Sendmail is responsible for an estimated 70% of all e-mail delivered on the Internet. With an estimated 100 million users, that's billions of messages daily. A stunning number.
Postfix attempts to be fast, easy to administer, and secure, while at the same time being sendmail compatible enough to not upset existing users.
Postfix
Overview - Goals and Features
Postfix Frequently Asked Questions
This assumes that your organization has set up multiple internal MX hosts for the local domain.
If your intranet does not use MX records internally, you have to specify the gateway host itself:
This assumes that your organization has set up multiple internal MX hosts for the local domain.
If your intranet does not use MX records internally, you have to specify the gateway host itself:
Specify dbm:/etc/postfix/transport if your system uses dbm files instead of db.
How to set up Postfix on the firewall machine so that it relays mail for my.domain to a gateway machine on the inside, and so that it refuses mail for *.my.domain? The problem is that the standard relay_domains mail relaying restriction allows mail to *.my.domain when you specify my.domain.
Specify dbm:/etc/postfix/virtual if your system uses dbm files instead of db.
Unfortunately, the solution cannot use the transport table, because that table is ignored for destinations that match $mydestination. That's an implementation error, and it will be removed.
If your machine is disconnected most of the time, there isn't a lot of opportunity for Postfix to deliver mail to hard-to-reach corners of the Internet. It's better to drop the mail to a machine that is connected all the time.
Normally, Postfix attempts to deliver outbound mail at its convenience. If your machine uses on-demand dialup IP, this causes your system to place a telephone call whenever you submit new mail, and whenever Postfix retries to deliver delayed mail. To prevent such telephone calls from being placed, disable spontaneous SMTP mail deliveries.
Some people use Postfix to deliver mail across a LAN that is disconnected most of the time. Under such conditions, mail delivery can suffer from delays while the Postfix SMTP client performs sender and recipient domain DNS lookups in order to be standards-compliant. To prevent these delays, disable all SMTP client DNS lookups.
When you disable DNS lookups, you must specify the relayhost as either a numeric IP address, or as a hostname that resolves to one or more IP addresses (with DNS lookup disabled, Postfix does no MX lookup).
Put the following command into your PPP or SLIP dialup scripts:
The exact location of the sendmail command is system-specific. With some UNIX versions, use /usr/lib/sendmail. If you have disabled spontaneous SMTP mail delivery, you also need to run the above command every now and then while the dialup link is up, so that newly-posted mail is flushed from the queue.
Address masquerading is intended for use only on mail gateways.
Note that the gateway should have append_dot_domain and append_myorigin turned on (which is the default setting) so that all addresses are fully qualified before they are subjected to address masquerading.
In some cases, you may wish to have certain users or hosts exempted from masquerading.
Note that the order above is crucial: exemptions such as somehost.my.domain must precede $mydomain in the statement.
It should go without saying that if a particular host you wish to exempt this way is originating mail as user@my.domain in the first place, you can hardly exempt it.
Currently, Postfix has no hooks to let other programs inspect every message, so the scanning has to be done before mail enters Postfix or while mail leaves Postfix, for example at mailbox delivery time.
Postfix supports the maildir mailbox format. Edit main.cf and specify a line with: home_mailbox = Maildir/ (any relative pathname that ends in / will do).
The maildir format is also supported for delivery from aliases or .forward files. Specify /file/name/ as destination. The trailing / turns on maildir delivery.
If you can, avoid using any shell meta characters or built-ins such as $ or " or IFS or &&, because they force Postfix to run an expensive shell process.
With a distributed mail system such as Postfix, this is difficult to implement. Postfix does not run any mail delivery process under control by a user. Instead, mail delivery is done by daemon processes that have no parental relationship with user processes. This eliminates a large variety of potential security exploits with environment variables, signal handlers, and with other process attributes that UNIX passes on from parent to child.
In addition, Postfix uses multiple processes in order to insulate subsystems from each other. Making the delivery agents talk directly to user processes would defeat a lot of the effort that went into making Postfix more secure than ordinary mailers.
Solutions, ranging from fighting symptoms to turning off the Delivered-To: header:
POSIX regular expression support (regexp) is enabled by default on modern UNIX systems. Perl-compatible regular expression support (pcre) is optional; see the PCRE_README file in the top-level Postfix source directory.
See also the FAQ item for problems with the majordomo approve command.
Currently, the workaround is to edit the approve script to strip any header lines that match:
Yes, this assumes that the moderator knows what she is doing.
This causes all mail for the some.domain (and subdomains thereof) to be sent via UUCP to the host uucp-host.
uucp unix - n n - - pipe
flags=F user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient)
This runs the uux command, and substitutes the next-hop hostname (uucp-host) and the recipients before executing the command. The uux command is executed without assistance from the shell, so there are no problems with shell meta characters.
Specify dbm instead of hash if your system has no db support.
uucp unix - n n - - pipe
flags=F user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient)
This runs the uux command, and substitutes the next-hop
hostname (uucp-gateway, or whatever you specified) and the
recipients before executing the command. The uux command
is executed without assistance from the shell, so there are no
problems with shell meta characters.
Over here we are using the scheme
In master.cf:
In the transports map:
Note: be sure to not advertise fax.your.domain in the DNS...
However, when you see mail deliveries fail consistently, you may
have a different problem: broken path MTU discovery.
A little background is in order. With the SMTP protocol, the HELO,
MAIL FROM and RCPT TO commands and responses are relatively short.
When you're talking to sendmail, every command and every response
is sent as a separate packet, because sendmail cannot implement
ESMTP command pipelining.
The message content, however, is sent as a few datagrams, each
datagram typically a kbyte large or even bigger, depending on your
local network MTU.
When mail fails consistently due to a timeout, I suspect that the
sending machine runs a modern UNIX which implements path MTU
discovery. That causes the machine to send packets as large as it
would send over the LAN, with the IP DONT'T FRAGMENT bit set,
preventing intermediate routers from fragmenting the packets that
are too big for their networks.
Depending on what network path a message follows, some router on
the way responds with an ICMP MUST FRAGMENT message saying the
packet is too big. Normally, the sending machine will re-send the
data after chopping it up into smaller pieces.
However, things break when some router closer to the sending system
is dropping such ICMP feedback messages, in a mistaken attempt to
protect systems against certain attacks. In that case, the ICMP
feedback message never reaches the sending machine, and the connection
times out.
This is the same configuration problem that causes trouble with
web servers behind a misconfigured packet filter: small images/files
are sent intact, large images/files time out because the server
does not see the MUST FRAGMENT ICMP feedback messages.
Workaround: disable path MTU discovery at the sending machine. Mail
will get out, but of course everyone else will still suffer. How
to disable path MTU discovery? It depends. Solaris has an ndd
command; other systems use different means such as sysctl
to control kernel parameters on a running system.
Fix: find the router that drops the ICMP MUST FRAGMENT messages,
and convince the person responsible for it to fix the configuration.
Answer: you're mixing BIND version 8 include files with a
different version of the resolver library.
Fix: use the right include files. For example:
In order to build Postfix with db support on UNIX systems
that do not have db support out of the box, you need the
db-1.85 release, or the current
version which has a db-1.85 compatible interface.
Use the following commands in the Postfix top-level directory.
The LD_LIBRARY_PATH unset commands may be required to avoid linking
in the wrong libraries.
Of course you will have to specify the actual location of the
include directory and of the object library.
One problem: older DB versions install a file /usr/include/ndbm.h
that is incompatible with the one in /usr/include. Be sure
to get rid of the bogus file, or the linker will fail to find
dbm_dirfno.
Once a message has reached the incoming queue the next step
is to deliver it. The figure shows the main components of the
Postfix mail delivery apparatus. For an explanation of the symbols,
click on the icon in the upper left-hand corner of this page.
The queue manager maintains a separate deferred queue for
mail that cannot be delivered, so that a large mail backlog will
not slow down normal queue accesses.
The queue manager maintains a small active queue with just
the few messages that it has opened for delivery. The active
queue acts as a limited window on the potentially much larger
incoming or deferred queues. The small active
queue prevents the queue manager from running out of memory under
heavy load.
Optionally, the queue manager bounces mail for recipients that are
listed in the relocated table.
This table contains contact information for users or even entire
domains that no longer exist.
Together with the sendmail mail
posting agent, the local delivery agent
implements the familiar Sendmail user interface.
The local delivery agent has hooks for
alternative forms of local delivery: you can configure it to
deliver to mailbox files in user home directories, and you can even
configure it to delegate mailbox delivery to an external command
such as the popular procmail program.
Enough daemon talk. The anatomy lesson ends with an introduction
to command-line utilities for day-to-day use of the Postfix mail
system. Besides the sendmail, mailq, and newaliases commands that were already
introduced, the Postfix system comes with it own collection of
utilities. For consistency, these are all named postsomething.
The figure shows the main Postfix system components, and the main
information flows between them. Postfix system components are
introduced in the Postfix anatomy
documentation.
The third parameter of interest controls the amount of mail sent
to the local postmaster:
By the way, if you change parameters of a running Postfix system,
don't forget to issue a postfix reload command.
If you run Postfix on a virtual network interface, or if your
machine runs other mailers on virtual interfaces, you'll have to
look at the other parameters listed here as well:
You can specify zero or more domain names, /file/name patterns
and/or type:name lookup tables, separated by whitespace
and/or commas. A /file/name is replaced by its contents;
type:name requests that a table lookup is done, typically
from a virtual database.
If your machine is a mail server for its entire domain, you must
list $mydomain as well.
Caution: in order to avoid mail delivery loops, you must list all
hostnames of the machine, including $myhostname, and localhost.$mydomain.
The Postfix system itself also reports problems to the postmaster
alias. You may not be interested in all types of trouble reports,
so this reporting mechanism is configurable. The default is to
report only serious problems (resource, software) to postmaster:
By default, myhostname is set to the local machine name.
If your machine name is not in fully-qualified domain name form,
or if you run Postfix on a virtual interface, you will have to
specify the fully-qualified domain name that the mail system
should use.
By default, mynetworks is set to the class A, B or C networks
that the machine is attached to. For example, for my machines at
home, the result is: 168.100.0.0/16 127.0.0.0/8. However,
network 168.100 is owned by my ISP. Of course I do not want
to consider all their customer systems as local, so I use instead:
The default is to listen on all active interfaces. If you run
mailers on virtual interfaces, you will have to specify what
interfaces to listen on. This includes the non-virtual mailer that
receives mail for the machine itself as well: it should never listen
on the virtual interfaces or you would have a mailer loop.
The previous sections gave a simplified overview of how the Postfix
system sends and receives mail. Several other things happen behind
the scenes. Unfortunately, this is hard to visualize on a
two-dimensional display, so this document has no illustration.
Postfix is implemented as a resident master server that runs Postfix
daemon processes on demand: daemon processes to send or receive
network mail messages, daemon processes to deliver mail locally,
etc. These processes are created up to a configurable number,
are re-used for a configurable number of times, and go away after
a configurable amount of idle time. This approach drastically
reduces process creation overhead while still providing the good
insulation from separate processes.
Postfix is intended to be a Sendmail replacement. For this reason
it tries to be compatible with existing infrastructure. However,
many parts of the Postfix system, such as the local delivery program,
are easily replaced by editing an inetd-like configuration
file. For example, the plan is to provide an alternate local
delivery program that runs at a fixed low privilege, for POP/IMAP
users that never log into the shell, and that may not even have a
UNIX account.
As a result of this architecture, Postfix is easy to strip down to
the bare minimum. Subsystems that are turned off cannot be exploited.
Firewalls do not need local delivery. On client workstations, one
disables both the smtp listener and local delivery subsystems; or
the client mounts the maildrop directory from a file server,
and runs no resident Postfix processes at all.
The amount of information passed on between Postfix processes is
limited. In many cases, the only information exchanged between
Postfix processes is a queue file name and a list of recipients or
some status information. Once an email message is saved to file it
stays there until it is read by a mail delivery program.
Postfix takes the usual precautions to avoid loss of information:
flush and fsync() all data before acknowledging receipt, and check
all system call results for error conditions. This style of
programming may be new to some people, but I can assure you that
it has been standard practice for years in many places.
- Comit Rseau des Universits
Reproduction strictement interdite
fax unix - n n - - pipe
flags= user=fax argv=/usr/bin/faxmail -d -n ${user}
fax.your.domain fax:localhost
Mail fails with timeout or lost connection
Occasionally, mail fails with "timed out while sending end of data
-- message may be sent more than once", or with: "lost connection after DATA".
Network outages happen, systems crash. There isn't much you can
do about it.
Undefined symbols: ___dn_expand, ___res_init etc.
Question: When I build Postfix I get the following errors:
ld: Undefined symbol
___dn_expand
___res_init
___res_search
*** Error code 1
make makefiles CCARGS="-I/usr/include".
Using DB libraries on Solaris etc.
The old dbm UNIX database has severe limitations when you
try to store lots of information. It breaks when the number of hash
collisions becomes so large that the entries no longer fit together
in a single disk block. The more modern db database does
not suffer these limitations. It is standard on 4.4BSD and Linux
systems.
Up one level | Postfix FAQ
postfix/doc/error.8.html 100664 1751 146 5676 7017475562 14501 0 ustar thivillo www
ERROR(8) ERROR(8)
NAME
error - Postfix error mailer
SYNOPSIS
error [generic Postfix daemon options]
DESCRIPTION
The Postfix error mailer processes message delivery
requests from the queue manager. Each request specifies a
queue file, a sender address, a domain or host name that
is treated as the reason for non-delivery, and recipient
information. This program expects to be run from the mas-
ter(8) process manager.
The error mailer client forces all recipients to bounce,
using the domain or host information as the reason for
non-delivery, updates the queue file and marks recipients
as finished, or it informs the queue manager that delivery
should be tried again at a later time.
Delivery problem reports are sent to the bounce(8) or
defer(8) daemon as appropriate.
SECURITY
The error mailer is not security-sensitive. It does not
talk to the network, and can be run chrooted at fixed low
privilege.
STANDARDS
None.
DIAGNOSTICS
Problems and transactions are logged to syslogd(8).
Depending on the setting of the notify_classes parameter,
the postmaster is notified of bounces and of other trou-
ble.
BUGS
CONFIGURATION PARAMETERS
The following main.cf parameters are especially relevant
to this program. See the Postfix main.cf file for syntax
details and for default values. Use the postfix reload
command after a configuration change.
Miscellaneous
bounce_notice_recipient
Postmaster for bounce error notices.
notify_classes
When this parameter includes the bounce class, send
mail to the postmaster with with the headers of the
bounced mail.
1
ERROR(8) ERROR(8)
SEE ALSO
bounce(8) non-delivery status reports
master(8) process manager
qmgr(8) queue manager
syslogd(8) system logging
LICENSE
The Secure Mailer license must be distributed with this
software.
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
2
postfix/doc/delivering.html 100664 1751 146 10535 7017475562 15340 0 ustar thivillo www
Postfix
Anatomy - Delivering Mail
Up one level | Receiving Mail | Delivering Mail | Behind the Scenes | Command-line Utilities
Up one level | Receiving Mail | Delivering Mail | Behind the Scenes | Command-line Utilities
postfix/doc/defer.8.html 100664 1751 146 7372 7017475562 14430 0 ustar thivillo www
BOUNCE(8) BOUNCE(8)
NAME
bounce - Postfix message bounce or defer daemon
SYNOPSIS
bounce [generic Postfix daemon options]
DESCRIPTION
The bounce daemon maintains per-message log files with
non-delivery status information. Each log file is named
after the queue file that it corresponds to, and is kept
in a queue subdirectory named after the service name in
the master.cf file (either bounce or defer). This program
expects to be run from the master(8) process manager.
The bounce daemon processes two types of service requests:
o Append a recipient status record to a per-message
log file.
o Post a bounce message, with a copy of a log file
and of the corresponding message. When the bounce
is posted successfully, the log file is deleted.
The software does a best effort to notify the sender that
there was a problem. A notification is sent even when the
log file or original message cannot be read.
Optionally, a client can request that the per-message log
file be deleted when the requested operation fails. This
is used by clients that cannot retry transactions by them-
selves, and that depend on retry logic in their own
client.
STANDARDS
RFC 822 (ARPA Internet Text Messages)
DIAGNOSTICS
Problems and transactions are logged to syslogd(8).
BUGS
The log files use an ad-hoc, unstructured format. This
will have to change in order to easily support standard
delivery status notifications.
CONFIGURATION PARAMETERS
The following main.cf parameters are especially relevant
to this program. See the Postfix main.cf file for syntax
details and for default values. Use the postfix reload
command after a configuration change.
bounce_notice_recipient
The recipient of single bounce postmaster notices.
1
BOUNCE(8) BOUNCE(8)
2bounce_notice_recipient
The recipient of double bounce postmaster notices.
delay_notice_recipient
The recipient of "delayed mail" postmaster notices.
bounce_size_limit
Limit the amount of original message context that
is sent in a non-delivery notification.
mail_name
Use this mail system name in the introductory text
at the start of a bounce message.
notify_classes
Notify the postmaster of bounced mail when this
parameter includes the bounce class. For privacy
reasons, the message body is not included.
SEE ALSO
master(8) process manager
qmgr(8) queue manager
syslogd(8) system logging
LICENSE
The Secure Mailer license must be distributed with this
software.
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
2
postfix/doc/commands.html 100664 1751 146 6420 7017475562 14767 0 ustar thivillo www
Postfix
Anatomy - Command-line Utilities
Up one level | Receiving Mail | Delivering Mail | Behind the Scenes | Command-line Utilities
Up one level | Receiving Mail | Delivering Mail | Behind the Scenes | Command-line Utilities
postfix/doc/cleanup.8.html 100664 1751 146 13750 7017475562 15007 0 ustar thivillo www
CLEANUP(8) CLEANUP(8)
NAME
cleanup - canonicalize and enqueue Postfix message
SYNOPSIS
cleanup [generic Postfix daemon options]
DESCRIPTION
The cleanup daemon processes inbound mail, inserts it into
the incoming mail queue, and informs the queue manager of
its arrival.
The cleanup daemon always performs the following transfor-
mations:
o Insert missing message headers: (Resent-) From:,
Message-Id:, and Date:.
o Extract envelope recipient addresses from (Resent-)
To:, Cc: and Bcc: message headers when no recipi-
ents are specified in the message envelope.
o Transform envelope and header addresses to the
standard user@fully-qualified-domain form that is
expected by other Postfix programs. This task is
delegated to the trivial-rewrite(8) daemon.
o Eliminate duplicate envelope recipient addresses.
The following address transformations are optional:
o Optionally, rewrite all envelope and header
addresses according to the mappings specified in
the canonical(5) lookup tables.
o Optionally, masquerade envelope sender addresses
and message header addresses (i.e. strip host or
domain information below all domains listed in the
masquerade_domains parameter, except for user names
listed in masquerade_exceptions). Address mas-
querading does not affect envelope recipients.
o Optionally, expand envelope recipients according to
information found in the virtual(5) lookup tables.
The cleanup daemon performs sanity checks on the content
of each message. When it finds a problem, by default it
returns a diagnostic status to the client, and leaves it
up to the client to deal with the problem. Alternatively,
the client can request the cleanup daemon to bounce the
message back to the sender in case of trouble.
STANDARDS
RFC 822 (ARPA Internet Text Messages)
1
CLEANUP(8) CLEANUP(8)
DIAGNOSTICS
Problems and transactions are logged to syslogd(8).
BUGS
Table-driven rewriting rules make it hard to express if
then else and other logical relationships.
CONFIGURATION PARAMETERS
The following main.cf parameters are especially relevant
to this program. See the Postfix main.cf file for syntax
details and for default values. Use the postfix reload
command after a configuration change.
Miscellaneous
always_bcc
Address to send a copy of each message that enters
the system.
hopcount_limit
Limit the number of Received: message headers.
Address transformations
empty_address_recipient
The destination for undeliverable mail from <>.
This substitution is done before all other address
rewriting.
canonical_maps
Address mapping lookup table for sender and recipi-
ent addresses in envelopes and headers.
recipient_canonical_maps
Address mapping lookup table for envelope and
header recipient addresses.
sender_canonical_maps
Address mapping lookup table for envelope and
header sender addresses.
masquerade_domains
List of domains that hide their subdomain struc-
ture.
masquerade_exceptions
List of user names that are not subject to address
masquerading.
virtual_maps
Address mapping lookup table for envelope recipient
addresses.
Resource controls
duplicate_filter_limit
Limit the number of envelope recipients that are
2
CLEANUP(8) CLEANUP(8)
remembered.
header_size_limit
Limit the amount of memory in bytes used to process
a message header.
SEE ALSO
canonical(5) canonical address lookup table format
qmgr(8) queue manager daemon
syslogd(8) system logging
trivial-rewrite(8) address rewriting
virtual(5) virtual address lookup table format
FILES
/etc/postfix/canonical*, canonical mapping table
/etc/postfix/virtual*, virtual mapping table
LICENSE
The Secure Mailer license must be distributed with this
software.
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
3
postfix/doc/canonical.5.html 100664 1751 146 14164 7017475562 15304 0 ustar thivillo www
CANONICAL(5) CANONICAL(5)
NAME
canonical - format of Postfix canonical table
SYNOPSIS
postmap /etc/postfix/canonical
DESCRIPTION
The optional canonical file specifies an address mapping
for local and non-local addresses. The mapping is used by
the cleanup(8) daemon. The address mapping is recursive.
The file serves as input to the postmap(1) command. The
result, an indexed file in dbm or db format, is used for
fast searching by the mail system. After an update it may
take a minute or so before the change becomes visible.
Issue a postfix reload command to eliminate the delay.
The canonical mapping affects both message header
addresses (i.e. addresses that appear inside messages) and
message envelope addresses (for example, the addresses
that are used in SMTP protocol commands). Think Sendmail
rule set S3, if you like.
Typically, one would use the canonical table to replace
login names by Firstname.Lastname, or to clean up
addresses produced by legacy mail systems.
The canonical mapping is not to be confused with virtual
domain support. Use the virtual(5) map for that purpose.
The canonical mapping is not to be confused with local
aliasing. Use the aliases(5) map for that purpose.
The format of the canonical table is as follows, mappings
being tried in the order as listed in this manual page:
blanks and comments
Blank lines are ignored, as are lines beginning
with `#'.
user@domain address
user@domain is replaced by address. This form has
the highest precedence.
This form useful to clean up addresses produced by
legacy mail systems. It can also be used to pro-
duce Firstname.Lastname style addresses, but see
below for a simpler solution.
user address
user@site is replaced by address when site is equal
to $myorigin, when site is listed in $mydestina-
tion, or when it is listed in $inet_interfaces.
1
CANONICAL(5) CANONICAL(5)
This form is useful for replacing login names by
Firstname.Lastname.
@domain address
Every address in domain is replaced by address.
This form has the lowest precedence.
In all the above forms, when address has the form @other-
domain, the result is the same user in otherdomain.
ADDRESS EXTENSION
When table lookup fails, and the address localpart con-
tains the optional recipient delimiter (e.g.,
user+foo@domain), the search is repeated for the unex-
tended address (e.g. user@domain), and the unmatched
extension is propagated to the result of table lookup. The
matching order is: user+foo@domain, user@domain, user+foo,
user, and @domain.
BUGS
The table format does not understand quoting conventions.
CONFIGURATION PARAMETERS
The following main.cf parameters are especially relevant
to this topic. See the Postfix main.cf file for syntax
details and for default values. Use the postfix reload
command after a configuration change.
canonical_maps
List of canonical mapping tables.
recipient_canonical_maps
Address mapping lookup table for envelope and
header recipient addresses.
sender_canonical_maps
Address mapping lookup table for envelope and
header sender addresses.
Other parameters of interest:
inet_interfaces
The network interface addresses that this system
receives mail on.
masquerade_domains
List of domains that hide their subdomain struc-
ture.
masquerade_exceptions
List of user names that are not subject to address
masquerading.
2
CANONICAL(5) CANONICAL(5)
mydestination
List of domains that this mail system considers
local.
myorigin
The domain that is appended to locally-posted mail.
owner_request_special
Give special treatment to owner-xxx and xxx-request
addresses.
SEE ALSO
cleanup(8) canonicalize and enqueue mail
postmap(1) create mapping table
virtual(5) virtual domain mapping
LICENSE
The Secure Mailer license must be distributed with this
software.
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
3
postfix/doc/bounce.8.html 100664 1751 146 7372 7017475562 14616 0 ustar thivillo www
BOUNCE(8) BOUNCE(8)
NAME
bounce - Postfix message bounce or defer daemon
SYNOPSIS
bounce [generic Postfix daemon options]
DESCRIPTION
The bounce daemon maintains per-message log files with
non-delivery status information. Each log file is named
after the queue file that it corresponds to, and is kept
in a queue subdirectory named after the service name in
the master.cf file (either bounce or defer). This program
expects to be run from the master(8) process manager.
The bounce daemon processes two types of service requests:
o Append a recipient status record to a per-message
log file.
o Post a bounce message, with a copy of a log file
and of the corresponding message. When the bounce
is posted successfully, the log file is deleted.
The software does a best effort to notify the sender that
there was a problem. A notification is sent even when the
log file or original message cannot be read.
Optionally, a client can request that the per-message log
file be deleted when the requested operation fails. This
is used by clients that cannot retry transactions by them-
selves, and that depend on retry logic in their own
client.
STANDARDS
RFC 822 (ARPA Internet Text Messages)
DIAGNOSTICS
Problems and transactions are logged to syslogd(8).
BUGS
The log files use an ad-hoc, unstructured format. This
will have to change in order to easily support standard
delivery status notifications.
CONFIGURATION PARAMETERS
The following main.cf parameters are especially relevant
to this program. See the Postfix main.cf file for syntax
details and for default values. Use the postfix reload
command after a configuration change.
bounce_notice_recipient
The recipient of single bounce postmaster notices.
1
BOUNCE(8) BOUNCE(8)
2bounce_notice_recipient
The recipient of double bounce postmaster notices.
delay_notice_recipient
The recipient of "delayed mail" postmaster notices.
bounce_size_limit
Limit the amount of original message context that
is sent in a non-delivery notification.
mail_name
Use this mail system name in the introductory text
at the start of a bounce message.
notify_classes
Notify the postmaster of bounced mail when this
parameter includes the bounce class. For privacy
reasons, the message body is not included.
SEE ALSO
master(8) process manager
qmgr(8) queue manager
syslogd(8) system logging
LICENSE
The Secure Mailer license must be distributed with this
software.
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
2
postfix/doc/big-picture.html 100664 1751 146 3303 7017475562 15375 0 ustar thivillo www
Postfix
- the Big Picture
In order to keep the big picture readable the following elements were omitted:
postfix/doc/big-picture.gif 100664 1751 146 14275 7017475563 15231 0 ustar thivillo www GIF89a*
! , *
ڋH扦ʶ L
ĢL*̦ JԪjܮ N
(8HXhx)9IYiy Zj*Jz:
;{"K{e˻ +\@l܃ -= \m } .>>Zn
/G_|o?ъ-@#_
1ĉ+Z!9 ;z Ǒ$36\%[rL˙C S"L.v3O2δI(Ρ?S0mҒOH:iX=VJ+W\ hi "m+=@D xW.HaV-<
8;Xe% ns]˗-fN mgXoKtkoΦu` ]t7˧ - Wյ 笳y
<$R@:*1C g; 3=L9!!# J|fU DKDƇA` BXpĠz QB|M?NpU WHC*̡fq
Q-F!
yD%D 4C,vqءx5x8SHr'Lqf x:jx@%r
| d =SHC)QE
DId${HI/e%9)B , d>IR SX zn+$WK"OxKt#̤3`J'Tã\)/LU2S| ӗҤn g'5HwiQfq)~VS
#5"{1T@9l0 CShE/;$<FE>nr*& jQΐ3-H?:C!h0Ӓ5=D}T&C/RԨ25 });ȥjU>iVurT/j
kOmՒ1(V%^g%k\ԜDZjؾ
!m
LĮSoPjVϺ
{,dصb},Q#+ٮt -iQ{Wթ(ug ]UKUm iKѷ֔
*Sv'}*8)Б&4r1XCHw])X
M6.{9[R:{]ٔUk9'ɮo%}K?8
/Z%EC
9a #%)~؍zTIZc7ƨ;; aCf_ bxrocpұ=Xªd(^56 s{yx \ '7 <3f yqgjatn|;5M)< z9~{WF3IJ5q<ff5W.RllPh~2}YZ
PG_[R6!@f2\F2ΦM mJWis߂gn Iule tДC]8pJέN[m6q l >Y{ڵr=aKnT
Wd
8,o pBڞUM9Gʝ1鑘ٶ6 =KfT5mznj욖4][oVxaH6-+_Wp%u5
8
(Ovna{Z]- ~}|b!Ͳ
}xlÙz7 <`+KL\] K7^ V< 9[O=g=sqJ#MO|ս ` Postfix Configuration - Basics
Up one level | Basic Configuration | UCE Controls | Rate
Controls | Resource Controls | Address Manipulation
Introduction
Postfix has about 100 configuration parameters that are controlled
via the main.cf file. Fortunately, they have sensible
default values. In most cases, you need to configure only two or
three parameters before you can use the Postfix mail system:
The default values for many other configuration parameters are
derived from just these two.
What domain to use in outbound mail
The myorigin parameter specifies the domain that appears in
mail that is posted on this machine. The default is to use the
local machine name, $myhostname,
which defaults to the name of the machine. Unless you are running
a really small site, you probably want to change that into $mydomain, which defaults to the parent
domain of the machine name.
What domains to receive mail for
The mydestination parameter specifies what domains this
machine will deliver locally, instead of forwarding to another
machine. The default is to receive mail for the machine itself.
Examples:
What trouble to report to the postmaster
You should set up a postmaster alias that points to a human person.
This alias is required to exist, so that people can report mail
delivery problems.
My own hostname
The myhostname parameter describes the fully-qualified domain
name of the machine running the Postfix system. $myhostname
appears as the default value in many other Postfix configuration
parameters.
My own domain name
The mydomain parameter specifies the parent domain of
$myhostname. By default it is derived from $myhostname
by stripping off the first part (unless the result would be a
top-level domain).
My own networks
The mynetworks parameter lists all networks that this machine
is attached to. This information can be used by the
anti-UCE features to distinguish between local systems and
strangers.
My own network addresses
The inet_interfaces parameter specifies all network interface
addresses that the Postfix system should listen on; mail addressed
to user@[network address] will be delivered locally,
as if it is addressed to a domain listed in $mydestination.
Up one level | Basic Configuration | UCE Controls | Rate
Controls | Resource Controls | Address Manipulation
postfix/doc/backstage.html 100664 1751 146 4210 7017475563 15106 0 ustar thivillo www
Postfix
Anatomy - Behind the Scenes
Up one level | Receiving Mail | Delivering Mail | Behind the Scenes |
Command-line Utilities
Up one level | Receiving Mail | Delivering Mail | Behind the Scenes |
Command-line Utilities
postfix/doc/architecture.html 100664 1751 146 10671 7017475563 15674 0 ustar thivillo www
Postfix
Overview - Global Architecture
Up one level | Introduction | Goals
and features | Global architecture | Queue
Management | Security
Introduction
Some mail systems such as Sendmail are implemented as one large
monolithic program that does everything. One large program certainly
makes it easy to share data between different parts of the system.
Unfortunately, one large program also makes it easy to make
fatal mistakes. Other mailers such as qmail use a rigid hierarchy
of programs that run other programs in a fixed order and throw them
away after use. This approach gives better insulation, at the cost
of some process creation overhead and inter-process communication.
The additional cost can be kept within acceptable limits by
partitioning the work in a sensible manner.
Postfix architecture
Postfix is based on semi-resident, mutually-cooperating, processes
that perform specific tasks for each other, without any particular
parent-child relationship. Again, doing work in separate processes
gives better insulation than using one big program. In addition,
the Postfix approach has the advantage that a service such as
address rewriting is available to every Postfix component program,
without incurring the cost of process creation just to rewrite one
address. By the way: I do not claim that Postfix is the only (mail)
program using this approach. Even in this relatively young discipline
it is hard to come up something new that no-one ever did before.
Communication between Postfix processes
The core of the Postfix system is implemented by a dozen semi-resident
programs. For privacy reasons, these Postfix processes communicate
via UNIX-domain sockets or FIFOs that live in a protected directory.
Despite this privacy, Postfix processes do not really trust the
data that they receive in this manner; just like the contents of
Postfix queue files, they merely treat it as gossip.
Up one level | Introduction | Goals
and features | Global architecture | Queue
Management | Security
postfix/doc/aliases.5.html 100664 1751 146 14440 7017475563 14774 0 ustar thivillo www
ALIASES(5) ALIASES(5)
NAME
aliases - format of the Postfix alias database
SYNOPSIS
postalias [-c config_dir] [-v] [file_type:]input_file
DESCRIPTION
The aliases file provides a system-wide mechanism to redi-
rect mail for local recipients.
The file serves as input to the postalias(1) command. The
result, an indexed file in dbm or db format, is used for
fast lookup by the mail system. After an update it may
take a minute or so before the change becomes visible.
Issue a postfix reload command to eliminate the delay.
The input and output file formats are expected to be com-
patible with Sendmail version 8, and are expected to be
suitable for the use as NIS maps.
Users can control delivery of their own mail by setting up
.forward files in their home directory. Lines in per-user
.forward files have the same syntax as the right-hand side
of aliases entries.
The format of the alias database input file is as follows:
o An alias definition has the form
name: value1, value2, ...
o Lines that begin with whitespace continue the pre-
vious line.
o Blank lines are ignored, as are lines beginning
with `#'.
The name is a local address (no domain part). Use double
quotes when the name contains any special characters such
as whitespace, `#', `:', or `@'. The name is folded to
lowercase, in order to make database lookups case insensi-
tive.
In addition, when an alias exists for owner-name, delivery
diagnostics are directed to that address, instead of to
the originator. This is typically used to direct delivery
errors to the owner of a mailing list, who is in a better
position to deal with mailing list delivery problems than
the originator of the undelivered mail.
The value contains one or more of the following:
address
Mail is forwarded to address, which is compatible
1
ALIASES(5) ALIASES(5)
with the RFC 822 standard.
/file/name
Mail is appended to /file/name. See local(8) for
details of delivery to file. Delivery is not lim-
ited to regular files. For example, to dispose of
unwanted mail, deflect it to /dev/null.
|command
Mail is piped into command. Commands that contain
special characters, such as whitespace, should be
enclosed between double quotes. See local(8) for
details of delivery to command.
When the command fails, a limited amount of command
output is mailed back to the sender. The file
/usr/include/sysexits.h defines the expected exit
status codes. For example, use |"exit 67" to simu-
late a "user unknown" error, and |"exit 0" to
implement an expensive black hole.
:include:/file/name
Mail is sent to the destinations listed in the
named file. Lines in :include: files have the same
syntax as the right-hand side of alias entries.
A destination can be any destination that is
described in this manual page. However, delivery to
"|command" and /file/name is disallowed by default.
To enable, edit the allow_mail_to_commands and
allow_mail_to_files configuration parameters.
ADDRESS EXTENSION
When alias database search fails, and the recipient local-
part contains the optional recipient delimiter (e.g.,
user+foo), the search is repeated for the unextended
address (e.g., user).
CONFIGURATION PARAMETERS
The following main.cf parameters are especially relevant
to this topic. See the Postfix main.cf file for syntax
details and for default values. Use the postfix reload
command after a configuration change.
alias_maps
List of alias databases.
allow_mail_to_commands
Restrict the usage of mail delivery to external
command.
allow_mail_to_files
Restrict the usage of mail delivery to external
file.
2
ALIASES(5) ALIASES(5)
owner_request_special
Give special treatment to owner-xxx and xxx-request
addresses.
recipient_delimiter
Delimiter that separates recipients from address
extensions.
STANDARDS
RFC 822 (ARPA Internet Text Messages)
SEE ALSO
local(8) local delivery agent
postalias(1) alias database management
LICENSE
The Secure Mailer license must be distributed with this
software.
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
3
postfix/doc/access.5.html 100664 1751 146 6043 7017475563 14574 0 ustar thivillo www
ACCESS(5) ACCESS(5)
NAME
access - format of Postfix access table
SYNOPSIS
postmap /etc/postfix/access
DESCRIPTION
The optional access table directs the Postfix SMTP server
to selectively reject or accept mail from or to specific
hosts, domains, networks, host addresses or mail
addresses.
The table serves as input to the postmap(1) command. The
result, an indexed file in dbm or db format, is used for
fast searching by the mail system. After an update it may
take a minute or so before the change becomes visible.
Issue a postfix reload command to eliminate the delay.
The format of the access table is as follows:
blanks and comments
Blank lines are ignored, as are lines beginning
with `#'.
pattern action
When pattern matches a mail address, domain or host
address, perform the corresponding action.
PATTERNS
Patterns are tried in the order as listed below:
user@domain
Matches the specified mail address.
domain.name
Matches the domain.name itself and any subdomain
thereof, either in hostnames or in mail addresses.
Top-level domains will never be matched.
user@ Matches all mail addresses with the specified user
part.
net.work.addr.ess
net.work.addr
net.work
net Matches any host address in the specified network.
A network address is a sequence of one or more
octets separated by ".".
ACTIONS
1
ACCESS(5) ACCESS(5)
[45]XX text
Reject the address etc. that matches the pattern,
and respond with the numerical code and text.
REJECT Reject the address etc. that matches the pattern. A
generic error response message is generated.
OK
Any other text
Accept the address etc. that matches the pattern.
BUGS
The table format does not understand quoting conventions.
SEE ALSO
postmap(1) create mapping table
smtpd(8) smtp server
LICENSE
The Secure Mailer license must be distributed with
this software.
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
2
postfix/doc/virtual.5.html 100664 1751 146 13061 7017475564 15040 0 ustar thivillo www
VIRTUAL(5) VIRTUAL(5)
NAME
virtual - format of Postfix virtual table
SYNOPSIS
postmap /etc/postfix/virtual
DESCRIPTION
The optional virtual table specifies redirections for
local and non-local recipients or domains. The redirec-
tions are used by the cleanup(8) daemon. The redirections
are recursive.
The virtual redirection is applied only to the recipient
envelope address, and does not affect message headers.
Think Sendmail rule set S0, if you like. Use canonical(5)
mapping to rewrite header and envelope addresses in gen-
eral.
The file serves as input to the postmap(1) command. The
result, an indexed file in dbm or db format, is used for
fast searching by the mail system. After an update it may
take a minute or so before the change becomes visible.
Issue a postfix reload command to eliminate the delay.
Typical support for a virtual domain looks like the fol-
lowing:
virtual.domain anything (right-hand content does not matter)
user1@virtual.domain address1
user2@virtual.domain address2, address3
With this, the SMTP server accepts mail for virtual.domain
(provided that the relay_domains parameter includes $vir-
tual_maps), and mail for unknown@virtual.domain is bounced
as undeliverable.
The format of the virtual table is as follows, mappings
being tried in the order as listed in this manual page:
blanks and comments
Blank lines are ignored, as are lines beginning
with `#'.
user@domain address, address, ...
Mail for user@domain is redirected to address.
This form has the highest precedence.
user address, address, ...
Mail for user@site is redirected to address when
site is equal to $myorigin, when site is listed in
$mydestination, or when it is listed in
$inet_interfaces.
This functionality overlaps with functionality of
1
VIRTUAL(5) VIRTUAL(5)
the local alias(5) database. The difference is that
virtual mapping can be applied to non-local
addresses.
@domain address, address, ...
Mail for any user in domain is redirected to
address. This form has the lowest precedence.
In all the above forms, when address has the form @other-
domain, the result is the same user in otherdomain. This
works for the first address in the expansion only.
ADDRESS EXTENSION
When the search fails, and the address localpart contains
the optional recipient delimiter (e.g., user+foo@domain),
the search is repeated for the unextended address (e.g.
user@domain), and the unmatched address extension is prop-
agated to the result of expansion. The matching order is:
user+foo@domain, user@domain, user+foo, user, and @domain.
BUGS
The table format does not understand quoting conventions.
CONFIGURATION PARAMETERS
The following main.cf parameters are especially relevant
to this topic. See the Postfix main.cf file for syntax
details and for default values. Use the postfix reload
command after a configuration change.
virtual_maps
List of virtual mapping tables.
Other parameters of interest:
inet_interfaces
The network interface addresses that this system
receives mail on.
mydestination
List of domains that this mail system considers
local.
myorigin
The domain that is appended to locally-posted mail.
owner_request_special
Give special treatment to owner-xxx and xxx-request
addresses.
SEE ALSO
cleanup(8) canonicalize and enqueue mail
postmap(1) create mapping table
2
VIRTUAL(5) VIRTUAL(5)
LICENSE
The Secure Mailer license must be distributed with this
software.
AUTHOR(S)
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
3
postfix/doc/main.cf.fr 100664 1751 146 17146 7017475564 14175 0 ustar thivillo www # Qui prend les bounces de bounces
2bounce_notice_recipient = postmaster
# Erreur renvoye si REJECT dans les ACLs (450=temporaire, 550=permanent)
access_map_reject_code = 550
# La base reconstruite par newaliases
alias_database = hash:/etc/postfix/aliases
# L'ensemble des aliases
alias_maps = hash:/etc/postfix/aliases
# Limitation des "|" dans les .forward
allow_mail_to_commands = alias,forward
# Idem pour les fichiers
allow_mail_to_files = alias,forward
# Reecriture user%domaine@domaine2
allow_percent_hack = yes
# Recopie de tous les messages
always_bcc =
# Ajoute @myorigin aux adresses non qualifiees
append_at_myorigin = yes
# Ajoute .domaine aux adresses user@host
append_dot_mydomain = yes
# YES si on veut eviter le "mail loopback to myself" si MX = lamachine et
# pas liste dans mydestination ou virtual
best_mx_transport =
# Biff sur local
biff = no
# Qui recoit les bounces si notify=bounce
bounce_notice_recipient = postmaster
# Taille limite des bounces
bounce_size_limit = 50000
# Reecriture en entree et en sortie
canonical_maps =
# Ou sont les post*
command_directory = /usr/local/postfix/sbin
# ?
command_time_limit = 1000
# Ou sont les dameons (qmgr, ...)
daemon_directory = /usr/local/postfix/libexec
daemon_timeout = 18000
# Debug vers certaines destinations
debug_peer_level = 2
# Liste des destinations
debug_peer_list =
# hash ou dbm
default_database_type = hash
# Combien de demons vers une seule destination.
# On peut avoir aussi smtp_destination....
default_destination_concurrency_limit = 10
# Combien de recipients max (idem)
default_destination_recipient_limit = 50
# Privilges tombent
default_privs = nobody
# Combien de process max par dmon (local,qmgr,bounce, ...)
default_process_limit = 50
default_transport = smtp
# Pour retarder l'envoi par smtp par exemple
defer_transports =
# Qui recoit les warning en plus de l'utilisateur
delay_notice_recipient = postmaster
# En heures, temps de warning (0=dsactiv)
delay_warning_time = 0
# Gestion des verrous
deliver_lock_attempts = 5
deliver_lock_delay = 1
# Pas document, pas sur que a marche. Dsactive DNS
disable_dns_lookups = no
dont_remove = 0
# Qui envoie les doubles bounces ...
double_bounce_sender = double-bounce
duplicate_filter_limit = 1000
# Ca parle de soi ...
empty_address_recipient = MAILER-DAEMON
error_notice_recipient = postmaster
# Si on arrive pas a y aller en direct, on passe sur ...
fallback_relay =
fallback_transport =
# Quand les dmons forkent ....
fork_attempts = 5
fork_delay = 1
# Recherche des .forward
forward_path = $home/.forward${recipient_delimiter}${extension},$home/.forward
# Hashing de /var/spool/postfix/defer
hash_queue_depth = 2
hash_queue_names = defer
# Table ou regexp pour la rejection sur les headers.
header_checks =
# Taille max des headers
header_size_limit = 102400
# Pour dlivrer dans $HOME
home_mailbox =
# Nb de receive
hopcount_limit = 50
# Pour dlivrer sur les A plutot que les MX (viole un RFC)
ignore_mx_lookup_error = no
# Interfaces qui coutent
inet_interfaces = all
# Nb de session initiales
initial_destination_concurrency = 2
#
invalid_hostname_reject_code = 501
# ?
ipc_idle = 100
ipc_timeout = 3600
# Longueur max des lignes.
line_length_limit = 2048
# Pour le mailer local
local_command_shell =
local_destination_concurrency_limit = 2
local_destination_recipient_limit = $default_destination_recipient_limit
# voir luser dans sendmail (qui recoit tous les unknown, ex smtp:[ailleurs])
luser_relay =
# Nom affiche
mail_name = Postfix
# Identit postfiw
mail_owner = postfix
# mailbox locales
mail_spool_directory = /var/mail
# La version
mail_version = Snapshot-19990410
# pour procmail
mailbox_command = /usr/local/bin/procmail
# ?
mailbox_transport =
# RBL et ORBL
maps_rbl_domains = rbl.maps.vix.com
maps_rbl_reject_code = 550
# *.$mydomain ===> $mydomain
masquerade_domains = $mydomain
masquerade_exceptions = root
# Apres combien de temps on ferme les dmons
max_idle = 100
max_use = 100
# Temps max entre les runs pour une dest.
maximal_backoff_time = 4000
# En jour, combien de temps on garde les mails en attente
maximal_queue_lifetime = 13
# Taille max des messages
message_size_limit = 8000000
# temps mini entre deux runs pour une meme destinations
minimal_backoff_time = 1000
# Les noms locaux
mydestination = $myhostname, localhost.$mydomain, $mydomain, www.$mydomain, news.$mydomain
# Le domaine
mydomain = hsc.fr
# Le nom de la machine
myhostname = itesec.hsc.fr
# Les rseaux Internes
mynetworks = 192.70.106.32/27, 192.70.106.64/27, 192.70.106.96/27, 192.70.106.128/27, 127.0.0.0/8
# Quell orginie pour les mails posts localement
myorigin = $mydomain
# Code de rejet sur le MAIL FROM: non qualifi
non_fqdn_reject_code = 504
# Qu'envoie t'on au postmaster (policy en + de ci dessous)
notify_classes = resource, software,protocol
# Traitement des owner- et -owner ala sendmail
owner_request_special = yes
# Ou on stocke les PIDS
process_id_directory = pid
# Les programmes (pas utilis si command_directory et daemon_directory)
program_directory = /usr/local/postfix/bin
#
qmgr_message_active_limit = 1000
qmgr_message_recipient_limit = 10000
queue_directory = /var/spool/postfix
queue_minfree = 0
# Intervalle
queue_run_delay = 1000
# Pour rcrire seulement les recipients
recipient_canonical_maps =
# at+toto=at (ala sendmail)
recipient_delimiter = +
# ?
recipient_feature_delimiter =
# Code de rejet global
reject_code = 550
# Qui relaye-t'on ? (virtual_maps est donn par virtual=)
relay_domains = $mydestination, $virtual_maps, /etc/postfix/RelayTo
relay_domains_reject_code = 550
# A qui on envoie le mail. par exmple : smtp:[mailhost:port]
relayhost =
# Pour les relogs ;)
relocated_maps =
# Reecriture des emmetteurs
sender_canonical_maps = hash:/etc/postfix/sender_canonical
# ?
service_throttle_time = 60
# Pour changer le dfaut timeout sur connect() (indispensable sur Linux 2.2)
smtp_connect_timeout = 0
# Autres timeouts
smtp_data_done_timeout = 600
smtp_data_init_timeout = 120
smtp_data_xfer_timeout = 180
# Nb de sessions smtp vers la meme dest.
smtp_destination_concurrency_limit = $default_destination_concurrency_limit
smtp_destination_recipient_limit = $default_destination_recipient_limit
# autres timeout
smtp_helo_timeout = 300
smtp_mail_timeout = 300
smtp_quit_timeout = 300
smtp_rcpt_timeout = 300
# Broken software ...
smtp_skip_4xx_greeting = no
smtp_skip_quit_response = yes
# Banniere SMTP
smtpd_banner = $myhostname ESMTP $mail_name
# Qui on jette sur la connexion
smtpd_client_restrictions = hash:/etc/postfix/access
# Sleep apres une erreur
smtpd_error_sleep_time = 5
# Qui peut lancer ETRN ?
smtpd_etrn_restrictions = permit_mynetworks, reject
# Apres hard_error, on ferme
smtpd_hard_error_limit = 10
# Demande un helo
smtpd_helo_required = yes
# Voir doc sur ce qui peut etre envoye dans le helo
smtpd_helo_restrictions =
# Nb de recipients accepts par session SMTP
smtpd_recipient_limit = 1000
# test sur le RCPT TO: (anti relayage)
smtpd_recipient_restrictions = permit_mynetworks,check_relay_domains
# test sur le MAIL FROM:
smtpd_sender_restrictions = reject_unknown_address, reject_non_fqdn_sender, hash:/etc/postfix/access
#
smtpd_soft_error_limit = 10
# ?
smtpd_timeout = 300
# pas de bounces gnrs localement : les messages restent dans la file
soft_bounce = no
stale_lock_time = 500
# Broken software
sun_mailtool_compatibility = no
# pour debangifier les @ UUCP.
swap_bangpath = yes
# Transport = mailertable
transport_maps = hash:/etc/postfix/transport
# ?
transport_retry_time = 60
# ?
trigger_timeout = 10
# Pour les rejets sur le DNS (450=temp,550=permanent)
unknown_address_reject_code = 450
unknown_client_reject_code = 450
unknown_hostname_reject_code = 450
# Domaines virtuels
virtual_maps = hash:/etc/postfix/virtual
#
postfix/doc/LDAP_README 100664 1751 146 20007 7017475564 13777 0 ustar thivillo www BUILDING WITH LDAP SUPPORT
==========================
You need to have LDAP libraries and include files installed somewhere on
your system, and you need to configure the Postfix Makefiles
accordingly.
If you're using the libraries from the UM distribution
(http://www.umich.edu/~dirsvcs/ldap/ldap.html) or OpenLDAP
(http://www.openldap.org), something like this should work:
% make tidy
% make makefiles CCARGS="-I/some/where/include -DHAS_LDAP" \
AUXLIBS="/some/where/libldap.a /some/where/liblber.a"
The `make tidy' command is needed only if you have previously built
Postfix without LDAP support.
If your LDAP libraries were built with Kerberos support, you'll also
need to include your Kerberos libraries in this line. Note that the KTH
Kerberos IV libraries might conflict with Postfix's lib/libdns.a, which
defines dns_lookup. If that happens, you'll probably want to link with
LDAP libraries that lack Kerberos support just to build Postfix, as it
doesn't yet support Kerberos binds to the LDAP server anyway. Sorry
about the bother.
If you're using one of the Netscape LDAP SDKs, you'll need to change the
AUXLIBS line to point to libldap10.so or libldapssl30.so or whatever you
have, and you may need to use the -R option so the executables can find
it at runtime.
USING LDAP LOOKUPS
==================
In order to use LDAP lookups, define at least one LDAP source as a table
lookup in main.cf, for example:
alias_maps = hash:/etc/aliases, ldap:ldapsource
Each LDAP source can have the following parameters, which should be
prefixed in main.cf with the name you've given the source in its
definition. To continue the example, the first parameter below,
"server_host", would be defined in main.cf as "ldapsource_server_host".
Defaults are given in parentheses:
server_host (localhost)
The name of the host running the LDAP server, e.g.
ldapsource_server_host = ldap.your.com
It should be possible with all the libraries mentioned above to
specify multiple servers separated by spaces, with the libraries
trying them in order should the first one fail.
server_port (389)
The port the LDAP server listens on, e.g.
ldapsource_server_port = 778
search_base (no default)
The base at which to conduct the search, e.g.
ldapsource_search_base = dc=your, dc=com
timeout (10 seconds)
The number of seconds a search can take before timing out, e.g.
ldapsource_timeout = 5
query_filter (mailacceptinggeneralid=%s)
The RFC2254 filter used to search the directory, where %s is a
substitute for the address Postfix is trying to resolve, e.g.
ldapsource_query_filter = (&(mail=%s)(paid_up=true))
lookup_wildcards (no)
Whether to search for addresses containing '*'. This has huge
potential for spammers, so by default, any address containing
'*' will cause the lookup to return nothing. Unless another
dictionary returns a valid lookup for it, the mail will bounce
with an 'unknown user' message.
result_attribute (maildrop)
The attribute Postfix will read from any directory entries
returned by the lookup, to be resolved to an email address.
ldapsource_result_attribute = mailbox
bind (yes)
Whether or not to bind to the LDAP server. Newer LDAP
implementations don't require clients to bind, which saves
time. Example:
ldapsource_bind = no
bind_dn ("")
If you do have to bind, do it with this distinguished name.
Example:
ldapsource_bind_dn = uid=postfix, dc=your, dc=com
bind_pw ("")
The password for the distinguished name above. If you have to
have this, you probably want to make main.cf readable only by
the Postfix user. Example:
ldapsource_bind_pw = postfixpw
Don't use quotes in these variables; at least, not until the Postfix
configuration routines understand how to deal with quoted strings.
EXAMPLE
=======
Here's a basic example. In main.cf, you have these configuration
parameters defined:
alias_maps = hash:/etc/aliases, ldap:ldapsource
ldapsource_server_host = ldap.my.com
ldapsource_search_base = dc=my, dc=com
Upon receiving mail for a local address "ldapuser" that isn't found in
the /etc/aliases database, Postfix will search the LDAP server listening
at port 389 on ldap.my.com. It will bind anonymously, search for any
directory entries whose mailacceptinggeneralid attribute is "ldapuser",
read the "maildrop" attributes of those found, and build a list of their
maildrops, which will be treated as RFC822 addresses to which the
message will be delivered.
NOTES AND THINGS TO THINK ABOUT
===============================
- You probably want to make sure that mailacceptinggeneralids are
unique, and that not just anyone can specify theirs as postmaster or
root, say.
- An entry can have an arbitrary number of maildrops. Maildrops can also
be comma-separated lists of addresses. For example, you could define
an entry intended for use as a mailing list that looks like this
(Warning! Schema made up just for this example):
dn: cn=Accounting Staff List, dc=my, dc=com
cn: Accounting Staff List
o: my.com
objectclass: maillist
mailacceptinggeneralid: accountingstaff
mailacceptinggeneralid: accounting-staff
maildrop: mylist-owner
maildrop: an-accountant
maildrop: some-other-accountant
maildrop: this, that, theother
- If you use an LDAP map for lookups other than aliases, you may have to
make sure the lookup makes sense. In the case of virtual lookups,
maildrops like "|/some/program" are pretty useless. Your query_filter
should probably look something like this:
virtual_query_filter =
(&(mailacceptinggeneralid=%s)(!(|(maildrop="*|*")(maildrop="*:*"))))
- And for that matter, you may not want users able to specify their
maildrops as programs, particularly if they'd be executed on the
server. A safer local query_filter could look something like:
local_query_filter = (&(mailacceptinggeneralid=%s)(|(!(maildrop="*|*"))(owner=cn=root, dc=your, dc=com)))
So that if the object had a program as its maildrop and weren't owned
by "cn=root" it wouldn't be returned as a valid local user. This will
probably require some thought on your part to implement safely,
considering the ramifications of includes and programs. You may decide
it's not worth the bother to allow any of that nonsense in LDAP
lookups, ban it in the query_filter, and keep things like majordomo
lists in local alias databases.
- It's not yet known how all this scales, but LDAP lookups are much more
expensive than checking a DB file. If you anticipate a lot of lookups,
it may pay to plan your directory to reduce the number of lookups. For
instance, rather than having a bunch of objects that serve as aliases
to just one object, you could simply add their mailacceptinggeneralids
to the target object. This:
dn: uid=firstlast, dc=your, dc=com
maildrop: firstlast@mailbox.your.com
mailacceptinggeneralid: firstlast
mailacceptinggeneralid: First.Last
mailacceptinggeneralid: F.Last
Not this:
dn: uid=firstlast, dc=your, dc=com
maildrop: firstlast@mailbox.your.com
mailacceptinggeneralid: firstlast
dn: cn=First.Last, dc=your, dc=com
maildrop: firstlast
mailacceptinggeneralid: First.Last
dn: cn=F.Last, dc=your, dc=com
maildrop: firstlast
mailacceptinggeneralid: F.Last
Any performance reports will be much appreciated on the postfix-users
list.
UPDATE: At Merit, I've seen over 150000 deliveries per day with no
noticeable delay from our OpenLDAP server. I'd now recommend not
resorting to the above unless you anticipate much more traffic than
that. It makes management of your directory less intuitive, which is
probably not worth the reduction in lookups.
CREDITS
=======
Support for LDAP was initially written by Prabhat K Singh of VSNL,
Bombay, India, and then hideously bloated by John Hensley to support
multiple sources and more configurable attributes. The caching bits were
initially worked out by Prabhat, then munged to support the multiple
sources. Other contributions have been submitted to move toward better
support of Netscape/LDAPv3 libraries, and any other improvements are of
course welcome.
postfix/main.cf 100664 1751 146 10647 7017475566 13023 0 ustar thivillo www 2bounce_notice_recipient = postmaster
access_map_reject_code = 550
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/postfix/aliases
allow_mail_to_commands = alias,forward
allow_mail_to_files = alias,forward
allow_percent_hack = yes
always_bcc =
append_at_myorigin = yes
append_dot_mydomain = yes
best_mx_transport =
biff = no
bounce_notice_recipient = postmaster
bounce_size_limit = 50000
canonical_maps =
command_directory = /usr/local/postfix/sbin
command_expansion_filter = 1234567890!@%-_=+:,./abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ
command_time_limit = 1000
daemon_directory = /usr/local/postfix/libexec
daemon_timeout = 18000
debug_peer_level = 2
debug_peer_list =
default_database_type = hash
default_destination_concurrency_limit = 10
default_destination_recipient_limit = 50
default_privs = nobody
default_process_limit = 50
default_transport = smtp
defer_transports = smtp
delay_notice_recipient = postmaster
delay_warning_time = 8
deliver_lock_attempts = 5
deliver_lock_delay = 1
disable_dns_lookups = yes
dont_remove = 0
double_bounce_sender = double-bounce
duplicate_filter_limit = 1000
empty_address_recipient = MAILER-DAEMON
error_notice_recipient = postmaster
fallback_relay =
fallback_transport = cyrus
fork_attempts = 5
fork_delay = 1
forward_path = $home/.forward${recipient_delimiter}${extension},$home/.forward
hash_queue_depth = 2
hash_queue_names = defer
header_checks = regexp:/etc/postfix/headreject
header_size_limit = 102400
home_mailbox =
hopcount_limit = 50
ignore_mx_lookup_error = no
inet_interfaces = all
initial_destination_concurrency = 2
invalid_hostname_reject_code = 501
ipc_idle = 100
ipc_timeout = 3600
line_length_limit = 2048
local_command_shell =
local_destination_concurrency_limit = 2
local_destination_recipient_limit = $default_destination_recipient_limit
luser_relay =
mail_name = Postfix release-19990601
mail_owner = postfix
mail_spool_directory = /var/mail
mail_version = Beta-19990601
mailbox_command = /usr/local/bin/procmail -Y
mailbox_transport =
maps_rbl_domains = rbl.maps.vix.com
maps_rbl_reject_code = 550
masquerade_domains =
masquerade_exceptions =
max_idle = 300
max_use = 100
maximal_backoff_time = 500
maximal_queue_lifetime = 5
message_size_limit = 6000000
minimal_backoff_time = 500
mydestination = $myhostname, localhost.$mydomain
mydomain = hsc.fr
myhostname = yoko.hsc.fr
mynetworks = 192.168.230.0/24,127.0.0.0/8
myorigin = $myhostname
non_fqdn_reject_code = 504
notify_classes = resource,software,bounce,policy,protocol,delay
owner_request_special = yes
process_id_directory = pid
program_directory = /usr/local/postfix/sbin
propagate_unmatched_extensions = alias, forward, canonical, virtual, include
qmgr_message_active_limit = 1000
qmgr_message_recipient_limit = 1000
queue_directory = /var/spool/postfix
queue_minfree = 0
queue_run_delay = 6000
recipient_canonical_maps = regexp:/etc/postfix/reecriture
recipient_delimiter = +
recipient_feature_delimiter =
reject_code = 550
relay_domains = $mydestination, $virtual_domains
relay_domains_reject_code = 550
relayhost = [192.70.106.33:25]
relocated_maps =
sender_canonical_maps = hash:/etc/postfix/canonical
service_throttle_time = 60
smtp_connect_timeout = 0
smtp_data_done_timeout = 600
smtp_data_init_timeout = 120
smtp_data_xfer_timeout = 180
smtp_destination_concurrency_limit = $default_destination_concurrency_limit
smtp_destination_recipient_limit = $default_destination_recipient_limit
smtp_helo_timeout = 300
smtp_mail_timeout = 300
smtp_quit_timeout = 300
smtp_rcpt_timeout = 300
smtp_skip_4xx_greeting = no
smtp_skip_quit_response = yes
smtpd_banner = yoko.hsc.fr ESMTP Server (Microsoft Exchange Internet Mail Service 5.5.2524.0) ready
smtpd_client_restrictions =
smtpd_delay_reject = no
smtpd_error_sleep_time = 5
smtpd_etrn_restrictions =
smtpd_hard_error_limit = 10
smtpd_helo_required = yes
smtpd_helo_restrictions =
smtpd_recipient_limit = 1000
smtpd_recipient_restrictions = permit_mynetworks,check_relay_domains
smtpd_sender_restrictions = hash:/etc/postfix/Access,
reject_non_fqdn_sender,
reject_unknown_address,
reject_maps_rbl
smtpd_soft_error_limit = 10
smtpd_timeout = 300
soft_bounce = no
stale_lock_time = 500
sun_mailtool_compatibility = no
swap_bangpath = yes
transport_maps = hash:/etc/postfix/transport
transport_retry_time = 60
trigger_timeout = 10
unknown_address_reject_code = 450
unknown_client_reject_code = 450
unknown_hostname_reject_code = 450
virtual_maps = regexp:/etc/postfix/regvirtual,hash:/etc/postfix/virtual
postfix/postfix001.html 100664 1751 146 4173 7020551562 14326 0 ustar thivillo www
![[debut]](../icons/info.gif){kind=icon}
Introduction
![[precedent]](../icons/prev.gif){kind=icon}
![[suivant]](../icons/next.gif){kind=icon}
Tutorial Postfix
12 Octobre 1999
- Alain Thivillon / Herv Schauer Consultants -
postfix/postfix002.html 100664 1751 146 4014 7020550426 14317 0 ustar thivillo www
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01
- Page 1 -
Agenda:Matin
Pourquoi Postfix
Prsentation de l'architecture logicielle
Compilation
Installation
Configuration de base
postfix/postfix003.html 100664 1751 146 3666 7020550426 14334 0 ustar thivillo www
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01
- Page 2 -
Agenda:Aprs Midi
Configuration avance
Maintenance
Exemple de migrations depuis sendmail
Applications, Questions, rponses
postfix/postfix004.html 100664 1751 146 4047 7020550426 14327 0 ustar thivillo www
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01
- Page 3 -
Buts - 1
Buts premiers : un nouveau MTA sous Unix
sr : bnficier de l'exprience Sendmail...
facile administrer : ce qui est facile comprendre est facile
scuriser.
rapide & volutif : le trafic SMTP de 1999 n'est pas celui de
1980. Il faut pouvoir faire un logiciel supportant les sites normes (ISP,
Accs des grosses entreprises, ...)
postfix/postfix005.html 100664 1751 146 4303 7020550426 14323 0 ustar thivillo www
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01
- Page 4 -
Buts - 2
Compatibilit sendmail maximale
avec les MUA existants (pine,mutt,mail, ...)
avec les gestionnaires de liste (majordomo, sympa, ...)
avec les formats de bote aux lettres (mh, mbox, qmail-dir, ...)
avec les agents d'acheminement local (procmail, deliver, cyrus, ...)
avec les configurations (UUCP, rcriture, mailertable, ...)
avec les utilisateurs (alias, .forward, ...)
postfix/postfix006.html 100664 1751 146 3531 7020550426 14326 0 ustar thivillo www
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01
- Page 5 -
Buts - 3
Respect ...
... des RFCs
... des machines locales
... des sites distants
... des administrateurs
postfix/postfix007.html 100664 1751 146 3046 7020550426 14330 0 ustar thivillo www
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01
- Page 6 -
Schema de principe
postfix/postfix008.html 100664 1751 146 4111 7020550426 14323 0 ustar thivillo www
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01
- Page 7 -
Architecture - 1
Une fonction / un programme (the Unix way)
Lecture des messages locaux
Rception SMTP
Rcriture
Envoi SMTP
Dlivrance locale
Traitement des erreurs (bounces)
Gestion des files
postfix/postfix009.html 100664 1751 146 3741 7020550426 14334 0 ustar thivillo www
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01
- Page 8 -
Architecture - 2
Apports en termes de scurit:
Dcomposition = programmes plus petits et plus lisibles
Plus difficile casser ou circonvenir
Chroot plus facile
Les programmes ne se font pas confiance : isolation de chaque fonction
postfix/postfix010.html 100664 1751 146 3562 7020550426 14325 0 ustar thivillo www
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01
- Page 9 -
Architecture - 3
Communication interprocessus par sockets Unix ou file (FIFO)
Portabilit aise
Messages courts dans les sockets
Ne pas faire confiance aux donnes
postfix/postfix011.html 100664 1751 146 4011 7020550426 14314 0 ustar thivillo www
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01
- Page 10 -
Architecture - 4
Semi rsidence
Les dmons sont rutiliss et contrls par Nombre maximum pour chaque fonction : contrle prcis du fonctionnement
Cot d'un nouveau message rduit (plus de fork)
Temps d'inactivit paramtrable
postfix/postfix012.html 100664 1751 146 4175 7020550426 14330 0 ustar thivillo www
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01
- Page 11 -
Architecture - 5
Files d'attente multiples
maildrop : messages locaux posts par sendmail
incoming : messages en cours de rcriture et de nettoyage
active : messages en cours ou en attente de transport
deferred : messages en attente
defer : arborescence d'attente (hache pour viter les trop gros
rpertoires -- problme dans Sendmail)
postfix/postfix013.html 100664 1751 146 4174 7020550427 14331 0 ustar thivillo www
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01
- Page 12 -
Compilation-1
Rcuprer les sources sur http://www.postfix.org/
ftp://ftp.porcupine.org/mirrors/postfix-release/index.html
Vrifier la signature PGP
tar xvfz postfix-<version>.tar.gz
cd postfix-<version> puis make
Voir la liste des plateformes
postfix/postfix014.html 100664 1751 146 3715 7020550427 14332 0 ustar thivillo www
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01
- Page 13 -
Compilation-2
Purger : make tidy
Changer les options:
% make makefiles CC=/opt/SUNWspro/bin/cc
% make
% make makefiles CCARGS="-DHAS_DB -DPATH_DB_H='
Portage
Voir makedefs et util/sys_defs.h
postfix/postfix015.html 100664 1751 146 6366 7020550427 14340 0 ustar thivillo www
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01
- Page 14 -
Compilation-3
Les commandes sont dans bin/
-rwxr-xr-x 1 thivillo thivillo 206293 Sep 14 17:30 postalias
-rwxr-xr-x 1 thivillo thivillo 69893 Sep 14 17:30 postcat
-rwxr-xr-x 1 thivillo thivillo 175568 Sep 14 17:31 postconf
-rwxr-xr-x 1 thivillo thivillo 259807 Sep 14 17:31 postdrop
-rwxr-xr-x 1 thivillo thivillo 157987 Sep 14 17:30 postfix
-rwxr-xr-x 1 thivillo thivillo 175056 Sep 14 17:31 postkick
-rwxr-xr-x 1 thivillo thivillo 160974 Sep 14 17:31 postlock
-rwxr-xr-x 1 thivillo thivillo 71422 Sep 14 17:31 postlog
-rwxr-xr-x 1 thivillo thivillo 185495 Sep 14 17:31 postmap
-rwxr-xr-x 1 thivillo thivillo 195837 Sep 14 17:31 postsuper
-rwxr-xr-x 1 thivillo thivillo 296176 Sep 14 17:30 sendmail
-rwxr-xr-x 1 thivillo thivillo 116069 Sep 14 17:30 smtp-sink
-rwxr-xr-x 1 thivillo thivillo 124378 Sep 14 17:30 smtp-source
Les dmons sont dans libexec/
-rwxr-xr-x 1 thivillo thivillo 391034 Sep 14 17:30 bounce
-rwxr-xr-x 1 thivillo thivillo 496274 Sep 14 17:30 cleanup
-rwxr-xr-x 1 thivillo thivillo 357009 Sep 14 17:30 error
-rwxr-xr-x 1 thivillo thivillo 575378 Sep 14 17:30 local
-rwxr-xr-x 1 thivillo thivillo 297706 Sep 14 17:30 master
-rwxr-xr-x 1 thivillo thivillo 346448 Sep 14 17:30 pickup
-rwxr-xr-x 1 thivillo thivillo 415171 Sep 14 17:30 pipe
-rwxr-xr-x 1 thivillo thivillo 464115 Sep 14 17:30 qmgr
-rwxr-xr-x 1 thivillo thivillo 327297 Sep 14 17:30 showq
-rwxr-xr-x 1 thivillo thivillo 510917 Sep 14 17:30 smtp
-rwxr-xr-x 1 thivillo thivillo 535152 Sep 14 17:30 smtpd
-rwxr-xr-x 1 thivillo thivillo 341580 Sep 14 17:30 trivial-rewrite
postfix/postfix016.html 100664 1751 146 4225 7020550660 14330 0 ustar thivillo www
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01
- Page 15 -
Installation-1
Arrter sendmail !
# cd /usr/sbin
# mv sendmail sendmail.OFF
# chmod 755 sendmail.OFF
# /usr/sbin/sendmail.OFF -q30m
# rm /usr/bin/newaliases /usr/sbin/purgestat /usr/sbin/hoststat /usr/bin/mailq
Crer un utilisateur et un groupe postfix, compte bloqu, pas de shell, pas de home
Crer les arborescences:
# umask 022
# mkdir /etc/postfix
# mkdir /var/spool/postfix
# mkdir /usr/local/postfix
# mkdir /usr/local/postfix/sbin
# mkdir /usr/local/postfix/libexec
postfix/postfix017.html 100664 1751 146 4144 7020550427 14332 0 ustar thivillo www
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01
- Page 16 -
Installation-2
Copie des binaires et dmons
# umask 022
# cp bin/* /usr/local/postfix/sbin
# cp libexec/* /usr/local/postfix/libexec
# ln -s /usr/local/postfix/sbin/* /usr/sbin
# ln -s /usr/local/postfix/sbin/sendmail /usr/bin/mailq
# ln -s /usr/local/postfix/sbin/sendmail /usr/bin/newaliases
Copie des squelettes de configuration
# cp conf/main.cf /etc/postfix
# cp conf/master.cf /etc/postfix
# cp conf/postfix-script-nosgid /etc/postfix/postfix-script
postfix/postfix018.html 100664 1751 146 4766 7020550755 14351 0 ustar thivillo www
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01
- Page 17 -
Installation-3
Alternative : utiliser INSTALL.sh
Moins de contrle sur les rpertoires
Il vaut mieux connaitre l'architecture :)
Attention aux distributions Linux et au bit Set-Uid sur /usr/sbin/sendmail !
Debian: suid-manager (diter /etc/suid.conf et supprimer l'entre sendmail)
RedHat: linuxconf : supprimer le module mail de /etc/conf.linuxconf et supprimer /usr/sbin/sendmail de /usr/lib/linuxconf/redhat/perm/mail
Autres systmes : voir
Dmarrage :
/usr/sbin/postfix {start|stop|reload}
OU : /usr/sbin/sendmail -bd
postfix/postfix019.html 100664 1751 146 4770 7020550427 14341 0 ustar thivillo www
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01
- Page 18 -
Mise en place du chroot
Les dmons peuvent tre chroots par master dans /var/spool/postfix
Crer /var/spool/postfix/{etc,usr/lib}
Dpend beaucoup du systme
Il faut au minimum:
$ ls -lR /var/spool/postfix/etc
total 132
-rw-r--r-- 1 root wheel 195 Mar 26 1999 host.conf
-r--r--r-- 1 root wheel 1088 Apr 13 12:53 localtime
-rw-r--r-- 1 root bin 61960 Mar 16 1999 services
Librairies dynamiques de la glibc sur Linux, /dev/tcp, etc... sous Solaris
Regarder examples/chroot-setup:
AIX42 FREEBSD3 HPUX9 LINUX2 OPENSTEP4
BSDI2 FreeBSD2 IRIX5 NETBSD1 OSF1
BSDI3 HPUX10 IRIX6 NEXTSTEP3 Solaris2
postfix/postfix020.html 100664 1751 146 4773 7020550427 14334 0 ustar thivillo www
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01
- Page 19 -
Configuration de base
master.cf
dfinit les dmons lancer, leur nombre et les "transports"
# ==========================================================================
# service type private unpriv chroot wakeup maxproc command + args
# (yes) (yes) (yes) (never) (50)
# ==========================================================================
smtp inet n - y - - smtpd
pickup fifo n n y 60 1 pickup
cleanup unix - - y - 0 cleanup
qmgr fifo n - y 300 1 qmgr
rewrite unix - - y - - trivial-rewrite
bounce unix - - y - 0 bounce
defer unix - - y - 0 bounce
smtp unix - - y - - smtp
showq unix n - y - - showq
local unix - n n - - local
cyrus unix - n n - - pipe
flags=R user=cyrus argv=/usr/cyrus/bin/deliver -e -q -m ${extension} ${user}
#uucp unix - n n - - pipe
flags=F user=uucp argv=uux -n -z -a$sender - $nexthop!rmail ($recipient)
postfix/postfix021.html 100664 1751 146 4312 7020550427 14322 0 ustar thivillo www
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01
- Page 20 -
Configuration de base 2
main.cf
Dfinit toute la configuration
parametre = valeur
paramtres multilignes
version francise
Utilitaire postconf
-d : donne les paramtres par dfaut
-n : donne les paramtres changs
postfix/postfix022.html 100664 1751 146 4411 7020550427 14323 0 ustar thivillo www
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01
- Page 21 -
Configuration de base 3
Configuration initiale
Rpertoires de base:
command_directory = /usr/local/postfix/sbin
daemon_directory = /usr/local/postfix/libexec
remplir myhostname, mydomain, myorigin, mydestination, relayhost
Dlivrance locale
Soit directe (voir mail_spool_directory = /var/spool/mail)
Soit via un agent externe : mailbox_command = /usr/bin/procmail
postfix/postfix023.html 100664 1751 146 5210 7020550427 14322 0 ustar thivillo www
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01
- Page 22 -
Configuration de base 4
Anti-relayage:
Remplir mynetworks = 192.168.0.0/24, ... (ou via /etc/postfix/fichier)
Remplir relay_domains = (idem)
smtpd_recipient_restrictions = permit_mynetworks,check_relay_domains
Eventuellement, ajouter "permit_mx_backup" si on ne connait pas tous les domaines dont on est MX secondaire.
Gestion de la file
maximal_queue_lifetime = 4 (jours)
delay_warning_time = (heures)
queue_run_delay = 1000 (secondes)
maximal_backoff_time = 4000 (secondes)
transport_destination_concurrency_limit=10
|
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01 |
- Page 23 - |
|
Configuration anti-spam : utilisation de liste noire
Dans la connexion:
# Ne pas accepter les machines sans DNS inverse (stupide et dangereux)
# Spammers a mettre dehors la connexion
smtpd_client_restrictions = reject_unkown_client,
hash:/etc/postfix/Access
Dans le MAIL FROM:
smtpd_sender_restrictions = hash:/etc/postfix/Access,
reject_non_fqdn_sender,
reject_unknown_address,
reject_maps_rbl
Refaire la table : postmap /etc/postfix/Access
|
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01 |
- Page 24 - |
|
Dans le RCPT TO:
smtpd_recipient_restrictions = permit_mynetworks,
check_recipient_access hash:/etc/postfix/accesseveryone,
check_relay_domains
Par dfaut, les erreurs sont renvoyes la fin de la phase (cf smtpd_delay_reject)
Autres paramtres: smtpd_helo_required, smtpd_etrn_restrictions, ...
Recevoir les messages rejets :
notify_classes = resource,software,bounce,policy,protocol,delay error_notice_recipient =(postmaster par dfaut)
|
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01 |
- Page 25 - |
|
Filtrage dans les headers : utilisation de regexp
header_checks = regexp:/etc/postfix/headreject /^From: .*\s+friend\@/ REJECT /^To: .*\s+friend\@/ REJECT /^X-Spanska/ 554 Happy99 Virus
Liste blanche dans le Mail FROM:
smtpd_recipient_restrictions = permit_mynetworks,
check_sender_access hash:/etc/postfix/Access,
check_relay_domains,
at@hsc.fr OK
Possibilit de POP avant SMTP
|
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01 |
- Page 26 - |
|
La table des transports est comparer la mailertable de sendmail.
Utilisation d'une table standard:
transport_maps = hash:/etc/postfix/transport domaine.com smtp:[interne.domaine.com] pauvre.domaine.com uucp:pauvre .domaine.com smtp:[interne.domaine.com]
Utilisation de regexp:
transport_maps = regexp:/etc/postfix/regtrans /(.*)\.anciendomaine\.com/ smtp:[$1.nouveaudomaine.com]
On peut dupliquer des transports dans master.cf (par exemple pour avoir un nombre fix de dmons SMTP pour les machines internes).
smtpint unix - - y - 10 smtp yoko.hsc.fr smtpint:[yoko.hsc.fr]
|
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01 |
- Page 27 - |
|
Masquerading:
masquerade_domains = domaine.fr : rcrit tout user@machine.domaine.fr en user@domaine.fr
masquerade_exceptions = root : permet de spcifier que root n'est pas rcrit (comportement par dfaut de sendmail).
Canonical:
canonical_maps = hash:/etc/postfix/canonical
user autreuser user@domaine1.fr autreutilisateur@domaine5.fr @domaine1.fr @domaine2.fr @domaine3.fr user@domaine4.fr
Variantes : sender_canonical_maps et recipient_canonical_maps
On peut aussi utiliser les regexp, mysql, ...
|
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01 |
- Page 28 - |
|
Permet d'hberger plusieurs domaines sur la mme machine sans rcrire les headers (ne rcrit que l'enveloppe):
virtual_maps = hash:/etc/postfix/virtual
domaine0 nimportequoi
user1@domaine1 adresse1,adresse2,...
user2 adresse3,adresse4, .... (comme les alias)
@domaine3.fr adresse5,adresse6,...
@domaine4.fr @domaine5.fr (pas de changement
de la partie gauche)
La aussi, on peut aussi utiliser les regexp, mysql, ...
|
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01 |
- Page 29 - |
|
Intgration avec OpenLDAP : rechercher le maildrop d'un utilisateur.
Compilation
% make tidy
% make makefiles CCARGS="-I/some/where/include -DHAS_LDAP" \
AUXLIBS="/some/where/libldap.a /some/where/liblber.a"
Intgration dans les aliases
alias_maps = hash:/etc/aliases, ldap:hsc
Dfinir la source (il peut y en avoir plusieurs):
hsc_server_host = ldap.hsc.fr hsc_search_base = dc=hsc, dc=fr hsc_bind_dn= uid=postfix, dc=hsc, dc=fr hsc_bind_pw= Argh-J-ai-Mis-le-Password-Dans-Le-Cours
Paramtres supplmentaires : voir LDAP_README
|
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01 |
- Page 30 - |
|
Serveur Imap et POP3 Cyrus
Gestion des utilisateurs indpendante de /etc/passwd
Mailboxes indexes
Tourne en identit non privilgie
Dans postfix, dclarer le transport cyrus dans master.cf:
cyrus unix - n n - - pipe
flags=R user=cyrus argv=/usr/cyrus/bin/deliver -e -q -m ${extension} ${user}
mailbox_transport = cyrus
ou
fallback_transport = cyrus
Utilisation du transport de type "pipe"
Pas d'utilisation du shell
Filtrage des caractres (command_expansion_filter= ...)
|
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01 |
- Page 31 - |
|
mailq : affichage de la file
47 [15:56] thivillo@yoko:~> mailq
-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
E1DCB12FF82 332 Fri Oct 8 15:56:21 Alain.Thivillon@hsc.fr
camarchepas@jesais.paou
-- 0 Kbytes in 1 Request.
postcat: affichage d'un message dans la file
2 [15:57] thivillo@yoko:~# postcat /var/spool/postfix/deferred/E1DCB12FF82 *** ENVELOPE RECORDS /var/spool/postfix/deferred/E1DCB12FF82 *** ...
postmap, postalias: reconstruction des tables et de l'ensemble des aliases
postsuper : nettoyage des files, vrification d'intgrit.
|
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01 |
- Page 32 - |
|
Penser syslog !
Oct 8 15:56:21 yoko postfix/pickup[36587]: E1DCB12FF82: uid=1001 from=<thivillo>
Oct 8 15:56:21 yoko postfix/cleanup[36731]: E1DCB12FF82: message-id=<19991008135621.E1DCB12FF82@yoko.hsc.fr>
Oct 8 15:56:21 yoko postfix/qmgr[35821]: E1DCB12FF82: from=<Alain.Thivillon@hsc.fr>, size=332 (queue active)
Oct 8 15:56:21 yoko postfix/qmgr[35821]: E1DCB12FF82: to=<camarchepas@jesais.paou>, relay=none, delay=0, status=deferred (deferred transport)
Oct 8 15:59:20 yoko postfix/smtpd[36790]: connect from itesec.hsc.fr[192.70.106.33]
Oct 8 15:59:20 yoko postfix/smtpd[36790]: E776C12FF83: client=itesec.hsc.fr[192.70.106.33]
Oct 8 15:59:20 yoko postfix/cleanup[36791]: E776C12FF83: message-id=<19991008135911.53165AF0A5@ns2.freenix.org>
Oct 8 15:59:21 yoko postfix/qmgr[35821]: E776C12FF83: from=<stump@ns2.freenix.org>, size=4896 (queue active)
Oct 8 15:59:21 yoko postfix/smtpd[36790]: disconnect from itesec.hsc.fr[192.70.106.33]
Oct 8 15:59:21 yoko postfix/local[36732]: E776C12FF83: to=<thivillo@yoko.hsc.fr>, relay=local, delay=1, status=sent ("|/usr/local/bin/procmail -Y")
Outil de statistiques : pflogsumm
|
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01 |
- Page 33 - |
|
Faire un bilan de l'existant sendmail
Pour qui je reois le mail ?
Pour qui je l'envoie ?
Rcritures, mailertable ?
Modifications directes sendmail.cf ?
Manquent dans postfix:
Pas de grammaire gnralise
Pas de rcriture 8bits/7bits et inversement
?
|
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01 |
- Page 34 - |
|
Features ...
| FEATURE(mailertable) | utiliser les transports |
| FEATURE(generics) | utiliser canonical_map |
| FEATURE(virtusertable) | utiliser virtual_maps |
| FEATURE(bestmx_is_local) | best_mx_transport = local |
Quelques paramtres:
| MaxMessageSize |
bounce_size_limit = 50000 header_size_limit = 102400 message_size_limit = 10240000 |
| HoldExpensive | deferred_transports=smtp,... |
| FallbackMXhost | fallback_relay= |
| SmtpGreetingMessage | smtpd_banner = $myhostname ESMTP $mail_name |
|
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01 |
- Page 35 - |
|
Attention : je ne connais pas bien ! :)
Variables
| ListeDomaines et AdressesLocales | mydestination= |
| AdressesInterne | relay_domains |
| RelaisExterieur | relayhost= |
| TableRoutages | Utiliser les transports |
| ListeNoire | smtpd_sender_restrictions=, voir aussi mynetworks et relay_domains |
| RevAliases | utiliser sender_canonical_maps= |
| SansCanonisation | disable_dns_lookups=yes mais impose un relais |
| MailerLocal | mailbox_command |
|
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01 |
- Page 36 - |
|
Bouclage d'aliases
www:www,postmaster donne une erreur dans postfix
Difficile dterminer
Pas de dduplication des aliases car ceux-ci ne sont consults qu' la fin.
un message unalias,uneadressedansaliase donne deux messages
utiliser "virtual"
Pas de priorit dans la file
Mais les multiples connexions par destination rglent plus ou moins le problme
ETRN lance toute la file (pour le moment).
|
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01 |
- Page 37 - |
|
La machine est MX record de domaine.fr et envoie sur un domaine interne
mydestination = firewall.domaine.fr myorigin = domaine.fr transport_maps = hash:/etc/postfix/transport
Dans la table transport, on indique domaine.fr smtp:[interne.domaine.fr]
On ne met pas de dlivrance locale, aliaser root et les autres comptes vers postmaster@domaine.fr
rglage strict du relayage :
mynetwork=<adresseipdumailinterne>
relay_domains = domaine.fr
smtp_rcpt_restrictions=permit_mynetworks, check_relay_domains
smtpd_sender_restrictions = hash:/etc/postfix/Access,
reject_non_fqdn_sender,
reject_unknown_address
|
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01 |
- Page 38 - |
|
NullClient : ne fait qu'envoyer un relais, pas d'utilisateur local
On arrete la partie SMTP et la partie dlivrance locale dans master.cf
Configuration:
mydestination=host.domaine.fr myorigin=domaine.fr masquerade_domains=domaine.fr relayhost=smtp:[mailhost.domaine.fr] disable_dns_lookups=yes
|
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01 |
- Page 39 - |
|
Contraintes:
Envoie tout au serveur de son FAI
A un domaine non existant cacher
Reoit par fetchmail
a un rseau interne pour le reste de la famille.
Configuration:
mydestination=machine.domaine.maison,localhost.domaine.maison,domaine.maison myorigin=machine.domaine.maison relayhost=smtp:[mailhost.fai.fr] disable_dns_lookups=yes deferred_transport=smtp sender_canonical_maps=hash:/etc/postfix/canonical mynetworks=192.168.3.0/24,127.0.0.1
La table /etc/postfix/canonical contient:
monlogin monadresse@fai.fr papa adressedepapa@fai.fr maman adressedemaman@fai.fr # Pour inn et les groupes modrs news monadresse@fai.fr
|
Herv SCHAUER Consultants 1999 -
142, rue de Rivoli -
75039 PARIS CEDEX 01 |
- Page 40 - |