Attaching my WIP patch here...
On Sat, Jun 20, 2015 at 04:37:11PM +, Adam Roses Wight wrote:
> Many hosting providers limit the number of outbound SMTP connections over
> time, and exceeding their threshold results in harsh consequences like
> dropped connections and unpredictable delays until
How are others handling dictionary attacks (AUTH) with Postfix. For
example:
Jun 19 21:28:24 mail postfix/smtpd[32583]: connect from
unknown[212.131.132.49]
Jun 19 21:28:24 mail postfix/smtpd[32583]: lost connection after AUTH
from unknown[212.131.132.49]
Jun 19 21:28:24 mail postfix/smtpd[32
Am 20.06.2015 um 20:23 schrieb Forrest:
How are others handling dictionary attacks (AUTH) with Postfix. For
example:
Jun 19 21:28:24 mail postfix/smtpd[32583]: connect from
unknown[212.131.132.49]
Jun 19 21:28:24 mail postfix/smtpd[32583]: lost connection after AUTH
from unknown[212.131.132.
On Sat, Jun 20, 2015 at 02:23:59PM -0400, Forrest wrote:
> How are others handling dictionary attacks (AUTH) with Postfix. For
> example:
Disable SASL auth on port 25. On port 587 require TLS before AUTH.
> I've limited the number of connections, and I suppose I could just ignore
> these as th
On Sat, Jun 20, 2015 at 04:48:24PM +, Adam Roses Wight wrote:
> Attaching my WIP patch here...
>
> On Sat, Jun 20, 2015 at 04:37:11PM +, Adam Roses Wight wrote:
> > Many hosting providers limit the number of outbound SMTP connections over
> > time, and exceeding their threshold results in
Adam Roses Wight:
> Attaching my WIP patch here...
>
> On Sat, Jun 20, 2015 at 04:37:11PM +, Adam Roses Wight wrote:
> > Many hosting providers limit the number of outbound SMTP connections over
> > time, and exceeding their threshold results in harsh consequences like
> > dropped connections
On 6/19/2015 11:05 PM, PGNd wrote:
>
>
> On Fri, Jun 19, 2015, at 06:44 PM, Noel Jones wrote:
>> You can control it with a check_recipient_access map in place of
>> your blanket reject_unverified_recipient.
>
> Ah.
>
> My goal is:
>
> -- for {spam,ham}.1...@mail..com accept & pipe to
On 6/20/2015 1:23 PM, Forrest wrote:
> How are others handling dictionary attacks (AUTH) with Postfix. For
> example:
>
disable AUTH on port 25, or at least require encryption with
smtpd_tls_auth_only = yes". Better to just disable it.
require encryption on submission service port 587 with
-
What is the order in which the mail is processed through postfix? Will
the smtpd_milters apply before the smtpd_client_restrictions?
I went through the documentation on MILTER_README and
SMTPD_ACCESS_README but the ordering isn't clear to me.
Thanks.
--
Atnakus Arzah
When in doubt, have a c
