[Postfix espanol] Postfix snapshot 1.1.11-20020527 with MIME support

[Wietse Venema]

Postfix snaphot 1.1.11-20020527 introduces the following features:

- Real MIME support. This improves built-in content filtering
  efficiency and accuracy, and improves inter-operability with mail
  systems that cannot receive 8-bit mail. More details below in
  the RELEASE_NOTES and HISTORY file summaries.

- Selective content filtering. In header/body_check patterns,
  specify "FILTER transport:nexthop" for mail that needs filtering.
  This requires different cleanup servers before and after the
  filter, with header/body checks turned off in the second cleanup
  server.  Examples for this new feature still need to be developed.
  This feature overrides the main.cf content_filter setting.

The difference between a snapshot and an official release is as
follows: the official release does not change except for bugfixes
and portability patches. New features are tried out in snapshot
releases.  Code that works and that stops changing becomes part of
Postfix official version 1.2.

Available from ftp://ftp.porcupine.org/mirrors/postfix-release/experimental:

      227039 May 27 14:36 postfix-1.1.11-20020527.HISTORY
       63278 May 27 14:52 postfix-1.1.11-20020527.RELEASE_NOTES
     1235684 May 27 14:52 postfix-1.1.11-20020527.tar.gz
	 152 May 27 14:52 postfix-1.1.11-20020527.tar.gz.sig

Soon to appear on the mirror sites listed on www.postfix.org.

	Wietse

Extract from RELEASE_NOTES file:

	Incompatible changes
	====================

	Message headers in MIME attachments etc. are no longer matched by
	body_checks, one input line at a time. They are now by default
	matched by header_checks, one multi-line header at a time.  To get
	the old behavior, specify "disable_mime_input_processing = yes",
	or specify separate patterns for header_checks, mime_header_checks
	and nested_header_checks. See conf/sample-mime.cf for details.

	Postfix now rejects mail if the MIME multipart structure is nested
	more than mime_nesting_limit levels (default: 20) when MIME input
	processing is enabled while receiving mail, or when Postfix is
	performing 8BITMIME to 7BIT conversion while delivering mail.

	Postfix now recognizes "name :" as a valid message header, but
	normalizes it to "name:" for consistency (actually, there is so
	much code in Postfix that would break with "name :" that there is
	little choice, except to not recognize "name :" headers).

	Queue files created with the header/body_checks "FILTER" feature
	are not compatible with "postqueue -r" (move queue files back to
	the maildrop directory) of previous Postfix releases.

	Major changes
	=============

	Postfix now has real MIME support. This improves content filtering
	efficiency and accuracy, and improves inter-operability with mail
	systems that cannot receive 8-bit mail. See conf/sample-mime.cf
	for details.

	Postfix header_checks now properly recognize MIME headers in
	attachments. This is much more efficient than previous versions
	that recognized MIME headers via body_checks.  MIME headers are
	now processed one multi-line header at a time, instead of one body
	line at a time.  

	In fact, Postfix now has three classes of header patterns:
	header_checks (for primary message headers except MIME headers),
	mime_header_checks (for MIME headers), and nested_header_checks
	(for headers of attached email messages except MIME headers).  By
	default, all headers are matched with header_checks.  To get the
	the old behavior, specify "disable_mime_input_processing = yes".
	More details in conf/sample-filter.cf.

	Selective content filtering. In header/body_check patterns, specify
	"FILTER transport:nexthop" for mail that needs filtering. This
	requires different cleanup servers before and after the filter,
	with header/body checks turned off in the second cleanup server.
	More info about content filtering is in the Postfix FILTER_README
	file. Examples for this new feature still need to be developed.
	This feature overrides the main.cf content_filter setting.

	The Postfix SMTP client will now convert 8BITMIME mail to 7BIT when
	delivering to an SMTP server that does not announce 8BITMIME support.
	To disable, specify "disable_mime_output_conversion = yes". However,
	this conversion is required by RFC standards.

	Postfix can enforce some aspects of the MIME standards while
	receiving mail. Specify "strict_8bitmime = yes" to disallow 8-bit
	characters except where allowed by the MIME standard, and specify
	"strict_mime_encoding_domain = yes" to block mail from poorly
	written mail software, including majordomo approval requests that
	contain valid 8BITMIME mail. More details in conf/sample-mime.cf.

Extract from HISTORY file:

20020515

	Workaround: flush the SMTP client output buffer when no
	output has happened for 10+ seconds. This prevents the
	socket from timing out, in case DNS CNAME expansion is
	slow.  Problem experienced by Alex Erdelyi, peregrine.com.
	File:  smtp/smtp_chat.c. We did the same thing for the SMTP
	server years ago, and one wonders why the coin didn't drop
	at the time that the SMTP client could suffer from a similar
	problem.

20020516

	Updated the FILTER_README file to turn off DNS lookups in
	the SMTP client that feeds mail into a content filter.

20020517

	Cleanup: Mailbox-Line: message header labels should be
	X-Mailbox-Line:  labels. Files: smtpd/smtpd.c, qmqpd/qmqpd.c.

20020515-21

	Feature: new MIME parser, written from scratch, that
	recognizes the structure of MIME encapsulated mail. Influenced
	by comments from Victor Duchovny. This code can detect but
	will not decode obscure MIME formats or obscure character
	string encoding that Liviu Daia expresses concern about.

	MIME header scanning now happens in header_checks, and is
	faster than body_checks could ever be. This also eliminates
	the problem with multi-line MIME headers being matched one
	line at a time.  Files:  global/mime_state.[hc],
	cleanup/cleanup_message.c.

20020521-22

	Feature: 8-bit to quoted-printable conversion. First use
	in the Postfix SMTP client. File: smtp/smtp_proto.c.

	Logging: the Postfix SMTP and LMTP clients now report the
	the protocol stage when they report a server reply.  File:
	smtp/smtp_proto.c, lmtp/lmtp_proto.c.

	Bugfix: the SMTP server warned about ignored client attributes
	(these were introduced 20020510) in mail that was submitted
	with "sendmail -bs".  File: smtpd/smtpd.c.

20020525

	Feature: separation of header checks into header_checks
	(all primary headers except MIME related headers),
	mime_header_checks (all MIME headers including MIME headers
	at the start of messages) and nested_header_checks (headers
	of attached messages, except MIME related headers).

	Cleanup: broke out the header value parser from the MIME
	processor so that the code can be reused elsewhere. File:
	global/header_token.c.

	Compatibility: Postfix now recognizes "name :" as a valid
	message header, but normalizes it to "name:" form or else
	lots of things would break all over the place.  Files:
	global/is_header.c, global/mime_state.c.

20020526

	Bugfix: the SMTP server now disallows RCPT TO:<"">, just
	like it disallows RCPT TO:<>.  File: smtpd/smtpd.c.

	Feature: disable_mime_input_processing=yes/no controls
	whether Postfix recognizes (and optionally enforces) MIME
	formats while receiving mail. Default is NO.

	Feature: disable_mime_output_conversion=yes/no controls
	whether Postfix will convert 8BITMIME to 7BIT mail when
	delivering mail to an SMTP server that does not announce
	8BITMIME support.  Default is NO.

	Feature: strict_8bitmime=yes/no controls whether Postfix
	rejects 8-bit characters in headers and 7-bit body parts.
	This blocks mail from poorly written software, including
	majordomo approval requests that contain a valid 8BITMIME
	email message, as well as mail that is piped into ancient
	/bin/mail implementations that do not MIME format 8-bit
	content. Default is NO.

	Feature: strict_mime_encoding_domain=yes/no controls whether
	Postfix rejects illegal content transfer encodings for
	multipart/* and message/*. This blocks mail from poorly
	written software. Default is NO.

20020527

	Feature: "FILTER transport:nexthop" in header/body checks.
	After the message is queued, the message is sent through
	a content filter. This requires different cleanup servers
	before and after the filter, with header/body checks turned
	off in the second cleanup server.
-
Para quitarte de la lista enviar la linea "unsubscribe postfix-espanol" en
el cuerpo de un mensaje a majordomo en WL0.org