> On Sep 11, 2019, at 6:15 PM, Bill Cole
> wrote:
>
> On 11 Sep 2019, at 17:05, J Doe wrote:
>
>> I glanced briefly to see if there were any other ways to restrict this but
>> none seemed evident to me.
>
>> Is there a way to achieve this ?
>
> As Viktor noted: a pcre check_helo_access
> On Sep 11, 2019, at 5:25 PM, Viktor Dukhovni
> wrote:
>
>> On Sep 11, 2019, at 5:05 PM, J Doe wrote:
>>
>> Is there a way to achieve this ? Alternatively, should I not be attempting
>> to do this because legitimate server’s sometimes EHLO address literals ?
>
> You could try something
On 11 Sep 2019, at 17:05, J Doe wrote:
I glanced briefly to see if there were any other ways to restrict this
but none seemed evident to me.
Is there a way to achieve this ?
As Viktor noted: a pcre check_helo_access map is useful.
I have such a map with a few dozen lines of patterns that
> On Sep 11, 2019, at 5:05 PM, J Doe wrote:
>
> Is there a way to achieve this ? Alternatively, should I not be attempting
> to do this because legitimate server’s sometimes EHLO address literals ?
You could try something like:
...
warn_if_reject check_helo_access
Hi,
I have a question regarding restrictions I can place on EHLO in the
smtpd_helo_restrictions parameter.
I have a Postfix server that is Internet facing. I periodically receive e-mail
where the other MTA sends a EHLO of an address literal. I checked RFC 5321
(SMTP), and confirmed that
