From: (no name) (no email)
Date: Thu Nov 13 2003 - 23:36:42 EST
On Thu, 13 Nov 2003, Jim Seymour wrote:
> > Valid, but not useful when the client did send EHLO.
>
> But useful if they send HELO and then try to pipeline, no? Or is
> the thinking that when they do that, they'll also try to pipeline
> right through DATA, as well, anyway?
The latter.
>
> I get regular rejects with reject_unauth_pipelining in
> smtpd_recipient_restrictions, btw.
>
Some spammers must netcat with HELO, but you will catch them with data
restrictions also.
> > This would catch the unlikely case that the client pipelines the
> > EHLO+sender+recipients, but not the rest of the SMTP dialog.
> >
> > Not useful, in my opinion.
>
> I'm unclear as to which part you're saying is not useful, but I *think*
> you're agreeing with Victor. Victor's telling me it's sufficient to
> put reject_unauth_pipelining in smtpd_data_restrictions. In fact, if I
> understand him correctly: He's saying it's not useful in
> smtpd_recipient_restrictions at all. Do you concur, Wietse?
>
You are asking Wietse, but I sometimes play him on TV :-). It is not
useful to check for pipelining in the recipient restrictions.
-- Viktor.
|
|
|