Hello i understod in the last discussion thread <Forcing imap authentication failure for certain IP addresses> that also IP can be filter, ok the ip are available in deny.ip. Please why this are not blocked?
# dovecot version 2.3.4.1 (f79e8e7e4)
passdb { args = /etc/dovecot/deny.ip args = /etc/dovecot/dovecot-sql.conf.ext driver = sql }
cat mail.log | grep 'sql(name,' Aug 06 01:29:11 Dovecot/auth-worker(7927): Info: sql(Name,A.B.232.146): unknown user
# cat deny.ip | grep A.B.232.146 A.B.232.146
meny thanks
A) Do you mean that client had a successful login although it's logged as "unknown user"?
B) Do you mean "unknown user" rejection message is not effective as a block?
El 6/8/23 a les 2:01, mauric@gmx.ch ha escrit:
Hello i understod in the last discussion thread «Forcing imap authentication failure for certain IP addresses» that also IP can be filter, ok the ip are available in deny.ip. Please why this are not blocked?
# dovecot version 2.3.4.1 (f79e8e7e4)
passdb { args = /etc/dovecot/deny.ip args = /etc/dovecot/dovecot-sql.conf.ext driver = sql }
cat mail.log | grep 'sql(name,' Aug 06 01:29:11 Dovecot/auth-worker(7927): Info: sql(Name,A.B.232.146): unknown user
# cat deny.ip | grep A.B.232.146 A.B.232.146
meny thanks
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
--
Narcis Garcia
I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors.
I don't follow you here, because both are not the goals I am really pursuing.
I was only trying to suppress a possible knock-on lock. And of course Dovecot is not made for such requirements, there are certainly other tools that can help better.
thanks
-----Ursprüngliche Nachricht----- Von: Narcis Garcia debianlists@actiu.net Gesendet: Sonntag, 6. August 2023 07:11 An: dovecot@dovecot.org Betreff: Re: passwdb deny.ip
A) Do you mean that client had a successful login although it's logged as "unknown user"?
B) Do you mean "unknown user" rejection message is not effective as a block?
El 6/8/23 a les 2:01, mauric@gmx.ch ha escrit:
Hello i understod in the last discussion thread «Forcing imap authentication failure for certain IP addresses» that also IP can be filter, ok the ip are available in deny.ip. Please why this are not blocked?
# dovecot version 2.3.4.1 (f79e8e7e4)
passdb { args = /etc/dovecot/deny.ip args = /etc/dovecot/dovecot-sql.conf.ext driver = sql }
cat mail.log | grep 'sql(name,' Aug 06 01:29:11 Dovecot/auth-worker(7927): Info: sql(Name,A.B.232.146): unknown user
# cat deny.ip | grep A.B.232.146 A.B.232.146
meny thanks
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
--
Narcis Garcia
I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors.
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
mauric@gmx.ch skrev den 2023-08-06 10:16:
I don't follow you here, because both are not the goals I am really pursuing.
I was only trying to suppress a possible knock-on lock. And of course Dovecot is not made for such requirements, there are certainly other tools that can help better.
such as weakforced ?
i am thankfully that a gentoo ebuild exists for it
if anyone code a weakforced that support postfix check-policy-service it would be nice
or maybe just a weakforced light, current is imho more or less best to openxchange (dovecot pro) but the api works with dovecot aswell
participants (3)
-
Benny Pedersen
-
mauric＠gmx.ch
-
Narcis Garcia