--
The mailbox file size limits for the local and virtual delivery
agents can be disabled by setting mailbox_size_limit and/or
virtual_mailbox_limit to zero.
Incompatible changes with snapshot-20010128
===========================================
REJECT in header/body_checks is now flagged as policy violation
rather than bounce, for consistency in postmaster notifications.
The mailbox size limit for local delivery is no longer controlled
by the message_size_limit paramater, but by a separate parameter
called mailbox_size_limit (default: 20MBytes).
The default RBL (real-time blackhole lists) domain examples have
been updated from *.vix.com to *.mail-abuse.org.
Major changes with snapshot-20010128
====================================
Updated nqmgr (experimental queue manager with clever queueing
strategy) by Patrik Rak. This code is still new. Once it stops
changing (for a long time!) it will become part of the non-beta
release.
Virtual mailbox delivery agent by Andrew McNamara. This delivery
agent can deliver mail for any number of domains. See the file
VIRTUAL_README for detailed examples. This code is still new. Once
it stops changing it will become part of the non-beta release.
Many "valid_hostname" warnings were eliminated. The complaints that
were not eliminated were replaced by something more informative.
SASL support (RFC 2554) for the LMTP delivery agent. This is required
by recent Cyrus implementations when delivering mail over TCP
sockets. The LMTP_README file has been updated but still contains
some obsolete information.
Workarounds for non-standard RFC 2554 (AUTH command) implementations.
Specify "broken_sasl_auth_clients = yes" to enable SMTP server
support for old Microsoft client applications. The Postfix SMTP
client supports non-standard RFC 2554 servers by default.
- bump NEED_VERSION
This is a bugfix release:
o Fix big5/gb2312 conversion logic.
o Fix authldap connection failure recovery
o Update INSTALL to reflect new upgrade instructions.
Summary
-------
This patch fixes a problem in the Postfix SMTP client's fallback
relay feature in snapshot releases after 20001005.
By default, Postfix does not use the fallback_relay feature. To
find out if your system uses it, issue the command:
postconf fallback_relay
The result is "fallback_relay =" when the feature is turned off.
Description
-----------
As of 20001005, the Postfix SMTP client will send mail to a fallback
relay host (if one is configured) even when the local machine is
a backup MX host for the final destination.
This causes a loop when the primary MX host is down. Postfix receives
the mail, because it's a backup MX host for the destination. Postfix
then sends the mail to the fallback relay, because the primary MX
host is down. The fallback sends the mail back to Postfix, because
it's a backup MX host. Mail then bounces after 25 or so iterations.
Laurent Wacrenier had the, um, pleasure, of finding this one.
Solution
--------
If the local machine is listed as MX host for the final destination,
do not send undeliverable mail to the fallback relay. That is how
releases prior to 20001005 work, including 19991231.
This patch should apply to all snapshots since 20001005, but I have
tested this only with 20001217.
To apply, step into the src/smtp source directory, feed this text
into the patch command, and rebuild. The "make install" command
replaces only the smtp client program.
--
This module allows direct manipulation of various types of e-mail
alias files.
The primary use of Mail::Alias is for manipulating alias files in
the SENDMAIL alias file format. Additionally it is possible to read
some other formats and to convert between various alias file formats.
The following actions are available:
o Set the name of the current aliases file being accessed
o Verify the presence of aliases
o Retrieve an alias line from the file
o Add aliases
o Change the addresses for aliases
o Delete aliases
- add a patch to correct some man page typos (fed back to author)
Note that Mail::Alias is no longer part of this package, and is now a
separate CPAN module.
by the -p option if it fails to bind to the port, otherwise it will always
print port 110 instead of the real port number.
Based on a patch from: Ian Darwin <ian@darwinsys.com>
- regenerate patches and name them consistently. Note that the
configuration file format and names have changed with this release
- add an INSTALL shell fragment to detect old versions of the config
files and warn the user to regenerate them
- config files now live in /etc/courier-imap, as they are very
generic names, and this avoid conflict with other imap daemons
Summary of changes:
This release fixes some bugs in the POP3 server, adds optional
support for gb2312 and big5 text search, and introduces a new
configuration file format.
The new configuration file format will allow future upgrades
to automatically preserve the existing system configuration data,
instead of installing a default set of configuration files
Extract from RELEASE_NOTES:
===========================
Major changes with snapshot-20001217
====================================
This release involves little change in functionality and a lot of
small changes to lots of files. The code is put out as a separate
snapshot release so that I have a tested baseline for further work.
All time-related configuration parameters now accept a one-letter
suffix to indicate the time unit (s: second, m: minute, h: hour,
d: day, w: week). The exceptions are the LDAP and MYSQL modules
which are maintained separately.
The mysql client was partially rewritten in order to elimimate some
memory allocation/deallocation problems. The code needs more work,
and needs to be tested in a real production environment.
The local_transport and default_transport configuration parameters
can now be specified in transport:destination notation, just like
the mailbox_transport and fallback_transport parameters. The
:destination part is optional. However, these parameters take only
one destination, unlike relayhost and fallback-relay which take
any number of destinations.
--
VMailMgr (short for Virtual MAIL ManaGeR) is a package of programs
designed to manage multiple domains of mail addresses and mailboxes
on a single host. It co-operates with qmail for mail delivery
and program control. It features:
* A password checking interface between qmail-popup and qmail-pop3d
which replaces the usual checkpassword, as well as an authentication
module for [15]Courier IMAP, that provide access to the virtual
mailboxes by one of three methods:
+ IP-based virtual server access (invisible to the POP3 user)
+ username-based access (username-virtualuser)
+ hostname-based access (virtualuser@virtual.host or
virtualuser:virtual.host)
* CDB-based password tables to speed up access for domains of any
size.
* Tools to setup a virtual domain, add and delete individual virtual
users and aliases, and to change passwords.
* CGI programs to accomplish the above tasks from a set of web
pages.
* A native PHP library to compliment or replace the CGIs.
* A daemon process that securely directs the operation of the CGIs
and PHP code.
* A separate delivery agent that automatically deals with any address
inside a virtual domain from a single .qmail-default file.
Extract from the RELEASE_NOTES file:
Incompatible changes with snapshot-20001210
===========================================
If this release does not work for you, you can go back to a previous
Postfix version without losing your mail, subject to the "incompatible
changes" listed for previous Postfix releases below.
When delivering to /file/name (as directed in an alias or .forward
file), the local delivery agent now logs a warning when it is unable
to create a /file/name.lock file. Mail is still delivered as before.
The "sun_mailtool_compatibility" feature is going away (a compatibility
mode that turns off kernel locks on mailbox files). It still works,
but a warning is logged. Instead of using "sun_mailtool_compatibility",
specify the mailbox locking strategy as "mailbox_delivery_lock =
dotlock".
The Postfix SMTP client now skips SMTP server replies that do not
start with "CODE SPACE" or with "CODE HYPHEN" and flags them as
protocol errors. Older Postfix SMTP clients silently treated "CODE
TEXT" as "CODE SPACE TEXT", i.e. as a valid SMTP reply.
This snapshot does not yet change default relay settings. That
change alone affects a dozen files, most of which documentation.
This may be an incompatibility with some people's expectations,
but such are my rules - between code freeze and release no major
functionality changes are allowed.
Several interfaces of libutil and libglobal routines have changed.
This may break third-party code written for Postfix. In particular,
the safe_open() routine has changed, the way the preferred locking
method is specified in the sys_defs.h file, as well as all routines
that perform file locking. When compiling third-party code written
for Postfix, the incompatibilities will be detected by the compiler
provided that #include file dependencies are properly maintained.
Major changes with snapshot-20001210
====================================
This snapshot includes bugfixes that were already released as
patches 12 and 13 for the 19991231 "stable" release:
- The queue manager could deadlock for 10 seconds when bouncing
mail under extreme load from one-to-one mass mailings.
- Local delivery performance was substandard, because the per-user
concurrency limit accidentally applied to the entire local
domain.
The mailbox locking style is now fully configurable at runtime.
The new configuration parameter is called "mailbox_delivery_lock".
Depending on the operating system type, mailboxes can be locked
with one or more of "flock", "fcntl" or "dotlock". The command
"postconf -l" shows the available locking styles. The default
mailbox locking style is system dependent. This change affects
all mailbox and all "/file/name" deliveries by the Postfix local
delivery agent.
The new "import_environment" and "export_environment" configuration
parameters now provide explicit control over what environment
variables Postfix will import, and what environment variables
Postfix will pass on to a non-Postfix process. This is better than
hard-coding my debugging environment into public releases.
The "mailbox_transport" and "fallback_transport" parameters now
understand the form "transport:nexthop", with suitable defaults
when either transport or nexthop are omitted, just like in the
Postfix transport map. This allows you to specify for example,
"mailbox_transport = lmtp:unix:/file/name".
The MYSQL client now supports server connections over UNIX-domain
sockets. Code provided by Piotr Klaban. See the file MYSQL_README
for examples of "host" syntax.
