maildrop (2.0.2-11) unstable; urgency=medium

  * The new maildrop 2.x package uses the PCRE (the Perl 5 Compatible Regular
    Expression Library) for pattern matching, or rather regular expressions.

    This change introduced the following incompatibilities, and possibly
    others:

     * The old pattern->variable syntax is no longer valid.
       That was the syntax where /first!second!third/ would create variables
       $MATCH1=first, $MATCH2=second and $MATCH3=third.

       You have to replace all the "!"s with parenthesis marks in the right
       places, and re-count your matches, since there is no more implicit
       matching of the part up to the first "!". That is, most likely what
       was previously MATCH2 will now become MATCH1.

       This is documented in the maildroprc(5) manual page, section
       "CONVERSION OF MAILDROP 1.X PATTERNS TO 2.0".

     * The checking of character classes became more rigorous, so maildrop
       will display an error when encountering a standalone named class
       [:something:] outside of a character class.

       This is fixed by adding another set of []s around each such instance.

    The above problems will *not* cause a temporary error and they
    themselves will not make the messages remain in MTA queue. Instead,
    maildrop will either fail to match (for the first issue), or it will
    just print a warning message (for the second issue). No mail should
    get lost, but it might not get properly delivered until manual
    intervention in the appropriate configuration files.

  * The new maildrop 2.x package uses the courier-authlib, the Courier
    authorization library, as a plug-in.

    This new functionality also causes the -d option to imply a connection
    to the Courier authentication daemon in order to determine the user data.
    If the daemon is not available, this maildrop will print a warning
    message, and then proceed to the normal getpwnam() mechanism.

    The printing of a message could cause problems for users who run
    maildrop from Exim with the return_output option set in the transport.
    Such a setup for Exim was previously mistakenly recommended by
    README.Debian. The proper option to use is return_fail_output.

    To avoid any interaction with the Courier authentication daemon,
    most users can simply use the MTA's own user/group-setting mechanism
    (both Exim and Postfix support this), and drop the -d call from their
    MTA configuration.

    This maildrop can also treat the lack of authdaemon availability as
    a temporary error if it is also passed the -a option.

    This behaviour is documented in the INSTALL file located in
    /usr/share/doc/maildrop, as well as the manual pages.

 -- Josip Rodin <joy-packages@debian.org>  Mon, 09 Oct 2006 00:01:25 +0200