File: cleanup/cleanup_message.c.
Workaround: OpenSSL 0.9.8[ab] with zlib support interoperability
- problem. Victor Duchovni. Files: tls/tls_client.c, tls/tls_misc.c,
- tls/tls_server.c.
+ problem. Victor Duchovni. Files: tls/tls_client.c,
+ tls/tls_misc.c, tls/tls_server.c.
Wish list:
tables. This requires that you become intimately familiar with the ideas
expressed in regexp_table(5), pcre_table(5) and virtual(5).
-Note: automatic BCC recipients are produced only for new mail. To avoid mailer
-loops, automatic BCC recipients are not generated for mail that is forwarded
-internally, and are not generated for mail that is generated by Postfix itself.
-
Virtual aliasing can be turned off selectively for mail received by smtpd(8),
qmqpd(8), or pickup(8), by overriding main.cf settings in the master.cf file.
This feature is available in Postfix version 2.1 and later.
up.domain.tld" domain. This prevents your mail queue from filling up with
undeliverable MAILER-DAEMON messages. If you can't maintain a list of valid
recipients then you must specify "relay_recipient_maps =" (that is, an
- empty value), or you must specify an "@example.com x" wild-card in the
- relay_recipients table.
+ empty value), or you must specify an "@the.backed-up.domain x" wild-card in
+ the relay_recipients table.
* Line 22: The [] forces Postfix to do no MX lookup.
intimately familiar with the ideas expressed in <a href="regexp_table.5.html">regexp_table(5)</a>,
<a href="pcre_table.5.html">pcre_table(5)</a> and <a href="virtual.5.html">virtual(5)</a>. </p>
-<p> Note: automatic BCC recipients are produced only for new mail.
-To avoid mailer loops, automatic BCC recipients are not generated
-for mail that is forwarded internally, and are not generated for
-mail that is generated by Postfix itself. </p>
-
<p> Virtual aliasing can be turned off selectively for mail received
by <a href="smtpd.8.html">smtpd(8)</a>, <a href="qmqpd.8.html">qmqpd(8)</a>, or <a href="pickup.8.html">pickup(8)</a>, by overriding <a href="postconf.5.html">main.cf</a> settings
in the <a href="master.5.html">master.cf</a> file. This feature is available in Postfix version
from filling up with undeliverable MAILER-DAEMON messages. If you
can't maintain a list of valid recipients then you must specify
"<a href="postconf.5.html#relay_recipient_maps">relay_recipient_maps</a> =" (that is, an empty value), or you must
-specify an "@example.com x" wild-card in the relay_recipients
+specify an "@the.backed-up.domain x" wild-card in the relay_recipients
table. </p>
<li> <p> Line 22: The <tt>[]</tt> forces Postfix to do no MX lookup. </p>
intimately familiar with the ideas expressed in regexp_table(5),
pcre_table(5) and virtual(5). </p>
-<p> Note: automatic BCC recipients are produced only for new mail.
-To avoid mailer loops, automatic BCC recipients are not generated
-for mail that is forwarded internally, and are not generated for
-mail that is generated by Postfix itself. </p>
-
<p> Virtual aliasing can be turned off selectively for mail received
by smtpd(8), qmqpd(8), or pickup(8), by overriding main.cf settings
in the master.cf file. This feature is available in Postfix version
from filling up with undeliverable MAILER-DAEMON messages. If you
can't maintain a list of valid recipients then you must specify
"relay_recipient_maps =" (that is, an empty value), or you must
-specify an "@example.com x" wild-card in the relay_recipients
+specify an "@the.backed-up.domain x" wild-card in the relay_recipients
table. </p>
<li> <p> Line 22: The <tt>[]</tt> forces Postfix to do no MX lookup. </p>
* Patches change both the patchlevel and the release date. Snapshots have no
* patchlevel; they change the release date only.
*/
-#define MAIL_RELEASE_DATE "20060430"
+#define MAIL_RELEASE_DATE "20060518"
#define MAIL_VERSION_NUMBER "2.3"
#ifdef SNAPSHOT