On 2018-01-11 11:57, Dominic Raferd wrote:
On 11 January 2018 at 10:15, MRob wrote:
I use reject_unknown_helo_hostname even though it rejects legitimate
mail,
it also catches a reasonable amount of bad things.
I want to whitelist some clients of course. I thought it
MRob:
> I use reject_unknown_helo_hostname even though it rejects legitimate
> mail, it also catches a reasonable amount of bad things.
>
> I want to whitelist some clients of course. I thought it should be easy:
>
> /etc/postfix/main.cf
> smtpd_helo_restrictions =
>
On 11.01.18 10:15, MRob wrote:
I use reject_unknown_helo_hostname even though it rejects legitimate
mail, it also catches a reasonable amount of bad things.
I want to whitelist some clients of course. I thought it should be easy:
/etc/postfix/main.cf
smtpd_helo_restrictions =
On 11 January 2018 at 10:15, MRob wrote:
> I use reject_unknown_helo_hostname even though it rejects legitimate mail,
> it also catches a reasonable amount of bad things.
>
> I want to whitelist some clients of course. I thought it should be easy:
>
> /etc/postfix/main.cf
>
Voytek:
> Jan 11 13:04:39 geko postfix/smtpd[5403]: warning: restriction
> `check_sasl_access' ignored: no SASL support
Postfix was compiled without SASL support. There is no code to
implement SASL. This cannot be changed with main.cf settings.
#ifdef USE_SASL_AUTH
} else if
I use reject_unknown_helo_hostname even though it rejects legitimate
mail, it also catches a reasonable amount of bad things.
I want to whitelist some clients of course. I thought it should be easy:
/etc/postfix/main.cf
smtpd_helo_restrictions =
reject_invalid_helo_hostname
On 11 January 2018 at 03:24, li...@lazygranch.com wrote:
> On Wed, 10 Jan 2018 21:59:26 -0500
>> On 1/10/2018 9:53 PM, li...@lazygranch.com wrote:
> I help with a few people I know that set up their own email to pass
> SPF and DKIM, but realistically no major corporation is