> I did not have time to fully test this patch, and guess what, some
> untested code does not work. I'll send a revised version Sunday.

An updated patch for Postfix 2.10 and 2.11 can be found on the
source-code mirrors, for example:

ftp://ftp.porcupine.org/mirrors/postfix-release/experimental/feature-patches/20141228-smtp-verify-target-2.10.diff
ftp://ftp.porcupine.org/mirrors/postfix-release/experimental/feature-patches/20141228-smtp-verify-target-2.10.diff.asc
ftp://ftp.porcupine.org/mirrors/postfix-release/experimental/feature-patches/20141228-smtp-verify-target-2.10.diff.sig

ftp://ftp.porcupine.org/mirrors/postfix-release/experimental/feature-patches/20141228-smtp-verify-target-2.11.diff
ftp://ftp.porcupine.org/mirrors/postfix-release/experimental/feature-patches/20141228-smtp-verify-target-2.11.diff.asc
ftp://ftp.porcupine.org/mirrors/postfix-release/experimental/feature-patches/20141228-smtp-verify-target-2.11.diff.sig

This is a minimal patch to support the smtp_address_verify_target feature:

    smtp_address_verify_target (default: rcpt)

        In the context of email address verification, the SMTP
        protocol stage that determines whether an email address is
        deliverable.  Specify one of "rcpt" or "data". The latter
        is needed with remote SMTP servers that reject recipients
        after the DATA command.

This does not include ssupport for smtp_address_verify_target_maps,
as that would complicate patches for older Postfix releases. To use
smtp_address_verify_target selectively, use the transport_maps
feature:

/etc/postfix/main.cf:
    transport_maps = hash:/etc/postfix/transport

/etc/postfix/transport:
    smtp-domain_that_verifies_after_data        smtp-data-target:
    lmtp-domain_that_verifies_after_data        lmtp-data-target:

/etc/postfix/master.cf:
    smtp-data-target unix  -       -       n       -       -       smtp
        -o smtp_address_verify_target=data
    lmtp-data-target unix  -       -       n       -       -       lmtp
        -o lmtp_address_verify_target=data

Unselective use is not harmful, but it will result in unnecessary
"lost connection after DATA" events at remote SMTP/LMTP servers.

        Wietse

Reply via email to