From: Wietse Venema Date: Thu, 19 Dec 2002 05:00:00 +0000 (-0500) Subject: postfix-1.1.12-20021219 X-Git-Tag: v2.0.0~2 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=a31a35baef0b9ea2a017b2087ccb388fe1228ed5;p=thirdparty%2Fpostfix.git postfix-1.1.12-20021219 --- diff --git a/postfix/HISTORY b/postfix/HISTORY index a68d0a460..ada3829d5 100644 --- a/postfix/HISTORY +++ b/postfix/HISTORY @@ -7479,6 +7479,18 @@ Apologies for any names omitted. site already ran Postfix with local_recipient_maps enabled. Files: smtpd/smtpd.c, smtpd/smtpd_check.c, conf/post-install. +20021219 + + Bugfix: longjmp() while sending "go away" without setjmp() + in the QMQP server. Patrik Rak. File: qmqpd/qmqpd.c. + + Safety: the XVERP extension is restricted to clients listed + in the authorized_verp_clients list (default: $mynetworks). + File: smtpd/smtpd.c. + + Workaround: preliminary IPV6 support in valid_hostliteral(). + File: util/valid_hostname.c. + Open problems: Low: after successful delivery, per-queue window += 1/window, diff --git a/postfix/INSTALL b/postfix/INSTALL index 53a2d6b57..6260b0d0a 100644 --- a/postfix/INSTALL +++ b/postfix/INSTALL @@ -239,9 +239,6 @@ In order to install or upgrade Postfix: Note: there should be no whitespace before "postdrop:". - NB: this group was optional with older Postfix releases; it is - now required. - - Optional: If you want to install symbol-stripped (non-debug) versions of the Postfix programs and daemons, do: @@ -496,6 +493,24 @@ files or device nodes. The examples/chroot-setup directory has a collection of scripts that help you set up chroot environments for Postfix systems. +IMPORTANT: if you enable chrooted operation of the SMTP server you +must copy the passwd file into the chroot jail, otherwise the SMTP +server will reject mail for local addresses. + +44BSD systems: + + # mkdir /var/spool/postfix/etc + # cp /etc/pwd.db /var/spool/postfix/etc + +Other systems: + + # mkdir /var/spool/postfix/etc + # cp /etc/passwd /var/spool/postfix/etc + +You may also have to copy /etc/nsswitch.conf and the files referenced +by /etc/nsswitch.conf. See the system dependent scripts in +examples/chroot-setup for suggestions. + 12 - Care and feeding of the Postfix system =========================================== diff --git a/postfix/README_FILES/INSTALL b/postfix/README_FILES/INSTALL deleted file mode 100644 index b495c125a..000000000 --- a/postfix/README_FILES/INSTALL +++ /dev/null @@ -1,520 +0,0 @@ -1 - Purpose of this document -============================ - -This document describes how to build, install and configure a -Postfix system so that it can do one of the following: - - - Send mail only, without changing an existing sendmail - installation. - - - Send and receive mail via a virtual host interface, still - without any change to an existing sendmail installation. - - - Replace sendmail altogether. - -2 - Typographical conventions -============================= - -In the instructions below, a command written as - - # command - -should be executed as the superuser. - -A command written as - - % command - -should be executed as an unprivileged user. - -3 - Documentation -================= - -Documentation is available as HTML web pages (point your browser -to html/index.html) and as UNIX-style man pages (point your MANPATH -environment variable to the `man' subdirectory; be sure to use an -absolute path). - -The sample configuration files in the `conf' directory have extensive -comments, but they may not describe every nuance of every feature. - -Many files have their own built-in manual page. Tools to extract -those embedded manual pages are available in the mantools directory. - -4 - Building on a supported system -================================== - -If your system is supported, it is one of - - AIX 3.2.5 - AIX 4.1.x - AIX 4.2.0 - BSD/OS 2.x - BSD/OS 3.x - BSD/OS 4.x - Darwin 1.x - FreeBSD 2.x - FreeBSD 3.x - FreeBSD 4.x - FreeBSD 5.x - HP-UX 9.x - HP-UX 10.x - HP-UX 11.x - IRIX 5.x - IRIX 6.x - Linux Debian 1.3.1 - Linux Debian 2.x - Linux RedHat 4.x - Linux RedHat 5.x - Linux RedHat 6.x - Linux RedHat 7.x - Linux Slackware 3.x - Linux Slackware 4.x - Linux Slackware 7.x - Linux SuSE 5.x - Linux SuSE 6.x - Linux SuSE 7.x - Mac OS X - NEXTSTEP 3.x - NetBSD 1.x - OPENSTEP 4.x - OSF1.V3 (Digital UNIX) - OSF1.V4 aka Digital UNIX V4 - OSF1.V5 aka Digital UNIX V5 - OpenBSD 2.x - Reliant UNIX 5.x - Rhapsody 5.x - SunOS 4.1.x (with Postfix 1.1.0) - SunOS 5.4..5.8 (Solaris 2.4..8) - Ultrix 4.x (well, that was long ago) - -or something closely resemblant. - -On Solaris, the "make" command and other utilities for software -development are in /usr/ccs/bin, so you MUST have /usr/ccs/bin in -your command search path. - -If you need to build Postfix for multiple architectures, use the -lndir command to build a shadow tree with symbolic links to the -source files. lndir is part of X11R6. - -If at any time in the build process you get messages like: "make: -don't know how to ..." you should be able to recover by running -the following command from the Postfix top-level directory: - - % make -f Makefile.init makefiles - -If you copied the Postfix source code after building it on another -machine, it is a good idea to cd into the top-level directory and - - % make tidy - -first. This will get rid of any system dependencies left over from -compiling the software elsewhere. - -To build with GCC, or with the native compiler if people told me -that is better for your system, just cd into the top-level Postfix -directory of the source tree and type: - - % make - -To build with a non-default compiler, you need to specify the name -of the compiler: - - % make makefiles CC=/opt/SUNWspro/bin/cc (Solaris) - % make - - % make makefiles CC="/opt/ansic/bin/cc -Ae" (HP-UX) - % make - - % make makefiles CC="purify cc" - % make - -and so on. In some cases, optimization is turned off automatically. - -In order to build with non-default settings, for example, with a -configuration directory other than /etc/postfix, use: - - % make makefiles CCARGS='-DDEF_CONFIG_DIR=\"/some/where\"' - % make - -Be sure to get the quotes right. These details matter a lot. - -Other parameters whose defaults can be specified in this way are: - - Macro name default value for - ------------------------------------- - DEF_COMMAND_DIR command_directory - DEF_DAEMON_DIR daemon_directory - DEF_SENDMAIL_PATH sendmail_path - DEF_MAILQ_PATH mailq_path - DEF_NEWALIAS_PATH newaliases_path - -In order to build Postfix for very large applications, where you -expect to run more than 1000 delivery processes, you may need to -override the definition of the FD_SETSIZE macro to make select() -work correctly: - - % make makefiles CCARGS=-DFD_SETSIZE=2048 - -In any case, if the command - - % make - -produces compiler error messages, it may be time to examine the -FAQ document (see html/faq.html). - -5 - Porting to on an unsupported system -======================================= - -- Each system type is identified by a unique name. Examples: -SUNOS5, FREEBSD4, and so on. Choose a SYSTEMTYPE name for the new -system. You must use a name that includes at least the major version -of the operating system (such as SUNOS4 or LINUX2), so that different -releases of the same system can be supported without confusion. - -- Add a case statement to the "makedefs" shell script in the -top-level directory that recognizes the new system reliably, and -that emits the right system-specific information. Be sure to make -the code robust against user PATH settings; if the system offers -multiple UNIX flavors (e.g. BSD and SYSV) be sure to build for the -native flavor, not the emulated one. - -- Add an #ifdef SYSTEMTYPE section to the central util/sys_defs.h -include file. You may have to invent new feature macros. Please -choose sensible feature macro names such as HAS_DBM or -FIONREAD_IN_SYS_FILIO_H. I strongly recommend against #ifdef -SYSTEMTYPE dependencies in individual source files. This may seem -to be the quickest solution, but it will create a mess that becomes -increasingly difficult to maintain over time. Moreover, with the -next port you'd have to place #ifdefs all over the source code -again. - -6 - Installing the software after successful compilation -======================================================== - -This text describes how to install Postfix from source code. See -the PACKAGE_README file if you are building a package for distribution -to other systems. - -IMPORTANT: if you are REPLACING an existing sendmail installation -with Postfix, you may need to keep the old sendmail program running -for some time in order to flush the mail queue. As superuser, -execute the following commands (your sendmail, newaliases and mailq -programs may be in a different place): - - # mv /usr/sbin/sendmail /usr/sbin/sendmail.OFF - # mv /usr/bin/newaliases /usr/bin/newaliases.OFF - # mv /usr/bin/mailq /usr/bin/mailq.OFF - # chmod 755 /usr/sbin/sendmail.OFF /usr/bin/newaliases.OFF \ - /usr/bin/mailq.OFF - -In order to install or upgrade Postfix: - -- Create a user account "postfix" with a user id and group id that - are not used by any other user account. Preferably, this is an - account that no-one can log into. The account does not need an - executable login shell, and needs no existing home directory. - My password file entry looks like this: - - postfix:*:12345:12345:postfix:/no/where:/no/shell - - Note: there should be no whitespace before "postfix:". - -- Make sure there is a corresponding alias in /etc/aliases: - - postfix: root - - Note: there should be no whitespace before "postfix:". - -- Create a group "postdrop" with a group id that is not used by - any other user account. Not even by the postfix user account. - My group file entry looks like: - - postdrop:*:54321: - - Note: there should be no whitespace before "postdrop:". - - NB: this group was optional with older Postfix releases; it is - now required. - -- Optional: If you want to install symbol-stripped (non-debug) versions - of the Postfix programs and daemons, do: - - % strip bin/* libexec/* - -- Run one of the following commands as the super-user: - - # make install (interactive version, first time install) - # make upgrade (non-interactive version, for upgrades) - - The non-interactive version needs the /etc/postfix/main.cf file - from a previous installation. If the file does not exist, use - interactive installation instead. - - The interactive version offers suggestions for pathnames that - you can override interactively, and stores your preferences in - /etc/postfix/main.cf for convenient future upgrades. - -- Proceed to the section on how you wish to run Postfix on your - particular machine: - - - Send mail only, without changing an existing sendmail - installation (section 7). - - - Send and receive mail via a virtual host interface, still - without any change to an existing sendmail installation - (section 8). - - - Replace sendmail altogether (section 9). - -7 - Configuring Postfix to send mail only -========================================= - -If you are going to use Postfix to send mail only, there is no need -to change your existing sendmail setup. Instead, set up your mail -user agent so that it calls the Postfix sendmail program directly. - -Follow the instructions in the "Mandatory configuration file edits" -in section 10, and review the "To chroot or not to chroot" text in -section 11. - -You MUST comment out the `smtp inet' entry in /etc/postfix/master.cf, -in order to avoid conflicts with the real sendmail. - -Start the Postfix system: - - # postfix start - -or, if you feel nostalgic, use the Postfix sendmail command: - - # sendmail -bd -qwhatever - -and watch your syslog file for any error messages. - - % egrep '(reject|warning|error|fatal|panic):' /some/log/file - -Typical logfile names are: /var/log/maillog or /var/log/syslog. -See /etc/syslog.conf for actual logfile names. - -In order to inspect the mail queue, use - - % sendmail -bp - -See also the "Care and feeding" section 12 below. - -8 - Configuring Postfix to send and receive mail (virtual interface) -==================================================================== - -Alternatively, you can use the Postfix system to send AND receive -mail while leaving your sendmail setup intact, by running Postfix -on a virtual interface address. Simply configure your mail user -agent to directly invoke the Postfix sendmail program. - -The examples/virtual-setup directory gives instructions for setting -up virtual interfaces for a variety of UNIX versions. - -In the /etc/postfix/main.cf file, I would specify - - myhostname = virtual.host.tld - inet_interfaces = $myhostname - mydestination = $myhostname - -Follow the instructions in the "Mandatory configuration file edits" -in section 10, and review the "To chroot or not to chroot" text in -section 11. - -Start the mail system: - - # postfix start - -or, if you feel nostalgic, use the Postfix sendmail program: - - # sendmail -bd -qwhatever - -and watch your syslog file for any error messages. - - % egrep '(reject|warning|error|fatal|panic):' /some/log/file - -Typical logfile names are: /var/log/maillog or /var/log/syslog. -See /etc/syslog.conf for actual logfile names. - -In order to inspect the mail queue, use - - % sendmail -bp - -See also the "Care and feeding" section 12 below. - -9 - Turning off sendmail forever -================================ - -Prior to installing Postfix you should save the existing sendmail -program files as described in section 6. - -Be sure to keep the old sendmail running for at least a couple -days to flush any unsent mail. To do so, stop the sendmail daemon -and restart it as: - - # /usr/sbin/sendmail.OFF -q - -After you have visited the "Mandatory configuration file edits" -section below, you can start the Postfix system with - - # postfix start - -But the good old sendmail way works just as well: - - # sendmail -bd -qwhatever - -and watch the syslog file for any complaints from the mail system. - - % egrep '(reject|warning|error|fatal|panic):' /some/log/file - -Typical logfile names are: /var/log/maillog or /var/log/syslog. -See /etc/syslog.conf for actual logfile names. - -See also the "Care and feeding" section 12 below. - -10 - Mandatory configuration file edits -======================================= - -By default, Postfix configuration files are in /etc/postfix, and -must be owned by root. Giving someone else write permission to -main.cf or master.cf means giving root privileges to that person. - -Whenever you make a change to a config file, execute the following -command in order to refresh a running mail system: - - # postfix reload - -In /etc/postfix/main.cf you will have to set up a minimal number of -configuration parameters. Postfix configuration parameters -resemble shell variables. You specify a variable as - - parameter = value - -and you use it by putting a $ in front of its name: - - other_parameter = $parameter - -You can use $parameter before it is given a value. The Postfix -configuration language uses lazy evaluation, and does not look at -a parameter value until it is needed at runtime. - -First of all, you must specify what domain will be appended to an -unqualified address (i.e. an address without @domain.tld). The -"myorigin" parameter defaults to the local hostname, but that is -probably OK only for very small sites. - -Some examples: - - myorigin = $myhostname - myorigin = $mydomain - -In the first case, local mail goes out as user@$myhostname, in -the second case the sender address is user@$mydomain. - -Next you need to specify what mail addresses Postfix should deliver -locally. - -Some examples: - - mydestination = $myhostname, localhost.$mydomain - mydestination = $myhostname, localhost.$mydomain, $mydomain - mydestination = $myhostname - -The first example is appropriate for a workstation, the second is -appropriate for the mailserver for an entire domain. The third -example should be used when running on a virtual host interface. - -If your machine is on an open network then you must specify what -client IP addresses are authorized to relay their mail through your -machine. The default setting includes all class A, B or C networks -that the machine is attached to. Often, that gives relay permission -to too many clients. My own settings are: - - mynetworks = 168.100.189.0/28, 127.0.0.0/8 - -If you're behind a firewall, you should set up a relayhost. If -you can, specify the organizational domain name so that Postfix -can use DNS lookups, and so that it can fall back to a secondary -MX host when the primary MX host is down. Otherwise just specify -a hard-coded hostname. - -Some examples: - - relayhost = $mydomain - relayhost = mail.$mydomain - relayhost = [mail.$mydomain] - -The form enclosed with [] eliminates DNS MX lookups. - -By default, the SMTP client will do DNS lookups for sender and -recipient addresses even when you specify a relay host. If your -machine has no access to a DNS server, turn off SMTP client DNS -lookups like this: - - disable_dns_lookups = yes - -The FAQ (html/faq.html) has more hints and tips for firewalled -and/or dial-up networks. - -Finally, if you haven't used Sendmail prior to using Postfix, you -will have to build the alias database (with: sendmail -bi, or: -newaliases). Be sure to set up aliases for root and postmaster that -forward mail to a real person. Postfix has a sample aliases file -conf/aliases that you can adapt to local conditions. - -11 - To chroot or not to chroot -=============================== - -Postfix can run most daemon processes in a chroot jail, that is, -the processes run at a fixed low privilege and with access only to -the Postfix queue directories (/var/spool/postfix). This provides -a significant barrier against intrusion. The barrier is not -impenetrable, but every little bit helps. - -With the exception of the Postfix daemons that deliver mail locally, -every Postfix daemon can run chrooted. - -Sites with high security requirements should consider to chroot -all daemons that talk to the network: the smtp and smtpd processes, -and perhaps also the lmtp client. - -The default /etc/postfix/master.cf file specifies that no Postfix -daemon runs chrooted. In order to enable chroot operation, edit -the file /etc/postfix/master.cf. Instructions are in the file. - -Note that a chrooted daemon resolves all filenames relative to the -Postfix queue directory (/var/spool/postfix). For successful use -of a chroot jail, most UNIX systems require you to bring in some -files or device nodes. The examples/chroot-setup directory has a -collection of scripts that help you set up chroot environments for -Postfix systems. - -12 - Care and feeding of the Postfix system -=========================================== - -The Postfix programs log all problems to the syslog daemon. The -names of logfiles are specified in /etc/syslog.conf. Note: the -syslogd will not create files. You must create them ahead of time -before (re)starting syslogd. At the very least you need something -like: - - mail.err /dev/console - mail.debug /var/log/maillog - -Hopefully, the number of problems will be small, but it is a good -idea to run every night before the syslog files are rotated: - - # postfix check - # egrep '(reject|warning|error|fatal|panic):' /some/log/file - -Typical logfile names are: /var/log/maillog or /var/log/syslog. -See /etc/syslog.conf for actual logfile names. - -The first line (postfix check) causes Postfix to report file -permission/ownership discrepancies. - -The second line looks for problem reports from the mail software, -and reports how effective the anti-relay and anti-UCE blocks are. diff --git a/postfix/README_FILES/INSTALL b/postfix/README_FILES/INSTALL new file mode 120000 index 000000000..99d491b4f --- /dev/null +++ b/postfix/README_FILES/INSTALL @@ -0,0 +1 @@ +../INSTALL \ No newline at end of file diff --git a/postfix/README_FILES/VERP_README b/postfix/README_FILES/VERP_README index 3ed89f1ad..49a8e33a9 100644 --- a/postfix/README_FILES/VERP_README +++ b/postfix/README_FILES/VERP_README @@ -20,7 +20,7 @@ address without requiring the list owner to parse bounce messages. The VERP concept was popularized by the qmail MTA and by the ezmlm mailing list manager. -The whole process is controlled by two configuration parameters. +The whole process is controlled by four configuration parameters. - default_verp_delimiters (default value: +=) controls what VERP delimiter characters Postfix uses when VERP style delivery is @@ -35,6 +35,17 @@ are used as part of a username or domain name (such as alphanumerics), or because they are non-ASCII or control characters. And who knows, some characters may tickle bugs in vulnerable software. +- authorized_verp_clients (default value: $mynetworks) controls +what network clients are allowed to request VERP style delivery. +Exceptions: the Postfix QMQP server uses its own access control +mechanism, and local submission (via /usr/sbin/sendmail etc.) is +always authorized. To authorize a host, list its name, IP address, +subnet (net/mask) or parent .domain. + +- disable_verp_bounces (default: no) controls if Postfix sends one +bounce report for multi-recipient VERP mail, or one bounce report +per recipient. The default, one per recipient, is what ezmlm needs. + Using VERP with majordomo etc. mailing lists ============================================ diff --git a/postfix/RELEASE_NOTES b/postfix/RELEASE_NOTES index 6232a89a4..97e0de8f8 100644 --- a/postfix/RELEASE_NOTES +++ b/postfix/RELEASE_NOTES @@ -12,6 +12,14 @@ snapshot release). Patches change the patchlevel and the release date. Snapshots change only the release date, unless they include the same bugfixes as a patch release. +Incompatible changes with Postfix snapshot 1.1.12-20021219 +========================================================== + +The use of the XVERP extension in the SMTP MAIL FROM command is +now limited to SMTP clients that match the hostnames, domains or +networks listed with the authorized_verp_clients parameter (default: +$mynetworks). + Incompatible changes with Postfix snapshot 1.1.12-20021209 ========================================================== @@ -20,9 +28,14 @@ file. If your Postfix is unable to connect to the "relay" service then you have not properly followed the installation procedure. The Postfix SMTP server now rejects mail for $mydestination domain -recipients that it does not know about. For this to work correctly, -you need to review the section titled "REJECTING UNKNOWN LOCAL -USERS" in conf/main.cf if one of the following is true: +recipients that it does not know about. This keeps undeliverable +mail out of your queue. For safety's sake, the default is to reply +with a 450 (try again later) status code so that you don't suddenly +lose mail. + +For this to work correctly, you need to review the section titled +"REJECTING UNKNOWN LOCAL USERS" in conf/main.cf if one of the +following is true: - You define $mydestination domain recipients in files other than /etc/passwd, /etc/aliases, or the $virtual_alias_maps files. @@ -37,7 +50,7 @@ USERS" in conf/main.cf if one of the following is true: Specify "local_recipient_maps =" (i.e. empty) to make the SMTP server accept mail for all known and unknown local recipients. -That was the default setting prior to Postfix version 1.2. +That was the default setting prior to Postfix version 2.0. Postfix no longer defaults to the "smtp" transport for all non-local destinations. This may affect your defer_transports settings. In diff --git a/postfix/conf/LICENSE b/postfix/conf/LICENSE deleted file mode 100644 index 45b98347a..000000000 --- a/postfix/conf/LICENSE +++ /dev/null @@ -1,221 +0,0 @@ -IBM PUBLIC LICENSE VERSION 1.0 - SECURE MAILER - -THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS IBM PUBLIC -LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE -PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT. - -1. DEFINITIONS - -"Contribution" means: - a) in the case of International Business Machines Corporation ("IBM"), - the Original Program, and - b) in the case of each Contributor, - i) changes to the Program, and - ii) additions to the Program; - where such changes and/or additions to the Program originate - from and are distributed by that particular Contributor. - A Contribution 'originates' from a Contributor if it was added - to the Program by such Contributor itself or anyone acting on - such Contributor's behalf. - Contributions do not include additions to the Program which: - (i) are separate modules of software distributed in conjunction - with the Program under their own license agreement, and - (ii) are not derivative works of the Program. - -"Contributor" means IBM and any other entity that distributes the Program. - -"Licensed Patents " mean patent claims licensable by a Contributor which -are necessarily infringed by the use or sale of its Contribution alone -or when combined with the Program. - -"Original Program" means the original version of the software accompanying -this Agreement as released by IBM, including source code, object code -and documentation, if any. - -"Program" means the Original Program and Contributions. - -"Recipient" means anyone who receives the Program under this Agreement, -including all Contributors. - -2. GRANT OF RIGHTS - - a) Subject to the terms of this Agreement, each Contributor hereby - grants Recipient a non-exclusive, worldwide, royalty-free copyright - license to reproduce, prepare derivative works of, publicly display, - publicly perform, distribute and sublicense the Contribution of such - Contributor, if any, and such derivative works, in source code and - object code form. - - b) Subject to the terms of this Agreement, each Contributor hereby - grants Recipient a non-exclusive, worldwide, royalty-free patent - license under Licensed Patents to make, use, sell, offer to sell, - import and otherwise transfer the Contribution of such Contributor, - if any, in source code and object code form. This patent license - shall apply to the combination of the Contribution and the Program - if, at the time the Contribution is added by the Contributor, such - addition of the Contribution causes such combination to be covered - by the Licensed Patents. The patent license shall not apply to any - other combinations which include the Contribution. No hardware per - se is licensed hereunder. - - c) Recipient understands that although each Contributor grants the - licenses to its Contributions set forth herein, no assurances are - provided by any Contributor that the Program does not infringe the - patent or other intellectual property rights of any other entity. - Each Contributor disclaims any liability to Recipient for claims - brought by any other entity based on infringement of intellectual - property rights or otherwise. As a condition to exercising the rights - and licenses granted hereunder, each Recipient hereby assumes sole - responsibility to secure any other intellectual property rights - needed, if any. For example, if a third party patent license - is required to allow Recipient to distribute the Program, it is - Recipient's responsibility to acquire that license before distributing - the Program. - - d) Each Contributor represents that to its knowledge it has sufficient - copyright rights in its Contribution, if any, to grant the copyright - license set forth in this Agreement. - -3. REQUIREMENTS - -A Contributor may choose to distribute the Program in object code form -under its own license agreement, provided that: - a) it complies with the terms and conditions of this Agreement; and - b) its license agreement: - i) effectively disclaims on behalf of all Contributors all - warranties and conditions, express and implied, including - warranties or conditions of title and non-infringement, and - implied warranties or conditions of merchantability and fitness - for a particular purpose; - ii) effectively excludes on behalf of all Contributors all - liability for damages, including direct, indirect, special, - incidental and consequential damages, such as lost profits; - iii) states that any provisions which differ from this Agreement - are offered by that Contributor alone and not by any other - party; and - iv) states that source code for the Program is available from - such Contributor, and informs licensees how to obtain it in a - reasonable manner on or through a medium customarily used for - software exchange. - -When the Program is made available in source code form: - a) it must be made available under this Agreement; and - b) a copy of this Agreement must be included with each copy of the - Program. - -Each Contributor must include the following in a conspicuous location -in the Program: - - Copyright (c) 1997,1998,1999, International Business Machines - Corporation and others. All Rights Reserved. - -In addition, each Contributor must identify itself as the originator of -its Contribution, if any, in a manner that reasonably allows subsequent -Recipients to identify the originator of the Contribution. - -4. COMMERCIAL DISTRIBUTION - -Commercial distributors of software may accept certain responsibilities -with respect to end users, business partners and the like. While this -license is intended to facilitate the commercial use of the Program, the -Contributor who includes the Program in a commercial product offering -should do so in a manner which does not create potential liability for -other Contributors. Therefore, if a Contributor includes the Program in -a commercial product offering, such Contributor ("Commercial Contributor") -hereby agrees to defend and indemnify every other Contributor -("Indemnified Contributor") against any losses, damages and costs -(collectively "Losses") arising from claims, lawsuits and other legal -actions brought by a third party against the Indemnified Contributor to -the extent caused by the acts or omissions of such Commercial Contributor -in connection with its distribution of the Program in a commercial -product offering. The obligations in this section do not apply to any -claims or Losses relating to any actual or alleged intellectual property -infringement. In order to qualify, an Indemnified Contributor must: - a) promptly notify the Commercial Contributor in writing of such claim, -and - b) allow the Commercial Contributor to control, and cooperate with - the Commercial Contributor in, the defense and any related - settlement negotiations. The Indemnified Contributor may - participate in any such claim at its own expense. - -For example, a Contributor might include the Program in a commercial -product offering, Product X. That Contributor is then a Commercial -Contributor. If that Commercial Contributor then makes performance -claims, or offers warranties related to Product X, those performance -claims and warranties are such Commercial Contributor's responsibility -alone. Under this section, the Commercial Contributor would have to -defend claims against the other Contributors related to those performance -claims and warranties, and if a court requires any other Contributor to -pay any damages as a result, the Commercial Contributor must pay those -damages. - -5. NO WARRANTY - -EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED -ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER -EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR -CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A -PARTICULAR PURPOSE. Each Recipient is solely responsible for determining -the appropriateness of using and distributing the Program and assumes -all risks associated with its exercise of rights under this Agreement, -including but not limited to the risks and costs of program errors, -compliance with applicable laws, damage to or loss of data, programs or -equipment, and unavailability or interruption of operations. - -6. DISCLAIMER OF LIABILITY - -EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR -ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, -INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING -WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF -LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING -NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION -OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF -ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - -7. GENERAL - -If any provision of this Agreement is invalid or unenforceable under -applicable law, it shall not affect the validity or enforceability of -the remainder of the terms of this Agreement, and without further action -by the parties hereto, such provision shall be reformed to the minimum -extent necessary to make such provision valid and enforceable. - -If Recipient institutes patent litigation against a Contributor with -respect to a patent applicable to software (including a cross-claim or -counterclaim in a lawsuit), then any patent licenses granted by that -Contributor to such Recipient under this Agreement shall terminate -as of the date such litigation is filed. In addition, If Recipient -institutes patent litigation against any entity (including a cross-claim -or counterclaim in a lawsuit) alleging that the Program itself (excluding -combinations of the Program with other software or hardware) infringes -such Recipient's patent(s), then such Recipient's rights granted under -Section 2(b) shall terminate as of the date such litigation is filed. - -All Recipient's rights under this Agreement shall terminate if it fails -to comply with any of the material terms or conditions of this Agreement -and does not cure such failure in a reasonable period of time after -becoming aware of such noncompliance. If all Recipient's rights under -this Agreement terminate, Recipient agrees to cease use and distribution -of the Program as soon as reasonably practicable. However, Recipient's -obligations under this Agreement and any licenses granted by Recipient -relating to the Program shall continue and survive. - -IBM may publish new versions (including revisions) of this Agreement -from time to time. Each new version of the Agreement will be given a -distinguishing version number. The Program (including Contributions) -may always be distributed subject to the version of the Agreement under -which it was received. In addition, after a new version of the Agreement -is published, Contributor may elect to distribute the Program (including -its Contributions) under the new version. No one other than IBM has the -right to modify this Agreement. Except as expressly stated in Sections -2(a) and 2(b) above, Recipient receives no rights or licenses to the -intellectual property of any Contributor under this Agreement, whether -expressly, by implication, estoppel or otherwise. All rights in the -Program not expressly granted under this Agreement are reserved. - -This Agreement is governed by the laws of the State of New York and the -intellectual property laws of the United States of America. No party to -this Agreement will bring a legal action under this Agreement more than -one year after the cause of action arose. Each party waives its rights -to a jury trial in any resulting litigation. diff --git a/postfix/conf/LICENSE b/postfix/conf/LICENSE new file mode 120000 index 000000000..ea5b60640 --- /dev/null +++ b/postfix/conf/LICENSE @@ -0,0 +1 @@ +../LICENSE \ No newline at end of file diff --git a/postfix/conf/transport b/postfix/conf/transport index c5c6cf8c6..73c15dbce 100644 --- a/postfix/conf/transport +++ b/postfix/conf/transport @@ -115,150 +115,98 @@ # A null transport field with non-null nexthop field does # not modify the transport information. # -# DEFAULT DELIVERY METHOD -# When the recipient address or domain does not match a -# transport table entry, Postfix uses one of the following -# delivery methods, with the recipient domain as the default -# nexthop. -# -# o The recipient domain matches $mydestination or -# $inet_interfaces. The transport and optional nex- -# thop are specified with $local_transport. -# -# o The recipient domain matches $virtual_mail- -# box_domains. The transport and optional nexthop -# are specified with $virtual_transport. -# -# o The recipient domain matches $relay_domains. The -# transport and optional nexthop are specified with -# $relay_transport. This overrides the nexthop infor- -# mation that is specified with $relayhost. -# -# o All other destinations. the transport and optional -# nexthop are specified with $relay_transport. This -# overrides the nexthop information that is specified -# with $relayhost. -# # EXAMPLES -# In order to deliver internal mail directly, while using a -# mail relay for all other mail, specify a null entry for -# internal destinations (do not change the delivery trans- -# port or the nexthop information) and specify a wildcard +# In order to deliver internal mail directly, while using a +# mail relay for all other mail, specify a null entry for +# internal destinations (do not change the delivery trans- +# port or the nexthop information) and specify a wildcard # for all other destinations. # # my.domain : # .my.domain : # * smtp:outbound-relay.my.domain # -# In order to send mail for foo.org and its subdomains via +# 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 +# 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: # # When no transport is specified, Postfix uses the transport # that matches the address domain class (see TRANSPORT FIELD -# discussion above). The following sends all mail for +# discussion above). 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 +# 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 host- +# In the case of delivery via SMTP, one may specify host- # name: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 hostname in order to disable +# 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 hostname in order to disable # MX lookups. # # The error mailer can be used to bounce mail: # -# .foo.org error:mail for *.foo.org is not deliv- +# .foo.org error:mail for *.foo.org is not deliv- # erable # -# This causes all mail for user@anything.foo.org to be +# This causes all mail for user@anything.foo.org to be # bounced. # # REGULAR EXPRESSION TABLES -# This section describes how the table lookups change when +# This section describes how the table lookups change when # the table is given in the form of regular expressions. For -# a description of regular expression lookup table syntax, +# a description of regular expression lookup table syntax, # see regexp_table(5) or pcre_table(5). # -# Each pattern is a regular expression that is applied to +# Each pattern is a regular expression that is applied to # the entire domain being looked up. Thus, some.domain.hier- # archy is not broken up into parent domains. # -# Patterns are applied in the order as specified in the -# table, until a pattern is found that matches the search +# Patterns are applied in the order as specified in the +# table, until a pattern is found that matches the search # string. # -# Results are the same as with indexed file lookups, with -# the additional feature that parenthesized substrings from +# Results are the same as with indexed file lookups, with +# the additional feature that parenthesized substrings from # the pattern can be interpolated as $1, $2 and so on. # # 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 +# 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. # # empty_address_recipient -# The address that is looked up instead of the null +# The address that is looked up instead of the null # sender address. # # parent_domain_matches_subdomains -# List of Postfix features that use domain.tld pat- -# terns to match sub.domain.tld (as opposed to +# List of Postfix features that use domain.tld pat- +# terns to match sub.domain.tld (as opposed to # requiring .domain.tld patterns). # # transport_maps # List of transport lookup tables. # -# Other parameters of interest: -# -# local_transport -# The default mail delivery transport when the desti- -# nation matches $mydestination or $inet_interfaces. -# -# virtual_transport -# The default mail delivery transport when the desti- -# nation matches $virtual_mailbox_domains. -# -# relay_transport -# The default mail delivery transport when the desti- -# nation matches $relay_domains. -# -# default_transport -# The default mail delivery transport when the desti- -# nation does not match a local, virtual or relay -# destination. -# -# mydestination -# The destinations that are given to $local_transport -# by default. -# -# relayhost -# The default host for destinations that do not match -# $mydestination, $inet_interfaces, $vir- -# tual_alias_domains or $virtual_mailbox_domains. -# # SEE ALSO # postmap(1) create mapping table # trivial-rewrite(8) rewrite and resolve addresses diff --git a/postfix/html/cleanup.8.html b/postfix/html/cleanup.8.html index 8efac446b..0e793b6a2 100644 --- a/postfix/html/cleanup.8.html +++ b/postfix/html/cleanup.8.html @@ -125,7 +125,7 @@ CLEANUP(8) CLEANUP(8) Reject mail with 8-bit text in content that claims to be 7-bit, or in content that has no explicit content encoding information. This blocks mail - mail poorly written mail software. Unfortunately, + from poorly written mail software. Unfortunately, this also breaks majordomo approval requests when the included request contains valid 8-bit MIME mail, and it breaks bounces from mailers that do diff --git a/postfix/html/error.8.html b/postfix/html/error.8.html index 308870567..d7563c434 100644 --- a/postfix/html/error.8.html +++ b/postfix/html/error.8.html @@ -52,7 +52,7 @@ ERROR(8) ERROR(8) notify_classes When this parameter includes the bounce class, send - mail to the postmaster with with the headers of the + mail to the postmaster with the headers of the bounced mail. SEE ALSO diff --git a/postfix/html/faq.html b/postfix/html/faq.html index 68accfa7b..f51db1c27 100644 --- a/postfix/html/faq.html +++ b/postfix/html/faq.html @@ -22,12 +22,12 @@