postfix-2.0.0-20030101

postfix/HISTORY

@@ -7622,8 +7622,18 @@ Apologies for any names omitted.
 	virtual alias class (error:User unknown) result.  File:
 	trivial-rewrite/transport.c.
 
+20030101
+
+	Documentation update: new-style virtual domains broke the
+	advanced content filtering example. Files: FILTER_README,
+	RELEASE_NOTES-2.0.
+
 Open problems:
 
+	Med: do not postpone rejected "MAIL FROM" size information,
+	and find a way to log the sender address in the rejected
+	command.
+
 	Low: after successful delivery, per-queue window += 1/window,
 	after failure, queue window -= 1 (Victor).
 

postfix/README_FILES/ADDRESS_VERIFICATION_README

@@ -1,5 +1,5 @@
-Sender address verification
+Address verification
-===========================
+====================
 
 Sender address verification blocks mail from an unknown sender
 address until after the address is verified.  An address is verified
@@ -7,15 +7,36 @@ by probing the nearest MTA for that address, without actually
 delivering mail to it (SMTP interruptus). Probe messages are like
 normail mail, but are discarded instead of being deferred or bounced.
 
-Normal mail will suffer only a short one-time delay of up to 9
+The same technique may be useful to block mail for undeliverable
-seconds while address verification happens for the first time.
+recipients, for example on mail relay hosts that do not have a copy
-When verification takes longer than 9 seconds, the Postfix SMTP
+of all the relayed recipient addresses.
-server defers the message with a 450 reply. Normal mail clients
-will connect again after some delay.  Once an address status is
-known, the status is cached and Postfix replies immediately.
 
-Address verification is turned on with the "reject_unverified_sender"
+With address verification turned on, normal mail will suffer only
-sender restriction.  To find out how this would affect your mail,
+a short delay of up to 9 seconds while an address is verified for
+the first time.  Once an address status is known, the status is
+cached and Postfix replies immediately.  When verification takes
+longer than 9 seconds the Postfix SMTP server defers the sender or
+recipient address message with a 450 reply. Normal mail clients
+will connect again after some delay.
+
+Sender and recipient address verification are turned on with the
+"reject_unverified_sender" and "reject_unverified_recipient"
+restrictions, respectively.
+
+Recipient address verification is relatively straightforward and
+there are no surprises. If a recipient probe fails, then Postfix
+rejects mail for the recipient address.  If a recipient probe
+succeeds, then Postfix accepts mail for the recipient address.
+
+Turning on sender address verification
+======================================
+
+Unfortunately, sender address verification cannot simply be turned
+on - you are likely to lose legitimate mail from mis-configured
+systems. You will almost certainly have to set up white lists for
+specific addresses or even for entire domains.
+
+To find out how sender address verification would affect your mail,
 specify "warn_if_reject reject_unverified_sender" so that you can
 see what mail would be blocked:
 

postfix/README_FILES/FILTER_README

@@ -1,8 +1,22 @@
+Introduction
+============
+
 This is a very first implementation of Postfix content filtering.
 A Postfix content filter receives unfiltered mail from Postfix and
-either bounces the mail or re-injects filtered mail back into Postfix.
+does one of the following:
 
-This document describes two approaches to content filtering.
+- re-injects the mail back into Postfix, perhaps after changing content
+- rejects the mail (by sending a suitable status code back to
+  Postfix) so that it is returned to sender.
+- sends the mail somewhere else
+
+This document describes two approaches to content filtering: simple
+and advanced. Both filter all the mail by default.
+
+At the end are examples that show how to filter only mail from
+users, about using different filters for different domains that
+you provide MX service for, and about selective filtering on the 
+basis of message envelope and/or header/body patterns.
 
 Simple content filtering example
 ================================
@@ -10,6 +24,7 @@ Simple content filtering example
 The first example is simple to set up.  It uses a shell script that
 receives unfiltered mail from the Postfix pipe delivery agent, and
 that feeds filtered mail back into the Postfix sendmail command.
+
 Only mail arriving via SMTP will be content filtered.
 
                   ..................................
@@ -24,7 +39,8 @@ Unfiltered mail----->smtpd \                /local---->Filtered mail
                |                                      |
                +-Postfix sendmail<----filter script<--+
 
-The /some/where/filter program can be a simple shell script like this:
+Mail is filtered by a /some/where/filter program. This can be a
+simple shell script like this:
 
     #!/bin/sh
 
@@ -51,18 +67,24 @@ The /some/where/filter program can be a simple shell script like this:
     exit $?
 
 The idea is to first capture the message to file and then run the
-content through a third-party content filter program.  If the
+content through a third-party content filter program.
-mail cannot be captured to file, mail delivery is deferred by
-terminating with exit status 75 (EX_TEMPFAIL).  If the content
-filter program finds a problem, the mail is bounced by terminating
-the shell script with exit status 69 (EX_UNAVAILABLE).  If the
-content is OK, it is given as input to Postfix sendmail, and the
-exit status of the filter command is whatever exit status Postfix
-sendmail produces.
 
-I suggest that you play with this script for a while until you are
+- If the mail cannot be captured to file, mail delivery is deferred
-satisfied with the results. Run it with a real message (headers+body)
+  by terminating with exit status 75 (EX_TEMPFAIL). Postfix will
-as input:
+  try again after some delay.
+
+- If the content filter program finds a problem, the mail is bounced
+  by terminating with exit status 69 (EX_UNAVAILABLE).  Postfix
+  will return the message to the sender as undeliverable.
+
+- If the content is OK, it is given as input to the Postfix sendmail
+  command, and the exit status of the filter command is whatever
+  exit status the Postfix sendmail command produces. Postfix will
+  deliver the message as usual.
+
+I suggest that you run this script by hand until you are satisfied
+with the results. Run it with a real message (headers+body) as
+input:
 
     % /some/where/filter -f sender recipient... <message-file
 
@@ -86,20 +108,20 @@ Once you're satisfied with the content filtering script:
         flags=Rq user=filter argv=/somewhere/filter -f ${sender} -- ${recipient}
 
 To turn on content filtering for mail arriving via SMTP only, append
-"-o content_filter=filter:" to the master.cf entry that defines
+"-o content_filter=filter:dummy" to the master.cf entry that defines
 the Postfix SMTP server:
 
     /etc/postfix/master.cf:
-	smtp      inet     ...stuff...      smtpd
+        smtp      inet     ...stuff...      smtpd
-	    -o content_filter=filter:
+            -o content_filter=filter:dummy
 
-Note the ":" at the end!!  The content_filter configuration parameter
+The content_filter configuration parameter accepts the same syntax
-accepts the same syntax as the right-hand side in a Postfix transport
+as the right-hand side in a Postfix transport table.  Execute
-table. Execute "postfix reload" to complete the change.
+"postfix reload" to complete the change.
 
 To turn off content filtering, edit the master.cf file, remove the
-"-o content_filter=filter:" text from the entry that defines the
+"-o content_filter=filter:dummy" text from the entry that defines
-Postfix SMTP server, and execute another "postfix reload".
+the Postfix SMTP server, and execute another "postfix reload".
 
 With the shell script as shown above you will lose a factor of four
 in Postfix performance for transit mail that arrives and leaves
@@ -113,21 +135,32 @@ Simple content filter limitations
 =================================
 
 The problem with content filters like the one above is that they
-are not very robust, because the software does not talk a well-defined
+are not very robust. The reason is that the software does not talk
-protocol with Postfix. If the filter shell script aborts because
+a well-defined protocol with Postfix. If the filter shell script
-the shell runs into some memory allocation problem, the script will
+aborts because the shell runs into some memory allocation problem,
-not produce a nice exit status as per /usr/include/sysexits.h and
+the script will not produce a nice exit status as defined in the
-mail will probably bounce. The same lack of robustness is possible
+file /usr/include/sysexits.h.  Instead of going to the deferred
+queue, mail will bounce.  The same lack of robustness can happen
 when the content filtering software itself runs into a resource
 problem.
 
 Advanced content filtering example
 ===================================
 
-The second example is considerably more complex, but can give much
+The second example is more complex, but can give much better
-better performance, and is less likely to bounce mail when the
+performance, and is less likely to bounce mail when the machine
-machine runs into a resource problem.  This approach uses content
+runs into a resource problem.  This approach uses content filtering
-filtering software that can receive and deliver mail via SMTP.
+software that can receive and deliver mail via SMTP.
+
+Some Anti-virus software is built to receive and deliver mail via
+SMTP and is ready to use as an advanced Postfix content filter.
+For non-SMTP capable content filtering software, Bennett Todd's
+SMTP proxy implements a nice PERL/SMTP content filtering framework.
+See: http://bent.latency.net/smtpprox/
+
+The example given here filters all mail, including mail that arrives
+via SMTP and mail that is locally submitted via the Postfix sendmail
+command.
 
 You can expect to lose about a factor of two in Postfix performance
 for transit mail that arrives and leaves via SMTP, provided that
@@ -160,7 +193,7 @@ To enable content filtering in this manner, specify in main.cf a
 new parameter:
 
     /etc/postfix/main.cf:
-	content_filter = scan:localhost:10025
+        content_filter = scan:localhost:10025
 
 This causes Postfix to add one extra content filtering record to
 each incoming mail message, with content scan:localhost:10025.
@@ -177,23 +210,19 @@ one would set up the service in the Postfix master.cf file:
 
     /etc/postfix/master.cf:
         scan      unix  -       -       n       -       10       smtp
-	    -o disable_dns_lookups=yes
 
-Turning off DNS lookups at this point can make a great difference
+Instead of a limit of 10 concurrent processes, use whatever process
-in content filtering performance. It also isolates the content
+limit is feasible for your machine.  Content inspection software
-filtering process from temporary outages in DNS service.
+can gobble up a lot of system resources, so you don't want to have
-
+too much of it running at the same time.
-Instead of 10, use whatever limit is feasible for your machine.
-Content inspection software can gobble up a lot of system resources,
-so you don't want to have too much of it running at the same time.
 
 The content filter can be set up with the Postfix spawn service,
 which is the Postfix equivalent of inetd. For example, to instantiate
 up to 10 content filtering processes on demand:
 
     /etc/postfix/master.cf:
-	localhost:10025     inet  n      n      n      -      10     spawn
+        localhost:10025     inet  n      n      n      -      10     spawn
-	    user=filter argv=/some/where/filter localhost 10026
+            user=filter argv=/some/where/filter localhost 10026
 
 "filter" is a dedicated local user account.  The user will never
 log in, and can be given a "*" password and non-existent shell and
@@ -206,15 +235,14 @@ instead of Postfix, then you must run your filter as a stand-alone
 program.
 
 Note: the localhost port 10025 SMTP server filter should announce
-itself as "220 localhost...", to silence warnings in the log.
+itself as "220 localhost...".  Postfix aborts delivery when it
+connects to an SMTP server that uses the same hostname, because
+that normally means you have a mail delivery loop problem.
 
-The /some/where/filter command is most likely a PERL script. PERL
+The example here assumes that the /some/where/filter command is a
-has modules that make talking SMTP easy. The command-line specifies
+PERL script. PERL has modules that make talking SMTP easy. The
-that mail should be sent back into Postfix via localhost port 10026.
+command-line specifies that mail should be sent back into Postfix
-
+via localhost port 10026.
-For now, it is left up to the Postfix users to come up with a
-PERL/SMTP framework for Postfix content filtering. If done well,
-it can be used with other mailers too, which is a nice spin-off.
 
 The simplest content filter just copies SMTP commands and data
 between its inputs and outputs. If it has a problem, all it has to
@@ -228,26 +256,33 @@ a dedicated listener on port localhost 10026:
 
     /etc/postfix/master.cf:
         localhost:10026     inet  n      -      n      -      10      smtpd
-	    -o content_filter= 
+            -o content_filter= 
-	    -o local_recipient_maps=
+            -o local_recipient_maps=
-	    -o myhostname=localhost.domain.tld
+            -o relay_recipient_maps=
-	    -o smtpd_helo_restrictions=
+            -o myhostname=localhost.domain.tld
-	    -o smtpd_client_restrictions=
+            -o smtpd_helo_restrictions=
-	    -o smtpd_sender_restrictions=
+            -o smtpd_client_restrictions=
-	    -o smtpd_recipient_restrictions=permit_mynetworks,reject
+            -o smtpd_sender_restrictions=
-	    -o mynetworks=127.0.0.0/8
+            -o smtpd_recipient_restrictions=permit_mynetworks,reject
+            -o mynetworks=127.0.0.0/8
 
-This is just another SMTP server. The "-o content_filter=" requests
+Warning for Postfix version 2 users: in this SMTP server after the
-no content filtering for incoming mail. The server has the same
+content filter, do not override main.cf settings for virtual_alias_maps
-process limit as the "filter" master.cf entry.
+or virtual_alias_domains. That would cause mail to be rejected with
+"User unknown".
 
-The "-o local_recipient_maps=" is a safety in case you have specified
+This SMTP server has the same process limit as the "filter" master.cf
-local_recipient_maps in the main.cf file. That could interfere with
+entry.
-content filtering. 
+
+The "-o content_filter=" requests no content filtering for incoming
+mail.
+
+The "-o local_recipient_maps=" and "-o relay_recipient_maps=" avoid
+unnecessary table lookups.
 
 The "-o myhostname=localhost.domain.tld" avoids a possible problem
-if the content filter is picky about the hostname that Postfix
+if your content filter is based on a proxy that simply relays SMTP
-sends in SMTP server replies.
+commands.
 
 The "-o smtpd_xxx_restrictions" and "-o mynetworks=127.0.0.0/8"
 turn off UCE controls that would only waste time here.
@@ -257,7 +292,7 @@ Squeezing out more performance
 
 Many refinements are possible, such as running a specially-configured
 smtp delivery agent for feeding mail into the content filter, and
-turning off address rewriting before or after content filtering.
+turning off address rewriting before content filtering.
 
 As the example below shows, things quickly become very complex,
 because a lot of main.cf like information gets listed in the
@@ -266,7 +301,8 @@ master.cf file. This makes the system hard to understand.
 If you need to squeeze out more performance, it is probably simpler
 to run multiple Postfix instances, one before and one after the
 content filter. That way, each instance can have simple main.cf
-and master.cf files, and the system will be easier to understand.
+and master.cf files, each instance can have its own mail queue,
+and the system will be easier to understand.
 
 As before, we will set up a content filtering program that receives
 SMTP mail via localhost port 10025, and that submits SMTP mail back
@@ -303,59 +339,53 @@ new parameter:
 #
 smtp                inet  n      -      n      -       -      smtpd
 #
+# ------------------------------------------------------------------
+#
 # This is the cleanup daemon that handles messages in front of
-# the content filter, it does header_checks and body_checks (if
+# the content filter. It does header_checks and body_checks (if
-# any), but does not do any address rewriting.
+# any), but does no virtual alias or canonical address mapping.
 #
-# The address rewriting happens in the second cleanup phase after
+# Virtual alias or canonical address mapping happens in the second
-# the content filter. This gives the content_filter access to
+# cleanup phase after the content filter. This gives the content_filter
-# *largely* unmodified addresses for maximum flexibility.
+# access to *largely* unmodified addresses for maximum flexibility.
 #
-# The trivial-rewrite daemon handles the logic of append_myorigin
+# Turning off append_myorigin/append_dot_mydomain address rewriting
-# and append_dot_mydomain, turning these off requires two
+# before the content filter would require two instances of the
-# trivial-rewrite services, by which point (if you are not
+# trivial-rewrite daemon. If you want to go to this trouble then
-# already) you are much better off with two complete Postfix
+# you're clearly better off with two complete Postfix instances: one
-# instances one in front of and one behind the content filter.
+# in front of and one behind the content filter.
 #
 # Note that some sites may specifically want to do the opposite:
 # perform rewrites in front of the content_filter which would
-# then see only cleaned up addresses, in this case the parameter
+# then see only cleaned up addresses. In that case the "-o" parameter
-# settings below should be moved to the second "cleanup"
+# settings below should be moved to the second "cleanup" instance.
-# instance.
 #
 cleanup             unix  n      -      n      -       0      cleanup
-	-o canonical_maps=
+        -o canonical_maps=
-	-o sender_canonical_maps=
+        -o sender_canonical_maps=
-	-o recipient_canonical_maps=
+        -o recipient_canonical_maps=
-	-o masquerade_domains=
+        -o masquerade_domains=
-	-o virtual_maps=
+        -o virtual_alias_maps=
+#
+# ------------------------------------------------------------------
 #
 # This is the delivery agent that injects mail into the content
-# filter.  It is tuned for low latency and low concurrency, most
+# filter.  It is tuned for low concurrency, because most content
-# content filters burn CPU and high concurrency causes thrashing.
+# filters burn CPU and use lots of memory.  The process limit of 10
-# The process limit of 10 reenforces the effect of
+# re-enforces the effect of $default_destination_concurrency_limit.
-# $default_destination_concurrency_limit, even without an
+# Even without an explicit process limit, the concurrency is bounded
-# explicit process limit, the concurrency is bounded because all
+# because all messages heading into the content filter have the same
-# messages heading into the content filter have the same
+# destination.
-# destination. The "disable_dns_lookups" setting prevents the
-# delivery agent from consuming precious "bandwidth" in the
-# narrow deliver channel waiting for slow DNS responses. It also
-# ensures that the original envelope recipient is seen by the
-# content filter.
 #
 scan                unix  -      -      n      -      10      smtp
-    -o disable_dns_lookups=yes
+#
+# ------------------------------------------------------------------
 #
 # This is the SMTP listener that receives filtered messages from
 # the content filter. It *MUST* clear the content_filter
 # parameter to avoid loops, and use a different hostname to avoid
 # triggering the Postfix SMTP loop detection code.
 #
-#
-# Since all recipients have been validated by the first "smtpd",
-# clear local_recipient_maps, virtual_maps and
-# virtual_mailbox_maps.
-#
 # This "smtpd" uses a separate cleanup that does no header or
 # body checks, but does do the various address rewrites disabled
 # in the first cleanup.
@@ -370,8 +400,7 @@ localhost:10026     inet  n      -      n      -       -      smtpd
     -o content_filter= 
     -o myhostname=localhost.domain.tld
     -o local_recipient_maps=
-    -o virtual_maps=
+    -o relay_recipient_maps=
-    -o virtual_mailbox_maps=
     -o cleanup_service_name=cleanup2 
     -o mynetworks=127.0.0.0/8
     -o mynetworks_style=host
@@ -381,9 +410,22 @@ localhost:10026     inet  n      -      n      -       -      smtpd
     -o smtpd_sender_restrictions=
     -o smtpd_recipient_restrictions=permit_mynetworks,reject
 #
-# This is the second cleanup daemon. No header or body checks.
+# Do not override main.cf settings here for virtual_alias_maps or
-# If preferable, enable rewrites in the first cleanup daemon, and
+# virtual_mailbox_maps. This causes mail to be rejected with "User
-# disable them here.
+# unknown in virtual (alias|mailbox) recipient table".
+#
+# ------------------------------------------------------------------
+#
+# This is the second cleanup daemon. No header or body checks,
+# because those have already been taken care of by the cleanup instance
+# before the content filter.  The second cleanup instance does all the
+# virtual alias and canonical address mapping that was disabled in
+# the first cleanup instance.
+#
+# If it is preferable to do the virtual alias and canonical address
+# mapping before the content filter, delete the "-o" lines that
+# disable canonical and virtual mappings in the above cleanup daemon
+# instance and insert them here.
 #
 cleanup2            unix  n      -      n      -       0      cleanup
     -o header_checks=
@@ -391,14 +433,14 @@ cleanup2            unix  n      -      n      -       0      cleanup
     -o nested_header_checks=
     -o body_checks=
 #
+# ------------------------------------------------------------------
+#
 # The normal "smtp" delivery agent for contrast with "scan".
-# Definitely do not set "disable_dns_lookups = yes" here if you
-# send mail to the Internet.
 #
 smtp                unix  -      -      n      -      -       smtp
 
-This causes Postfix to add one extra content filtering record to
+The above example causes Postfix to add one content filtering record
-each incoming mail message, with content scan:localhost:10025.
+to each incoming mail message, with content scan:localhost:10025.
 You can use the same syntax as in the right-hand side of a Postfix
 transport table.  The content filtering records are added by the
 smtpd and pickup servers.
@@ -412,3 +454,82 @@ low concurrency, throughput dependent on predictably low latency).
 See the previous example for setting up the content filter with
 the Postfix spawn service; you can of course use any server that
 can be run stand-alone outside the Postfix environment.
+
+Filtering mail from outside users only
+======================================
+
+The easiest approach is to configure ONE Postfix instance with TWO
+SMTP server addresses in master.cf:
+
+- One SMTP server address for inside users only that never invokes
+  content filtering.
+
+- One SMTP server address for outside users that always invokes
+  content filtering.
+
+/etc/postfix.master.cf:
+    # SMTP service for internal users only, no content filtering.
+    1.2.3.4:smtp        inet  n       -       n       -       -       smtpd
+        -o smtpd_client_restrictions=permit_mynetworks,reject
+    127.0.0.1:smtp      inet  n       -       n       -       -       smtpd
+        -o smtpd_client_restrictions=permit_mynetworks,reject
+
+    # SMTP service for external users, with content filtering.
+    1.2.3.5:smtp        inet  n       -       n       -       -       smtpd
+        -o content_filter=foo:bar
+
+Different content filters for different MX domains
+==================================================
+
+This is a variant on the previous example. You configure ONE
+Postfix instance with multiple SMTP server addresses. Each
+SMTP server invokes a different content filter.
+
+/etc/postfix.master.cf:
+    # MX server for destinations that use the foo:bar content filter.
+    1.2.3.5:smtp        inet  n       -       n       -       -       smtpd
+        -o content_filter=foo:bar 
+	-o relay_domains=/etc/postfix/foo-bar-domains
+        -o smtpd_recipient_restrictions=reject_unauth_destination
+
+    # MX server for destinations that use the bar:baz content filter.
+    1.2.3.6:smtp        inet  n       -       n       -       -       smtpd
+        -o content_filter=bar:baz 
+	-o relay_domains=/etc/postfix/bar-baz-domains
+        -o smtpd_recipient_restrictions=reject_unauth_destination
+
+    # SMTP servers for internal users only.
+    1.2.3.4:smtp        inet  n       -       n       -       -       smtpd
+        -o smtpd_recipient_restrictions=permit_mynetworks,reject
+    127.0.0.1:smtp      inet  n       -       n       -       -       smtpd
+        -o smtpd_recipient_restrictions=permit_mynetworks,reject
+
+Getting really nasty
+====================
+
+The above filtering configurations are static. Mail that follows
+a given path is either always filtered or it is never filtered. As
+of Postfix 2.0 you can also turn on content filtering on the fly.
+The Postfix UCE features allow you to specify a filtering action
+on the fly:
+
+    FILTER foo:bar
+
+You can do this in smtpd access maps as well as the cleanup server's
+header/body_checks.  This feature must be used with great care:
+you must disable all the UCE features in the after-filter smtpd
+and cleanup daemons or else you will have a content filtering loop.
+
+Limitations:
+
+- There can be only one content filter action per message.
+
+- FILTER actions from smtpd access maps and header/body_checks take
+  precedence over filters specified with the main.cf content_filter 
+  parameter.
+
+- Only the last FILTER action from smtpd access maps or in
+  header/body_checks takes effect.
+
+- The same content filter is applied to all the recipients of a
+  given message.

postfix/README_FILES/LOCAL_RECIPIENT_README

@@ -105,7 +105,7 @@ following is true:
     You need to add the database that lists the non-UNIX users:
 
 	/etc/postfix/main.cf
-	    local_recipient_maps = unix_passwd.byname, $alias_maps,
+	    local_recipient_maps = unix:passwd.byname, $alias_maps,
 		<the database with non-UNIX accounts>
 
     Your database will be searched for the user@domain address as

postfix/RELEASE_NOTES-2.0

@@ -1,9 +1,13 @@
+==============================================================
 NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE
+==============================================================
 Before upgrading from Postfix 1.1 you must stop Postfix ("postfix
 stop").  Some internal protocols have changed.  No mail will be
 lost if you fail to stop and restart Postfix, but Postfix won't be
 able to receive any new mail, either.
+==============================================================
 NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE
+==============================================================
 
 In the text below, changes are labeled with the Postfix snapshot
 that introduced the change, and whether the change introduced a
@@ -82,6 +86,14 @@ is now used for address lookups only.
 
 For details, see the VIRTUAL_README file.
 
+[Incompat 20021209] If you use the "advanced content filter"
+technique, you MUST NOT override the virtual aliases and virtual
+mailbox settings in the SMTP server that receives mail from the
+content filter, or else mail for virtual recipients will be rejected
+with "User unknown".
+
+For details, see the FILTER_README file.
+
 Incompatible queue file format changes
 ======================================
 
@@ -265,7 +277,7 @@ TCP/IP stacks have an atrociously large default timeout value.
 [Feature 20020505] Finer control over Berkeley DB memory usage,
 The parameter "berkeley_db_create_buffer_size" (default:  16 MBytes)
 specifies the buffer size for the postmap and postalias commands.
-The parameter "berkeley_db_read_buffer_size" (default:  256 kBytes)
+The parameter "berkeley_db_read_buffer_size" (default:  128 kBytes)
 specifies the buffer size for all other applications.  Specify
 "berkeley_db_read_buffer_size = 1048576" to get the old read buffer
 size. Contributed by Victor Duchovni. For more information, see
@@ -696,6 +708,11 @@ Assorted changes
 the original recipient address in the X-Original-To: message header.
 This header can also be emitted by the pipe(8) delivery agent.
 
+[Incompat 20021028] With "domain in one mailbox", one message with
+multiple recipients is no longer delivered only once. It is now
+delivered as one copy for each original recipient, with the original
+recipient address listed in the X-Original-To: message header.
+
 [Feature 20021024] New proxy_interfaces parameter, for sites behind a
 network address translation gateway or other type of proxy. You
 should specify all the proxy network addresses here, to avoid avoid

postfix/conf/postfix-files

@@ -174,6 +174,7 @@ $sample_directory/sample-transport.cf:f:root:-:644
 $sample_directory/sample-verify.cf:f:root:-:644
 $sample_directory/sample-virtual.cf:f:root:-:644
 $readme_directory/ADDRESS_CLASS_README:f:root:-:644
+$readme_directory/ADDRESS_VERIFICATION_README:f:root:-:644
 $readme_directory/DB_README:f:root:-:644
 $readme_directory/DEBUG_README:f:root:-:644
 $readme_directory/ETRN_README:f:root:-:644

postfix/examples/chroot-setup/Solaris2

@@ -25,7 +25,7 @@ fi
 for dir in etc/default etc/inet dev usr/lib usr/share/lib/zoneinfo ; do
   if [ ! -d ${CHROOT}/${dir} ]; then mkdir -p ${CHROOT}/${dir} ; fi
 done
-chmod -R 755 ${CHROOT}
+#chmod -R 755 ${CHROOT}
 
 # AFS support.
 if [ "`echo $CHROOT | cut -c1-4`" = "/afs" ]; then

postfix/html/faq.html

@@ -2015,7 +2015,7 @@ systems for performance and/or security reasons.
 
 <p>
 
-The Postfix warning message means that new mail notificiation failed
+The Postfix warning message means that new mail notification failed
 because the <b>comsat</b> network service is turned off.
 
 <p>
@@ -2034,7 +2034,7 @@ specify:
 
 Note: recent versions of <b>procmail</b> also produce <b>biff</b>
 notifications. To silence <b>biff</b> completely you may also have
-to updte <b>procmail</b> configuration files.
+to update <b>procmail</b> configuration files.
 
 <p>
 
@@ -2317,7 +2317,7 @@ is unable to access the UNIX password database.
 
 <li> If you're running the Postfix SMTP server chrooted (see
 <b>master.cf</b>) then you may have to copy the password file and
-perhaps a bunch of other files into Postfix queue directory; a
+perhaps a bunch of other files into the Postfix queue directory; a
 typical destination would be <b>/var/spool/postfix/etc</b>. See also
 the chroot setup scripts in the <b>examples</b> directory of the
 Postfix source code distribution.
@@ -2638,19 +2638,19 @@ destinations don't work in virtual domains</h3>
 
 <p>
 
-Quick answer: set up a transport map entry that gives the mail to
+Quick answer: set up "punch through" virtual aliases that redirect
-the Postfix local delivery agent:
+the mail to local Postfix aliases:
 
 <p>
 
 <pre>
     /etc/postfix/main.cf:
-        transport_maps = hash:/etc/postfix/transport
+        virtual_alias_maps = hash:/etc/postfix/virtual
 
-    /etc/postfix/transport:
+    /etc/postfix/virtual:
-        listname@virtual.tld            local:
+        listname@virtual.tld            listname
-        owner-listname@virtual.tld      local:
+        owner-listname@virtual.tld      owner-listname
-        listname-request@virtual.tld    local:
+        listname-request@virtual.tld    listname-request
 
     /etc/aliases:
         listname: "|whatever"
@@ -2660,6 +2660,13 @@ the Postfix local delivery agent:
 
 <p>
 
+This redirects mail for virtual address <i>listname@virtual.tld</i>
+etc. to local address <i>listname@your.domain.tld</i> etc.. Mail
+for these local aliases is then delivered to external commands or
+files etc. by the Postfix local delivery agent.
+
+<p>
+
 Long answer:
 
 <p>

postfix/src/global/mail_version.h

@@ -20,7 +20,7 @@
   * Patches change the patchlevel and the release date. Snapshots change the
   * release date only, unless they include the same bugfix as a patch release.
   */
-#define MAIL_RELEASE_DATE	"20021223"
+#define MAIL_RELEASE_DATE	"20030101"
 
 #define VAR_MAIL_VERSION	"mail_version"
 #define DEF_MAIL_VERSION	"2.0.0-" MAIL_RELEASE_DATE

postfix/src/trivial-rewrite/resolve.c

@@ -400,12 +400,18 @@ void    resolve_addr(char *addr, VSTRING *channel, VSTRING *nexthop,
 	 */
 	if (virt_alias_doms
 	    && string_list_match(virt_alias_doms, rcpt_domain)) {
-	    if (var_helpful_warnings
+	    if (var_helpful_warnings) {
-		&& virt_mailbox_doms
+		if (virt_mailbox_doms
-		&& string_list_match(virt_mailbox_doms, rcpt_domain))
+		    && string_list_match(virt_mailbox_doms, rcpt_domain))
-		msg_warn("do not list domain %s in BOTH %s and %s",
+		    msg_warn("do not list domain %s in BOTH %s and %s",
-			 rcpt_domain, VAR_VIRT_ALIAS_DOMS,
+			     rcpt_domain, VAR_VIRT_ALIAS_DOMS,
-			 VAR_VIRT_MAILBOX_DOMS);
+			     VAR_VIRT_MAILBOX_DOMS);
+		if (relay_domains
+		    && domain_list_match(relay_domains, rcpt_domain))
+		    msg_warn("do not list domain %s in BOTH %s and %s",
+			     rcpt_domain, VAR_VIRT_ALIAS_DOMS,
+			     VAR_RELAY_DOMAINS);
+	    }
 	    vstring_strcpy(channel, MAIL_SERVICE_ERROR);
 	    vstring_sprintf(nexthop, "User unknown%s",
 			    var_show_unk_rcpt_table ?
@@ -422,6 +428,13 @@ void    resolve_addr(char *addr, VSTRING *channel, VSTRING *nexthop,
 	 */
 	else if (virt_mailbox_doms
 		 && string_list_match(virt_mailbox_doms, rcpt_domain)) {
+	    if (var_helpful_warnings) {
+		if (relay_domains
+		    && domain_list_match(relay_domains, rcpt_domain))
+		    msg_warn("do not list domain %s in BOTH %s and %s",
+			     rcpt_domain, VAR_VIRT_MAILBOX_DOMS,
+			     VAR_RELAY_DOMAINS);
+	    }
 	    vstring_strcpy(channel, var_virt_transport);
 	    vstring_strcpy(nexthop, rcpt_domain);
 	    blame = VAR_VIRT_TRANSPORT;