OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Wietse Venema (wietse_at_porcupine.org)
Date: Mon Dec 02 2002 - 10:12:48 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    It is getting time for the Postfix 1.2 release. As usual, this
    release evolves from the series of snapshots that were released
    over the past year. Snapshot 20021202 is the latest.

    Part of the work is polishing. If you found major ommissions or
    inconsistencies in the documentation of recent snapshots, now is
    a good time to let me know.

    The other part of the work is deciding what snapshot features are
    good enough for version 1.2, and what old features need to go away.

    Sofar I am looking at the following:

    change hash_queue_depth default

        The default depth of 2 subdirectory levels makes mailq
        unnecessarily slow for most sites. I am inclined to make the
        default 1, which sucks when your site has lots of mail queued.

    deprecate check_relay_domains

        This restriction should go away. As of version 1.2, any use of
        check_relay_domains should produce a warning and suggest using
        "reject_unauth_destination" instead, and this feature should
        be removed from the documentation.

    change smtpd_recipient_restrictions default

        As of version 1.2, replace the default from "permit_mynetworks,
        check_relay_domains" by "permit_mynetworks, reject_unauth_destination".

    keep HOLD/DISCARD actions

        I'm inclined to include these in the 1.2 release, even though
        their use in smtpd_xxx_restrictions is currently limited to
        access maps.

    keep qmgr_clog_warn_time

        I'm inclined to include this in the 1.2 release. When this
        parameter setting is non-zero, the Postfix queue manager warns
        when mail for some destination is piling up in the active queue,
        and suggests a variety of remedies to speed up delivery (increase
        per-destination concurrency limit, increase active queue size,
        use a separate delivery transport, increase per-transport
        process limit). The heuristics and recommendations are a bit
        questionable, but I haven't heard any complaints, which means
        either people don't read their logs or the suggestions actually
        help.

    snapshot only: sender-based routing

        I'm inclined to not include this in the 1.2 release. With
        sender_based_routing=yes, Postfix will choose the delivery
        transport and "nexthop" host by looking at the sender address
        instead of the recipient.

    If you found other problematic default settings or features in
    recent snapshots, now is a good time to let me know.

    The transition from snapshot to stable release is not the time for
    feature requests. New features must be field tested in snapshots
    before they can become part of the stable release.

    Looking forward for your feedback.

            Wietse