Displaying 4 results from an estimated 4 matches for "password_databases_passdb".
2019 Sep 23
4
Spam Blocking by filtering on username / id
This is probably quite an easy question, but I haven't been able to find the answer. I'm running a server where all the email addresses are in the format "user at domain.com". I've noticed that a large number of fake login attempts use the format "user" eg. reception, service, root, admin.
Is it possible to prevent any such logins to these email users without an
2019 Sep 25
1
Spam Blocking by filtering on username / id
...vourite, CSF, which in my opinion does a better job than fail2ban, but still not exactly what I envisaged.
> you can add username_filter = *@domain.com
> or deny-passdb before actual passdb with username_filter = !*@domain.com
> https://doc.dovecot.org/configuration_manual/authentication/password_databases_passdb/
This is more like what I had in mind. Let me try this out and I'll report back.
P.
2019 Nov 24
2
Proxy GSSAPI + PLAIN authentication
Hi,
I try to configure a proxy accepting GSSAPI and PLAIN authentication.
When authenticating with Kerberos, Dovecot uses master user and password to
authenticate to backends (backends can be Cyrus or Exchange servers too)
When authenticating with PLAIN passwords, Dovecot sends user's login and
password to the backend.
For GSSAPI, I use extrafields :
k5principals=principal at REALM proxy=Y
2019 Nov 24
0
Proxy GSSAPI + PLAIN authentication
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
If your dovecot is recent enough you can use mechanisms setting on passdb block. See https://doc.dovecot.org/configuration_manual/authentication/password_databases_passdb/
<br>
</div>
<blockquote type="cite">
<div>
On 24/11/2019 17:17 Sam via dovecot <dovecot@dovecot.org> wrote:
</div>
<div>
<br>
</div>
<div>
<br>
</div>
<div dir="ltr&quo...