Hello list!
Is there a way to prevent postfix from offering SASL auth (and that
includes
denying open relaying) to clients based on DNS RBL lookups? I've discovered
the option smtpd_sasl_exceptions_networks which allows to do that by adding
static subnet entries or adding a hash map.
The idea
Kai Krakow:
> Hello list!
>
> Is there a way to prevent postfix from offering SASL auth (and
> that includes denying open relaying) to clients based on DNS RBL
> lookups? I've discovered the option smtpd_sasl_exceptions_networks
> which allows to do that by adding static subnet entries or adding
>
Wietse Venema schrieb:
> Kai Krakow:
>> Hello list!
>>
>> Is there a way to prevent postfix from offering SASL auth (and
>> that includes denying open relaying) to clients based on DNS RBL
>> lookups? I've discovered the option smtpd_sasl_exceptions_networks
>> which allows to do that by adding
Kai Krakow:
> How is one supposed to automatically block such hijacked accounts within
> postfix? A simple heuristic could be detecting unusual high mail volume for
> that account, probably by detecting the always repeating or similar
> subjects.
Typically, this is done with postfwd (a third-pa
On 6/7/2014 8:33 AM, Kai Krakow wrote:
> Wietse Venema schrieb:
>
>> Kai Krakow:
>>> Hello list!
>>>
>>> Is there a way to prevent postfix from offering SASL auth (and
>>> that includes denying open relaying) to clients based on DNS RBL
>>> lookups? I've discovered the option smtpd_sasl_exception
Am 07.06.2014 17:25, schrieb Noel Jones:
> I wonder why you're just trying to stop SASL from those client...
> Why not just use reject_rbl_client (and maybe other restrictions)
> before permit_sasl_authenticated to reject all mail from them? If
> you're unwilling to accept SASL credentials, why
On 07 Jun 2014, at 09:53 , li...@rhsoft.net wrote:
> i condsidered that but it would take weeks and months to
> explain all customers that they have to fix their client configs
> and i see even new configured clients using 25 because the idiotic
> MUA's still default to 25 and burrie the port set
Am 07.06.2014 18:29, schrieb LuKreme:
>
> On 07 Jun 2014, at 09:53 , li...@rhsoft.net wrote:
>
>> i condsidered that but it would take weeks and months to
>> explain all customers that they have to fix their client configs
>> and i see even new configured clients using 25 because the idiotic
>>
Am 07.06.2014 09:59, schrieb Kai Krakow:
> Hello list!
>
> Is there a way to prevent postfix from offering SASL auth (and that
> includes
> denying open relaying) to clients based on DNS RBL lookups? I've discovered
> the option smtpd_sasl_exceptions_networks which allows to do that by adding
On 6/7/2014 10:53 AM, li...@rhsoft.net wrote:
>
>
> Am 07.06.2014 17:25, schrieb Noel Jones:
>> I wonder why you're just trying to stop SASL from those client...
>> Why not just use reject_rbl_client (and maybe other restrictions)
>> before permit_sasl_authenticated to reject all mail from them?
> On 07 Jun 2014, at 10:39 , li...@rhsoft.net wrote:
>
>
>
> Am 07.06.2014 18:29, schrieb LuKreme:
>>
>> On 07 Jun 2014, at 09:53 , li...@rhsoft.net wrote:
>>
>>> i condsidered that but it would take weeks and months to
>>> explain all customers that they have to fix their client configs
>>>
Am 07.06.2014 22:53, schrieb LuKreme:
>> On 07 Jun 2014, at 10:39 , li...@rhsoft.net wrote:
>>
>> Am 07.06.2014 18:29, schrieb LuKreme:
>>>
>>> On 07 Jun 2014, at 09:53 , li...@rhsoft.net wrote:
>>>
i condsidered that but it would take weeks and months to
explain all customers that they
12 matches
Mail list logo
