As far as I've understood, this is an anti-illegal-pipelining thing?
If yes, I have two questions.

First, why not to implement

    smtpd_reject_unauth_pipelining = (yes|no)

(with hopefully 'yes' as default :-)) instead of what you have written
about? IMHO this is more clear to understand, but I may be wrong...

Second, one can specify 'reject_unauth_pipelining' in any of
smtpd_*_restrictions - is there any difference in which of them he/she
does it?

On Fri, 6 Sep 2002 13:08:33 -0400 (EDT), wietseporcupine.org (Wietse Venema) wrote:

> In order to detect sites that send mail content before Postfix has
> replied to the SMTP DATA command, I have introduced a somewhat
> bizarre restriction called smtpd_data_restrictions.
>
> smtpd_data_restrictions does NOT look at message content. All it
> does is look at the SMTP DATA command itself.
>
> With this, you can say:
>
> smtpd_data_restrictions = reject_unauth_pipelining
>
> and block sites that don't play by the SMTP rules. This is also
> the only useful smtpd_data_restrictions application that I currently
> am aware of.
>
> These restrictions are done after the recipient restrictions, so
> perhaps someone comes up with a creative use.
>
> Wietse
> -
> To unsubscribe, send mail to majordomopostfix.org with content
> (not subject): unsubscribe postfix-users

-- 
Aleksey Perov
Postmaster
ALP215-RIPE
JSC Svyazinform, Penza, Russia
phone: +7 8412 520215
-
To unsubscribe, send mail to majordomopostfix.org with content
(not subject): unsubscribe postfix-users

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