Cormack, Ken wrote:
>> Does this mean that for those of us who reject on invalid EHLO/HELO
>> this rejection will now have to take place after the DATA phase,
> Michael, about your helo check...
>
> Where I had the following in filter_relay():
>
> #sub filter_relay {
> #
> # my ($hostip, $host
> Does this mean that for those of us who reject on invalid EHLO/HELO this
rejection
> will now have to take place after the DATA phase, instead of after MAIL?
In the
> past four days, my relay has rejected 17,463 delivery attempts due to
EHLO/HELO
> parameters that contain my domain, or are bare I
On Fri, 7 May 2004, Michael Sims wrote:
> David F. Skoll wrote:
> > The next release will call filter_relay immediately after the remote
> > machine connects.
> Does this mean that for those of us who reject on invalid EHLO/HELO
> this rejection will now have to take place after the DATA phase,
David F. Skoll wrote:
> Currently, filter_relay is not called until after the MAIL command.
> The next release will call filter_relay immediately after the remote
> machine connects.
[...]
> I don't think this will have a huge impact on people; just move any
> tests that require $helo and/or a Send
4 matches
Mail list logo
